It looks useful. At least to understand better. It looks like the timer interrupt is actually connected to pin 0 of the apic, not pin 2 as the override tells the system. Sadly I messed up with the debug options, so the apic table was not dumped (the right one is apic=debug). But even with what is there, it looks like "cat /proc/interrups" will show IO-APIC as interrupt source. Which means Linux found the right apic pin by guessing. This proves the BIOS is incorrect at that point. What I cannot say is, whether Linux has a chance to detect this automatically. In other cases I saw, this required some knowledge of the chipset and in some cases this was NDA. You have an Intel chipset, maybe there are chances. All in all you should, with that work-around, have no more troubles with that sort of hangs.
-- Hardy, Intrepid, Jaunty 64 "hiccup" on Sager notebook. https://bugs.launchpad.net/bugs/217849 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
