All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Robert Love <rml@tech9.net>, Thomas Molina <tmolina@cox.net>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.5 Problem Status Report
Date: Wed, 11 Sep 2002 11:28:08 +0400	[thread overview]
Message-ID: <20020911112808.A6341@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209110915140.5546-100000@localhost.localdomain>

Hello!

On Wed, Sep 11, 2002 at 09:26:40AM +0200, Ingo Molnar wrote:
> > > >    BUG at kernel/sched.c        open                  10 Sep 2002
> > > What exactly is this?
> > Looks like this is my bugreport for BUG in kernel/sched.c:944 in the middle
> > of partition parsing output on boot.
> > Subject of email was
> > '2.5.34 BUG at kernel/sched.c:944 (partitions code related?)'
> > msgid: 20020910175639.A830@namesys.com
> very strange backtrace:
>  >>EIP; c0115818 <schedule+18/4a0>   <=====
>  Trace; c01053a0 <default_idle+0/40>

I noticed it too.

> i've once seen the 2.5 IDE code doing a schedule_timeout() from an IRQ
> handler, but the above has to be something else. Could you hack sched.c to
> print out the exact preemption count? It could be a preempt-count
> underflow due to an unbalanced spin_unlock, or an inbalanced
> preempt_enable. [or the IRQ code - but i doubt that, we'd have seen

I have preemption disabled.

> problems much earlier if this was the case.]

> Oleg, do you have CONFIG_DEBUG_SPINLOCK enabled? That should catch an
> unbalanced spin_unlock().

Yes, I do.
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SLAB=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_HIGHMEM=y

Bye,
    Oleg

  reply	other threads:[~2002-09-11  7:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11  2:00 2.5 Problem Status Report Thomas Molina
2002-09-11  2:29 ` William Lee Irwin III
2002-09-11 18:33   ` Thomas Molina
2002-09-11 20:23     ` William Lee Irwin III
2002-09-11  4:00 ` Robert Love
2002-09-11  7:07   ` Oleg Drokin
2002-09-11  7:26     ` Ingo Molnar
2002-09-11  7:28       ` Oleg Drokin [this message]
2002-09-11  7:38         ` Ingo Molnar
2002-09-11  8:05           ` Oleg Drokin
2002-09-11 10:25             ` Jens Axboe
2002-09-11 10:29               ` Jens Axboe
2002-09-11 10:47                 ` Oleg Drokin
2002-09-11 10:58                   ` Jens Axboe
2002-09-11 11:07                     ` Jens Axboe
2002-09-11 11:16                     ` Oleg Drokin
2002-09-11 11:17                       ` Jens Axboe
2002-09-11 11:49                         ` Jens Axboe
2002-09-11 12:10                           ` Oleg Drokin
2002-09-11 15:38                             ` Oleg Drokin
2002-09-11 15:46                               ` Ingo Molnar
2002-09-11 15:52                                 ` Ingo Molnar
2002-09-11 17:49                                 ` Oleg Drokin
2002-09-11  8:07     ` Thomas Molina
2002-09-11  8:12       ` Oleg Drokin
2002-09-11  9:18       ` Adrian Bunk
2002-09-11  7:12   ` Ingo Molnar
2002-09-11  8:04 ` Axel Siebenwirth
2002-09-11  9:21 ` Clemens Schwaighofer
  -- strict thread matches above, loose matches on Subject: below --
2002-08-25 11:21 Thomas Molina
2002-08-26 16:42 ` Greg KH
2002-08-26 21:32   ` Thomas Molina
2002-08-02  2:39 2.5 Problem Status report Thomas Molina

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=20020911112808.A6341@namesys.com \
    --to=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rml@tech9.net \
    --cc=tmolina@cox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.