mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Pineau <benjamin_pineau@zouh.org>
To: linux-kernel@vger.kernel.org
Subject: 2.6.22-rc3 : "BUG: scheduling while atomic: swapper/0x00000100/0"
Date: Mon, 4 Jun 2007 15:55:14 +0200	[thread overview]
Message-ID: <20070604135514.GA14426@zouh.org> (raw)

Hi,
The stock 2.6.22-rc3 (with no alien modules or patchs) on my i386 desktops
fired this message in loop like a mad (thousands of times/second) until
reboot, for no evident reason (I mean, I don't know what I did to get this, 
from an end-user perspective : I was just editing text on vim and surfing 
the web with firefox). 

The same kernel worked for several days without exposing surch a problem
and this never occured with the olders kernels I used (2.6.17, 2.6.21).

Beside the log presure, the only symptom I noted is that reboot didn't work:
it killed X and probably most userland, but got silently stuck on the console,
without actually restarting the machine. Then, on the console, everytime I 
typed a key, 2 new "BUG: scheduling ..." lines appeared. Typing ctrl-alt-del 
finaly forced it to physically reboot.

I've got more details in dmesg. Sample (full dmesg plus more
at http://oshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt):

[333259.145874]  =======================
[333259.145894] BUG: scheduling while atomic: swapper/0x00000100/0
[333259.145906]  [<c03f254c>] schedule+0x4dc/0x860
[333259.145915]  [<c0141c76>] getnstimeofday+0x36/0xd0
[333259.145932]  [<c013fcc6>] ktime_get_ts+0x16/0x50
[333259.145941]  [<c013a358>] rcu_pending+0x38/0x50
[333259.145949]  [<c013a3a2>] rcu_needs_cpu+0x32/0x40
[333259.145964]  [<c01022d0>] mwait_idle+0x0/0x20
[333259.145974]  [<c010245c>] cpu_idle+0x9c/0xe0
[333259.145985]  [<c0558a7f>] start_kernel+0x31f/0x3b0
[333259.145994]  [<c05581f0>] unknown_bootoption+0x0/0x260
[333259.146007]  =======================
[334129.061709] BUG: scheduling while atomic: swapper/0x00000100/0
[334129.061735]  [<c03f254c>] schedule+0x4dc/0x860
[334129.061760]  [<c013f96b>] enqueue_hrtimer+0x6b/0x110
[334129.061773]  [<c0140245>] hrtimer_start+0xc5/0x130
[334129.061785]  [<c01459e1>] tick_nohz_restart_sched_tick+0xf1/0x140
[334129.061796]  [<c01022d0>] mwait_idle+0x0/0x20
[334129.061806]  [<c010245c>] cpu_idle+0x9c/0xe0
[334129.061817]  [<c0558a7f>] start_kernel+0x31f/0x3b0
[334129.061827]  [<c05581f0>] unknown_bootoption+0x0/0x260
[333259.148510]  =======================

Since I see the word "time" there : note I have NO_HZ, HIGH_RES_TIMERS,
TIMER_STATS and HPET (but according to /proc/timer_list, hpet is not active),
but no IRQ_BALANCE.
And for the boot options (?), /proc/cmdline is :
root=UUID=349f275c-a633-4d1d-8ab7-b3a75d67dc51 ro locale=fr_FR

lspci -vv, lspci -vn, /proc/config.gz, /proc/timer_list, lsmod,
/proc/interrupts, /proc/vmstat, ps auxf, and dmesg (with and 
without the bug's logs) outputs at
http://oshima.zouh.org/~ben/2.6.23-rc3_bug_details.txt

Thank you.
Benjamin Pineau


             reply	other threads:[~2007-06-04 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 13:55 Benjamin Pineau [this message]
2007-06-04 14:39 ` Björn Steinbrink
2007-06-04 14:41   ` Björn Steinbrink
2007-06-04 15:21     ` Boaz Harrosh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070604135514.GA14426@zouh.org \
    --to=benjamin_pineau@zouh.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®