http://bugzilla.kernel.org/show_bug.cgi?id=6180
------- Additional Comments From avuton@xxxxxxxxx 2006-03-14 00:17 -------
|Could you unmount and run xfs_repair please, and capture the output.
|(fsck is a no-op on XFS).
My apoligies, I actually already ran xfs_repair. Since I've had it crash since,
so I will run it again and send you info, within the next 24h.
|I spent some time last week on this, just didnt get a message out to
|you - my disassembly of the code around the point of your panic gave
|me no real clues - I think (not 100% sure though...) its an xfs_inode
|NULL pointer deref, but my disassemly didnt have instructions quite
|lining up with yours (probably different gcc versions). I'm taking a
|stab in the dark that you may have a corrupt inode nlink field ondisk
|for a particular inode, but thats just a guess at this stage based on
|the oops.
I was probably running gcc-4.0.2
|Can you try figure out more exactly when this started? (is there a
|kernel version you've reverted back to where it doesn't occur?). If
I'm sorry, I can't say where it started or ended, I believe after 2.6.15 until
now. Every time it happened I would try to upgrade git and recompile hopeing
not to see the issue again. I did that probably 3 or 4 times over 2 weeks.
|there is anything unusual in the xfs_repair output, pls add it here.
I'll post the full output.
|Also, is it always the xdm process (from yoour trace) that triggers
|this or does it vary?
It definitely varys. I've had it happen at different times.
|And are your stacktrace EIP always in xfs_read
|as in your hand-copied trace here?
I'm sorry, I only looked at the older traces long enough to see XFS being the
cause and I had to reboot to get more work done :/. The good news is it hasn't
happened in the last 5 days. I will get the xfs_repair output to you asap,
thanks for looking at this.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|