xfs
[Top] [All Lists]

RE: Pb with XFS

To: GLENAT Grégory <gregory.glenat@xxxxxxxxxxxxxxxxxx>
Subject: RE: Pb with XFS
From: Eric Sandeen <sandeen@xxxxxxx>
Date: 18 Jul 2001 10:30:05 -0500
Cc: linux-xfs list <linux-xfs@xxxxxxxxxxx>
In-reply-to: <4.3.2.7.2.20010718144631.034ba518@xxxxxxxxxxxxx>
References: <4.3.2.7.2.20010718144631.034ba518@xxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
On 18 Jul 2001 14:48:01 +0200, GLENAT Grégory wrote:
> More Detail :
> Here what appairs in the boot (extract from dmsg )
> ==========
> checking TSC synchronization across CPUs: passed.
> Setting commenced=1, go go go
> mtrr: your CPUs had inconsistent fixed MTRR settings
> mtrr: probably your BIOS does not setup all CPUs
> PCI: PCI BIOS revision 2.10 entry at 0xfd2fc, last bus=4
> PCI: Using configuration type 1
> ==========

I don't think any of this is particularly unusual.

> What more detail do you need ?

You said you tried 2 kernels on 2 different machines - 
do you see exactly the same behavior in all cases?

Does this lockup seem to depend on whether nfs is enabled?
Does it depend on samba?  Does it only happen after a lot
of nfs traffic?  Etc...

You can turn on kdb with

$ echo 1 > /proc/sys/kernel/kdb

then hit the Pause/Break key to get into kdb when things "seem dead" -  
"ps" will get you a list of what's running and what state things are in,
"btp <process ID>" will do a backtrace on any process...

kdb is easiest to use if you're at a text console, don't start it from
X.
You can also do it via a serial console.

-Eric

-- 
Eric Sandeen      XFS for Linux     http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx   SGI, Inc.


<Prev in Thread] Current Thread [Next in Thread>