On Sun, Dec 01, 2002 at 04:07:32PM -0500, Chuck Robey <[EMAIL PROTECTED]> wrote:
> I've been on vacation for the last week, so I haven't been watching > -current like a good boy should, but I've suddenly been seeing a serious > problem, and it *might* not have been reported, and seeing as code freeze > is almost here, it's worth risking a bit of embarrassment, I guess. > > Anyhow, it's the console, it's been locking up. I just retried it with a > kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock > up, and once even froze the PC speaker (beeping annoyingly at me). > > There don't seem to be any hung processes. I can use X, and I can also > ssh into the box, so it's the console only. Can't switch to different > vty's, and the one i'm on is frozen, no response to any keys. > > It seems to come on more quickly if I do something serious, like a > buildkernel. Happened once on startup, but even though rc hadn't > finished, I WAS able to ssh into the box and shut it down (indicating to > me that rc had finished, just no response from the console). > > Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks > and eide both. It's interesting that you seem to have almost same machine as I have. Tyan Thunder with SCSI and ATA disks, SMP and the only difference seems to be memory size, 1GB vs. 512MB. Not counting network interfaces and such. I've also lost console after rebuild yesterday. The kernel from Nov. 29 works. Mine (console) not locks up but is simply missing from the start. Otherwise system is up and running. I don't think it's coincidence, something is broken and related to the Tyan mobos we have. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
