All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Van Maren, Kevin" <kevin.vanmaren@unisys.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Kernel BUG report
Date: Fri, 03 Aug 2001 14:54:59 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005999@msgid-missing> (raw)

I hit this running mkfs on a 8GB, 4X Lion running 4 mkfs processes,
each on an 8-disk "md", with 8 disks on each of 4 Adaptec scsi channels
[each md has 2 disks on each controller], with the boot disk on a separate
adaptec controller; ql12160 unused.

Running the latest 2.4.7 IA64 patches, plus SGI's kernel profiling patches
and the latest 6.20 adaptec driver from Justin Gibbs
(people.freebsd.org/~gibbs/linux).

I had previously run that test with a couple "sync"s running in other
vt logins and it ran (*very* slowly, hence the profiling).

  Kernel BUG at page_alloc.c: 75!
  Unable to handle kernel paging request at virtual address 0000000000000000
  mkfs.ext2[1582]: Oops 11003706212352

This is in __free_pages_ok:
	if (page->mapping)
=>		BUG();

Unfortunatly I didn't write down more info before the machine was rebooted;
looks like I'll have to set up a serial console.


I've also been getting a LOT (100's, not 10's) of these:
  Warning - running *really* short on DMA buffers
which appear to be coming from the SCSI subsystem.


Update: I ran the "test" again, and I got a bunch more "short on DMA
buffers"
messages, and then I got a bunch of lines like:
  Segment 0xe000000228eb7840, blocks 2, addr 0x228eb13ff
followed by:
  Kernel panic:  Ththththaats all folks.  Too dangerous to continue.


Kevin


             reply	other threads:[~2001-08-03 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-03 14:54 Van Maren, Kevin [this message]
2001-08-06 12:30 ` [Linux-ia64] Kernel BUG report Martin Wilck

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=marc-linux-ia64-105590693005999@msgid-missing \
    --to=kevin.vanmaren@unisys.com \
    --cc=linux-ia64@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.