Messages in this thread | | | Date | Fri, 13 Feb 1998 10:06:29 +0000 (WET) | From | Klaus Lichtenwalder <> | Subject | Re: mysterious 2.0.33 crashes |
| |
On Mon, 12 Feb 1996, Jon Torrez wrote:
> (in responce to my previous note) > > Yes! (read on fool :) ) > > Well, try this Patrick: > 1. remove all the patches and run from a clean unpatched kernel; > unless your system needs them. > > 2. do remote logging with syslogd do *.*, something might show up. > > 3. cross your fingers. >
Well, I have to chime in. I'm also administering a web server remotely, 2.0.33 with Solar Designers security patches, a bunch of isdn interfaces, ethernet to internet backbone, 24 ethernet aliases. This machine tends to just lock, after 3 days of uptime. Just now is updated to Doug's latest adaptec driver, in case it's a scsi timeout on the disk /var is mounted.
The other strange effect I already posted about is a mixup of routes (or a bug in isdn or overwriting of some kernel structs). It just happened for the 4th time in a row after 3 days of uptime. The kernel (isdn subsystem?) just uses the wrong isdn interface for *some* devices. The routes are ok (netstat -r), but of using isdnN it uses isdnM...
Klaus Lichtenwalder ------------------------------------------------------------------------ Klaus Lichtenwalder, Dipl. Inform., PGP Key: email to key@Four11.com Lichtenwalder@ACM.org http://www.wp.com/Klaus K.Lichtenwalder@Computer.org fax: +49-89-91072699 Mausoberflaechen sind meistens pelzig -- Ricarda
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |