From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Albert Chin-A-Young <china@thewrittenword.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel BUG at inode.c:1204! in 2.2.26
Date: Thu, 29 Apr 2004 12:12:16 -0300 [thread overview]
Message-ID: <20040429151216.GB19181@logos.cnet> (raw)
In-Reply-To: <20040429144623.GA52886@mail1.thewrittenword.com>
On Thu, Apr 29, 2004 at 09:46:23AM -0500, Albert Chin-A-Young wrote:
> On Thu, Apr 29, 2004 at 11:33:51AM -0300, Marcelo Tosatti wrote:
> >
> > I believe this mibht be caused by the VMWare modules you are using.
> >
> > Mind trying to reproduce it without external modules?
>
> Sure. I'll reboot tonight without the modules. BTW, why do you think
> this?
Because I've never seen such report on mainline.
But actually this might be related to some fixes in the VFS.
In the meantine, run without the vmware modules please.
> > On Wed, Apr 28, 2004 at 11:14:20PM -0500, Albert Chin-A-Young wrote:
> > > Upgraded to 2.2.26 on April 26 and received the following on April 27:
> > >
> > > kernel: kernel BUG at inode.c:1204!
> > > kernel: invalid operand: 0000
> > > kernel: CPU: 0
> > > kernel: EIP: 0010:[iput+608/624] Tainted: PF
> > > kernel: EFLAGS: 00010246
> > > kernel: eax: 00000000 ebx: de603980 ecx: de603990 edx: de603990
> > > kernel: esi: f7e6bc00 edi: 00000000 ebp: 00007a61 esp: f7e71efc
> > > kernel: ds: 0018 es: 0018 ss: 0018
> > > kernel: Process kswapd (pid: 4, stackpage=f7e71000)
> > > kernel: Stack: 00000292 de605880 00000292 de605918 de605900 de603980 c0148a4d de603980
> > > kernel: de605880 00000017 c1886114 c0260e38 000063ad c0148da4 00009446 c012d336
> > > kernel: 00000006 000001d0 ffffffff 000001d0 00000017 00000020 000001d0 c0260e38
> > > kernel: Call Trace: [prune_dcache+221/336] [shrink_dcache_memory+36/64] [shrink_cache+358/896] [shrink_caches+61/96] [try_to_free_pages_zone+98/240]
> > > kernel: [kswapd_balance_pgdat+102/176] [kswapd_balance+40/64] [kswapd+152/192] [kswapd+0/192] [rest_init+0/64] [arch_kernel_thread+46/64]
> > > kernel: [kswapd+0/192]
> > > kernel:
> > > kernel: Code: 0f 0b b4 04 86 4b 23 c0 e9 c3 fd ff ff 8d 76 00 8b 54 24 04
> > >
> > > I did not encounter an OOPS. I saw this and then rebooted.
prev parent reply other threads:[~2004-04-29 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 4:14 Albert Chin-A-Young
2004-04-29 14:33 ` Marcelo Tosatti
2004-04-29 14:46 ` Albert Chin-A-Young
2004-04-29 15:12 ` Marcelo Tosatti [this message]
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=20040429151216.GB19181@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=china@thewrittenword.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®