From: Adam Kropelin <akropel1@rochester.rr.com>
To: linux-kernel@vger.kernel.org
Subject: 2.5.28: "bad: schedule() with irqs disabled!"
Date: Thu, 25 Jul 2002 23:19:14 -0400 [thread overview]
Message-ID: <20020726031914.GA32749@www.kroptech.com> (raw)
With 2.5.28 compiled for SMP+preempt (and running on 2 CPU SMP box) I get...
bad: schedule() with irqs disabled!
...followed by a backtrace early in the boot process. Without preempt this
notice does not appear. Below is a decoded version followed by the original
with several lines of context in case that is of use.
--Adam
ksymoops 2.4.1 on i686 2.5.28. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.5.28/ (default)
-m /boot/System.map-2.5.28 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
Warning (compare_maps): ksyms_base symbol GPLONLY___wake_up_sync not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol GPLONLY_idle_cpu not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol GPLONLY_set_cpus_allowed not found in System.map. Ignoring ksyms_base entry
c9fd1f84 c0288240 c0346436 c0313900 c0119844 00000000 00000001 00000000
c02dd7fe c028723d 00000001 00000000 00000000 00000000 00000000 c02dfac5
00000bd1 c02d8000 00000286 c02c0724 c02d9f94 c01154ec 00000000 c02d8000
Call Trace: [<c0119844>] [<c01154ec>] [<c0115505>] [<c0119850>]
Warning (Oops_read): Code line not seen, dumping what data is available
Trace; c0119844 <printk+144/180>
Trace; c01154ec <__wake_up+2c/50>
Trace; c0115505 <__wake_up+45/50>
Trace; c0119850 <printk+150/180>
6 warnings issued. Results may not be reliable.
CPU0: Intel 00/01 stepping 09
per-CPU timeslice cutoff: 730.16 usecs.
task migration cache decay timeout: 1 msecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000004
ESR value after enabling vector: 00000000
Booting processor 1/1 eip 2000
Initializing CPU#1
bad: schedule() with irqs disabled!
c9fd1f84 c0288240 c0346436 c0313900 c0119844 00000000 00000001 00000000
c02dd7fe c028723d 00000001 00000000 00000000 00000000 00000000 c02dfac5
00000bd1 c02d8000 00000286 c02c0724 c02d9f94 c01154ec 00000000 c02d8000
Call Trace: [<c0119844>] [<c01154ec>] [<c0115505>] [<c0119850>]
masked ExtINT on CPU#1
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Calibrating delay loop... 397.31 BogoMIPS
CPU: Before vendor init, caps: 0000fbff 00000000 00000000, vendor = 0
CPU: L1 I cache: 8K, L1 D cache: 8K
CPU: L2 cache: 256K
CPU: After vendor init, caps: 0000fbff 00000000 00000000 00000000
Intel machine check reporting enabled on CPU#1.
CPU: After generic, caps: 0000fbff 00000000 00000000 00000000
CPU: Common caps: 0000fbff 00000000 00000000 00000000
CPU1: Intel 00/01 stepping 09
Total of 2 processors activated (787.45 BogoMIPS).
next reply other threads:[~2002-07-26 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 3:19 Adam Kropelin [this message]
2002-07-26 3:34 ` Adam Kropelin
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=20020726031914.GA32749@www.kroptech.com \
--to=akropel1@rochester.rr.com \
--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®