Re: Lockup since 2.4.4 when switching from X to console

[thomas graichen <list-linux.sgi.xfs@spoiled.org>]

"Eric Sandeen" <sandeen@sgi.com> wrote:
> Juri Haberland wrote:

>> On all test I used the kgcc. Every time besides the last (2.4.9) test I
>> compiled the XFS-enabled kernel with kdb, but not even the kdb kicked in.
>> 
>> Any hints on how to debug? I really would like to use XFS on this system...

> hi Juri - 

> I really wouldn't suspect XFS, but it sounds like you do have it
> narrowed down.  :)  

> By complete lockup, do you mean NOTHING works, or is just the console
> hung up?  Can you access the machine over the network?  If so, can you
> see what is running via "ps" from a normal network login?

> If you can't get to it over the network, what I would do is enable KDB,
> and hook up a serial console if you can... then when the machine locks
> up, invoke KDB yourself (CTRL-A on the serial console), and type "ps" to
> see what's running.  You could try hitting the "pause" key on the normal
> console, but if the machine is in X, you won't see the kdb prompt.

maybe its kdb somehow itself - as far as i can see the only
component which differs from the plain kernel and the xfs one
which has a little bit to do with the console ... maybe trying
to disable it or on the other side: add the kdb patch to the
plain kernel and see if the problem apears there too ...

t

-- 
thomas graichen <tgr@spoiled.org> ... perfection is reached, not
when there is no longer anything to add, but when there is no
longer anything to take away. --- antoine de saint-exupery