From: "yuval yeret" <yuval_yeret@hotmail.com>
To: linux-kernel@vger.kernel.org
Cc: yuval@exanet.com
Subject: 2.4.18-24 SMP Machine stuck in zombie state after kernel Oops in devfs_d_iput
Date: Sun, 13 Jul 2003 12:12:42 +0300 [thread overview]
Message-ID: <BAY2-F10090EVrQQehr00006765@hotmail.com> (raw)
Hi,
Tried to find information about a kernel OOPS I've seen twice already on two
different machines - but nothing seems to be said about this in the list
archives or anywhere else for that matter (except someone saw this a while
ago on a 2.5.X kernel -
http://groups.google.com/groups?q=devfs_d_iput&hl=en&lr=lang_en|lang_iw&ie=UTF-8&oe=UTF-8&safe=off&selm=20030424211014%242fa9%40gated-at.bofh.it&rnum=1
)
We are running 2.4.18-24 and doing heavy IO to disk and networking. (Qlogic
HBAs and Intel e1000 NICs are used)
At some point the machine oopses (no scenario except heavy nfs-server like
load):
Jul 9 09:49:02 node0 kernel: devfs_d_iput(generic): de: f5a99600 dentry:
f558f500 de->dentry: f558f900
Jul 9 09:49:02 node0 kernel: Forcing Oops
Jul 9 09:49:02 node0 kernel: ------------[ cut here ]------------
Jul 9 09:49:02 node0 kernel: kernel BUG at base.c:2852!
Jul 9 09:49:02 node0 kernel: invalid operand: 0000
Jul 9 09:49:02 node0 kernel: CPU: 0
Jul 9 09:49:02 node0 kernel: EIP: 0010:[devfs_d_iput+63/112] Not
tainted
Jul 9 09:49:02 node0 kernel: EIP: 0010:[<c0186dcf>] Not tainted
Jul 9 09:49:02 node0 kernel: EFLAGS: 00010286
Jul 9 09:49:02 node0 kernel:
Jul 9 09:49:02 node0 kernel: EIP is at (2.4.18-24exa)
Jul 9 09:49:02 node0 kernel: eax: 0000000d ebx: f5a99600 ecx: 00000001
edx: f5c8c000
Jul 9 09:49:02 node0 kernel: esi: f558f500 edi: f1250180 ebp: 00000055
esp: c992df3c
Jul 9 09:49:02 node0 kernel: ds: 0018 es: 0018 ss: 0018
Jul 9 09:49:02 node0 kernel: Process kswapd (pid: 12, stackpage=c992d000)
Jul 9 09:49:02 node0 kernel: Stack: c02be2c5 c02c7f60 c02be45b f5a99649
f5a99600 f558f500 f558f900 f558f518
Jul 9 09:49:02 node0 kernel: f558f500 f1250180 c01562c0 f558f500
f1250180 c0303f50 000f4240 00000000
Jul 9 09:49:02 node0 kernel: 00000000 c0302f20 00000216 00000151
00000000 000001d0 00000000 00000000
Jul 9 09:49:02 node0 kernel: Call Trace: [prune_dcache+208/432]
(0xc992df64))
Jul 9 09:49:02 node0 kernel: Call Trace: [<c01562c0>] (0xc992df64))
Jul 9 09:49:02 node0 kernel: [shrink_dcache_memory+32/48] (0xc992dfa0))
Jul 9 09:49:02 node0 kernel: [<c01566f0>] (0xc992dfa0))
Jul 9 09:49:02 node0 kernel: [do_try_to_free_pages+28/416] (0xc992dfa8))
Jul 9 09:49:02 node0 kernel: [<c013961c>] (0xc992dfa8))
Jul 9 09:49:02 node0 kernel: [kswapd+321/896] (0xc992dfd4))
Jul 9 09:49:02 node0 kernel: [<c0139971>] (0xc992dfd4))
Jul 9 09:49:02 node0 kernel: [_stext+0/80] (0xc992dfe8))
Jul 9 09:49:02 node0 kernel: [<c0105000>] (0xc992dfe8))
Jul 9 09:49:02 node0 kernel: [kernel_thread+38/48] (0xc992dff0))
Jul 9 09:49:02 node0 kernel: [<c01072d6>] (0xc992dff0))
Jul 9 09:49:02 node0 kernel: [kswapd+0/896] (0xc992dff8))
Jul 9 09:49:02 node0 kernel: [<c0139830>] (0xc992dff8))
After the oops networking stack continues to function, some running daemons
continue to work (I'm seeing network traffic from the machine which
indicates that clearly), but login into the node is not possible via
console, ssh, rsh, and the majority of the application processes are dead.
Any information / pointers will be appreciated.
Thanks,
--
Yuval Yeret
Exanet
yuval@exanet.com
http://www.exanet.com
Tel. 972-9-9717782
Fax. 972-9-9717778
_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
next reply other threads:[~2003-07-13 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 9:12 yuval yeret [this message]
2003-07-13 9:27 ` 2.4.18-24 SMP Machine stuck in zombie state after kernel Oops in devfs_d_iput Christoph Hellwig
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=BAY2-F10090EVrQQehr00006765@hotmail.com \
--to=yuval_yeret@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yuval@exanet.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;
as well as URLs for NNTP newsgroup(s).