[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#528422: marked as done (linux-image-2.6.26-2-amd64: repeated warning "scheduling from the idle thread")

Your message dated Tue, 4 Jun 2013 00:30:38 +0200
with message-id <20130603223038.GE5604@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #528422,
regarding linux-image-2.6.26-2-amd64: repeated warning "scheduling from the idle thread"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
528422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528422
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- Package: linux-image-2.6-amd64
Version: 2.6.26+17+lenny1

Linux 2.6.26-2-amd64 #1 SMP Fri Mar 27 04:02:59 UTC 2009 x86_64 GNU/Linux

# cat syslog   OR   # cat kern.log  will show:

May 12 11:43:39 drako kernel: [ 1257.684686] bad: scheduling from the idle thread!
May 12 11:43:39 drako kernel: [ 1257.684694] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1
May 12 11:43:39 drako kernel: [ 1257.684698]
May 12 11:43:39 drako kernel: [ 1257.684700] Call Trace:
May 12 11:43:39 drako kernel: [ 1257.684710]  [<ffffffff80230783>] dequeue_task_idle+0x29/0x34
May 12 11:43:39 drako kernel: [ 1257.684721]  [<ffffffff8022810a>] dequeue_task+0x13/0x1e
May 12 11:43:39 drako kernel: [ 1257.684731]  [<ffffffff8022813b>] deactivate_task+0x26/0x43
May 12 11:43:39 drako kernel: [ 1257.684743]  [<ffffffff80427b69>] schedule+0x14a/0x635
May 12 11:43:39 drako kernel: [ 1257.684752]  [<ffffffff8024d246>] clockevents_notify+0x24/0x6d
May 12 11:43:39 drako kernel: [ 1257.684769]  [<ffffffff803a9ad1>] cpuidle_idle_call+0x0/0xaf
May 12 11:43:39 drako kernel: [ 1257.684782]  [<ffffffff8020ac9e>] cpu_idle+0xae/0xb3
May 12 11:43:39 drako kernel: [ 1257.684810]
May 12 11:43:39 drako kernel: [ 1257.776962] bad: scheduling from the idle thread!
May 12 11:43:39 drako kernel: [ 1257.776962] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1
May 12 11:43:39 drako kernel: [ 1257.776962]
May 12 11:43:39 drako kernel: [ 1257.776962] Call Trace:
May 12 11:43:39 drako kernel: [ 1257.776962]  [<ffffffff8024e153>] tick_dev_program_event+0x29/
0x9b
May 12 11:43:39 drako kernel: [ 1257.776962]  [<ffffffff80230783>] dequeue_task_idle+0x29/0x34
May 12 11:43:39 drako kernel: [ 1257.776962]  [<ffffffff8022810a>] dequeue_task+0x13/0x1e
May 12 11:43:39 drako kernel: [ 1257.776962]  [<ffffffff8022813b>] deactivate_task+0x26/0x43
May 12 11:43:39 drako kernel: [ 1257.776962]  [<ffffffff80427b69>] schedule+0x14a/0x635
May 12 11:43:39 drako kernel: [ 1257.776962]  [<ffffffff80248b8e>] hrtimer_start+0x112/0x134
May 12 11:43:39 drako kernel: [ 1257.776962]  [<ffffffff803a9ad1>] cpuidle_idle_call+0x0/0xaf
May 12 11:43:39 drako kernel: [ 1257.776962]  [<ffffffff8020ac9e>] cpu_idle+0xae/0xb3
... and on and on.

Syslog is more than 400MB and kern.log is more than 500MB. This is in about 3h of laptop usage.

The system is a Dell Latitude D630. I am using Debian Squeeze with kernel 2.6.26-2-amd64.
After a long time on, when I try to open a file from the Internet, Iceweasel says there is not enough room in tmp to store the file.
I can see regular activity in the hard drive, in the system monitor, which I'm sure is log writing.

Thank you,
António


--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: