mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Lukasz Trabinski <lukasz@wsisiz.edu.pl>
Cc: akpm@zip.com.au, Andreas Dilger <adilger@clusterfs.com>,
	linux-kernel@vger.kernel.org,
	Bartlomiej Solarz-Niesluchowski <solarz@wsisiz.edu.pl>
Subject: Re: 2.4.21-pre3 - problems with ext3 (long)
Date: 21 Jan 2003 13:56:26 +0000	[thread overview]
Message-ID: <1043157386.2447.56.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.51.0301210029010.30053@oceanic.wsisiz.edu.pl>

Hi,

On Tue, 2003-01-21 at 00:25, Lukasz Trabinski wrote:

> system boot  2.4.20:
> Dec 15 15:27:01 oceanic kernel: Assertion failure in journal_start_Rsmp_c2be780a
> () at transaction.c:248: "handle->h_transaction->t_journal == journal

> With earlier kernels 2.4.X (for example 2.4.20-rc2) this machine has much 
> longer uptime.

OK, which was the last one which ran stable for you?  I note that you've
got a failure marked "2.4.20" in the log.

> Dec 15 15:27:01 oceanic kernel: Kernel panic: EXT3-fs panic (device sd(8,23)): load_block_bitmap: block_group >= groups_count - block_group = 524287, groups_count = 2126

Do you have the backtrace for that?  I can't see any way that particular
error can happen unless the kernel's memory is getting corrupt, or
there's a corrupt superblock coming in from the disk.  

Also, are you sure you've been ksymoops'ing these from the right
System.map files?  The traces really don't make a lot of sense.

Finally,

> By the way, last crash was with messages:
> Jan 19 11:50:20 oceanic kernel: kernel BUG at highmem.c:159!
> Jan 19 11:50:20 oceanic kernel: invalid operand: 0000
> Jan 19 11:50:20 oceanic kernel: CPU:    1

If that happens again, serial console is the best way of getting the
full oops.  How much memory does your system have?  Have you ever seen
this error before?  

Cheers,
 Stephen


  reply	other threads:[~2003-01-21 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14 13:15 2.4.21-pre3 - problems with ext3 Lukasz Trabinski
2003-01-14 15:15 ` Stephen C. Tweedie
2003-01-14 15:48   ` Lukasz Trabinski
2003-01-20 22:38 ` Stephen C. Tweedie
2003-01-21  0:25   ` 2.4.21-pre3 - problems with ext3 (long) Lukasz Trabinski
2003-01-21 13:56     ` Stephen C. Tweedie [this message]
2003-01-21 14:22       ` Bartlomiej Solarz-Niesluchowski
2003-01-21 14:38         ` Stephen C. Tweedie
2003-01-21 14:54           ` Bartlomiej Solarz-Niesluchowski
2003-02-06 15:47           ` Bartlomiej Solarz-Niesluchowski

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=1043157386.2447.56.camel@sisko.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=adilger@clusterfs.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz@wsisiz.edu.pl \
    --cc=solarz@wsisiz.edu.pl \
    /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

all inboxes | Powered by JetHome®