On Wed, Dec 28, 2011 at 06:11:14PM +0100, Mathieu Malaterre wrote: > On Thu, Dec 22, 2011 at 8:52 PM, Sarah Sharp > <sarah.a.sharp@xxxxxxxxxxxxxxx> wrote: > > On Thu, Dec 22, 2011 at 04:18:56PM +0100, Mathieu Malaterre wrote: > >> On Fri, Dec 16, 2011 at 11:27 AM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > >> System: Dell System Vostro 3750 / Portable Computer > >> > >> Ok. So I am running: 3.2.0-rc4-amd64 from debian experimental. > >> > >> No mouse plugged to USB 2.0/3.0 interface: boot is fine > >> Mouse plugged to USB 2.0 interface: boot is fine > >> Mouse plugged to USB 3.0 interface: boot simply stops > > > > Does the boot stop when you have a non-HID USB device plugged into the > > USB 3.0 port (e.g. hub or flash drive or USB speaker)? It could be an > > issue with a buggy BIOS trying to use the mouse and keyboard (HID > > devices) attached to the USB 3.0 host. Perhaps it changes the ACPI > > tables when it tries to use the USB 3.0 host controller, and > > accidentally overlaps the regions? But if your keyboard and mouse were > > under USB 2.0, maybe it will only map in the USB 2.0 host controller. > > I tried booting kernel 3.0.2 (debian/unstable 3.2.0-rc4-amd64) with a > USB key plugged into USB 3.0 and was stuck again. So I can confirm > that with a normal USB key (non-HID) plugged in USB 3.0 port, makes > the kernel refuse to boot. Please try a USB hub as well. It's possible the BIOS is trying to read from the flash drive (which is what I assume you mean by USB key). > >> As suggested by Jonathan N. [1] here is what I did next: > >> > >> $ cat /etc/modprobe.d/mm-blacklist-xhci.conf > >> blacklist xhci_hcd > >> $ update-initramfs -u -k all > >> $ sudo reboot > > > > Were you blacklisting xhci only because of the "xhci_hcd 0000:03:00.0: > > WARN: Stalled endpoint" messages? Because those messages are harmless, > > and don't mean anything is *wrong* with the host controller. > > I simply blindly follow the suggestion. Yeah, don't try to blacklist xhci-hcd. It's not useful. > > Even if there's no xHCI driver loaded, it seems that ACPI is noticing > > the conflict between the PCI registers and another region. So unloading > > the xHCI driver won't help your system boot. You'd need to get a fix > > into the ACPI subsystem to work around the conflict. I don't think any > > xHCI driver modification can help here. > > Is there a way to check if bug is related to ACPI or rather USB 3.0 ? The log messages seem to indicate that it's either an ACPI or a BIOS issue. I really can't suggest any other tests without some input from the ACPI folks. The best solution I can suggest is not boot with a USB device plugged into your USB 3.0 port. Sarah Sharp -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
