Date: 14 May 1998 21:50:18 -0000 From: "Brian Feldman" <brianfeldman@hotmail.com> To: freebsd-current@FreeBSD.ORG Subject: SoftUpdates stable?? Message-ID: <19980514215018.6031.qmail@m2.findmail.com>
next in thread | raw e-mail | index | archive | help
I don't know about this, it seems not to be stable to me. After a 1-week uptime, at the end which I decided to rebuild a kernel with softupdates, it seemed to work fine. After a little while, I was in X, with xlock running, and left my station alone. Later I tried to telnet to it to no avail; when I got home, I found it completely locked, "wedged" to use recent terminology, having been up maybe 15 or so hours at most. Now, seeing as the system did not respond at all, I had to hit the actual reboot button, and on the next boot, running dumpon, there was no panic and no coredump to recover. So, my question is, is it really possible for the softupdates code to literally hang my system instead of panicking it? So now I am running without softupdates, and I'll see if this locking up problem resurfaces, to see if it's truly softupdates's fault. As a side note, during that one week uptime and after making install on the new kernel, I was about o reboot; a minute earlier I had dropped into DDB, continued, and switched back into X; minutes later, my system locked, with the all-too-familiar infinite beep of trying to switch consoles when the system is locked. Think DDB, delaying the system by a couple seconds without the userland knowing, could have caused this one crash? Cheers, Brian Feldman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980514215018.6031.qmail>