[Bugme-new] [Bug 10944] New: hrtimers and dyntick broken due tu lapic "not functionnal"

bugme-daemon at bugzilla.kernel.org bugme-daemon at bugzilla.kernel.org
Sat Jun 21 01:53:43 PDT 2008


http://bugzilla.kernel.org/show_bug.cgi?id=10944

           Summary: hrtimers and dyntick broken due tu lapic "not
                    functionnal"
           Product: Timers
           Version: 2.5
     KernelVersion: 2.6.26-rc6
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: Other
        AssignedTo: johnstul at us.ibm.com
        ReportedBy: casteyde.christian at free.fr


Latest working kernel version: 2.6.25.6
Earliest failing kernel version: 2.6.26-rc6 or less
Distribution: Bluewhite64 (64 bits Slackware)
Hardware Environment: Athlon 64 X2, 64 bits
Software Environment: Dynticks, hrtimers activated in config
Problem Description:
It may very well be only a trace or a warning on something that never worked,
but since 2.6.26 I got the following warnings in dmesg:

Clockevents: could not switch to one-shot mode: lapic is not functional.
Could not switch to high resolution mode on CPU 0
Clockevents: could not switch to one-shot mode: lapic is not functional.
Could not switch to high resolution mode on CPU 1

followed by:
Clockevents: could not switch to one-shot mode:<6>Clockevents: could not switch
to one-shot
 mode: lapic is not functional.
Could not switch to high resolution mode on CPU 0
 lapic is not functional.
Could not switch to high resolution mode on CPU 1

These logs were not present with 2.6.25. They seem to indicate that lapic code
is not working anymore in 2.6.26. I do not see any problem otherwise in using
the kernel.

I append full 2.6.25 and 2.6.26 dmesg logs for analysis.

Steps to reproduce:
Maybe this is platform specific. I can do test and patch if necessary.


-- 
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.


More information about the Bugme-new mailing list