All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mircea Damian <dmircea@kappa.ro>
To: Thibaut Laurent <thibaut@celestix.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:00:27 +0300	[thread overview]
Message-ID: <20010705160027.A14170@linux.kappa.ro> (raw)
In-Reply-To: <20010704232816.B590@marvin.mahowi.de> <20010705104650.A2820@linux.kappa.ro> <20010705185243.2e3a942e.thibaut@celestix.com>
In-Reply-To: <20010705185243.2e3a942e.thibaut@celestix.com>; from thibaut@celestix.com on Thu, Jul 05, 2001 at 06:52:43PM +0800

On Thu, Jul 05, 2001 at 06:52:43PM +0800, Thibaut Laurent wrote:
> Hi,
> 
> I posted a message 2 weeks ago regarding this bug, though I can't trigger the
> kernel panic every time (see original post). My CPU is a MediaGX, and
> Manfred's one is a 6x86MX. What about yours ?
> After my first unsuccessful attempt with a 2.4.6-pre3, I tried several other
> 2.4.6-preX and 2.4.5-acX kernels. All 2.4.6 (since pre1) seem to be
> affected, and so do the latest ac's. I don't have tested 2.4.7-pre[12] yet,
> but looking at the changelog, I doubt the fix is in.

My CPU is:

root@cyrix:~# cat /proc/cpuinfo 
processor       : 0
vendor_id       : CyrixInstead
cpu family      : 6
model           : 2
model name      : 6x86MX 2.5x Core/Bus Clock
stepping        : 7
cpu MHz         : 166.452
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : yes
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu de tsc msr cx8 pge cmov mmx cyrix_arr
bogomips        : 331.77



-- 
Mircea Damian
E-mails: dmircea@kappa.ro, dmircea@roedu.net
WebPage: http://taz.mania.k.ro/~dmircea/

  reply	other threads:[~2001-07-05 12:59 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 10:52   ` Thibaut Laurent
2001-07-05 13:00     ` Mircea Damian [this message]
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 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
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
  -- strict thread matches above, loose matches on Subject: below --
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=20010705160027.A14170@linux.kappa.ro \
    --to=dmircea@kappa.ro \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.