From: Andrea Arcangeli <andrea@suse.de>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: [2.4.6] kernel BUG at softirq.c:206!
Date: Thu, 5 Jul 2001 16:40:46 +0200 [thread overview]
Message-ID: <20010705164046.S17051@athlon.random> (raw)
In-Reply-To: <20010704232816.B590@marvin.mahowi.de> <20010705162035.Q17051@athlon.random> <3B447B6D.C83E5FB9@redhat.com>
In-Reply-To: <3B447B6D.C83E5FB9@redhat.com>; from arjanv@redhat.com on Thu, Jul 05, 2001 at 03:36:29PM +0100
On Thu, Jul 05, 2001 at 03:36:29PM +0100, Arjan van de Ven wrote:
> Andrea Arcangeli wrote:
> >
> > On Wed, Jul 04, 2001 at 11:28:17PM +0200, Manfred H. Winter wrote:
> > > Hi!
> > >
> > > I tried to install kernel 2.4.6 with same configuration as 2.4.5, but
> > > booting failed with:
> > >
> > > kernel BUG at softirq.c:206!
> >
> > do you have any problem with those patches applied?
> >
> > ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.6pre5aa1/00_ksoftirqd-7
> > ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.6pre5aa1/00_softirq-fixes-4
> >
>
> Is there anything in here that fixes a Via/Cyrix specific bug ?
definitely not. The softirq.c:206 bug cannot be caused by any hardware
bug, unless the bug triggers memory corruption exactly in the
tasklet->state word (which sounds unlikely since different people
triggered the bug using different binary kernels that are unlikely to
allocate t->state exactly in the same place).
Andrea
next prev parent reply other threads:[~2001-07-05 14:41 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 [this message]
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
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=20010705164046.S17051@athlon.random \
--to=andrea@suse.de \
--cc=arjanv@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).