All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Kowalski <kowalski@datrix.co.za>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.4.3 Crash - (Kernel BUG at highmem.c:155)
Date: Tue, 10 Apr 2001 18:11:15 +0200	[thread overview]
Message-ID: <0104101811150C.25951@webman> (raw)

Hi All

This is quite a long email which I have split in two for those that are 
interested problem and background...

---Problem---

Kernel Panic Occured with Messages:
Kernel BUG at highmem.c:155
Invalid Operand ???? With sshd somewhere in the mix. 

Unfortunately I did a task dump with SYSRQ before I could get the rest of the 
info..  and syslogd had stopped logging to disk already. I then had to reboot.

Looking at line 155 :
/*
         * A count must never go down to zero
         * without a TLB flush!
         */
        switch (--pkmap_count[nr]) {
        case 0:
                BUG();
        case 1:
                wake_up(&pkmap_map_wait);
        }
        spin_unlock(&kmap_lock);

WHat went wrong???? to make the count go to zero??

---Background----

I am running Linux 2.4.3 on A HP netserver 2000r, it has 1.2gigs of RAM, at 
dual 933mhz Xeon (Piii actually, but paid for Xeons??) and a Netraid 4m SCSI 
Card with 6x 18.4gig HP Drives in a Raid 5 Configuration with No Hot Standby.
The Root FS is on a 9.2 GIG HP Scsi Drive. Both root and home are reiserfs 
(9.4 gig and 85gig respectively).
The kernel is patch with the axboe-scsi-patch and the latest aacraid patch. 
Running under SUse Linux 7.0 (new modutils).

THe server is running samba, httpd, sendmail, mrtg, named and a number of 
other porcesses but the loadaverage tends to stay below 1.0 mostly, although 
it exhibits erratic behaviour with load climbing to 3-5-6 with top showing no 
apparent candidate, with most of the time spent in SYStem calls. 
Occassional lockups lasting 5-20 seconds were experienced when working on the 
box under 2.4.2 but seem to be much better in 2.4.3.

Today the server tends to "eat up" shared+used memory over time eventually 
using +- 700mb of RAM with no process reflecting this in top.

Running SWAPoff today, when 64mb of swap was being used, resulted in complete 
machine lockup for about 30-40 seconds. 

I strongly suspect the aacraid drivers but need further proof to convince the 
powers that be to swap for a Mylex or something better supported....

Any advice/answers would be very welcome.

TIA
MARCin


-- 
-----------------------------
     Marcin Kowalski
     Linux/Perl Developer
     Datrix Solutions
     Cel. 082-400-7603
      ***Open Source Kicks Ass***
-----------------------------

             reply	other threads:[~2001-04-10 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10 16:11 Marcin Kowalski [this message]
2001-04-10 19:49 ` Kernel 2.4.3 Crash - (Kernel BUG at highmem.c:155) Jeff Lessem

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=0104101811150C.25951@webman \
    --to=kowalski@datrix.co.za \
    --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.