Bug 3007
Summary: | USB 2.0 IDE harddisk (scsi emulation), system hangs on shutdown | ||
---|---|---|---|
Product: | Drivers | Reporter: | Robert Klotzner (jfanatiker) |
Component: | USB | Assignee: | Greg Kroah-Hartman (greg) |
Status: | RESOLVED CODE_FIX | ||
Severity: | high | CC: | bunk, dbrownell, dieterd2005 |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.6 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 5089 |
Description
Robert Klotzner
2004-07-03 09:40:51 UTC
It'd be worth trying this on a 2.6.13 kernel ... Sice there wasno answer to the question whether it's still present in a recent kernel I'm assuming it's already fixed. Please reopen this bug if it's still present in a recent kernel. I haven't got any system hangs or data loss since kernel version 2.6.12, but I've still got strange log messages: ---------------------------------------------------------------------------------------------------------------- [4295145.053000] usb 4-1: new high speed USB device using ehci_hcd and address 3 [4295146.564000] SCSI subsystem initialized [4295146.575000] Initializing USB Mass Storage driver... [4295146.605000] scsi0 : SCSI emulation for USB Mass Storage devices [4295146.606000] usb-storage: device found at 3 [4295146.606000] usb-storage: waiting for device to settle before scanning [4295146.606000] usbcore: registered new driver usb-storage [4295146.606000] USB Mass Storage support registered. [4295151.606000] Vendor: WDC WD20 Model: 00BB-00FTA0 Rev: 15.0 [4295151.606000] Type: Direct-Access ANSI SCSI revision : 00 [4295151.614000] usb-storage: device scan complete [4295151.947000] SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB) [4295151.947000] sda: assuming drive cache: write through [4295151.972000] SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB) [4295151.972000] sda: assuming drive cache: write through [4295151.972000] sda: sda1 [4295151.989000] Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 [4295324.634000] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. [4295324.634000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode [4295324.634000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode [4295324.634000] [drm] Loading R200 Microcode [4295331.506000] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. [4295331.506000] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode [4295331.506000] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode [4295331.506000] [drm] Loading R200 Microcode [4295380.228000] cdrom: open failed. [4295380.749000] device-mapper: dm-linear: Device lookup failed [4295380.749000] device-mapper: error adding target to table [4295380.758000] device-mapper: dm-linear: Device lookup failed [4295380.758000] device-mapper: error adding target to table [4295380.860000] device-mapper: dm-linear: Device lookup failed [4295380.860000] device-mapper: error adding target to table [4295380.869000] device-mapper: dm-linear: Device lookup failed [4295380.869000] device-mapper: error adding target to table [4295380.871000] device-mapper: dm-linear: Device lookup failed [4295380.871000] device-mapper: error adding target to table [4295380.885000] device-mapper: dm-linear: Device lookup failed [4295380.886000] device-mapper: error adding target to table [4295380.888000] device-mapper: dm-linear: Device lookup failed [4295380.888000] device-mapper: error adding target to table [4295380.891000] device-mapper: dm-linear: Device lookup failed [4295380.891000] device-mapper: error adding target to table [4295380.893000] device-mapper: dm-linear: Device lookup failed [4295380.893000] device-mapper: error adding target to table [4295380.896000] device-mapper: dm-linear: Device lookup failed [4295380.896000] device-mapper: error adding target to table [4295380.898000] device-mapper: dm-linear: Device lookup failed [4295380.899000] device-mapper: error adding target to table [4295380.901000] device-mapper: dm-linear: Device lookup failed [4295380.901000] device-mapper: error adding target to table [4295380.903000] device-mapper: dm-linear: Device lookup failed [4295380.904000] device-mapper: error adding target to table [4295380.963000] device-mapper: dm-linear: Device lookup failed [4295380.964000] device-mapper: error adding target to table [4295380.966000] device-mapper: dm-linear: Device lookup failed [4295380.966000] device-mapper: error adding target to table [4295380.969000] device-mapper: dm-linear: Device lookup failed [4295380.969000] device-mapper: error adding target to table [4295380.971000] device-mapper: dm-linear: Device lookup failed [4295380.971000] device-mapper: error adding target to table [4295380.974000] device-mapper: dm-linear: Device lookup failed [4295380.974000] device-mapper: error adding target to table [4295380.976000] device-mapper: dm-linear: Device lookup failed [4295380.977000] device-mapper: error adding target to table [4295380.979000] device-mapper: dm-linear: Device lookup failed [4295380.979000] device-mapper: error adding target to table ---------------------------------------------------------------------------------------- I'm using evms on this harddisk. Knoppix 4.02: If I put it with the knoppix installer (not tohd=...) on an external HD then booting hangs up. That is related on my ASUS Z9213 hardware a little. Kernel gots irritated by sda (USB as SCSI bounded by driver) and one multichip which is used for IDE and SCSI. So it start direct SCSI access, which of course is nonsense there and systems hangs after twenty messages of block failures access of blocks with 1xxxxxx number. What is the status of this issue in kernel 2.6.16.1? I don't know what's about the issue in 2.6.16.1- the kernel currently refuses to compile for me- I'll solve that problem, but for me no system crashes or data loss occured for a rather long time. The only "problem" remaining in 2.6.12 is the error messages: 4295380.749000] device-mapper: dm-linear: Device lookup failed [4295380.749000] device-mapper: error adding target to table I'm not sure if these messages occured at all with kernel 2.6.16, I just tested it- no error messages- it just worked :) No system crashes or data loss since at least 2.6.12- error messages seem to be gone since at least 2.6.16 - (I haven't tested any kernels in between) Really good work!- I love Linux more and more from day to day ;-) For me the problem is solved- I don't know what's about Dieters problem. Best regards, Robert Great, thanks for letting us know. Am closing. As a side note, please let the kernel developers know why you can't build 2.6.16.1, otherwise it might never get fixed... I think it is because I'm using gcc 4.03 now- I built the last kernel with 3.4.x- It complains about a symbol that isn't valid. Maybe the maping of C code to machine code has changed somehow between the releases so that some peace of assembler code has become invalid. ok- I would have played a little more with it, but if you think I should report it, I will, although I can't really tell them more about it than I just told you. Best regards and thanks for every thing! robert P.S.: That's all the output I get: Using gcc version: 4.0.3 Installing in dir: /usr/src/linux-2.6.16 linux 2.6.16 This is the version: 2.6.16 making for a 2.6 kernel CHK include/linux/version.h SPLIT include/linux/autoconf.h -> include/config/* CHK include/linux/compile.h CHK usr/initramfs_list KSYM .tmp_kallsyms1.S No valid symbol. make: *** [.tmp_kallsyms1.S] Error 1 Ok- I'll report it any way, I just wasn't able to resist telling you. Am Thursday, 6. April 2006 19:06 schrieben Sie: > http://bugzilla.kernel.org/show_bug.cgi?id=3007 > > greg@kroah.com changed: > > What |Removed |Added > --------------------------------------------------------------------------- >- Status|NEEDINFO |RESOLVED > Resolution| |CODE_FIX > > > > ------- Additional Comments From greg@kroah.com 2006-04-06 10:06 ------- > Great, thanks for letting us know. Am closing. > > As a side note, please let the kernel developers know why you can't build > 2.6.16.1, otherwise it might never get fixed... > > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de |