linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Bob_Tracy <rct@gherkin.sa.wlk.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
	Arjan van de Ven <arjanv@redhat.com>,
	Thibaut Laurent <thibaut@celestix.com>,
	linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!
Date: Fri, 06 Jul 2001 13:42:46 +1000	[thread overview]
Message-ID: <3B4533B6.7E67A0D1@uow.edu.au> (raw)
In-Reply-To: <20010705181544.Y17051@athlon.random> "from Andrea Arcangeli at Jul 5, 2001 06:15:44 pm" <m15IHnE-0005khC@gherkin.sa.wlk.com>

Bob_Tracy wrote:
> 
> Andrea Arcangeli quoted:
> > On Thu, Jul 05, 2001 at 11:46:33AM -0400, Arjan van de Ven wrote:
> > > On Thu, Jul 05, 2001 at 11:32:00PM +0800, Thibaut Laurent wrote:
> > > > And the winner is... Andrea. Kudos to you, I've just applied these patches,
> > > > recompiled and it seems to work fine.
> > > > Too bad, this was the perfect excuse for getting rid of those good old Cyrix
> > > > boxen ;)
> > >
> > > As Andrea's patches don't actually fix anything Cyrix related it's obvious
> > > that they just avoid the real bug instead of fixing it.
> > > It's a very useful datapoint though.
> 
> Put me in the "it works for me" camp also.  Do we have the definitive answer
> as far as what is/was broken?   Thanks, Andrea...

The Cyrix setup code in arch/i386/kernel/setup.c is unconditionally
enabling interrupts when it shouldn't.  This allows timer interrupts
to start running before the softirq system has been set up.  A
subsequent softirq_init() mucks up the softirq data structures and
we hit the BUG().

The setup code needs to not reenable interrupts, and softirq_init()
should be called prior to time_init().  Both these changes are in
2.4.7-pre3.

-

  reply	other threads:[~2001-07-06  3:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-04 21:28 PROBLEM: [2.4.6] kernel BUG at softirq.c:206! Manfred H. Winter
2001-07-05  7:46 ` Mircea Damian
2001-07-05 11:18   ` Alan Cox
2001-07-05 12:10     ` Bob_Tracy
2001-07-05 13:04     ` Mircea Damian
2001-07-05 14:15     ` Manfred H. Winter
2001-07-05 10:52 ` Thibaut Laurent
2001-07-05 13:00   ` Mircea Damian
2001-07-05 11:04 ` Manfred H. Winter
2001-07-05 14:20 ` Andrea Arcangeli
2001-07-05 14:30   ` Alan Cox
2001-07-05 14:36   ` Arjan van de Ven
2001-07-05 14:40     ` Andrea Arcangeli
2001-07-05 15:32     ` Thibaut Laurent
2001-07-05 15:46       ` Arjan van de Ven
2001-07-05 15:56         ` Andrew Morton
2001-07-05 16:04           ` Alan Cox
2001-07-05 16:11             ` Andrew Morton
2001-07-05 16:15         ` Andrea Arcangeli
2001-07-05 22:40           ` Bob_Tracy
2001-07-06  3:42             ` Andrew Morton [this message]
2001-07-06 10:58         ` Manfred H. Winter
2001-07-06 12:43       ` Andrea Arcangeli
2001-07-06 14:18       ` Thibaut Laurent
2001-07-06 15:02         ` Andrea Arcangeli
2001-07-05 15:19   ` Manfred H. Winter
2001-07-05 12:14 Bob_Tracy
2001-07-05 13:42 ` Alan Cox
2001-07-05 14:02   ` Bob_Tracy
     [not found] <E15I8gj-0002W7-00@the-village.bc.nu>
2001-07-05 13:59 ` Bob_Tracy
     [not found] <3B4450DF.82EEC851@uow.edu.au>
2001-07-05 14:28 ` Manfred H. Winter
2001-07-05 15:23   ` Andrew Morton
2001-07-05 17:31     ` Manfred H. Winter

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=3B4533B6.7E67A0D1@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=andrea@suse.de \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rct@gherkin.sa.wlk.com \
    --cc=thibaut@celestix.com \
    /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;
as well as URLs for NNTP newsgroup(s).