Re: Can't connect to paer

[Matt Taggart <taggart@debian.org>]

Hi Ian,

Thanks for the report, I'm cc'ing debian-hppa in case others are seeing it or 
have ideas about what the problem might be.

Ian Lynagh writes...

> Trying to ssh to paer stops after:
> 
> $ ssh -v paer.debian.org
> OpenSSH_3.8.1p1 Debian-8.sarge.4, OpenSSL 0.9.7e 25 Oct 2004
> debug1: Reading configuration data /home/igloo/.ssh/config
> debug1: Applying options for *.debian.org
> debug1: Applying options for *.debian.org
> debug1: Applying options for *
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: Applying options for *
> debug1: Connecting to paer.debian.org [192.25.206.11] port 22.
> debug1: Connection established.
> debug1: identity file /home/igloo/.ssh/id_dsa_debian type 2

When I connected to the console is was printing this over and over and I 
couldn't get a login prompt,

spin_lock(00000000104f3140) CPU#0 NIP 000000001019d530 holder: cpu 0 pc 
1019F364
spin_lock(00000000104b9528) CPU#1 NIP 000000001013536c holder: cpu 0 pc 
1013536C

I power cycled it and it rebooted fine and I can ssh in now.

The last entry in /var/log/messages was,

May 21 06:01:42 paer kernel: sys32_ioctl: Unknown cmd fd(2) cmd(00005461) 
arg(00000000)

and the reboot was 6 hours later at 12:05. There are some normal named 
messages in syslog from 6-6:27 and then nothing until the reboot.

Keep in mind paer is still running a 2.4 kernel (2.4.26-64-smp version 
2.4.26-6) and woody so there my not be much we can do (but there's probably a 
newer 2.4 kernel we can move to at least if we think it would help).

-- 
Matt Taggart
taggart@debian.org