linux-kernel - Re: Linux 3.8-rc1 - another regression on USB :-(

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 for Android: free password hash cracker in your pocket

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

Message-ID: <50D7CFFE.2010504@gmail.com>
Date:	Sun, 23 Dec 2012 22:46:06 -0500
From:	Woody Suwalski <terraluna977@...il.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	USB list <linux-usb@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.8-rc1 - another regression on USB :-(

Greg Kroah-Hartman wrote:
> On Sun, Dec 23, 2012 at 02:35:49PM -0800, Linus Torvalds wrote:
>> Woody,
>>   Any chance you can bisect this? It's not going to be hugely pleasant
>> (with 11k+ commits in between 3.7 and 3.8-rc1 you'll have to compile
>> and test at least 14 kernels), but it would help enormously. Of
>> course, maybe some USB person can guess what would cause the device to
>> go offline..
>>
>> Added Greg and the linux-usb mailing list to the participants list:
>> the images are in the original email on lkml, but there isn't anything
>> particularly interesting there, it really just seems to be an
>> unexpected and spurious USB disconnect, resulting in "USB disconnect,
>> device number 2" followed by "Rejecting I/O to offline device".
> I don't see any images on lkml, sorry.
>
> The kernel log for when the disconnect happened would be great to get.
>
> The kernel can't cause a device to disconnect, that's an electrical
> thing usually, is this perchance a flaky device/connection?  Or has it
> always worked on older kernels?
>
> What host controller is being used here (xhci, ehci, etc.?)
>
> thanks,
>
> greg k-h
I backtrack - it is not directly a USB problem.
If I boot the image into a single mode, and then verify reading the 
squashfs as a compressed file or the files in the mounted uncompressed 
image - there are no errors on read.
Yet if i let it boot into X - it does not - gets bogged with disk access 
errors.
And then there is no access to a USB key anymore.
Will need to investigate further..

Sorry for the alarm, Greg...

--
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/