registry team mailing list archive

[Orcie <mef.vanschalkwijk@xxxxxxxxx>]

Very encouraging Leif. My impatience is more at rest now.

On Mon, May 31, 2010 at 7:39 PM, Leif Walsh <leif.walsh@xxxxxxxxx>
wrote:

> Dear all who think this bug is taking too long:
>
> You're right.  It's been outstanding for quite some time now, and
> really should have been fixed before release, or else the 2.6.32
> kernel shouldn't have been accepted.
>
> As it is, the bug is not fixed.  The best people for the job are the
> linux kernel devs, not ubuntu employees/contributors.  They have a
> patch and are in the process of reviewing it.  Believe me when I tell
> you that you want them to finish reviewing it.
>
> Once it's accepted, it'll be pushed in the next 2.6.32 maintenance
> release.  I expect to see this in .15, if it's not already in .14
> (which got pushed a last week and since I haven't been following this
> patch, I don't know if it's in there).  If it goes in .15, it'll be
> another few weeks to couple of months.  Once that happens, the ubuntu
> people can package it up and release it as a maintenance update.
>
> Depending on the climate, you may also see this patch in a newer,
> backported kernel (2.6.33 and above), so if you enable backports you
> might see it sooner.
>
> Either way, there's nothing you can do except either wait for a newer
> kernel or downgrade to an older kernel (2.6.31 is a good choice, as
> evidenced by some people above).
>
> Another way to soften the blow of this bug is simply to give the load
> balancer less to do.  I've noticed that, while it certainly causes far
> more wakeups than it should, the wakeups *scale with the load* of the
> computer.  Therefore, if you do all the things you normally do to
> reduce wakeups, the load balancer will be less of an issue as well.
>
> Whatever you choose to do (I'm just sticking with the kernel and
> living with the bug...it's not so bad with my usage pattern), be
> patient.  You'll get the fix soon enough, and soon after that you'll
> forget it was ever a problem.
>
> <wink>If that's not enough for you, go install slackware.</wink>
>
> --
> Tens of wakes per second in "[kernel scheduler] Load balancing tick" on
> Core 2 Duo even with only 1 core enabled
> https://bugs.launchpad.net/bugs/524281
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Confirmed
> Status in “linux-2.6” package in Debian: Incomplete
>
> Bug description:
> powertop reports above 70 wakes per second in "[kernel scheduler] Load
> balancing tick" task, and above 200 when there's any little load, running on
> a Core 2 Duo processor (T6500) with a single core enabled (multicore
> disabled in BIOS).
> Will still try noapic, nolapic, maxcpus and nosmp in the boot parameters
> and reproduce it with the mainline kernel.
>
> ProblemType: Bug
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
> Architecture: i386
> ArecordDevices:
>  **** List of CAPTURE Hardware Devices ****
>  card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
>    Subdevices: 1/1
>    Subdevice #0: subdevice #0
> AudioDevicesInUse:
>  USER        PID ACCESS COMMAND
>  /dev/snd/controlC0:  etrusco    1606 F.... pulseaudio
>                       etrusco   15151 F.... foobar2000.exe
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
>  Card hw:0 'Intel'/'HDA Intel at 0xfddf8000 irq 22'
>    Mixer name   : 'Realtek ALC269'
>    Components   : 'HDA:10ec0269,1b0a4009,00100004
> HDA:11c11040,1b0a4007,00100200'
>    Controls      : 19
>    Simple ctrls  : 11
> Card1.Amixer.info:
>  Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfebec000 irq 17'
>    Mixer name   : 'ATI R6xx HDMI'
>    Components   : 'HDA:1002aa01,00aa0100,00100100'
>    Controls      : 4
>    Simple ctrls  : 1
> Card1.Amixer.values:
>  Simple mixer control 'IEC958',0
>    Capabilities: pswitch pswitch-joined penum
>    Playback channels: Mono
>    Mono: Playback [on]
> Date: Fri Feb 19 05:25:42 2010
> DistroRelease: Ubuntu 10.04
> EcryptfsInUse: Yes
> MachineType: Philco PHN10XXX.
> Package: linux-image-2.6.32-13-generic 2.6.32-13.18
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-13-generic
> root=UUID=d482e94f-9370-4ad2-9536-986541003db5 ro acpi.power_nocheck=1
> acpi_osi=linux radeon.blacklist=yes
> ProcEnviron:
>  LANG=en_US.UTF-8
>  SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
> Regression: No
> RelatedPackageVersions: linux-firmware 1.29
> Reproducible: Yes
> RfKill:
>  0: phy0: Wireless LAN
>   Soft blocked: no
>   Hard blocked: no
> SourcePackage: linux
> TestedUpstream: No
> Uname: Linux 2.6.32-13-generic i686
> dmi.bios.date: 06/01/2009
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 1.01
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.vendor: PEGATRON CORP.
> dmi.board.version: To be filled by O.E.M.
> dmi.chassis.asset.tag: To Be Filled By O.E.M.
> dmi.chassis.type: 10
> dmi.chassis.vendor: PEGATRON CORP.
> dmi.chassis.version: To Be Filled By O.E.M.
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr1.01:bd06/01/2009:svnPhilco:pnPHN10XXX.:pvr1.01:rvnPEGATRONCORP.:rn:rvrTobefilledbyO.E.M.:cvnPEGATRONCORP.:ct10:cvrToBeFilledByO.E.M.:
> dmi.product.name: PHN10XXX.
> dmi.product.version: 1.01
> dmi.sys.vendor: Philco
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/524281/+subscribe
>

-- 
Tens of wakes per second in "[kernel scheduler] Load balancing tick" on Core 2 Duo even with only 1 core enabled
https://bugs.launchpad.net/bugs/524281
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.