Date: Sat, 10 Feb 2001 10:00:02 -0800 (PST) From: "Paul A. Scott" <pscott@cue.net> To: freebsd-bugs@FreeBSD.org Subject: RE: Re: kern/24958: Fatal trap 12 in kernel mode (swapper) on Compaq Presario Message-ID: <200102101800.f1AI02r57780@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/24958; it has been noted by GNATS. From: "Paul A. Scott" <pscott@cue.net> To: "Paul A. Scott" <pscott@the-frontier.org>, <freebsd-gnats-submit@FreeBSD.org>, <pscott@cue.net> Cc: Subject: RE: Re: kern/24958: Fatal trap 12 in kernel mode (swapper) on Compaq Presario Date: Sat, 10 Feb 2001 09:56:15 -0800 > "Paul A. Scott" <pscott@the-frontier.org> writes: >> #gdb /sys/compile/GENERIC/sysv_msg.o >This is meaningless unless the kernel that crashed includes this >precise object file. You are correct. But, I compiled and linked the GENERIC kernel to get sysv_msg.o and it matches exactly in size the kernel on the CDROM. All the offsets in sysv_msg.o also match the offsets in the kernel. It's a good bet they're the same. I'll get further into this when I'm back to work on Monday. >This still belongs on the lists, not in a PR. Why? Seriously, I'd like to know what criteria you use for defining a "problem." Let's look at this rationally. I have a brand-new, current generation, Compaq Presario right out of the box. With the help of V-com's System Commander 2000 boot manager, I installed Windows Me, and Windows/2000 Server on the box without any problems. Both Microsoft OS's run fine. However, after installing FreeBSD 4.2-RELEASE on the box--which actually installed without any problems--I boot the kernel and after it probes ppi0 it panics. Furthermore, I can't even use the userconfig utility because the syscons driver can't even write to the screen in an age-old standard way. Lemme see, MS Windows runs, FreeBSD GENERIC doesn't. All devices are standard ATA, PCI, and PNP; no ISA or legacy hardware. * kernel panics after probing ppi0 * userconfig scrambles screen Wouldn't you call these problems? I spent 4 hours searching your precious mailing lists archives. Couldn't find anything even close to kern/24957 and kern 24958. You should know that I've been an avid FreeBSD user--and a minor hacker--since the first FreeBSD 1.0 CDROM was delivered. I have a Walnut Creek subscription and have installed and used in business--and personally--nearly every release through 4.2-RELEASE. In that time, I've reported a half-dozen pr reports, all of them received courteous responses, and most were fixed in the next release. At one time, I submitted a patch to the matcd driver, which made it into the next release. In conf/3354 I reported a problem with the syscons driver, which is very similar to kern/24957 I'm now reporting, and was e-mailed a fix by a very courteous Kazutaka san. Over the past 8 years, I've become quite familiar with FreeBSD. So, with that background, please explain why this isn't a problem, and why it doesn't belong in gnats. Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102101800.f1AI02r57780>