[lkml]   [2007]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [5/6] 2.6.21-rc2: known regressions
    On Mon, 2007-03-05 at 02:50 +0100, Adrian Bunk wrote:
    > Subject : ThinkPad T60: system doesn't come out of suspend to RAM
    > (CONFIG_NO_HZ)
    > References :
    > Submitter : Michael S. Tsirkin <>
    > Handled-By : Thomas Gleixner <>
    > Ingo Molnar <>
    > Status : unknown
    > Subject : macbook pro suspend to ram broken (clockevents)
    > References :
    > Submitter : Soeren Sonnenburg <>
    > Caused-By : Thomas Gleixner <>
    > commit e9e2cdb412412326c4827fc78ba27f410d837e6e
    > Status : unknown

    I can reproduce this on my dual core VAIO. There are some issues:

    1) clockevents code needs probably a resume fix, which I'm working on

    2) The BOGOMIPS calibration of CPU#1 after resume is completely hosed.
    CPU#1 has ~ 200000 Bogomips after resume, which is off by factor 500.
    BOGOMIPS is calibrated vs. jiffies, This was also observed by Ingo on
    his T60. This is similar to the LAPIC calibration problems I had seen
    before the LAPIC rework. IRQ#0 comes in extremly slow (probably caused
    by SMM crap, e.g. PS/2 keyboard emulation)

    3) on suspend we shut down CPU#1 on dual core machines. resume restarts
    CPU#1. Now one would expect that acpi_processor_power_verify would be
    called, so that the "LAPIC/TSC stops in C3"-workaround gets applied to
    CPU#1. Len confirmed that it should be called, when the cpu is brought
    online. This was not noticed before as the old apic code kept the
    broadcast bit on cpu shutdown.

    Len, can you please look into #3 ?

    > Subject : dynticks makes ksoftirqd1 use unreasonable amount of cpu time
    > References :
    > Submitter : Emil Karlson <>
    > Handled-By : Thomas Gleixner <>
    > Status : problem is being debugged

    Delayed until the above is sorted out.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-03-06 00:39    [W:0.021 / U:90.292 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site