From: Jake Maciejewski <maciejej@msoe.edu>
To: "Łukasz Mierzwa" <prymitive@pcserwis.net>
Cc: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: reiser4 oops
Date: Sun, 02 Jul 2006 22:24:37 -0600 [thread overview]
Message-ID: <1151900677.10172.22.camel@gentoo> (raw)
In-Reply-To: <op.tb00v9njd4os1z@localhost>
I'm seeing this on 2.6.16.20 with the -4 patch, amd64 with preempt. The
OOM killer was called even though I have 1GB RAM and 4GB swap. My logs
are available at:
http://people.msoe.edu/~maciejej/patches/AMD64_reiser4_debug/20060702/oom.txt.gz
Both affected filesystems (rsync was using one filesystem, cc1 the
other) came up clean with fsck.
On Sat, 2006-07-01 at 22:08 +0200, £ukasz Mierzwa wrote:
> I'm running x86 gentoo system with / on reiser4, I'm using
> suspend-sources-2.6.16-r8 kernel with 2.6.16-4 patch. Today I run emerge
> --sync, after that I started to compile new xine-lib while browsing net,
> when xine-lib was finishing I got this errors:
>
> kernel BUG at fs/inode.c:253!
> invalid opcode: 0000 [#1]
> PREEMPT
> Modules linked in: ndiswrapper fglrx acer_acpi nsc_ircc irda crc_ccitt
> snd_atiixp snd_ac97_codec snd_ac97_bus yenta_socket rsrc_nonstatic
> pcmcia_core tifm_7xx1 tifm_core
> CPU: 0
> EIP: 0060:[<c017bc56>] Tainted: P VLI
> EFLAGS: 00010206 (2.6.16-suspend2-r8 #2)
> EIP is at clear_inode+0x16/0xb0
> eax: 00000003 ebx: d5245d20 ecx: 00000000 edx: d5245df8
> esi: df2099c0 edi: c2a3a000 ebp: c2a3a000 esp: c2a3be94
> ds: 007b es: 007b ss: 0068
> Process emerge (pid: 9123, threadinfo=c2a3a000 task=c2a0ba70)
> Stack: <0>df2099c0 d5245d20 df2099c0 c01db519 c017a385 00000000 00000400
> d5245e28
> d5245d20 c2a3a000 d415c114 d5245d20 c01db4e0 c017bd59 d5245d20
> dfe9b000
> c017b81c d415c114 c017a431 00000000 dfe9b000 df533000
> c2a3bf50 c0172d74
> Call Trace:
> [<c01db519>] reiser4_delete_inode+0x39/0xc0
> [<c017a385>] dput+0x25/0x170
> [<c01db4e0>] reiser4_delete_inode+0x0/0xc0
> [<c017bd59>] generic_delete_inode+0x69/0x100
> [<c017b81c>] iput+0x5c/0x70
> [<c017a431>] dput+0xd1/0x170
> [<c0172d74>] sys_renameat+0x1c4/0x1f0
> [<c0172dc7>] sys_rename+0x27/0x30
> [<c0102ef3>] sysenter_past_esp+0x54/0x75
> Code: 80 98 00 00 00 8b 40 38 eb c4 8d 74 26 00 8d
> bc 27 00 00 00 00 56 53 89 c3 83 ec 04 e8 14 b0 fe ff 8b 83 c4 00 00 00 85
> c0 74 08 <0f> 0b fd 00 ab d4 37 c0 8b 83 20 01 00 00 a8 10 75 08 0f 0b ff
> <4>reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
> reiser4[emerge(9123)]: release_unix_file
> (fs/reiser4/plugin/file/file.c:2294)[vs-44]:
> WARNING: out of memory?
>
> I rebooted, remounted / read only and run fsck --fix, I had to run fsck
> --build-fs becouse of fatal corruptions, I got whole lot of errors
> referring to /usr/portage dir but fs is now ok.
--
Jake Maciejewski <maciejej@msoe.edu>
next prev parent reply other threads:[~2006-07-03 4:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 20:08 reiser4 oops Łukasz Mierzwa
2006-07-01 20:13 ` Łukasz Mierzwa
2006-07-03 4:24 ` Jake Maciejewski [this message]
[not found] ` <1151921448.6335.42.camel@tribesman.namesys.com>
2006-07-03 11:51 ` Łukasz Mierzwa
2006-07-03 23:23 ` Jake Maciejewski
2006-07-07 7:18 ` Jake Maciejewski
[not found] ` <1152278167.6236.21.camel@tribesman.namesys.com>
2006-07-11 6:43 ` Jake Maciejewski
-- strict thread matches above, loose matches on Subject: below --
2009-07-02 8:34 Reiser4 oops Piotr Sawuk
2010-12-19 19:01 Reiser4 Oops Андрей Колченко
2010-12-19 22:33 ` Edward Shishkin
2010-12-20 22:31 ` Edward Shishkin
[not found] ` <AANLkTinbSRgNhi5heC2npLNzU4xsuUjzEXBD5qDBiYDw@mail.gmail.com>
2011-01-05 12:10 ` Edward Shishkin
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=1151900677.10172.22.camel@gentoo \
--to=maciejej@msoe.edu \
--cc=prymitive@pcserwis.net \
--cc=reiserfs-list@namesys.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 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.