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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2016859.MDetYcSki9@linux-5eaq.site>
Date:	Wed, 16 Jan 2013 09:25:55 +0100
From:	Oliver Neukum <oliver@...kum.org>
To:	Woody Suwalski <terraluna977@...il.com>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Andreas Mohr <andi@...as.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	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 :-(

On Tuesday 15 January 2013 23:26:20 Woody Suwalski wrote:

> The modules are insmoded in a fixed order:
> usb-common, usbcore, xhci-hcd, ehci-hcd, uhci-hcd, ohci-hcd, usbhid, 
> usb_storage,...
> 
> If all USB is built as modules - I get read errors from USB drives when 
> accessing squash image, boot fails.
> If usb-common and usbcore are built in, system seems to crawl with a 
> very slow USB, but boots. That could be caused by timing between hcd 
> modules.

Have you checked which bus the storage device is on?
If it is attached to a companion controller that would explain the speed
issue.

> If usb-common, usbcore and ehci-hcd are built-in, all works OK like 
> "before 3.8".
> I was testing on machines  without xhci or ohci hardware, so these 
> drivers probably are not playing any role.
> I have retried initramfs with a 1s sleep between insmods to verify if it 
> is timing - still the same read errors - so the main issue is _not_ timing.
> The read errors problem is 100% reproducible for me, the blocks where 
> read fails are not fixed - every (failed) boot errors start appearing in 
> a bit different location.

Do you get read errors on the SCSI level only or also errors on the USB level?

	Regards
		Oliver

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