mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christian Borntraeger" <CBORNTRA@de.ibm.com>
To: ext3-users@redhat.com, linux-kernel@vger.kernel.org
Cc: "Carsten Otte" <COTTE@de.ibm.com>
Subject: BUG: Assertion failure with ext3-0.95 for 2.4.7
Date: Wed, 8 Aug 2001 10:46:41 +0200	[thread overview]
Message-ID: <OF5E574EE5.AF3B6F6F-ONC1256AA2.0026D8D3@de.ibm.com> (raw)


Hello ext3-users,


I tested ext3 on a Linux for S/390 with several stress and benchmark test
tests and faced a kernel bug message.
The console showed the following output:

Message from syslogd@boeaet34 at Fri Aug  3 11:34:16 2001 ...
boeaet34 kernel: Assertion failure in journal_forget() at
transaction.c:1184: "!
jh->b_committed_data"

I tried the Patch from http://www.zip.com.au/~akpm/ext3-2.4-0.9.5-247.gz
with the kernel 2.4.7 with a new LVM- patch(0.9.1)  and some S/390 specific
patches. I use mke2fs version 1.22.
S/390 is a 32bit big endian machine. After compiling and running the kernel
I created an ext3-file system on an 70GB LVM. When running the postmark
test I get (reproduceable) the message from above. dmesg shows:

kernel BUG at transaction.c:1184!
illegal operation: 0001
CPU:    1
Process bench (pid: 2453, stackpage=08CEF000)

Kernel PSW:    07080000 8007f458         =journal_forget
task: 08cee000 ksp: 08cefaa8 pt_regs: 08cefa10
Kernel GPRS:
00000000  8001c118  00000022  00000001
8007f456  00c27000  00194f9a  00000001
030d2c80  074ed294  00001899  092ca350
0001f94c  8007f2c8  8007f456  08cefaa8
Kernel ACRS:
00000000  00000000  00000000  00000000
00000001  00000000  00000000  00000000
00000000  00000000  00000000  00000000
00000000  00000000  00000000  00000000
Kernel BackChain  CallChain
       08cefaa8   [<0007f456>]                =journal_forget
       08cefb10   [<000744c6>]                =ext3_forget
       08cefb70   [<000767b4>]                =ext3_clear_blocks
       08cefbd8   [<000768d4>]                =ext3_free_data
       08cefc50   [<00076c38>]                =ext3_truncate
       08cefd08   [<00074732>]                =ext3_delete_inode
       08cefd68   [<0006659a>]                =iput
       08cefdc8   [<00063dfc>]                =d_delete

I resolved the functions using the system.map file.

Has anyone saw this message before? Any ideas, clues, hints?

Please CC me , because I am not on the list.


--
Mit freundlichen Grüßen / Best Regards

Christian Bornträger
IBM Deutschland Entwicklung GmbH
eServer SW  System Evaluation + Test
email: CBORNTRA@de.ibm.com
Tel +49 7031-16-3507



             reply	other threads:[~2001-08-08  8:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08  8:46 Christian Borntraeger [this message]
2001-08-08  9:26 ` Arjan van de Ven
2001-08-08 15:16 ` Tom Rini
2001-08-09 18:58 ` Andrew Morton
2001-08-10 17:44   ` Tom Rini
2001-08-10 18:09     ` Andrew Morton
2001-08-10 18:10       ` Tom Rini
2001-08-08  9:36 Christian Borntraeger
2001-08-08 14:38 Christian Borntraeger
2001-08-08 15:27 ` Tom Rini
2001-08-09  9:26 Christian Borntraeger
2001-08-13  6:53 Christian Borntraeger
2001-08-14  8:34 Christian Borntraeger

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=OF5E574EE5.AF3B6F6F-ONC1256AA2.0026D8D3@de.ibm.com \
    --to=cborntra@de.ibm.com \
    --cc=COTTE@de.ibm.com \
    --cc=ext3-users@redhat.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®