From: frode <frode@freenix.no>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, ext3-users@redhat.com
Subject: Re: OOPS: kernel BUG at transaction.c:1857 on 2.4.17 while rm'ing 700mb file on ext3 partition.
Date: Thu, 24 Jan 2002 23:53:27 +0100 [thread overview]
Message-ID: <3C509067.20108@freenix.no> (raw)
In-Reply-To: <3C502E3A.9070909@freenix.no> <20020124191927.A9564@redhat.com>
Stephen C. Tweedie wrote:
> On Thu, Jan 24, 2002 at 04:54:34PM +0100, frode wrote:
>>I got the following error while rm'ing a 700mb file from an ext3 partition:
>>Assertion failure in journal_unmap_buffer() at transaction.c:1857:
>>"transaction == journal->j_running_transaction"
> Hmm --- this is not one I think I've ever seen before.
[oops trace snipped]
>>NVRM: loading NVIDIA NVdriver Kernel Module 1.0.2313 Tue Nov 27 12:01:24 PST 2001
> with this driver loaded we really can't make any guarantees about your
> system stability at all. If you manage to eliminate other oopses and
> still get the ext3 one, even without the NVidia driver loaded, then
> there would be a much better change of debugging things, but right now
> it sounds like a hardware problem.
OK, I rebooted and gzip'ed the NVdriver in /lib/modules... to make sure the
module doesn't load (lsmod now says my kernel isn't tainted). I'll try using the
plain 'nv' driver shipped with XFree instead for a while. I tried making another
700mb iso image and fool around with it (loopback mount it, umount it, then rm
it) but couldn't trigger anything - but I just spent five minutes trying.
As I mentioned I have had quite a few oopses lately, most of them regarding
paging etc. (but I'm no kernel expert). See for example
http://marc.theaimsgroup.com/?l=linux-kernel&m=101096234600708&w=2
and
http://marc.theaimsgroup.com/?l=linux-kernel&m=101128528029736&w=2
I'm running linux on an old p100 as well but don't see any problems, so as you
say I suspected a hardware problem. I ran MemTest86 for about half an hour
without any errors (but of course there's plenty of other things that may be wrong).
Do you have any suggestions on other ways I could try to put my hardware
stability on trial, or try to reproduce the bug (to see if it occurs on a
non-tainted kernel)?
- Frode
next prev parent reply other threads:[~2002-01-24 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 15:54 OOPS: kernel BUG at transaction.c:1857 on 2.4.17 while rm'ing 700mb file on ext3 partition frode
2002-01-24 19:19 ` Stephen C. Tweedie
2002-01-24 22:53 ` frode [this message]
2002-01-29 14:11 ` Stephen C. Tweedie
2002-01-29 14:24 ` frode
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=3C509067.20108@freenix.no \
--to=frode@freenix.no \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/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