From: "louie miranda" <louie@chikka.com>
To: <linux-kernel@vger.kernel.org>, <redhat-list@redhat.com>
Subject: kernel: journal /ext3 problem. "Assertion failure"
Date: Thu, 27 Jun 2002 09:58:56 +0800 [thread overview]
Message-ID: <003b01c21d7e$32498900$6b48becb@noc2> (raw)
In-Reply-To: Pine.LNX.3.96.1020627032159.2332J-100000@pioneer
Jun 26 05:16:56 chsvr kernel: Assertion failure in
journal_commit_transaction() at commit.c:535: "buffer_jdirty(bh)"
Jun 26 05:16:56 chsvr kernel: ------------[ cut here ]------------
Jun 26 05:16:56 chsvr kernel: kernel BUG at commit.c:535!
Jun 26 05:16:56 chsvr kernel: invalid operand: 0000
Jun 26 05:16:56 chsvr kernel: iptable_filter ip_tables eepro100 usb-ohci
usbcore ext3 jbd aic7xxx sd_mod scs
Jun 26 05:16:56 chsvr kernel: CPU: 1
Jun 26 05:16:56 chsvr kernel: EIP: 0010:[<f88540e4>] Not tainted
Jun 26 05:16:56 chsvr kernel: EFLAGS: 00010286
Jun 26 05:16:56 chsvr kernel:
Jun 26 05:16:56 chsvr kernel: EIP is at journal_commit_transaction [jbd]
0xb04 (2.4.18-3smp)
Jun 26 05:16:56 chsvr kernel: eax: 0000001c ebx: 0000000a ecx: c02eee60
edx: 00003684
Jun 26 05:16:56 chsvr kernel: esi: f7376b80 edi: f7271f00 ebp: f75aa000
esp: f75abe78
Jun 26 05:16:56 chsvr kernel: ds: 0018 es: 0018 ss: 0018
Jun 26 05:16:56 chsvr kernel: Process kjournald (pid: 191,
stackpage=f75ab000)
Jun 26 05:16:56 chsvr kernel: Stack: f885aeee 00000217 f74d2eb8 00000000
00000fbc f1745044 00000000 f23a2460
Jun 26 05:16:56 chsvr kernel: f6558610 00001a64 00000001 f882ad2f
f74d2e00 00000008 f1905260 edec9560
Jun 26 05:16:56 chsvr kernel: edec95c0 edec9620 edec9680 edec96e0
edcbc9e0 edcbca40 edcbcaa0 edcbcb00
Jun 26 05:16:56 chsvr kernel: Call Trace: [<f885aeee>] .rodata.str1.1 [jbd]
0x26e
Jun 26 05:16:56 chsvr kernel: [<f882ad2f>] rw_intr [sd_mod] 0x20f
Jun 26 05:16:56 chsvr kernel: [<c0119048>] schedule [kernel] 0x348
Jun 26 05:16:56 chsvr kernel: [<f88567d6>] kjournald [jbd] 0x136
Jun 26 05:16:56 chsvr kernel: [<f8856680>] commit_timeout [jbd] 0x0
Jun 26 05:16:56 chsvr kernel: [<c0107286>] kernel_thread [kernel] 0x26
Jun 26 05:16:56 chsvr kernel: [<f88566a0>] kjournald [jbd] 0x0
Jun 26 05:16:56 chsvr kernel:
Jun 26 05:16:56 chsvr kernel:
Jun 26 05:16:56 chsvr kernel: Code: 0f 0b 5a 59 6a 04 8b 44 24 18 50 56 e8
4b f1 ff ff 8d 47 48
Hi, i've encountered this error yesterday.
The machine dont run anything big and its
not yet on production.
The machine hangs, and does not accept some
connections on some apps like ssh, etc.
I tried to reboot the machine, and after it works
fine again.
Im not sure where to send it, and not sure
if its redhat problem or the main kernel.
BTW: its redhat 7.3
Kernel 2.4.18-3smp
A default install so far.
Please advise,
louie...
next prev parent reply other threads:[~2002-06-27 1:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D1A2DC1.6040401@travellingkiwi.com>
2002-06-27 0:19 ` New Zaurus Wishlist - removable media handling David Golden
2002-06-27 1:40 ` Tomasz Rola
2002-06-27 1:58 ` louie miranda [this message]
2002-06-27 2:18 ` David D. Hagood
2002-06-27 8:11 ` Xavier Bestel
2002-06-27 11:29 ` David D. Hagood
2002-06-27 13:42 ` Tomasz Rola
2002-06-27 2:38 ` [Zaurus-general] " Larry Garfield
2002-06-27 17:26 ` Kent Sandvik
2002-06-27 17:36 ` Denis Vlasenko
2002-06-29 0:39 ` Horst von Brand
2002-06-27 2:11 kernel: journal /ext3 problem. "Assertion failure" Philip Wyett
2002-06-27 3:04 ` louie miranda
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='003b01c21d7e$32498900$6b48becb@noc2' \
--to=louie@chikka.com \
--cc=linux-kernel@vger.kernel.org \
--cc=redhat-list@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