All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Madden <weez@freelists.org>
To: linux-kernel@vger.kernel.org
Subject: oopses on 2.2.19 under load, mylex raid
Date: Wed, 8 Aug 2001 22:38:07 -0500	[thread overview]
Message-ID: <0108082238077N.00173@weez> (raw)

I'm suspecting this to be a hardware issue, but I can't pin it down, and 
I'm hoping someone here might be able to help.  The system's a new 
built-from-scratch, so I guess the problem could be any of the components. 
 The system oopses *hard* under heavy load (make -j64 bzImage) pretty 
consistently.

Hardware: 512mb PC133, single pIII/800EB on a dual Tyan S2507, Mylex 170LP 
(DAC960) RAID controller on 4 18gig disks.  (Patched with Zubkoff's DAC960 
patch, version 2.2.10 for kernel 2.2.18)

I've swapped the RAM around and with some from a known-good system and I 
still get the crashes.  They're generally so hard that I can't scroll back 
to copy anything from the screen.  What I do get are lines like this one: 

[<c010f73c>] [<c012798e>] [c011c1cc>]...

repeating for at least a screen full, then:

Code: 39 73 74 75 2d c7 43 50 11 00 00 00 ff 83 dc 04 00 00 a1 b0

One oops that wasn't hard enough to take out the entire system looked like 
this: 

kmem_free: Bad obj addr (objp=dbad0220, name=vm_area_struct)
Unable to handle kernel NULL pointer dereference at virtual address 
00000000
current->tss.cr3=00101000, %%crs = 00101000
*pde = 00000000

Any ideas? 

Thanks,
  John


-- 
# John Madden  weez@freelists.org ICQ: 2EB9EA
# FreeLists, Free mailing lists for all: http://www.freelists.org
# UNIX Systems Engineer, Ivy Tech State College: http://www.ivy.tec.in.us
# Linux, Apache, Perl and C: All the best things in life are free!

                 reply	other threads:[~2001-08-09  3:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0108082238077N.00173@weez \
    --to=weez@freelists.org \
    --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 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.