linux-kernel - Re: Stable regression: usb-storage is stuck in 2.6.26.5

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: <48CBB626.4050300@msgid.tls.msk.ru>
Date:	Sat, 13 Sep 2008 16:46:30 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	linux-kernel@...r.kernel.org
Subject: Re: Stable regression: usb-storage is stuck in 2.6.26.5

Michael Tokarev wrote:
> Just updated my machine from 2.6.26.1 to 2.6.26.5, and it does not
> wan to boot anymore.  It says "Initializing USB Mass Storage driver.."
> (when trying to load usb-storage module) and sits here forever, every
> 2 minutes showing warnings about stuck processes (traces below).
> With 2.6.26.1 or any previous version I never experienced this
> problem.  Both 32- and 64-bits kernels behave the same way.
> While waiting for usb-storage to complete, no other USB devices
> works (incl. mouse and keyboard).
> 
> The machine is an AMD X2-64 (BE-2400) processor with an nVidia MCP51
> chipset (lspci is below).  Motherboard is Asus M2NPV-VM, latest BIOS
> (1401, dated 08/07/2008)
> 
> I'm rebuilding 2.6.26.3 for now -- trying to bisect the issue...
[...]

And it's more: even without usb-storage, other USB devices does
not work, waiting in the same usb_start_wait_urb.

Ok, it turned out to be pretty.. interesting.

It's not a regression within -stable kernel series.  The problem
happens when BOTH are true:

   - using latest BIOS for this mobo (1401), AND
   - enabling KVM_GUEST in kernel.

The only difference in my kernel config between .1 and .5 was
to enable KVM_GUEST and KVM_CLOCK, and also I2C_HELPER_AUTO
which was added by kernel update.

Going with previous BIOS (1201) OR disabling PARAVIRT_GUEST
fixes the problem.  I'll try to figure out which config
option is at problem here.

> Thanks.
> 
> /mjt
> 
--
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/