On Tue, 25 Oct 2005, Kunael wrote:

I use SuSE 10.0. I installed it some days ago and works fine in general sense in my opinion (the increase of speed is great specially).

Today I was working with this SuSE 10 box from another machine using ssh connection. The problem is the system crash totally (in remote machine, of course); the system doesn't reboot or suspend ssh services, simply appears "freeze"... mouse doesn't works, keyboard doesn't works...

When the system crash I was using ssh+screen, so I've try without screen but I've got same crash again.

Could you please point out a way how to reproduce this problem? I don't think this is a "bug" in OpenSSH, but rather a hardware or kernel problem... ;) Regards Christoph

On Tue, 25 Oct 2005, Kunael wrote:

...

Could you please point out a way how to reproduce this problem? I don't think this is a "bug" in OpenSSH, but rather a hardware or kernel problem... ;)

Yes Christoph you've all the reason... the post title isn't the best.

The only way to reproduce (the only way I know at present moment) the crash is simply use a ssh connection. The ssh-client machine simply lose connection, but not appear anymore problem and the ssh-server (the machine which runs under SuSE 10) appears completly freeze.

Only mechanical reset is able :(

I've watched in /var dir and I've not found anything interesting.

¿Where do I watch to get more info?

First, verify that the software that is installed is not corrupt. Do this in a shell, as root (use "su -" not "su" if you don't login as root): ( rpm -Va 2>&1 ) | tee rpmVa or rpm -Va > rpmVa 2>&1 and then examine the file rpmVa for files that have changed. There will always be some, devices, some files in /etc, and so on, but pay particular attention to *anything* in /sbin, /usr/sbin, /bin, /usr/bin, etc.... However, I'm guessing that you have hardware issues, just based upon experience with this sort of thing. One thing you could tell us is what the output from dmesg is after startup; knowing the hardware could help - it's entirely possible that it's a strange or weird network card and ssh just triggers a bug in the driver. -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson

"Just using ssh connections" isn't very specific + I guess I'm not the only one who is using ssh very intensively on a daily basis (and I didn't slip into this once).

Ok. I'll think is a hardware problem of my machine; in fact is the first time I've these problems with ssh sessions. A conflict with hardware is really possibility...

I'd recomment to "monitor" that very maschine with a serial console to be able to catch potential error messages or even oops.

I'll do it. -- ¡Share your knowledge! Linux user id 332494 # http://counter.li.org/ PGP id 0xC5ABA76A # http://pgp.mit.edu/