On Wed, 9 Jan 2002 09:41:36 +0300
Oleg Drokin <[EMAIL PROTECTED]> 

> Uh, Oh!
> where are most of these patches from? What is their source?
> Can you reproduce your problem with 2.4.17 (or 2.4.18-pre2 if you prefer)
> without any additional patches, or with only patches from 
>ftp://ftp.namesys.com/pub/reiserfs-for-2.4/<kernelversion>.pending ?
> Unfortunatelly having so much patches, you have, applied makes things
> very heavy to debug, including the fact, I never heard of some of 
> these patches at all (e.g nesting_reiserfs-8, reiser-snapshot-fix,
> reiserfs-stable-2.4.16 (what is this? you should already have 2.4.16) etc).
>  

> > > BTW, have you tried to run reiserfsck on this partition? Does it reports  any 
>errors?
> > No, i run it without options.
> Ok, at least your on-disk data is good.
> 
> > > > EIP:    0010:[<c0187a65>]    Tainted: P 
> > > > What does you mean with 'You are running binary kernel modules?' ??
> > > I mean that you run some modules source for which is not available.
> > > E.g. nvidia drivers, or win4lin or similar stuff.
> > also no. The only binaries that i use are Firmware stuff for my active
> > ISDN controller. Its loaded up to the card. Thats all.
> Ok. Must be someone forgot to include apropriate LICENSE tag in one of the modules.
> 
> Looking forward to hear from you on reproducing your problem on kernel with only 
>official namesys patches.
> If it cannot be reproduced, then, you might want to apply all additional patches 
>one-by-one
> until problem arises again. This last patch will be the culprit, then.


Hello Oleg,

well with a virginally 2.4.17 kernel and also one with all pending patches it happens.
Attached is a dump log from a virgin 2.4.17. After some deliberations. I changed my 
RPMBUILD root(do you remember, dumps caused by rpm builds) to another  partition and...
it works. I wasn't sure witch resierprogs i had used to build the involved  partition. 
Installed were 3.x.0kpre13. Maybe i used 3.x.0kpre10-12 anyway i'm unsure.

Well after installed 3.x.0k final and remaking my partition. These dump never more
appered with my 2.4.16 till 2.4.17pending. 

Its happily for me but the chance to track down the trigger ist gone. Sorry.

till next dump

Camus Moire


Reply via email to