From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: linux-kernel@vger.kernel.org
Subject: Oops in schedule in 2.5.24
Date: Thu, 27 Jun 2002 23:11:29 +0200 [thread overview]
Message-ID: <95039BC6D12@vcnet.vc.cvut.cz> (raw)
Hi,
I decided to give 2.5.24 a try now when IDE94 and IDE95 were out.
So I applied IDE94/95 and built usual kernel (PIII, SMP) for my UP P4
host. And it died with
Unable to handle kernel NULL reference to 0x0000002A
Call trace: schedule + 491/1102
sys_sched_yield + 444/455
syscall
>From looking at the code, it looks like that queue->next (sched.c, line
866) was 0x00000002, so next happened to be 0xFFFFFFE2, and then it
died when context_switch() tried to access next->mm :-( No idea how 0x000002
happened to be in queue->next.
Another explanation is that rq->idle was 0xFFFFFFE2, and rq->nr_running
was 0. But it looks impossible too.
Does anybody have any idea what's wrong? Crash happened few minutes
after boot. For now I reverted back to 2.5.21-changeset1.493, which
works flawlessly.
Box is running slapd (which invoked yield()) and grabs TV teletext
using bttv. Network card driver is e100. There should be always one
process ready to run: dnetc.
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
reply other threads:[~2002-06-27 21:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=95039BC6D12@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--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