All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Heilwagen <andreas.heilwagen@jamba.net>
To: linux-kernel@vger.kernel.org
Cc: stefan.altenkamp@jamba.net
Subject: 2.5.66 kernel panic: fs/xfs/pagebuf/page_buf..c
Date: Wed, 21 May 2003 12:15:34 +0200	[thread overview]
Message-ID: <3ECB51C6.30309@jamba.net> (raw)

Hi,

I am in the unfortunate position to run a production server with 2.5.66 
since the SuperMicro CSE-742S-500 has no suitable APIC support in the 
2.4.x series. Why I do not run 2.5.69? The machine panics twice a day.

2.5.66 dies once a day with "kernel panic: Aiee, killing interrupt 
handler" in fs/xfs/pagebuf/page_buf.c:1287. The reason is an "invalid 
operand:0000 #5" on CPU:0 with "EIP:0060:[<c024f059>] Not tainted". In 
my case slapd from the OpenLDAP package caused the crash.

I have an 39320 Dual U320 SCSI controller in the machine with a Overland 
PowerLoader LTO-1 (17 slots) and a Infortrend IFT 6300-12 IDE-Raid with 
one 700G XFS volume configured.

Currently I am not able to backup the machine using Arkeia 5.1.7 without 
running one backup process on the local machine in a long-term disk 
sleep or getting a panic.

I'd like to get in touch with an person actively working on the XFS or 
APIC stuff to discuss how I can contribute to stabilize the APIC code 
for the Supermicro board and how to analyze/fix the XFS problem. I dot 
not want to file Bugzilla entries at this time before I cannot be sure 
that I missed an obvious solution.


Looking forward,

Andreas Heilwagen


                 reply	other threads:[~2003-05-21 10:02 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=3ECB51C6.30309@jamba.net \
    --to=andreas.heilwagen@jamba.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan.altenkamp@jamba.net \
    /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.