LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Robert Scussel <listuser@omniti.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel OOPS
Date: Fri, 18 Jul 2003 15:44:06 -0400 [thread overview]
Message-ID: <3F184E06.5070200@omniti.com> (raw)
Background Information:
We are currently writing about 1MB per second of data, and creating
and deleting about 600+ inodes per second. The following OOPS shows
that the problem occurs in the 2.4.20-18.7smp kernel. Tracing the code,
it appears that if inode_has_buffers(inode) returns true then the BUG is
thrown.
We are running with ext3 fs, and my guess would be that the problem
exists in one of the following situations:
The process grows, to the point where it is using more memory, and it
tickles something in the virtual memory which corrupts the
inode->i_dirty_buffers list so that the i_dirty_buffers are in fact not
empty. ( This is a conjecture based on the fact that the ext3
journaling doesn't store the i_dirty_buffers info with the inode itself ).
The other possibility is that such a high I/O rate is somehow
corrupting the journaling, causeing the same type of issue.
Any hints/suggestions/input would be appreciated.
Thanks
------------[ cut here ]------------
kernel BUG at inode.c:126!
invalid operand: 0000
e1000 ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables
usb-ohci usbcore ext3 jbd aacraid sd_mod scsi_mod
CPU: 0
EIP: 0010:[<c015b840>] Not tainted
EFLAGS: 00010202
EIP is at destroy_inode [kernel] 0x10 (2.4.20-18.7smp)
eax: 00000001 ebx: d913ab80 ecx: 00000001 edx: d913ab80
esi: d913ab80 edi: f8859b00 ebp: dd330a80 esp: c4667ef8
ds: 0018 es: 0018 ss: 0018
Process ecelerity (pid: 17532, stackpage=c4667000)
Stack: d913ab80 c015d0f5 d913ab80 ffffffff e41d2980 dd330b00 c024a7cc
dd330a80
d913ab80 e41d2980 c015aec6 d913ab80 dd330b00 c4666000 fffffff0
e41d2980
c4666000 00000000 c01530f0 dd330a80 00000000 d6706780 c4667f9c
e41d2980
Call Trace: [<c015d0f5>] iput [kernel] 0x275 (0xc4667efc))
[<c015aec6>] d_delete [kernel] 0x66 (0xc4667f20))
[<c01530f0>] vfs_unlink [kernel] 0x1e0 (0xc4667f40))
[<c0150b80>] cached_lookup [kernel] 0x10 (0xc4667f58))
[<c0151c3a>] lookup_hash [kernel] 0x4a (0xc4667f68))
[<c01531b9>] sys_unlink [kernel] 0x89 (0xc4667f88))
[<c0108be3>] system_call [kernel] 0x33 (0xc4667fc0))
Code: 0f 0b 7e 00 ba 95 25 c0 8b 83 9c 00 00 00 8b 40 20 8b 40 04
next reply other threads:[~2003-07-18 19:17 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 19:44 Robert Scussel [this message]
2003-07-18 21:31 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2008-07-23 12:52 kernel oops Andrei Popa
2008-07-23 17:11 ` Vegard Nossum
2008-08-18 16:33 ` Vegard Nossum
2008-08-18 16:39 ` Greg KH
[not found] <e8eb01770803120245x7690e6a9te8ad04296aa3fc4d@mail.gmail.com>
2008-03-12 9:49 ` Zbynek Drlik
2008-03-12 10:33 ` Al Viro
2008-03-12 13:12 ` Zbynek Drlik
2008-02-05 12:57 Andrej Hocevar
2008-02-06 17:55 ` Len Brown
2006-09-12 10:21 Kernel Oops Marcin Prączko
2006-09-13 3:43 ` Andrew Morton
2005-10-15 1:03 Marc Perkel
2005-10-15 1:21 ` Randy.Dunlap
2005-10-15 1:43 ` Marc Perkel
2005-10-15 1:52 ` Randy.Dunlap
2005-01-03 21:10 Kernel oops Marat BN
2005-01-05 10:13 ` Andrew Morton
2004-06-11 7:27 tmp
2004-05-24 20:19 tmp
2004-05-16 12:08 Kernel OOPS tmp
2004-05-16 23:27 ` Andrew Morton
2004-05-17 0:33 ` tmp
2004-03-09 22:13 Kernel oops Philipp Baer
2004-03-09 23:11 ` Andrew Morton
2004-03-12 7:46 ` Philipp Baer
2004-02-08 11:05 Kernel Oops Mathieu LESNIAK
2004-02-08 16:35 ` Greg KH
2004-02-09 7:06 ` Mathieu LESNIAK
2003-11-28 23:15 Kernel oops Ville Jutvik
2003-11-28 5:45 Anderson Levi
2003-08-09 12:39 kernel oops Jean-Yves LENHOF
2003-08-09 20:37 ` Jean-Yves LENHOF
2003-08-09 9:28 Jean-Yves LENHOF
2003-07-07 12:53 Anders Karlsson
2003-07-07 13:14 ` Alan Cox
2003-07-07 13:32 ` Anders Karlsson
2003-07-07 13:37 ` Alan Cox
2003-07-07 13:56 ` Anders Karlsson
2003-07-08 9:39 ` Marcelo Tosatti
[not found] ` <200307072009.50677.bernd-schubert@web.de>
2003-07-08 5:13 ` Anders Karlsson
2003-05-31 1:32 Nadeem Riaz
2003-03-26 15:52 Steve Terrell
2003-02-03 1:18 Kernel Oops Daniel Espinoza
2003-02-03 3:23 ` vishwas
2002-08-09 5:25 sanket rathi
2002-06-23 19:39 Dirk Schmidt
2002-06-10 8:46 kernel oops Robert Litwiniec
2002-02-26 18:26 Suporte RedeBonja
2002-02-27 13:35 ` Erik Mouw
2001-11-13 13:23 Kernel oops Anthony
2001-11-14 6:02 ` Thiago Rondon
2001-10-08 12:59 kernel oops Terry Kendal
2001-09-27 9:49 kewl
2001-06-01 15:13 Kernel oops David Harris
2001-06-01 15:12 David Harris
2001-04-19 18:32 kernel oops Ronald Bultje
2001-04-19 19:04 ` Alan Cox
2001-04-19 19:08 ` Ronald Bultje
2001-02-19 14:44 Kernel Oops Alberto Bertogli
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=3F184E06.5070200@omniti.com \
--to=listuser@omniti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rscuss@omniti.com \
--subject='Re: Kernel OOPS' \
/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
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).