linux-kernel - Re: [usb-storage] 2.6.22-rc4-mm2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1181320228.7348.290.camel@twins>
Date:	Fri, 08 Jun 2007 18:30:28 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	USB Storage list <usb-storage@...ts.one-eyed-alien.net>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [usb-storage] 2.6.22-rc4-mm2 - usb-storage

On Fri, 2007-06-08 at 10:16 -0400, Alan Stern wrote:
> [Trimmed the recipients list]
> 
> On Fri, 8 Jun 2007, Peter Zijlstra wrote:
> 
> > On Thu, 2007-06-07 at 18:20 -0400, Alan Stern wrote:
> > > On Thu, 7 Jun 2007, Peter Zijlstra wrote:
> > > 
> > > > My kernel went chatty when I tried to access my usb-stick; which it
> > > > didn't seem to find.
> ....
> > > This is false-alarm output from something intended to track down a 
> > > reported bug.  The patch responsible is this one: 
> > 
> > Right, well then I have another problem. Because it doesn't find my
> > usb-stick.
> > 
> > I noticed from D states (quite easy to reproduce, just modprobe
> > usb-storage):
> > 
> > scsi_eh_6     D ffff8100079ed640     0  3568      2 (L-TLB)
> >  ffff81000ac45e10 0000000000000046 0000000000000000 0000000180252936
> >  0000000000000002 0000000100000000 ffff81000ac42700 ffff8100043ca240
> >  ffff81000ac42978 ffffffff8024fc8d 00000000000000ff ffff81000ac42700
> > Call Trace:
> >  [<ffffffff804775a9>] wait_for_completion+0x82/0xc1
> >  [<ffffffff88201673>] :usb_storage:command_abort+0x7c/0x86
> >  [<ffffffff8805f54f>] :scsi_mod:scsi_error_handler+0x28e/0x4cc
> >  [<ffffffff8024a7ff>] kthread+0x47/0x74
> >  [<ffffffff8020cc28>] child_rip+0xa/0x12
> 
> Okay, this is a separate problem.  To help diagnose it, please turn on 
> CONFIG_USB_DEBUG and CONFIG_USB_STORAGE_DEBUG and then post the 
> resulting dmesg log.

Here goes:

 http://programming.kicks-ass.net/misc/dmesg


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/