On Monday 06 February 2006 12:02 am, Carlo E. Prelz wrote: > > > Interesting ... feels like a BIOS problem. If you want to experiment, > > there's a right bracket -- "}" -- immediately before that. Try moving > > it right after that write, so that write_config_byte is covered by the > > preceding "if LEGSUP_BIOS" test; or copying the much later "disable SMI" > > clause into an "else" for that "if". > > The first one would be useless - I inserted lots of printouts to find > out where the freeze took place, and I know that the > EHCI_USBLEGSUP_BIOS flag is on (cap is 0x10001). The value remains the > same after the 'spin till it hands it over' loop - so that this > printout appears: > > 0000:00:13.2 EHCI: BIOS handoff failed (BIOS bug ?)
If it printed that, then how is it possible that it hung _before_ printing that message??? Your reports are not making any sense to me. Maybe that whole "if" block that turns that SMI _on_ is the problem; it was part of the "early handoff" code, which came from who knows where, was clearly buggy, and was never widely used until recently. Enabling the SMI seemed pretty dubious to me, but I suspect that some undescribed buggy BIOS really does need it ... maybe whoever provided that "early" handoff version could report what they were trying to do by enabling the SMI? - Dave ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
