From: Simon <sur3@gmx.de>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: ReiserFS Development List <reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 for Linux-2.6.36
Date: Tue, 30 Nov 2010 17:00:47 +0100 [thread overview]
Message-ID: <4CF51FAF.4040904@gmx.de> (raw)
In-Reply-To: <4CF4E224.2040203@gmail.com>
> Are you sure that you have reiser4-for-2.6.36
> stuff applied? The problem has gone for me...
Yep, looked it up in my zsh-history, so i'm sure:
% patch -p1 < ../reiser4-for-2.6.36.patch
> Could you send kernel messages?
I wish i could, but as it seemes the messages from the crash aint saved,
probably because the kernel does crash completely and so not sync anymore.
Anyway i found some messages hours before the crash, probably the bug
depends on them or they have nothing to do with it, but they mention
ext3 and sda7, this is funny, as ext3 is my root-partition on sda1, and
sda7 is my home-partition with reiser4:
Nov 29 20:49:40 localhost kernel: [61364.033613] Pid: 1856, comm:
ent:sda7! Tainted: P 2.6.36-gentoo-r1 #1
Nov 29 20:49:40 localhost kernel: [61364.033617] Call Trace:
Nov 29 20:49:40 localhost kernel: [61364.033627] [<ffffffff81167775>] ?
ext3_write_inode+0x45/0x50
Nov 29 20:49:40 localhost kernel: [61364.033633] [<ffffffff810dfbf4>] ?
writeback_single_inode+0x214/0x2a0
Nov 29 20:49:40 localhost kernel: [61364.033637] [<ffffffff810e0005>] ?
generic_writeback_sb_inodes+0xe5/0x170
Nov 29 20:49:40 localhost kernel: [61364.033640] [<ffffffff810e09c0>] ?
writeback_inodes_wb+0x140/0x190
Nov 29 20:49:40 localhost kernel: [61364.033644] [<ffffffff8113b432>] ?
entd_flush+0xa2/0xe0
Nov 29 20:49:40 localhost kernel: [61364.033647] [<ffffffff8113b59d>] ?
entd+0x12d/0x280
Nov 29 20:49:40 localhost kernel: [61364.033652] [<ffffffff810561d0>] ?
autoremove_wake_function+0x0/0x30
Nov 29 20:49:40 localhost kernel: [61364.033655] [<ffffffff8113b470>] ?
entd+0x0/0x280
Nov 29 20:49:40 localhost kernel: [61364.033658] [<ffffffff8113b470>] ?
entd+0x0/0x280
Nov 29 20:49:40 localhost kernel: [61364.033661] [<ffffffff81055d56>] ?
kthread+0x96/0xa0
Nov 29 20:49:40 localhost kernel: [61364.033665] [<ffffffff81003154>] ?
kernel_thread_helper+0x4/0x10
Nov 29 20:49:40 localhost kernel: [61364.033668] [<ffffffff81055cc0>] ?
kthread+0x0/0xa0
Nov 29 20:49:40 localhost kernel: [61364.033671] [<ffffffff81003150>] ?
kernel_thread_helper+0x0/0x10
next prev parent reply other threads:[~2010-11-30 16:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 1:31 Reiser4 for Linux-2.6.36 Edward Shishkin
2010-11-21 11:17 ` Matt
2010-11-21 15:39 ` dimas
[not found] ` <4CE93CEB.8050504@ya.ru>
2010-11-21 18:08 ` Edward Shishkin
2010-11-21 20:58 ` Юрий Заикин
2010-11-22 2:47 ` Edward Shishkin
2010-11-22 3:54 ` Edward Shishkin
2010-12-05 18:33 ` Юрий Заикин
2010-11-30 10:09 ` Simon
2010-11-30 11:38 ` Edward Shishkin
2010-11-30 16:00 ` Simon [this message]
2011-01-10 15:01 ` Simon
2011-01-10 15:28 ` Edward Shishkin
2011-01-10 17:14 ` Simon
2010-12-19 9:43 ` Serkan Kaba
2010-12-19 16:05 ` Edward Shishkin
2010-12-19 16:15 ` Serkan Kaba
2010-12-20 17:47 ` Serkan Kaba
2010-12-20 18:07 ` 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=4CF51FAF.4040904@gmx.de \
--to=sur3@gmx.de \
--cc=edward.shishkin@gmail.com \
--cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).