On 05-Dec-2000 Lord, Steve wrote:
>
> You state that your news server hangs after about a week - this is
> the thing which needs digging into I think. Have you tried dropping
> into kdb when this happens - a dump of all stack traces might be a
> good starting point.
>
Well, I didn't have to wait too long. Here's my hand copied bt. If
you need any more debugging, let me know, I still have the machine in
kdb:
CPU1
----
find_inode+0x14 (0xf7676e00, 0x11028129, 0xf7e47568, 0x0, 0x0)
ihold4+0x58 (0xf7676e00, 0x11028129, 0x0, 0x0)
vn_get+0x28 (0xe9a9e5cc, 0xe07333db8, 0x0)
xfs_iget_core+0x1d2 (0x0, 0xf7b6d000, 0x0, 0x11028129, 0x0)
xfs_iget+0x2d (0xf7b6d000, 0x0, 0x11028129, 0x0, 0x0)
xfs_dir_lookup_int+0x137 (0x0, 0xd28169a8, 0x5, 0xdcad980, 0xe0755f00)
xfs_lookup+0x8a (0xd28169a8, 0xdacad980, 0xe0733efc, 0xe0733f00, 0x0)
linvfs_lookup+0x70 (0xd29034c0, 0xdacad920)
real_looup+0x7d
path_walk+0x64f
__user_walk+0x3c
sys_newlstat+0x17
system_call_0x33
CPU0
----
stext_lock+0x2180
permission+0x32 (0xf76807c0, 0x1)
path_walk+0x878 (0xe2857010, 0xf75fdfa0)
__user_walk+0x3c (0x940b718, 0x9, 0xf75ddfa0)
sys_access+0x86 (0x940b718, 0x4, 0xbffff0a4, 0xbffff036, 0xbffff006)
-tony
---
E-Mail: Tony Gale <gale@xxxxxxxxxxxxxxxxxx>
Reappraisal, n.:
An abrupt change of mind after being found out.
The views expressed above are entirely those of the writer
and do not represent the views, policy or understanding of
any other person or official body.
|