From: Martin Zwickel <martin.zwickel@technotrend.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.4.26: kernel BUG at checkpoint.c:587
Date: Fri, 8 Oct 2004 10:58:37 +0200 [thread overview]
Message-ID: <20041008105837.67442205@phoebee> (raw)
[-- Attachment #1: Type: text/plain, Size: 3277 bytes --]
Hi there!
I got this oops today after an uptime of many days.
On the machine runs a squid and the fs's are ext3.
It also exports some directories over nfs and has some
iptables rules.
Oct 8 10:08:18 router kernel: kernel BUG at checkpoint.c:587!
Oct 8 10:08:18 router kernel: invalid operand: 0000
Oct 8 10:08:18 router kernel: CPU: 0
Oct 8 10:08:18 router kernel: EIP: 0010:[<c015f934>] Not tainted
Oct 8 10:08:18 router kernel: EFLAGS: 00010286
Oct 8 10:08:18 router kernel: eax: 00000069 ebx: c2d9b9a0 ecx: cfb82000 edx: 00000000
Oct 8 10:08:18 router kernel: esi: cfe76800 edi: c2d9b9a0 ebp: cc2c0a60 esp: cfb83e20
Oct 8 10:08:18 router kernel: ds: 0018 es: 0018 ss: 0018
Oct 8 10:08:18 router kernel: Process kjournald (pid: 56, stackpage=cfb83000)
Oct 8 10:08:18 router kernel: Stack: c02aff60 c02b0161 c02aff41 0000024b c02b0144 cc2c0a60 c015f7e2 cfe76800
Oct 8 10:08:18 router kernel: c2d9b9a0 cc90cda0 cc2c0a60 c015f21b cc2c0a60 cc2c0a60 c015f772 cc2c0a60
Oct 8 10:08:18 router kernel: cfe76800 cfe76800 cfe76838 c2d9b7a0 00000001 c4d9b5a0 c4d9b5a0 c015dbb3
Oct 8 10:08:18 router kernel: Call Trace: [<c015f7e2>] [<c015f21b>] [<c015f772>] [<c015dbb3>] [<c0204059>]
Oct 8 10:08:18 router kernel: [<c0114f9d>] [<c01603f6>] [<c01602d0>] [<c0106e98>]
Oct 8 10:08:18 router kernel:
Oct 8 10:08:18 router kernel: Code: 0f 0b 4b 02 41 ff 2a c0 83 c4 14 90 83 7b 1c 00 74 2a 68 80
here the resolved syms:
>>EIP; c015f934 <__journal_drop_transaction+60/288> <=====
Trace; c015f7e2 <__journal_remove_checkpoint+52/6c>
Trace; c015f21b <__try_to_free_cp_buf+1b/3c>
Trace; c015f772 <__journal_clean_checkpoint_list+4e/6c>
Trace; c015dbb3 <journal_commit_transaction+1d3/f07>
Trace; c0204059 <ide_do_rw_disk+31/38>
Trace; c0114f9d <schedule+2d1/2f8>
Trace; c01603f6 <kjournald+116/1cc>
Trace; c01602d0 <commit_timeout+0/c>
Trace; c0106e98 <arch_kernel_thread+28/38>
Code; c015f934 <__journal_drop_transaction+60/288>
00000000 <_EIP>:
Code; c015f934 <__journal_drop_transaction+60/288> <=====
0: 0f 0b ud2a <=====
Code; c015f936 <__journal_drop_transaction+62/288>
2: 4b dec %ebx
Code; c015f937 <__journal_drop_transaction+63/288>
3: 02 41 ff add 0xffffffff(%ecx),%al
Code; c015f93a <__journal_drop_transaction+66/288>
6: 2a c0 sub %al,%al
Code; c015f93c <__journal_drop_transaction+68/288>
8: 83 c4 14 add $0x14,%esp
Code; c015f93f <__journal_drop_transaction+6b/288>
b: 90 nop
Code; c015f940 <__journal_drop_transaction+6c/288>
c: 83 7b 1c 00 cmpl $0x0,0x1c(%ebx)
Code; c015f944 <__journal_drop_transaction+70/288>
10: 74 2a je 3c <_EIP+0x3c>
Code; c015f946 <__journal_drop_transaction+72/288>
12: 68 80 00 00 00 push $0x80
After this oops squid hung in the kernel and was unkillable.
Also a reboot did not work. Had to manually reset the server.
Regards,
Martin
--
MyExcuse:
kernel panic: write-only-memory (/dev/wom0) capacity exceeded.
Martin Zwickel <martin.zwickel@technotrend.de>
Research & Development
TechnoTrend AG <http://www.technotrend.de>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-10-08 8:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041008105837.67442205@phoebee \
--to=martin.zwickel@technotrend.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.