On Mon, 2000-09-04 08:57:09 +1100, Keith Owens wrote:
> klogd has got in first and stamped on the trace, got it wrong
> and left no useful trace data for ksymoops. Can you change
> klogd to run as "klogd -x" and reproduce the problem? -x stops
> klogd attempting to translate the oops log, I change it in
> /etc/rc.d/init.d/syslog then /etc/rc.d/init.d/syslog restart.
All right, while hunting another oops, I reproduced the
vnode-crash situation. Attached is the oops (copied by hand)
processed by ksymoops. Keith, your tip with "klogd -x" didn't
help---it simply dies in case of an oops and nothing gets logged.
Can anyone enlighten me please, what's this f000000 in the call
 "XFS assertion failed: XFS_FORCED_SHUTDOWN(ip->i_mount) ||
ip->i_delayed_blks == 0, file: xfs_vnodeops.c, line: 5415"
Unfortunately the oops text is lost (the kernel did not lock up
completely, but there was no response to keyboard/mouse events,
and the blanker kicked in---it's handy to have setterm -blank 0
when you're copying an oops by hand...)
.+'''+. .+'''+. .+'''+. .+'''+. .+''
Kelemen Péter / \ / \ Peter.Kelemen@xxxxxxx
.+' `+...+' `+...+' `+...+' `+...+'
Description: Text document