Created attachment 30072 [details] 2.6.35.4 dmesg without problems I have a problem since I bought a Gigabyte GA-MA69VM-S2 motherboard in 03/2008. Since then, I dual boot with Windows Vista and Windows 7. If I reboot from Windows to Linux, the kernel returns "ohci_hcd 0000:00:13.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ." and the USB mouse doesn't work. Recently, I moved my keyboard from PS/2 to USB, and it also fails with that scenario. The workaround is to, before booting into Linux, go to the BIOS and change "USB Mouse" from "Yes" to "No" or from "No" to "Yes. Doing that, both USB mouse and keyboard work. I don't know what causes it, but it's very annoying if I forget to go to the BIOS. I'm attaching both dmesg, in case it helps. BTW, it's really 2.6.35.4, just without EXTRAVERSION.
Created attachment 30082 [details] 2.6.35.4 dmesg with problems
On Tue, Sep 14, 2010 at 09:57:38PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > I have a problem since I bought a Gigabyte GA-MA69VM-S2 motherboard in > 03/2008. > > Since then, I dual boot with Windows Vista and Windows 7. Can you verify that you have the latest BIOS update as this really looks like the BIOS isn't properly initializing the hardware.
I don't have the latest (if I update now, I'd have to reinstall Windows), but from the one I have, the only difference is support for a new CPU. I very doubt they fixed anything besides that, as the motherboard was released in 2007.
On Wed, Sep 15, 2010 at 12:28:55AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > I don't have the latest (if I update now, I'd have to reinstall Windows), but > from the one I have, the only difference is support for a new CPU. I very > doubt > they fixed anything besides that, as the motherboard was released in 2007. You said you already had Windows on the machine, so why can't you update it? And I would suggest doing the update, as this most likely is a BIOS issue.
The last time I changed the BIOS, I had to reinstall Windows, because it'd BSOD also trying to boot in Safe Mode. But what if I update the BIOS and it doesn't solve the issue ? I really doubt that the new BIOS, which, as I said, only lists CPU updates, would fix it. If it doesn't work, would it be possible to make a workaround in the kernel ? I see various in other places, like "Enable it if you have a BIOS X and your kernel does Y". It's really strange to only get the problem going from Windows to Linux, not from Linux to Windows or Linux to Linux.
On Wed, Sep 15, 2010 at 04:10:17AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote: > The last time I changed the BIOS, I had to reinstall Windows, because it'd > BSOD > also trying to boot in Safe Mode. Sounds like a Windows bug :) > But what if I update the BIOS and it doesn't solve the issue ? I really doubt > that the new BIOS, which, as I said, only lists CPU updates, would fix it. This is not something that the Linux kernel controls. > If it doesn't work, would it be possible to make a workaround in the kernel ? > I > see various in other places, like "Enable it if you have a BIOS X and your > kernel does Y". If you can figure out what is going on wrong here, yes, we can. Try emailing linux-usb@vger.kernel.org about this and the developers there can help you out. > It's really strange to only get the problem going from Windows to Linux, not > from Linux to Windows or Linux to Linux. I agree.
Comparing your dmesg logs, one suspicious thing is this (from the broken case): +pci 0000:00:13.5: EHCI: unrecognized capability 30 Can you attach another pair of working/broken logs, using the "pci=earlydump" option? Maybe there's a clue there.
Created attachment 30802 [details] good dmesg with pci=earlydump
Created attachment 30812 [details] bad dmesg with pci=earlydump
All USB bugs should be sent to the linux-usb@vger.kernel.org mailing list, and not entered into bugzilla. Please bring this issue up there, if it is still a problem in the latest kernel release.