Date: Thu, 25 Nov 2004 21:28:33 -0800
From: Pete Zaitcev <zaitcev@redhat.com>
To: sct@redhat.com
Cc: zaitcev@redhat.com, linux-kernel@vger.kernel.org, jgarzik@redhat.com
Subject: 2.4.28-bk3 ext3 oopses at boot
Message-ID: <20041125212833.0ff3af4f@lembas.zaitcev.lan>
Organization: Red Hat, Inc.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1490
Lines: 55

Hi, Guys:

I keep getting pretty random oopses at boot which point at either ext3 or
the SATA. This is a Dell PE750 which Matt sent me, BTW. So, it's SATA-only
and I had to use Jeff's patches to get ____request_resource. This, I suppose
makes this suspect, but if the box passes the boot, everything is peachy.
No filesystem corruption of any kind.

Failures are generally random, and they look like this (transcribed by hand):

VA NULL (0x0c)
EIP: write_one_revoke_record
journal_commit_transaction
scrup
vgacon_cursto
clear_selection
poke_blanked_console
vt_console_print
schedule
__call_console_drivers
release_console_sem
kjournald

VA 0x89e389d5
EIP: find_revoke_record
journal_cancel_revoke
do_get_write_access
journal_alloc_journal_head
ext3_mark_inode_dirty
journal_get_write_access
ext3_add_entry
start_this_handle
new_handle
ext3_add_nondir
ext3_mknod
vfs_mknod
unix_bind
sys_bind
dput
sys_socketcall

The EIP is always in something related to jbd.

A self-built 2.4.21-20.EL works dandy, so this ought to rule out the
a toolchain problem (it's RHEL3 with gcc-3.2). There was a small bunch
of changes in jbd and ext3 since then, but nothing in revoke.c.

I dunno if this report has any value, but thought I'd add a data point.

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/