Bug 11302
| Summary: | I get a kernel OOPS! If I try to attach an usb card reader, SD, MMC, ecc.. to my Slamd64 | ||
|---|---|---|---|
| Product: | IO/Storage | Reporter: | Paolo (pinc_o) |
| Component: | SCSI | Assignee: | linux-scsi (linux-scsi) |
| Status: | CLOSED OBSOLETE | ||
| Severity: | blocking | CC: | alan, pinc_o, stern |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.26.2 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
|
Description
Paolo
2008-08-10 13:45:47 UTC
Reply-To: akpm@linux-foundation.org (switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Sun, 10 Aug 2008 13:45:49 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=11302 > > Summary: I get a kernel OOPS! If I try to attach an usb card > reader, SD, MMC, ecc.. to my Slamd64 > Product: IO/Storage > Version: 2.5 > KernelVersion: 2.6.26.2 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: blocking > Priority: P1 > Component: SCSI > AssignedTo: linux-scsi@vger.kernel.org > ReportedBy: pinc_o@yahoo.it Is this a scsi regresion, or an mmc regression? > > Latest working kernel version: 2.6.25.x > Earliest failing kernel version: > Distribution: SLAMD64 12.1 > Hardware Environment: Asus A7 deluxe > Software Environment: KDE/command line > Problem Description: > > If attach my usb card reader, without load mmc_block an mmc_core modules, > then > the follow OOPS appear(If first load them, simply doesn't mount the SD. > Please > note: I always use "automatic loading kernel modules" compiled in "my" > kernelS. > But from many time, the recent kernelS not load the mmc_block module): > > ========================================================================== > usb 1-6: new high speed USB device using ehci_hcd and address 6 > usb 1-6: configuration #1 chosen from 1 choice > scsi5 : SCSI emulation for USB Mass Storage devices > usb-storage: device found at 6 > usb-storage: waiting for device to settle before scanning > scsi 5:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0 > usb 1-6: reset high speed USB device using ehci_hcd and address 6 > usb 1-6: reset high speed USB device using ehci_hcd and address 6 > usb 1-6: reset high speed USB device using ehci_hcd and address 6 > usb 1-6: can't restore configuration #1 (error=-71) > sd 5:0:0:0: Device offlined - not ready after error recovery > sd 5:0:0:0: rejecting I/O to offline device > sd 5:0:0:0: rejecting I/O to offline device > sd 5:0:0:0: rejecting I/O to offline device > sd 5:0:0:0: [sdd] READ CAPACITY failed > sd 5:0:0:0: [sdd] Result: hostbyte=0x01 driverbyte=0x00 > sd 5:0:0:0: [sdd] Sense not available. > sd 5:0:0:0: rejecting I/O to offline device > sd 5:0:0:0: [sdd] Write Protect is off > sd 5:0:0:0: [sdd] Mode Sense: 00 00 00 00 > sd 5:0:0:0: [sdd] Assuming drive cache: write through > sd 5:0:0:0: [sdd] Attached SCSI removable disk > sd 5:0:0:0: Attached scsi generic sg3 type 0 > usb 1-6: USB disconnect, address 6 > BUG: unable to handle kernel NULL pointer dereference at 0000000000000004 > IP: [<ffffffff8039bea1>] slave_alloc+0x33/0x5b > PGD be142067 PUD aab0e067 PMD 0 > Oops: 0000 [1] PREEMPT SMP > CPU 1 > Modules linked in: nvidia(P) [last unloaded: nvidia] > Pid: 6201, comm: usb-stor-scan Tainted: P 2.6.26.2 #2 > RIP: 0010:[<ffffffff8039bea1>] [<ffffffff8039bea1>] slave_alloc+0x33/0x5b > RSP: 0018:ffff8100aa969c20 EFLAGS: 00010202 > RAX: 0000000000000000 RBX: ffff8100a29745c8 RCX: 0000000000000000 > RDX: ffff810026abd000 RSI: 0000000000000202 RDI: ffff8100bed14100 > RBP: ffff8100a2977800 R08: 00000000ffffffff R09: ffff8100a2977c30 > R10: 0000000000000000 R11: 0000000000000000 R12: ffff810099d46428 > R13: ffff8100a2974000 R14: 0000000000000000 R15: ffff810099d46400 > FS: 00007f5f94bd26f0(0000) GS:ffff8100bf806480(0000) knlGS:00000000f714e6c0 > CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b > CR2: 0000000000000004 CR3: 00000000aa9ec000 CR4: 00000000000006e0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 > Process usb-stor-scan (pid: 6201, threadinfo ffff8100aa968000, task > ffff8100864e85c0) > Stack: ffff810099d46428 ffff8100a2977800 ffff810099d46400 ffffffff80366082 > ffff8100a2974000 0000000000000000 0000000000000000 0000000000000000 > 0000000000000000 ffffffff80366348 ffff81000000157c ffff810000000003 > Call Trace: > [<ffffffff80366082>] ? scsi_alloc_sdev+0x1b6/0x1fd > [<ffffffff80366348>] ? scsi_probe_and_add_lun+0xef/0x926 > [<ffffffff80343032>] ? attribute_container_add_device+0x27/0x124 > [<ffffffff802ed533>] ? kobject_get+0x12/0x17 > [<ffffffff8033ea29>] ? get_device+0x17/0x20 > [<ffffffff80365e66>] ? scsi_alloc_target+0x225/0x28b > [<ffffffff80366e1c>] ? __scsi_scan_target+0xb1/0x4f6 > [<ffffffff80234b1b>] ? process_timeout+0x0/0x5 > [<ffffffff8039d3e9>] ? usb_stor_scan_thread+0x0/0x12e > [<ffffffff8046bc98>] ? wait_for_common+0x126/0x138 > [<ffffffff80224fbb>] ? default_wake_function+0x0/0xe > [<ffffffff803672af>] ? scsi_scan_channel+0x4e/0x81 > [<ffffffff80367373>] ? scsi_scan_host_selected+0x91/0xd3 > [<ffffffff8039d4fb>] ? usb_stor_scan_thread+0x112/0x12e > [<ffffffff8023e3bc>] ? autoremove_wake_function+0x0/0x2e > [<ffffffff8039d3e9>] ? usb_stor_scan_thread+0x0/0x12e > [<ffffffff8023e29f>] ? kthread+0x47/0x74 > [<ffffffff80227e8b>] ? schedule_tail+0x28/0x5d > [<ffffffff8020c008>] ? child_rip+0xa/0x12 > [<ffffffff8023e258>] ? kthread+0x0/0x74 > [<ffffffff8020bffe>] ? child_rip+0x0/0x12 > > > Code: 08 48 8b 1f c6 87 93 00 00 00 24 48 8b 7f 08 48 81 c3 c8 05 00 00 8b 43 > 3c 48 8b 53 18 c1 e8 0f 83 e0 0f 48 8b 84 c2 d0 02 00 00 <0f> b7 70 04 ff ce > e8 > 26 86 f4 ff 80 7b 64 04 75 11 48 8b 85 c0 > RIP [<ffffffff8039bea1>] slave_alloc+0x33/0x5b > RSP <ffff8100aa969c20> > CR2: 0000000000000004 > ---[ end trace d443c8e181da42c1 ]--- > > ======================================================================== > > Dual Core AMD Opteron(tm) Processor 185 > 3GB of memory > SLAMD64 12.1 > > Best Regards > > > Steps to reproduce: > Reply-To: drzeus@drzeus.cx On Sun, 10 Aug 2008 13:53:44 -0700 Andrew Morton <akpm@linux-foundation.org> wrote: > > (switched to email. Please respond via emailed reply-to-all, not via the > bugzilla web interface). > > On Sun, 10 Aug 2008 13:45:49 -0700 (PDT) bugme-daemon@bugzilla.kernel.org > wrote: > > > http://bugzilla.kernel.org/show_bug.cgi?id=11302 > > > > Summary: I get a kernel OOPS! If I try to attach an usb card > > reader, SD, MMC, ecc.. to my Slamd64 > > Product: IO/Storage > > Version: 2.5 > > KernelVersion: 2.6.26.2 > > Platform: All > > OS/Version: Linux > > Tree: Mainline > > Status: NEW > > Severity: blocking > > Priority: P1 > > Component: SCSI > > AssignedTo: linux-scsi@vger.kernel.org > > ReportedBy: pinc_o@yahoo.it > > Is this a scsi regresion, or an mmc regression? > There are no USB based "real" MMC controllers, so I'd say SCSI. > > If attach my usb card reader, without load mmc_block an mmc_core modules, > then > > the follow OOPS appear(If first load them, simply doesn't mount the SD. > Please > > note: I always use "automatic loading kernel modules" compiled in "my" > kernelS. > > But from many time, the recent kernelS not load the mmc_block module): I don't know what kind of weird ass scripts loaded them for USB mass storage to begin with. As for the claimed lack of crashes when loaded; no idea as there is no interaction between the SCSI and MMC layer. > > Modules linked in: nvidia(P) [last unloaded: nvidia] This is always a good start.. Rgds Reply-To: akpm@linux-foundation.org On Mon, 11 Aug 2008 07:45:53 +0200 Pierre Ossman <drzeus@drzeus.cx> wrote: > On Sun, 10 Aug 2008 13:53:44 -0700 > Andrew Morton <akpm@linux-foundation.org> wrote: > > > > > (switched to email. Please respond via emailed reply-to-all, not via the > > bugzilla web interface). > > > > On Sun, 10 Aug 2008 13:45:49 -0700 (PDT) bugme-daemon@bugzilla.kernel.org > wrote: > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=11302 > > > > > > Summary: I get a kernel OOPS! If I try to attach an usb card > > > reader, SD, MMC, ecc.. to my Slamd64 > > > Product: IO/Storage > > > Version: 2.5 > > > KernelVersion: 2.6.26.2 > > > Platform: All > > > OS/Version: Linux > > > Tree: Mainline > > > Status: NEW > > > Severity: blocking > > > Priority: P1 > > > Component: SCSI > > > AssignedTo: linux-scsi@vger.kernel.org > > > ReportedBy: pinc_o@yahoo.it > > > > Is this a scsi regresion, or an mmc regression? > > OK. There have been some regressions in the scsi area but I thought that a) they were fixed and b) none manifested as an oops in slave_alloc(). Perhaps James can take a look please? > There are no USB based "real" MMC controllers, so I'd say SCSI. > > > > If attach my usb card reader, without load mmc_block an mmc_core modules, > then > > > the follow OOPS appear(If first load them, simply doesn't mount the SD. > Please > > > note: I always use "automatic loading kernel modules" compiled in "my" > kernelS. > > > But from many time, the recent kernelS not load the mmc_block module): > > I don't know what kind of weird ass scripts loaded them for USB mass > storage to begin with. As for the claimed lack of crashes when loaded; > no idea as there is no interaction between the SCSI and MMC layer. > > > > Modules linked in: nvidia(P) [last unloaded: nvidia] > > This is always a good start.. I very much doubt it. Paolo, can you please check to see if the crash happens in a kernel into which the nvidia driver has never been loaded? Reply-To: James.Bottomley@HansenPartnership.com On Sun, 2008-08-10 at 23:33 -0700, Andrew Morton wrote: > On Mon, 11 Aug 2008 07:45:53 +0200 Pierre Ossman <drzeus@drzeus.cx> wrote: > > > On Sun, 10 Aug 2008 13:53:44 -0700 > > Andrew Morton <akpm@linux-foundation.org> wrote: > > > > > > > > (switched to email. Please respond via emailed reply-to-all, not via the > > > bugzilla web interface). > > > > > > On Sun, 10 Aug 2008 13:45:49 -0700 (PDT) bugme-daemon@bugzilla.kernel.org > wrote: > > > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=11302 > > > > > > > > Summary: I get a kernel OOPS! If I try to attach an usb card > > > > reader, SD, MMC, ecc.. to my Slamd64 > > > > Product: IO/Storage > > > > Version: 2.5 > > > > KernelVersion: 2.6.26.2 > > > > Platform: All > > > > OS/Version: Linux > > > > Tree: Mainline > > > > Status: NEW > > > > Severity: blocking > > > > Priority: P1 > > > > Component: SCSI > > > > AssignedTo: linux-scsi@vger.kernel.org > > > > ReportedBy: pinc_o@yahoo.it > > > > > > Is this a scsi regresion, or an mmc regression? > > > > > OK. There have been some regressions in the scsi area but I thought > that a) they were fixed and b) none manifested as an oops in > slave_alloc(). > > Perhaps James can take a look please? Well, this does illustrate one of the problems of making everything static: slave_configure isn't a terribly distinguished name. However, I'd bet this is usbstorage/scsiglue.c:slave_configure() the taxonomy looks identical to bugs 11088 and 11072. Which are being fixed (have been fixed) in the USB tree. James Hi Andrew, I have tryed without load the nvidia module. The problem is the same. I have attached to this e-mail dmesg output, after some seconds which I have connected usb card reader, and output of lsmod. I hope you find this useful. Attach my .config too. Probably is not useful, however you are the expert ... I not put everything static, but I put static only things which are always in use and connected to my desktop. Some things which I use only sometime, i.e. card reader, then compile it as module. I never use firewire at alI, then I never compile it. I use this method from ago on the notebook too and always work well. Excuse me for my bad English. Best Regards --- Lun 11/8/08, Andrew Morton <akpm@linux-foundation.org> ha scritto: Da: Andrew Morton <akpm@linux-foundation.org> Oggetto: Re: [Bugme-new] [Bug 11302] New: I get a kernel OOPS! If I try to attach an usb card reader, SD, MMC, ecc.. to my Slamd64 A: "Pierre Ossman" <drzeus@drzeus.cx> Cc: linux-scsi@vger.kernel.org, bugme-daemon@bugzilla.kernel.org, pinc_o@yahoo.it, "James Bottomley" <James.Bottomley@HansenPartnership.com> Data: Lunedì 11 agosto 2008, 08:33 On Mon, 11 Aug 2008 07:45:53 +0200 Pierre Ossman <drzeus@drzeus.cx> wrote: > On Sun, 10 Aug 2008 13:53:44 -0700 > Andrew Morton <akpm@linux-foundation.org> wrote: > > > > > (switched to email. Please respond via emailed reply-to-all, not via the > > bugzilla web interface). > > > > On Sun, 10 Aug 2008 13:45:49 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote: > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=11302 > > > > > > Summary: I get a kernel OOPS! If I try to attach an usb card > > > reader, SD, MMC, ecc.. to my Slamd64 > > > Product: IO/Storage > > > Version: 2.5 > > > KernelVersion: 2.6.26.2 > > > Platform: All > > > OS/Version: Linux > > > Tree: Mainline > > > Status: NEW > > > Severity: blocking > > > Priority: P1 > > > Component: SCSI > > > AssignedTo: linux-scsi@vger.kernel.org > > > ReportedBy: pinc_o@yahoo.it > > > > Is this a scsi regresion, or an mmc regression? > > OK. There have been some regressions in the scsi area but I thought that a) they were fixed and b) none manifested as an oops in slave_alloc(). Perhaps James can take a look please? > There are no USB based "real" MMC controllers, so I'd say SCSI. > > > > If attach my usb card reader, without load mmc_block an mmc_core modules, then > > > the follow OOPS appear(If first load them, simply doesn't mount the SD. Please > > > note: I always use "automatic loading kernel modules" compiled in "my" kernelS. > > > But from many time, the recent kernelS not load the mmc_block module): > > I don't know what kind of weird ass scripts loaded them for USB mass > storage to begin with. As for the claimed lack of crashes when loaded; > no idea as there is no interaction between the SCSI and MMC layer. > > > > Modules linked in: nvidia(P) [last unloaded: nvidia] > > This is always a good start.. I very much doubt it. Paolo, can you please check to see if the crash happens in a kernel into which the nvidia driver has never been loaded? Posta, news, sport, oroscopo: tutto in una sola pagina. Crea l'home page che piace a te! www.yahoo.it/latuapagina<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi Andrew,<br><br>I have tryed without load the nvidia module. The problem is the same.<br><br>I have attached to this e-mail dmesg output, after some seconds which I have connected usb card reader, and output of lsmod. I hope you find this useful. Attach my .config too. Probably is not useful, however you are the expert ...<br>I not put everything static, but I put static only things which are always in use and connected to my desktop. Some things which I use only sometime, i.e. card reader, then compile it as module. I never use firewire at alI, then I never compile it. I use this method from ago on the notebook too and always work well.<br><br>Excuse me for my bad English.<br><br><br>Best Regards<br><br>--- <b>Lun 11/8/08, Andrew Morton <i><akpm@linux-foundation.org></i></b> ha scritto:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">Da: Andrew Morton <akpm@linux-foundation.org><br>Oggetto: Re: [Bugme-new] [Bug 11302] New: I get a kernel OOPS! If I try to attach an usb card reader, SD, MMC, ecc.. to my Slamd64<br>A: "Pierre Ossman" <drzeus@drzeus.cx><br>Cc: linux-scsi@vger.kernel.org, bugme-daemon@bugzilla.kernel.org, pinc_o@yahoo.it, "James Bottomley" <James.Bottomley@HansenPartnership.com><br>Data: Lunedì 11 agosto 2008, 08:33<br><br><pre>On Mon, 11 Aug 2008 07:45:53 +0200 Pierre Ossman <drzeus@drzeus.cx> wrote:<br><br>> On Sun, 10 Aug 2008 13:53:44 -0700<br>> Andrew Morton <akpm@linux-foundation.org> wrote:<br>> <br>> > <br>> > (switched to email. Please respond via emailed reply-to-all, not via<br>the<br>> > bugzilla web interface).<br>> > <br>> > On Sun, 10 Aug 2008 13:45:49 -0700 (PDT)<br>bugme-daemon@bugzilla.kernel.org wrote:<br>> > <br>> > > http://bugzilla.kernel.org/show_bug.cgi?id=11302<br>> > > <br>> > > Summary: I get a kernel OOPS! If I try to attach an<br>usb card<br>> > > reader, SD, MMC, ecc.. to my Slamd64<br>> > > Product: IO/Storage<br>> > > Version: 2.5<br>> > > KernelVersion: 2.6.26.2<br>> > > Platform: All<br>> > > OS/Version: Linux<br>> > > Tree: Mainline<br>> > > Status: NEW<br>> > > Severity: blocking<br>> > > Priority: P1<br>> > > Component: SCSI<br>> > > AssignedTo: linux-scsi@vger.kernel.org<br>> > > ReportedBy: pinc_o@yahoo.it<br>> > <br>> > Is this a scsi regresion, or an mmc regression?<br>> > <br><br>OK. There have been some regressions in the scsi area but I thought<br>that a) they were fixed and b) none manifested as an oops in<br>slave_alloc().<br><br>Perhaps James can take a look please?<br><br>> There are no USB based "real" MMC controllers, so I'd say<br>SCSI.<br>> <br>> > > If attach my usb card reader, without load mmc_block an mmc_core<br>modules, then<br>> > > the follow OOPS appear(If first load them, simply doesn't<br>mount the SD. Please<br>> > > note: I always use "automatic loading kernel modules"<br>compiled in "my" kernelS.<br>> > > But from many time, the recent kernelS not load the mmc_block<br>module):<br>> <br>> I don't know what kind of weird ass scripts loaded them for USB mass<br>> storage to begin with. As for the claimed lack of crashes when loaded;<br>> no idea as there is no interaction between the SCSI and MMC layer.<br>> <br>> > > Modules linked in: nvidia(P) [last unloaded: nvidia]<br>> <br>> This is always a good start..<br><br>I very much doubt it.<br><br>Paolo, can you please check to see if the crash happens in a kernel<br>into which the nvidia driver has never been loaded?<br><br></pre></blockquote></td></tr></table><br> <hr size=1> Posta, news, sport, oroscopo: tutto in una sola pagina<br> <a href="http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http://us.rd.yahoo.com/evt=52437/*http://www.yahoo.it/latuapagina" target=_blank>Crea l'home page che piace a te!</a>. Hi Andrew, with the new kernel 2.6.26.3 the SD are now read and wrote correctly, but SDHC are not read! The kernel repeat the error. Follow the error: Sep 1 22:08:20 athos -- MARK -- Sep 1 22:19:12 athos kernel: usb 1-6: new high speed USB device using ehci_hcd and address 5 Sep 1 22:19:12 athos kernel: usb 1-6: configuration #1 chosen from 1 choice Sep 1 22:19:12 athos kernel: scsi5 : SCSI emulation for USB Mass Storage devices Sep 1 22:19:17 athos kernel: scsi 5:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0 Sep 1 22:19:47 athos kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 5 Sep 1 22:20:14 athos last message repeated 3 times Sep 1 22:20:14 athos kernel: sd 5:0:0:0: Device offlined - not ready after error recovery Sep 1 22:20:14 athos kernel: usb 1-6: USB disconnect, address 5 Sep 1 22:20:14 athos kernel: sd 5:0:0:0: [sdd] READ CAPACITY failed Sep 1 22:20:14 athos kernel: sd 5:0:0:0: [sdd] Result: hostbyte=0x01 driverbyte=0x00 Sep 1 22:20:14 athos kernel: sd 5:0:0:0: [sdd] Sense not available. Sep 1 22:20:14 athos kernel: sd 5:0:0:0: [sdd] Write Protect is off Sep 1 22:20:14 athos kernel: sd 5:0:0:0: [sdd] Attached SCSI removable disk Sep 1 22:20:14 athos kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0 Sep 1 22:20:14 athos kernel: usb 1-6: new high speed USB device using ehci_hcd and address 6 Sep 1 22:20:14 athos kernel: usb 1-6: configuration #1 chosen from 1 choice Sep 1 22:20:14 athos kernel: scsi6 : SCSI emulation for USB Mass Storage devices Sep 1 22:20:19 athos kernel: scsi 6:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0 Sep 1 22:20:49 athos kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 6 Sep 1 22:20:59 athos kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 6 Sep 1 22:21:00 athos kernel: usb 1-6: USB disconnect, address 6 Sep 1 22:21:00 athos kernel: sd 6:0:0:0: Device offlined - not ready after error recovery Sep 1 22:21:00 athos kernel: sd 6:0:0:0: [sdd] READ CAPACITY failed Sep 1 22:21:00 athos kernel: sd 6:0:0:0: [sdd] Result: hostbyte=0x01 driverbyte=0x00 Sep 1 22:21:00 athos kernel: sd 6:0:0:0: [sdd] Sense not available. Sep 1 22:21:00 athos kernel: sd 6:0:0:0: [sdd] Write Protect is off Sep 1 22:21:00 athos kernel: sd 6:0:0:0: [sdd] Attached SCSI removable disk Sep 1 22:21:00 athos kernel: sd 6:0:0:0: Attached scsi generic sg3 type 0 Sep 1 22:21:00 athos kernel: usb 1-6: new high speed USB device using ehci_hcd and address 7 Sep 1 22:21:00 athos kernel: usb 1-6: configuration #1 chosen from 1 choice Sep 1 22:21:00 athos kernel: scsi7 : SCSI emulation for USB Mass Storage devices Sep 1 22:21:05 athos kernel: scsi 7:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0 Sep 1 22:21:35 athos kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 7 Sep 1 22:21:36 athos kernel: usb 1-6: USB disconnect, address 7 Sep 1 22:21:36 athos kernel: sd 7:0:0:0: Device offlined - not ready after error recovery Sep 1 22:21:36 athos kernel: sd 7:0:0:0: [sdd] READ CAPACITY failed Sep 1 22:21:36 athos kernel: sd 7:0:0:0: [sdd] Result: hostbyte=0x01 driverbyte=0x00 Sep 1 22:21:36 athos kernel: sd 7:0:0:0: [sdd] Sense not available. Sep 1 22:21:36 athos kernel: sd 7:0:0:0: [sdd] Write Protect is off Sep 1 22:21:36 athos kernel: sd 7:0:0:0: [sdd] Attached SCSI removable disk Sep 1 22:21:36 athos kernel: sd 7:0:0:0: Attached scsi generic sg3 type 0 Sep 1 22:22:00 athos kernel: usb 1-6: new high speed USB device using ehci_hcd and address 8 Sep 1 22:22:00 athos kernel: usb 1-6: configuration #1 chosen from 1 choice Sep 1 22:22:00 athos kernel: scsi8 : SCSI emulation for USB Mass Storage devices Sep 1 22:22:05 athos kernel: scsi 8:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0 Sep 1 22:22:27 athos kernel: sd 8:0:0:0: [sdd] READ CAPACITY failed Sep 1 22:22:27 athos kernel: sd 8:0:0:0: [sdd] Result: hostbyte=0x07 driverbyte=0x00 Sep 1 22:22:27 athos kernel: sd 8:0:0:0: [sdd] Sense not available. Sep 1 22:22:27 athos kernel: sd 8:0:0:0: [sdd] Write Protect is off Sep 1 22:22:28 athos kernel: sd 8:0:0:0: [sdd] Attached SCSI removable disk Sep 1 22:22:28 athos kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0 Sep 1 22:22:28 athos kernel: usb 1-6: USB disconnect, address 8 ====================================================================== I hope this is useful to you and to us! :) Best Regards Paolo P.S. Please, excuse me for my Bad English! --- Lun 11/8/08, Andrew Morton <akpm@linux-foundation.org> ha scritto: > Da: Andrew Morton <akpm@linux-foundation.org> > Oggetto: Re: [Bugme-new] [Bug 11302] New: I get a kernel OOPS! If I try to > attach an usb card reader, SD, MMC, ecc.. to my Slamd64 > A: "Pierre Ossman" <drzeus@drzeus.cx> > Cc: linux-scsi@vger.kernel.org, bugme-daemon@bugzilla.kernel.org, > pinc_o@yahoo.it, "James Bottomley" <James.Bottomley@HansenPartnership.com> > Data: Luned Reply-To: James.Bottomley@HansenPartnership.com On Mon, 2008-09-01 at 23:30 +0000, pinco pallino wrote: > Hi Andrew, > > with the new kernel 2.6.26.3 the SD are now read and wrote correctly, but > SDHC are not read! The kernel repeat the error. Follow the error: > > Sep 1 22:08:20 athos -- MARK -- > Sep 1 22:19:12 athos kernel: usb 1-6: new high speed USB device using > ehci_hcd and address 5 > Sep 1 22:19:12 athos kernel: usb 1-6: configuration #1 chosen from 1 choice > Sep 1 22:19:12 athos kernel: scsi5 : SCSI emulation for USB Mass Storage > devices > Sep 1 22:19:17 athos kernel: scsi 5:0:0:0: Direct-Access Generic USB SD > Reader 1.00 PQ: 0 ANSI: 0 > Sep 1 22:19:47 athos kernel: usb 1-6: reset high speed USB device using > ehci_hcd and address 5 > Sep 1 22:20:14 athos last message repeated 3 times This is definitely a USB issue (correct cc's added). It looks like some attempted reset finally ... > Sep 1 22:20:14 athos kernel: sd 5:0:0:0: Device offlined - not ready after > error recovery > Sep 1 22:20:14 athos kernel: usb 1-6: USB disconnect, address 5 ... leads to disconnection here. > Sep 1 22:20:14 athos kernel: sd 5:0:0:0: [sdd] READ CAPACITY failed > Sep 1 22:20:14 athos kernel: sd 5:0:0:0: [sdd] Result: hostbyte=0x01 > driverbyte=0x00 > Sep 1 22:20:14 athos kernel: sd 5:0:0:0: [sdd] Sense not available. > Sep 1 22:20:14 athos kernel: sd 5:0:0:0: [sdd] Write Protect is off > Sep 1 22:20:14 athos kernel: sd 5:0:0:0: [sdd] Attached SCSI removable disk > Sep 1 22:20:14 athos kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0 This is all symptomatic of the command SCSI is trying to send never reaching the device. Then USB begins again with the same device: > Sep 1 22:20:14 athos kernel: usb 1-6: new high speed USB device using > ehci_hcd and address 6 > Sep 1 22:20:14 athos kernel: usb 1-6: configuration #1 chosen from 1 choice > Sep 1 22:20:14 athos kernel: scsi6 : SCSI emulation for USB Mass Storage > devices > Sep 1 22:20:19 athos kernel: scsi 6:0:0:0: Direct-Access Generic USB SD > Reader 1.00 PQ: 0 ANSI: 0 And runs into identical problems. Most likely, knowing USB, it's either some interface problem, or the device hung up on a SCSI command it didn't like. What's the last known good kernel? If the usb people don't recognise it, then likely we'll need a bisection search from there. James On Mon, 1 Sep 2008, James Bottomley wrote:
> On Mon, 2008-09-01 at 23:30 +0000, pinco pallino wrote:
> > Hi Andrew,
> >
> > with the new kernel 2.6.26.3 the SD are now read and wrote correctly, but
> SDHC are not read! The kernel repeat the error. Follow the error:
> >
> > Sep 1 22:08:20 athos -- MARK --
> > Sep 1 22:19:12 athos kernel: usb 1-6: new high speed USB device using
> ehci_hcd and address 5
> > Sep 1 22:19:12 athos kernel: usb 1-6: configuration #1 chosen from 1
> choice
> > Sep 1 22:19:12 athos kernel: scsi5 : SCSI emulation for USB Mass Storage
> devices
> > Sep 1 22:19:17 athos kernel: scsi 5:0:0:0: Direct-Access Generic USB
> SD Reader 1.00 PQ: 0 ANSI: 0
> > Sep 1 22:19:47 athos kernel: usb 1-6: reset high speed USB device using
> ehci_hcd and address 5
> > Sep 1 22:20:14 athos last message repeated 3 times
>
> This is definitely a USB issue (correct cc's added). It looks like some
> attempted reset finally ...
>
> > Sep 1 22:20:14 athos kernel: sd 5:0:0:0: Device offlined - not ready after
> error recovery
> > Sep 1 22:20:14 athos kernel: usb 1-6: USB disconnect, address 5
>
> ... leads to disconnection here.
Try building a kernel with CONFIG_USB_STORAGE_DEBUG enabled and post or
attach the dmesg log showing what happens when you plug in the device.
Alan Stern
Reply-To: drzeus@drzeus.cx On Mon, 1 Sep 2008 23:30:56 +0000 (GMT) pinco pallino <pinc_o@yahoo.it> wrote: > Hi Andrew, > > with the new kernel 2.6.26.3 the SD are now read and wrote correctly, but > SDHC are not read! The kernel repeat the error. Follow the error: > Have you checked that the reader does in fact support SDHC? They tend to fail in all sorts of ways when they don't. Yes, excuse me. I probably have confused my card reader with my notebook built-in card reader ... In fact, my Trust card reader doesn't read SDHC, it read only SD. For your information: However, I have tryed on my notebook. On my notebook I have kernels 2.6.25.9 and 2.6.23.17. With kernel 2.6.25.9, using the builtin card reader, get the same error as the kernel above. Instead, if I start the system with old kernel 2.6.23.17, my SDHC in the built-in card reader is read and wrote correctly, instantaneous. Unfortunately, now I not have more time, but soon I compile the new kernel 2.6.26.3 or better, in my notebook too and try ... Please,excuse me for the inconvenience and for my bad English. Best Regards |