Am 25.08.2007 05:30 schrieb Andrew Morton: > On Sat, 25 Aug 2007 02:47:59 +0200 Tilman Schmidt <tilman@xxxxxxx> wrote: >>>> - on console early during boot, also in SuSE's /var/log/boot.msg: >>>> >>>> your system time is not correct: >>>> Wed Jul 13 13:15:31 UTC 1910 >>>> setting system time to: >>>> Tue Jul 24 00:00:00 UTC 2007 With 2.6.23-rc4-mm1 this doesn't happen anymore, so whatever it was seems to be fixed. >> --- /tmp/bootmsg-2.6.23-rc3 2007-08-25 02:25:54.000000000 +0200 >> +++ /tmp/bootmsg-2.6.23-rc3-mm1 2007-08-25 02:26:08.000000000 +0200 [...] >> <6>..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 >> -<6>checking TSC synchronization [CPU#0 -> CPU#1]: passed. >> +<6>checking TSC synchronization [CPU#0 -> CPU#1]: >> +<4>Measured 32 cycles TSC warp between CPUs, turning off TSC clock. >> +<4>Marking TSC unstable due to: check_tsc_sync_source failed. This still happens identically with 2.6.23-rc4-mm1. Mainline kernels like my TSC, -mm kernels don't. >> -<7>hpet_resources: 0xfed00000 is busy >> +<4>hpet_acpi_add: no address or irqs in _CRS > > oh boy 2.6.23-rc4-mm1 reverts to mainline behaviour here. (ie. "busy" instead of "no address or irqs") Dunno if that's good or bad. >> +<4>thermal: Unknown symbol acpi_processor_set_thermal_limit > > I think there are acpi fixes in Len's latest tree which will fix this. Gone in 2.6.23-rc4-mm1. HTH Tilman -- Tilman Schmidt E-Mail: tilman@xxxxxxx Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
Attachment:
signature.asc
Description: OpenPGP digital signature
