I've hit the same panic looping kernel builds (while true ; do make
mrproper ; make allmodconfig ; make -j4 ; done) on 2.6.21.1 with the
Namesys patch and reiser4 debug enabled. I've seen it on my amd64
desktop and x86 laptop.
Another one I've seen is:
reiser4 panicked cowardly: reiser4[fixdep(16043)]: sibling_list_remove (fs/reiser4/tree_walk.c:814)[zam-32245]
In both cases the fsck didn't find anything, as you observed.
On Wed, 2007-07-11 at 06:46 +0200, Ingo Bormuth wrote:
> Hmm, whenever I try to build busybox (1.4.2) I get nikita-191 panics:
>
> [...]
> cc console_tools/clear.o
> reiser4 panicked cowardly: reiser4[cc1(13066)]: save_file_hint (fs/reiser4/plugin/file.c:705) [nikity-1991]:
> kernel panic - not syncing: reiser4[cc1(13066)]: save_file_hint (fs/reiser4/plugin/file.c:705) [nikity-1991]:
>
> Running fsck.reiser4 before and after the panic doesn't show any complaints.
> The partition is heavily used. I'm not aware of any other problem.
>
> Vanilla-2.6.21.6 (kernel.org) with reiser4-2.6.21-path (namesys.com).
>
> Not that I understood the code, but why is it an assertion at all?
> Couldn't one just use an empty hint if the current one is invalid?
>
--
Jake Maciejewski <maciejej@xxxxxxxx>
-
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
