Finally, one didn't freeze up everything but networkin,
and I can copy the logs. I do not know how typical these are.
Linux 2.0.33 helped some. Recompiling sshd a zillionth time
helped a bit too, I have no idea why. glibc-2.0.5c system.
Jan 3 11:44:34 Q kernel: general protection: 97bc
Jan 3 11:44:34 Q kernel: CPU: 0
Jan 3 11:44:34 Q kernel: EIP: 0010:[ret_from_sys_call+133/136]
Jan 3 11:44:34 Q kernel: EFLAGS: 00010202
Jan 3 11:44:34 Q kernel: eax: 00000001 ebx: 00000007 ecx: bffff854 edx: bffff7d4
Jan 3 11:44:34 Q kernel: esi: 00000000 edi: bffff750 ebp: bffff758 esp: 0108dfec
Jan 3 11:44:34 Q kernel: ds: 002b es: 002b fs: 002b gs: 002 bss: 0018
Jan 3 11:44:34 Q kernel: Process sshd (pid: 19854, process nr: 66, stackpage=0108d000)
Jan 3 11:44:34 Q kernel: Stack: 400b45ce 00000023 00000286 bffff720 000097bf
Jan 3 11:44:34 Q kernel: Call Trace:
Jan 3 11:44:34 Q kernel: Code: cf 89 f6 89 e1 51 f7 41 38 00 00 02 00 75 2c 53 e8 fa fb ff
=======
In other unrelated news, this is a Linux 2.0.33 panic:
Jan 3 12:36:19 Q rwhod[803]: sendto(10.0.0.3): Operation not permitted
Jan 3 18:39:34 Q syslogd 1.3-3: restart (remote reception).
It happened today. No more logs or panic information in serial
console panix dialog. Linux 2.1.76 sometimes feels more stable.
(Wish 2.1 went the 2.2 track soon.)
There should be a "sync" option to the serial console panic routines.
That would help reduce recovery problems. (Perhaps it already does?
Afraid to mount SCSI partition to check at the moment, want to send
email ...)
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQEVAwUBNK7QBJxWhFYc6x9VAQFH4wgA1uDBr7uFU6Mf42qtIlBs73oqZ400Vc8P
C2FMuQFMNdRr0j4QyZx6Nb4zr0wOpnQ0W2oMlN1MI0eyOdUYWsZEhTZXxu0e4+gB
BYm09sYdQ3JdOISO3RU+3UkEPIC4aBp93R/arIiLAwQF5W/qJ3t562BfrrgDZWhx
vI5rEMBdLzZUu7bMyMdvQV+5dCHngty95a06b9eXCU8IAqamSYcqVawF1qMSPm/M
hU0TM+RGboKkD0RHbzsQ62wyMmbCZJGjwhdLIwI86pSQZ/YRTc+Vx2S9A3J2Z9Nn
jPX7X/ZEQVqjnfEl+zuJeGiFK+QiZZPvApj/xdta2yvybF3Z/FR6pQ==
=0RPW
-----END PGP SIGNATURE-----