Date: Fri, 14 Apr 1995 17:10:08 -0500 (CDT) From: "Carl M. Fongheiser" <cmf@ins.infonet.net> To: current@FreeBSD.org Subject: Interesting (and odd) effect in -current Message-ID: <199504142209.RAA00277@kf0yn.ampr.org>
next in thread | raw e-mail | index | archive | help
Thanks to hardware trouble, I haven't had a chance to boot a reasonably current -current kernel until a few days ago. In particular, this is the first kernel that didn't have the memory test in it. The first time I booted it (warm boot), it booted fine. I ran with it for a couple days. Wednesday night, we had a power failure, and I discovered that the thing wouldn't cold boot with that kernel. It gets all the way through the autoboot, but it trapped when it started up a getty due to a kernel reference to address 0. It failed again on the reboot. My old kernel (from late Jan.) booted fine. A perusal of the crash dump showed the trap happened inside of scopen(). Yesterday, I supped again, and built another kernel. This one falls over the same way, but slightly earlier in stty. This time it looks like it happened in spec_ioctl(). Just to summarize, my late January kernel runs flawlessly, but my 2 most recent kernels sometimes fall over late in the boot sequence. I don't know if this could be uncovering some flakiness in my hardware, or if there's something that isn't getting initialized properly. My hardware configuration: PCI/I-486SP3G motherboard, 256k L2 cache, 8M main memory. 2 Maxtor 7345AT drives 1 Quantum LT730S drive STB 4COM (4-port serial card) 3COM 3C503 ethernet card #9 GXE64 PCI video card Any help would be appreciated, and I'd be happy to supply further details on request. Carl Fongheiser cmf@ins.infonet.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504142209.RAA00277>