NIlfs panic
Hi
Quoted 7 lines · Ryusuke Konishi
Hi,
Quoted 4 lines · Dave
Hi,
Was running a make, find and i paniced. I know this i'm running tanited due to nvidia closed binary, but it may be something worth looking at.
Quoted 7 lines
I've identified the function and instruction arising the fault.
Two questions:
- The kernel seems 2.6.28 not 2.6.30. Which version of nilfs2-modules did you applied? 2.0.14 ? or HEAD on nilfs2-modules.git ?
It's 2.0.14 and yes on 2.6.28 (haven't moved to 2.6.29 because of forcedeth network bug).
Quoted 1 line
- Is is reproducible?
I'll try again today.
Thanks
D
Quoted 17 lines · Dave
Hi
Quoted 6 lines · Ryusuke Konishi
Hi,
Quoted 4 lines · Dave
Hi,
Was running a make, find and i paniced. I know this i'm running tanited due to nvidia closed binary, but it may be something worth looking at.
Quoted 7 lines
I've identified the function and instruction arising the fault.
Two questions:
- The kernel seems 2.6.28 not 2.6.30. Which version of nilfs2-modules did you applied? 2.0.14 ? or HEAD on nilfs2-modules.git ?
Quoted 7 lines
It's 2.0.14 and yes on 2.6.28 (haven't moved to 2.6.29 because of forcedeth network bug).
Quoted 1 line
- Is is reproducible?
I'll try again today.
I've been unable to reproduce this so far and i've not lost any data in the original panic so i'll just have to wait see if it happens again in the future. At least we have the panic recorded in the mailing list for future.
Thanks
D
Hi Dave,
Quoted 23 lines · Dave
Quoted 22 lines · Dave
Hi
Quoted 6 lines · Ryusuke Konishi
Hi,
Quoted 4 lines · Dave
Hi,
Was running a make, find and i paniced. I know this i'm running tanited due to nvidia closed binary, but it may be something worth looking at.
Quoted 7 lines
I've identified the function and instruction arising the fault.
Two questions:
- The kernel seems 2.6.28 not 2.6.30. Which version of nilfs2-modules did you applied? 2.0.14 ? or HEAD on nilfs2-modules.git ?
It's 2.0.14 and yes on 2.6.28 (haven't moved to 2.6.29 because of forcedeth network bug).
Quoted 1 line
- Is is reproducible?
Quoted 7 lines
Quoted 2 lines
I'll try again today.
I've been unable to reproduce this so far and i've not lost any data in the original panic so i'll just have to wait see if it happens again in the future. At least we have the panic recorded in the mailing list for future.
Thank you. The repeatability itself is an important hint. Some kind of (rare) timing problem likely remains around delete or truncate path of regular files. If we can narrow down suspicious code path or conditions, I will try to review the path. Please send us report if you meet a successive problem.
Thanks,
Ryusuke Konishi