mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Straight <junfan@penguinfarm.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.0test10 crash (RAID+SMP)
Date: Mon, 6 Nov 2000 06:51:24 -0500	[thread overview]
Message-ID: <00110606512400.07791@jeetkunedo.penguinfarm.com> (raw)
In-Reply-To: <3A05CC59.7B0566C7@netidea.com>
In-Reply-To: <3A05CC59.7B0566C7@netidea.com>

It may be a filesystem problem, I had a problem like this with a 200GB raid 0 
array using reiserfs, it went down 3 times in 2 days. I switched to ext2 on 
md0 and everything has been fine now for weeks.




On Sunday 05 November 2000 16:08, ryan wrote:

> > Hi,
>
> I tried 2.4.0test10, but I get a kernel oops quite often.  I have
> configured my kernel for raid and smp ... autodetected raid, in the
> kernel everything, so no raid modules necessary.  But when I go to boot,
> it starts to reconstruct the raid array and fsck the /dev/md0 and
> eventually it just crashes on me.  Kernel oops. A message like:
>
> "Detected LOCKUP on CPU0"
> or sometimes its CPU1...
>
> If I dont use raid its cool, if I remove smp its also cool.  So the
> particular combination of raid+smp seems to be the problem.
>
> My hardware is :
> Asus P2B-D, 2 PII-400
> 128 mb ram in 2 * 64 dimms (pc100)
> Matrox G400 singlehead.
> Enqsonique ENS1371
> Realtek 8029 Ethernet card (ne2k-pci )
>
>
> I have included my config that causes this problem.
>
> Incidently mga DRI doesnt work either in either SMP or non-SMP
> kernels... it just locks up the console, the system is still running.
> maybe I'm missing something?
>
> My software resembes Debian woody,
> gcc --version:
> 2.95.2
>
>
> Hope this helps.
>
> -ryan
> (PS: my raid array is from a 2.2.16 patched with the latest raid patches
> for that kernel... debian raidtools2 uses this patch, so its the "latest
> one".  I'm not sure how relevant this is)

----------------------------------------
Content-Type: text/plain; charset="us-ascii"; name="ryan.config"
Content-Transfer-Encoding: 7bit
Content-Description: 
----------------------------------------

-- 
Jason Straight - NMO.net Senior Network Tech
Penguinfarm.com - Personal Page
http://www.penguinfarm.com/
ICQ 1796276
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-06 11:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-05 21:08 ryan
2000-11-06  0:04 ` Keith Owens
2000-11-06  1:39   ` ryan
2000-11-06  3:12     ` Neil Brown
2000-11-06  0:09       ` ryan
2000-11-06  9:00       ` Jeff Garzik
2000-11-06  9:40         ` Andre Hedrick
2000-11-06 22:19         ` Neil Brown
2000-11-06 11:51 ` Jason Straight [this message]
2000-11-07  0:02 Ion Badulescu

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=00110606512400.07791@jeetkunedo.penguinfarm.com \
    --to=junfan@penguinfarm.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

all inboxes | Powered by JetHome®