linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Clewett <B.Clewett@roadrunner.uk.com>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: Kernel Panic
Date: Mon, 07 Apr 2003 14:43:16 +0100	[thread overview]
Message-ID: <3E918074.1080102@roadrunner.uk.com> (raw)
In-Reply-To: <3E8F7C30.21091.31D33A@localhost>

Dear Linux Admin,

On Linux 2.4 I have had three Kernel Panics recently.

They include the following: journal.o "( ret != 0 )".  I see in the 
source code that there is an assertion: J_ASSERT(ret != 0) in the function:

unsigned long journal_bmap(journal_t *journal, unsigned long blocknr)

Which looks like a possible place for the origin of this.

There is also a large amount of Hex data, which I do not have, unless 
logged somewhere on my system unknown to me.  (I don't get many Panics, 
not sure where panic data is logged...)

On reboot I loose files.  Although nothing serious yet.

The system is a POP3 server, handling about 1,000 email files and about 
10,000 email's a day, so there is constantly great disk load by sendmail 
and the default redhat POP3.

Should I upgrade my kernel, or may I be doing something specific to 
cause this?

Thanks with any help,

Ben Clewett.


  parent reply	other threads:[~2003-04-07 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06  7:00 Recomended IDE-RAID MB Andrew B. Cramer
2003-04-06 14:38 ` Christian Reis
2003-04-06 19:25   ` Andrew B. Cramer
2003-04-06 22:12     ` Matt McKenzie
2003-04-06 23:45       ` Andrew B. Cramer
2003-04-07 13:43 ` Ben Clewett [this message]
2003-04-07 13:48   ` Kernel Panic Jamie Harris
2003-04-07 14:22     ` Ben Clewett
  -- strict thread matches above, loose matches on Subject: below --
2003-04-07 14:48 Jamie Harris

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=3E918074.1080102@roadrunner.uk.com \
    --to=b.clewett@roadrunner.uk.com \
    --cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).