From: "sean whalen" <swhalen@denature.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] further scheduling weirdness
Date: Thu, 20 Nov 2003 13:12:15 -0800 [thread overview]
Message-ID: <000201c3afaa$fed85f40$6801a8c0@nexxus> (raw)
Hi All --
Continuing yesterday's thread where 2.6.0-test9-um was bombing on a
schedule_timeout() or interruptible_sleep_on_wait() call due to a null
pointer dereference in sched.c, I decided to try 2.4.22-um and see what
calling schedule_timeout() would do. Again it crashes at sched.c:564, which
is a different place and has a different back trace. This time the back
trace is:
(gdb)
451 schedule();
(gdb)
Kernel panic: kernel BUG at sched.c:564!
In interrupt handler - not syncing
start_idle_thread (stack=0xa023e000, switch_buf_ptr=0xa023c578,
fork_buf_ptr=0x2) at process.c:281
281 if(n == 0)
(gdb) bt
#0 start_idle_thread (stack=0xa023e000, switch_buf_ptr=0xa023c578,
fork_buf_ptr=0x2) at process.c:281
#1 0xa00fd15b in start_uml_skas () at process_kern.c:167
#2 0xa00f7421 in linux_main (argc=0, argv=0xa0800000) at um_arch.c:382
#3 0xa000d3a6 in main (argc=8, argv=0xbffff824, envp=0xbffff848)
at arch/um/main.c:143
This is simply due to a schedule_timeout call in a module. Does anyone have
any ideas on this? It seems to critical a function to actually be broken.
Thanks,
-Sean
-
sean whalen . ucdavis security lab
swhalen at denature.org || node99.org
'if god had wanted us to evolve past the non sequitur,
he wouldn't have left all these fish in the tub.'
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2003-11-20 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 21:12 sean whalen [this message]
2003-11-21 2:22 ` [uml-devel] further scheduling weirdness Jeff Dike
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='000201c3afaa$fed85f40$6801a8c0@nexxus' \
--to=swhalen@denature.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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