http://bugzilla.kernel.org/show_bug.cgi?id=9528
------- Comment #91 from [EMAIL PROTECTED] 2008-02-01 09:13 ------- I suspect, based on what we've observed now, that something like this has occurred: 1) Some time ago, an old nVidia reference BIOS had an SMI trap with code that really did need to poke at the OHCI PCI device. 2) nVidia have long since removed this part of the trap from their reference BIOS (certainly pre nForce 4). 3) Many BIOS vendors have not updated their BIOS's accordingly, and the old SMI trap has found its way into more modern machines (so far - nForce 4, 5 & 6 at least). 4) Some vendors have then removed the offending part of the trap later (I suspect, for instance, that Robert Hancock has a much newer BIOS on his board than Arthur, hence could not reproduce the problem). So Asus at least are on the ball and have fixed this in later BIOS releases, I know of a Tyan that cannot reproduce this problem, whilst Abit _still_ haven't fixed this as of their latest BIOS. So, yes, technically this is a bad BIOS issue, and some vendors have fixed it, but I suspect Windows still implements the old suspend behaviour anyway (since there will be a lot of boards with the older BIOS's still floating about), and blanket bans PCI autosuspend for the OHCI controller on offending chipsets to play it safe (I know at least on nForce 4 this is the case - I'm not sure for newer chipsets). -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
