http://bugzilla.kernel.org/show_bug.cgi?id=10409
------- Comment #46 from [EMAIL PROTECTED] 2008-05-20 13:34 ------- Thanks, but ... well, my intention was to get reliable debug data from your tests. Unfortunately taking pictures doesn't help much. (BTW, your screenshot indeed contains some parts of the desired output ;-) But to compare dmesg output of several boots, screenshots are not very helpful. I think w/o proper debugging means (e.g. serial console) it's not possible to fix the IO-A-PIC configuration on your machine to get hpet working. Many similar issues with timer/hpet and IOAPIC pin assignment were reported in the past. Often the problems went away when a BIOS update was applied, (If a BIOS update with a suitable fix was available...) It seems that you just have to live with a "broken" hpet on this machine. The question is whether it is acceptable to use "hpet=disable" or whether the blacklisting from Shaohua (comment #36) should be applied. -- 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
