Date: Sat, 10 May 2003 11:50:12 -0700 (PDT) From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: freebsd-bugs@FreeBSD.org Subject: RE: kern/51016: kernel panic: ufsdirhash_lookup: bad offset in hash array Message-ID: <200305101850.h4AIoCOK047322@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/51016; it has been noted by GNATS. From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: <alexovch@ic.kharkov.ua> Cc: <freebsd-gnats-submit@FreeBSD.org> Subject: RE: kern/51016: kernel panic: ufsdirhash_lookup: bad offset in hash array Date: Sat, 10 May 2003 11:44:45 -0700 >If some port can cause a system crash it's probably a kernel >security bug and >it's have to be fixed imho. This is true if the port crashes on every FreeBSD system it is tried on. However if your system is the only one that is crashing then it's most likely something specific to your system. Many times hardware problems with hardware, or device driver bugs, can hand back garbage to the kernel and cause a panic. You should include a dmesg printout so we can see the kind of hardware your running. Since the leafnode+ maintainer obviously is running leafnode he can confirm if there's any history of crashing. I've also compiled and installed leafnode myself with no ill effects, although I don't currently use it, I use NewsCache. Note that you need to CC freebsd-gnats-submit@FreeBSD.org and leave the subject line intact in order for your responses to be made part of the audit trail. Ted Mittelstaedt tedm@toybox.placo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305101850.h4AIoCOK047322>