From: florin@iucha.net (Florin Iucha)
To: Oleg Drokin <green@namesys.com>
Cc: Jens Axboe <axboe@suse.de>,
linux-kernel@vger.kernel.org, viro@math.psu.edu,
andre@linux-ide.org
Subject: Re: 2.5.34 BUG at kernel/sched.c:944 (partitions code related?)
Date: Sun, 15 Sep 2002 11:36:14 -0500 [thread overview]
Message-ID: <20020915163614.GA20293@iucha.net> (raw)
In-Reply-To: <20020910181153.B1095@namesys.com>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
On Tue, Sep 10, 2002 at 06:11:53PM +0400, Oleg Drokin wrote:
> Hello!
>
> On Tue, Sep 10, 2002 at 04:06:22PM +0200, Jens Axboe wrote:
>
> > > Now it does it in reverse like this:
> > > hdb: host protected area => 1
> > > hdb: 120103200 sectors (61493 MB) w/1916KiB Cache, CHS=119150/16/63
> > > hdb: hdb1
> > > hda: host protected area => 1
> > > hda: 120103200 sectors (61493 MB) w/1916KiB Cache, CHS=119150/16/63
> > > hda: hda1 hda2 hda3 hda4 < hda5PANIC
> > Kernel compiled with preempt support or not?
>
> No.
I am seeing the same message "kernel BUG at sched.c:944" on 2.5.34-curr
on my Toshiba laptop. It only appears when preempt is set. Without
preempt the problem does not occur. I do not have CONFIG_TOSHIBA set.
It appears before probing for IDE devices: I had to turn off the vga
framebuffer in order to see the traceback.
I cannot capture it on serial port since my laptop has none.
florin
--
"If it's not broken, let's fix it till it is."
41A9 2BDE 8E11 F1C5 87A6 03EE 34B3 E075 3B90 DFE4
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-09-15 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 13:56 2.5.34 BUG at kernel/sched.c:944 (partitions code related?) Oleg Drokin
2002-09-10 14:06 ` Jens Axboe
2002-09-10 14:11 ` Oleg Drokin
2002-09-10 14:24 ` Jens Axboe
2002-09-10 14:45 ` Oleg Drokin
2002-09-15 16:36 ` Florin Iucha [this message]
2002-09-10 17:19 ` Alexander Viro
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=20020915163614.GA20293@iucha.net \
--to=florin@iucha.net \
--cc=andre@linux-ide.org \
--cc=axboe@suse.de \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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