Le 13.07.2006 16:16, Vladimir V. Saveliev a écrit : > Hello > > On Wed, 2006-07-12 at 21:50 +0200, Laurent Riffard wrote: >> Hello reiser4 maintainers, >> >> I've been hit a few times by a reiser4 panic, namely nikita-1936. >> >> The box was running 2.6.18-rc1-mm1 + hot-fixes + >> reiser4-generic_file_read-fix.patch (from Edward Shishkin). >> .config is attached. >> >> What should I do ? >> - fsck ? > > You should fsck from time to time. I do not think that this panic > indicates any corruptions in a filesystem, though.
Yes, you're right. I fsck'd this FS, but there were no corruptions. >> - send a debugfs.reiser4 -P output before fsck ? > > no > >> - comment out this assertion ? > > no > >> - wait for a fix ? >> > > can you reproduce the problem? How to do that, if yes? > can you please try to find whether previous kernel you used can also be > crashed that way? What is that kernel? This FS is my working area for compiling kernels. Reiser4 panicked twice yesterday during a compilation. But today, all proceeded correctly. I think - not sure - 2.6.18-rc1-mm1 is the first kernel with those problems. I was hit by many other (unrelated to reiser 4) problems in 2.6.18-mm* and maybe one of those panic happened, but I can't remember. The problem is, if I start X and if such a panic happens, the box is frozen and I can't see any message. I have to work with a character terminal (not a graphical one) to see the panic's output message. -- laurent
