[vox-tech] not sure what to call it

[Patrick Stockton]

The kernel continues to remain active as evidnt by it continuing to pass
internet traffic to my windows box.  But if I try to ssh in to it from that
Windows I get the same series of events, prompt for username, prompt for
password, hang.  SAMBA connections also hang up and stop responding.

I wonder if it could be a problm with the password verification.  Although
that wouldn't explain the same series of events when trying to connect to
Webmin because it has it's own password file that I don't believe relies on
the system but I could be wrong.

When sitting at a text login at the actuall box for example I'll enter the
username and password and it'll stop moving.  So I'll hit ALT+F3 to get a
different terminal and I get a black screen, no prompts.  So I hit ALT+F7 to
get to my X windows and still get the black screen.

I'll boot it in to single user mode and see what happens.  But it could be a
day or two before it hangs.  It can work fine for a few days before it hangs
up like this.

----- Original Message -----
From: "Peter Jay Salzman" <p@dirac.org>
To: <vox-tech@lists.lugod.org>
Sent: Saturday, April 13, 2002 11:46 AM
Subject: Re: [vox-tech] not sure what to call it


> begin Patrick Stockton <codejnki@codejnki.com>
> > Actually this a new install.  It is about 3 weeks old and has done it
since
> > I installed it.  The problem is that it's almost random.  My girlfriend
and
> > I use it as an internet terminal and one of us will log out and the
other
> > will try to log in and it'll hang.
>
> just to be clear - the kernel doesn't hang.  the keyboard and mouse
> become unresponsive, right?  you can ssh in just fine even after the
> problem happens?
>
> > But speaking of new RPM's I did add Sun Java because she likes to play
Yahoo
> > card games.  I'm wondering if that could be the problem.
>
> never liked java anyhow.  ;)   it's unbelievably slow and brings my
> system performance down even worse than GNOME/KDE does.
>
> > Scanning both dmesg and messages hasn't revealed a prime suspect which
is
> > why I turned to the list.  I guess I'm just too used to things working
:)
>
> > I've dissabled USB and will watch to see what happens.
>
> barring that, boot into single user mode.  if the problem doesn't exist
> in single user mode, then it's most likely easy to fix -- one of your
> services is screwing up the system.
>
> if the problem does exist in single user mode, i'd compile a custom made
> kernel.  go back to an early 2.4 or something.  maybe even 2.2.
>
> pete

*snip*