>> On Thu, 23 Feb 2006 21:27:01, Dave Jones <davej@redhat.com> said:

   >> Some pattern analysis would be useful. All the same chipset,
   >> revision?

   > From first impression, it seems they're all (including mine) HP
   > laptops with ATI chipsets.

I have an HP _desktop_ with an ATI chipset and a dual-core 3800+ that
exhibits this.  If your patch just inhibits output for machines with
one logical CPU, it won't be inhibiting it on mine.  I'm seeing:

   powernow-k8: error - out of sync, fix 0xa 0x2, vid 0xa 0x12
   APIC error on CPU0: 00(40)       # once, at boot
   APIC error on CPU0: 40(40)       # repeated regularly after boot

   > I wonder if this is related at all to the 'time goes double speed'
   > bug that some folks see (incidentally, I don't on mine).

Yes, my machine exhibited this bug in earlier 2.6 releases.  Passing
enable_timer_pin_1 fixed it for me before the chipset detection was
brought into mainline.  Now that it's fixed, I still see the errors
above; while both problems are caused by ATI's bizarre chipset, the
error doesn't mean that double time is happening.

   >> Best you collect boot logs.

   > I'll try to gather some more data.

My dmesg and lspci are attached, let me know if you'd like anything
else.  The machine's an HP Pavilion A1250N.