From: Alexander Zarochentsev <zam@namesys.com>
To: reiserfs-list@namesys.com
Cc: Alexey Polyakov <alexey.polyakov@gmail.com>
Subject: Re: Kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:80
Date: Tue, 16 May 2006 08:25:30 +0400 [thread overview]
Message-ID: <200605160825.30995.zam@namesys.com> (raw)
In-Reply-To: <b5d90b2a0605151227n77a48810rce8fb2b3638b4bd5@mail.gmail.com>
Hi
On Monday 15 May 2006 23:27, Alexey Polyakov wrote:
> Hi!
>
> Did it reach the list?
yes.
> I'm a bit worried cause I'm stuck at 2.6.15 and I really want to
> upgrade to .16. :)
can you fsck the partition?
>
> Thanks.
>
> On 5/12/06, Alexey Polyakov <alexey.polyakov@gmail.com> wrote:
> > Hi,
> >
> > after running for a couple hours, kernel reports a different bug.
> > Then again processes get stuck in D state, and only hard reset
> > helps.
> >
> > Here's this new error message:
> >
> > May 11 07:19:22 titanic kernel: <4>reiser4[httpd(11176)]:
> > plugin_by_unsafe_id (fs/reiser4/plugin/plugin.c:296)[nikita-2913]:
> > May 11 07:19:22 titanic kernel: WARNING: Invalid plugin id: [2:235]
> > May 11 07:19:22 titanic kernel: Unable to handle kernel NULL
> > pointer dereference at 0000000000000004 RIP:
> > May 11 07:19:22 titanic kernel:
> > <ffffffff80229461>{obtain_item_plugin+17} May 11 07:19:22 titanic
> > kernel: PGD 37d86067 PUD e1ba8067 PMD 0 May 11 07:19:22 titanic
> > kernel: Oops: 0000 [1] SMP
> > May 11 07:19:22 titanic kernel: CPU 3
> > May 11 07:19:22 titanic kernel: Modules linked in:
> > May 11 07:19:22 titanic kernel: Pid: 11176, comm: httpd Not tainted
> > 2.6.16-cks9 #2
> > May 11 07:19:22 titanic kernel: RIP: 0010:[<ffffffff80229461>]
> > <ffffffff80229461>{obtain_item_plugin+17}
> > May 11 07:19:22 titanic kernel: RSP: 0018:ffff8100edd39b48 EFLAGS:
> > 00010292 May 11 07:19:22 titanic kernel: RAX: 0000000000000000 RBX:
> > ffff81016df732d0 RCX: ffffffff80406c68
> > May 11 07:19:22 titanic kernel: RDX: 0000000000000000 RSI:
> > 0000000000000292 RDI: ffffffff80406c60
> > May 11 07:19:22 titanic kernel: RBP: ffff81016df732d0 R08:
> > 0000000000000003 R09: 0000000000000001
> > May 11 07:19:22 titanic kernel: R10: 0000000000000000 R11:
> > ffffffff80118cd0 R12: ffff81013e91f000
> > May 11 07:19:22 titanic kernel: R13: ffffffff80419000 R14:
> > ffff81013e91f4f0 R15: 0000000000000000
> > May 11 07:19:22 titanic kernel: FS: 00002ab7a85cc8e0(0000)
> > GS:ffff8101045370c0(0000) knlGS:0000000000000000
> > May 11 07:19:22 titanic kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
> > 000000008005003b
> > May 11 07:19:22 titanic kernel: CR2: 0000000000000004 CR3:
> > 00000000d9e67000 CR4: 00000000000006e0
> > May 11 07:19:22 titanic kernel: Process httpd (pid: 11176,
> > threadinfo ffff8100edd38000, task ffff810037d3f100)
> > May 11 07:19:23 titanic kernel: Stack: ffff81016df732d0
> > ffffffff801f14d1 ffff81016df732d0 ffffffff801f17ad
> > May 11 07:19:23 titanic kernel: 0000000000000001
> > ffffffff801ed372 ffff8100edd39b70 ffffffff00000001
> > May 11 07:19:23 titanic kernel: 0000000000000000
> > 0000000000000000 May 11 07:19:23 titanic kernel: Call Trace:
> > <ffffffff801f14d1>{coord_num_units+17}
> > <ffffffff801f17ad>{coord_init_after_item_end+13}
> > May 11 07:19:23 titanic kernel:
> > <ffffffff801ed372>{carry_insert_flow+1106}
> > <ffffffff801eb9ab>{carry+267}
> > May 11 07:19:23 titanic kernel:
> > <ffffffff801eac05>{post_carry+85}
> > <ffffffff801ef267>{insert_flow+263} May 11 07:19:23 titanic kernel:
> > <ffffffff80221de5>{write_tail+245}
> > <ffffffff801e8e35>{jload_gfp+437} May 11 07:19:23 titanic kernel:
> > <ffffffff80211bbe>{extent2tail+942}
> > <ffffffff8020fd40>{release_unix_file+192}
> > May 11 07:19:23 titanic kernel:
> > <ffffffff80179d02>{__fput+194} <ffffffff80162a01>{remove_vma+65}
> > May 11 07:19:23 titanic kernel:
> > <ffffffff8016417e>{do_munmap+670} <ffffffff801649e2>{sys_munmap+82}
> > May 11 07:19:23 titanic kernel:
> > <ffffffff8010aaf6>{system_call+126} May 11 07:19:23 titanic kernel:
> > May 11 07:19:23 titanic kernel: Code: 0f be 40 04 88 43 0c 5b c3 66
> > 66 90 66 66 90 53 0f b6 47 0c
> > May 11 07:19:23 titanic kernel: RIP
> > <ffffffff80229461>{obtain_item_plugin+17} RSP <ffff8100edd39b48>
> > May 11 07:19:23 titanic kernel: CR2: 0000000000000004
> >
> > On 5/11/06, Alexander Zarochentsev <zam@namesys.com> wrote:
> > > Hello.
> > >
> > > please apply the attached patch.
> >
> > --
> > Alexey Polyakov
--
Alex.
prev parent reply other threads:[~2006-05-16 4:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 21:19 Kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:80 Alexey Polyakov
2006-05-11 12:23 ` Alexander Zarochentsev
2006-05-11 20:19 ` Alexey Polyakov
2006-05-15 19:27 ` Alexey Polyakov
2006-05-16 4:25 ` Alexander Zarochentsev [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=200605160825.30995.zam@namesys.com \
--to=zam@namesys.com \
--cc=alexey.polyakov@gmail.com \
--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.