Bootup time regression from 2.6.27 to 2.6.28-rc3+ - Kernel

This is a discussion on Bootup time regression from 2.6.27 to 2.6.28-rc3+ - Kernel ; On Sunday 09 November 2008, Thomas Gleixner wrote: > Find below the lineup of the timers-fixes-for-linus branch of the tip > tree (the same as Arjan posted minus the irq fixes) I've tested with Thomas' patch set on top of ...

+ Reply to Thread
Page 2 of 2 FirstFirst 1 2
Results 21 to 25 of 25

Thread: Bootup time regression from 2.6.27 to 2.6.28-rc3+

  1. Re: Bootup time regression from 2.6.27 to 2.6.28-rc3+

    On Sunday 09 November 2008, Thomas Gleixner wrote:
    > Find below the lineup of the timers-fixes-for-linus branch of the tip
    > tree (the same as Arjan posted minus the irq fixes)


    I've tested with Thomas' patch set on top of v2.6.28-rc3-261-g8b805ef.

    The notebook boots normally, but spends way too much time in C0.

    Cheers,
    FJP


    POWERTOP BEFORE
    ===============
    This is somewhere around -rc3-200 with peek_ahead disabled with a return
    in the function. System is on battery after having been suspended to RAM
    a few times

    Note the double C0 and missing P-states.

    Cn Avg residency P-states (frequencies)
    C0 (cpu running) ( 3.2%)
    C0 0.0ms ( 0.0%)
    C1 0.0ms ( 0.0%)
    C2 0.9ms ( 0.1%)
    C4 3.4ms (96.7%)

    Wakeups-from-idle per second : 289.1 interval: 10.0s
    Power usage (ACPI estimate): 9.8W (4.5 hours)

    Top causes for wakeups:
    42.8% (136.5) : extra timer interrupt
    30.5% ( 97.2) : PS/2 keyboard/mouse/touchpad
    12.4% ( 39.5) : Rescheduling interrupts
    3.6% ( 11.6) : iwlagn
    2.5% ( 8.0) : mod_timer (rh_timer_func)
    1.7% ( 5.4) artsd : schedule_hrtimeout_range (hrtimer_wakeup)
    1.1% ( 3.6) : hrtimer_start (tick_sched_timer)
    1.0% ( 3.1) : acpi
    0.6% ( 2.0) kicker : schedule_hrtimeout_range (hrtimer_wakeup)
    0.4% ( 1.2) klipper : schedule_hrtimeout_range (hrtimer_wakeup)
    0.3% ( 1.1) kdesktop : schedule_hrtimeout_range (hrtimer_wakeup)
    0.3% ( 1.0) kwifimanager : schedule_hrtimeout_range (hrtimer_wakeup)
    0.3% ( 1.0) : enqueue_task_rt (sched_rt_period_timer)
    0.3% ( 1.0) artsd : hrtimer_start (it_real_fn)
    0.3% ( 1.0) kwrapper : do_nanosleep (hrtimer_wakeup)
    0.3% ( 1.0) kwin : schedule_hrtimeout_range (hrtimer_wakeup)
    0.3% ( 0.9) Xorg : schedule_hrtimeout_range (hrtimer_wakeup)
    0.2% ( 0.5) iwlagn : mod_timer (ieee80211_sta_timer)
    0.2% ( 0.5) gpg-agent : schedule_hrtimeout_range (hrtimer_wakeup)
    0.2% ( 0.5) hald-addon-stor : schedule_hrtimeout_range (hrtimer_wakeup)


    POWERTOP AFTER
    ==============
    Again on battery; P-states are back and the second C0 is now "polling"
    (both same as with 2.6.27.4).

    System permanently remains very high in C0!
    Wakeups go down to ~30 without user input (keyboard/mouse activity), which
    is a bit lower than I get with .27.4.

    Cn Avg residency P-states (frequencies)
    C0 (cpu running) (49.7%) 1333 Mhz 0.0%
    polling 0.0ms ( 0.0%) 1200 Mhz 0.0%
    C1 0.0ms ( 0.0%) 1067 Mhz 0.0%
    C2 7.5ms ( 1.9%) 800 Mhz 100.0%
    C4 8.5ms (48.4%)

    Wakeups-from-idle per second : 59.6 interval: 15.0s
    Power usage (ACPI estimate): 9.7W (4.4 hours)

    Top causes for wakeups:
    34.6% ( 36.3) : PS/2 keyboard/mouse/touchpad
    16.0% ( 16.7) : Rescheduling interrupts
    8.9% ( 9.3) : iwlagn
    8.4% ( 8.8) : extra timer interrupt
    7.8% ( 8.1) : mod_timer (rh_timer_func)
    5.6% ( 5.9) : hrtimer_start (tick_sched_timer)
    5.2% ( 5.4) artsd : schedule_hrtimeout_range (hrtimer_wakeup)
    2.9% ( 3.0) kicker : schedule_hrtimeout_range (hrtimer_wakeup)
    1.1% ( 1.2) kdesktop : schedule_hrtimeout_range (hrtimer_wakeup)
    1.0% ( 1.1) Xorg : schedule_hrtimeout_range (hrtimer_wakeup)
    1.0% ( 1.0) kwifimanager : schedule_hrtimeout_range (hrtimer_wakeup)
    1.0% ( 1.0) artsd : hrtimer_start (it_real_fn)
    1.0% ( 1.0) kwrapper : do_nanosleep (hrtimer_wakeup)
    1.0% ( 1.0) kwin : schedule_hrtimeout_range (hrtimer_wakeup)
    1.0% ( 1.0) klipper : schedule_hrtimeout_range (hrtimer_wakeup)
    0.5% ( 0.5) hald-addon-stor : schedule_hrtimeout_range (hrtimer_wakeup)
    0.5% ( 0.5) iwlagn : mod_timer (ieee80211_sta_timer)
    0.5% ( 0.5) : __mod_timer (neigh_periodic_timer)
    0.4% ( 0.5) gpg-agent : schedule_hrtimeout_range (hrtimer_wakeup)
    0.4% ( 0.4) knotify : schedule_hrtimeout_range (hrtimer_wakeup)

    In both cases there's no C3, but I think that's because C3 changes to C4
    when on battery?

    Cheers,
    FJP
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  2. Re: Bootup time regression from 2.6.27 to 2.6.28-rc3+

    On Sun, Nov 09, 2008 at 10:57:45PM +0100, Thomas Gleixner wrote:
    > > hmm, on the other hand, powertop application shows that C4 state is 51.5%
    > > residency and C0 is 47.3% residency. I have about 5% C0 residency and 95-98%
    > > C3 residency. Is this expected?

    >
    > Hmm. I do not understand. Where from are the second numbers ?


    sorry, the second numbers are without your patch.

    > Can you please provide your .config ?


    attached.

    --
    Lukáš Hejtmánek


  3. Re: Bootup time regression from 2.6.27 to 2.6.28-rc3+

    On Sun, Nov 09, 2008 at 10:57:45PM +0100, Thomas Gleixner wrote:
    > > > it would be greatly appreciated if those that see this issue can test the
    > > > patch below (which is a combo patch of thomas' fixes, to make testing
    > > > easier) and confirm if this fixes the hangs. If they do fix the issue we
    > > > don't need to disable anything and get better power savings as bonus as
    > > > well.


    another observation, it sometimes happens that a key press causes a repeat too
    fast.

    --
    Lukáš Hejtmánek
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  4. Re: Bootup time regression from 2.6.27 to 2.6.28-rc3+

    On dim, 2008-11-09 at 13:24 -0800, Arjan van de Ven wrote:
    > On Sun, 9 Nov 2008 21:34:32 +0100
    > Lukas Hejtmanek wrote:
    >
    > > On Sun, Nov 09, 2008 at 12:28:35PM -0800, Arjan van de Ven wrote:
    > > > for me, the plan is that we need to get Thomas' fixes tested by
    > > > someone who can reproduce this very reliably. If they fix it, great.

    > >
    > > as for me, 100% of boots require a key hit to proceed in 2.6.28-rc3
    > > (more precisely, the current git head).
    > >

    >
    > it would be greatly appreciated if those that see this issue can test
    > the patch below (which is a combo patch of thomas' fixes, to make
    > testing easier) and confirm if this fixes the hangs.
    > If they do fix the issue we don't need to disable anything and get betterpower
    > savings as bonus as well.


    Under 2.6.28-rc4 the bootime seems ok, but I have way too much powertop
    wakups:

    corsac@hidalgo: sudo powertop -d
    PowerTOP 1.10 (C) 2007, 2008 Intel Corporation

    Collecting data for 15 seconds


    Cn Avg residency
    C0 (cpu running) ( 4,3%)
    C0 0,0ms ( 0,0%)
    C1 0,0ms ( 0,0%)
    C2 0,5ms ( 0,3%)
    C4 2,8ms (95,5%)
    P-states (frequencies)
    2,21 Ghz 1,3%
    2,21 Ghz 0,0%
    1,60 Ghz 0,5%
    800 Mhz 98,1%
    Wakeups-from-idle per second : 346,5 interval: 15,0s
    Power usage (ACPI estimate): 15,1W (1,6 hours)
    Top causes for wakeups:
    74,1% (278,5) : extra timer interrupt
    8,8% ( 33,2) : Rescheduling interrupts
    4,1% ( 15,3) : uhci_hcd:usb5, yenta,
    i915@pci:0000:00:02.0
    3,6% ( 13,7) : iwlagn
    1,7% ( 6,5) : acpi
    1,1% ( 4,1) : usb_hcd_poll_rh_status
    (rh_timer_func)
    1,0% ( 3,9) : ahci

    Cheers,
    --
    Yves-Alexis

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.9 (GNU/Linux)

    iEYEABECAAYFAkkYOwgACgkQTUTAIMXAW67PrACfbRNHIwcS/a3ZcrdZleGos+CX
    F2oAnjc8SEDfYS3/0tuJ9X7ACehu8j90
    =C2q1
    -----END PGP SIGNATURE-----


  5. Re: Bootup time regression from 2.6.27 to 2.6.28-rc3+



    > Under 2.6.28-rc4 the bootime seems ok, but I have way too much powertop
    > wakups:


    I see the same on a T61.
    There was a boot-stall in -rc3, now gone in rc4.
    (as of today's top of tree: 3ad4f597058301c97f362e500a32f63f5c950a45)

    However, I'm seeing over 800 "extra timer interrupt" per second when idle

    -Len
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

+ Reply to Thread
Page 2 of 2 FirstFirst 1 2