Date: Tue, 30 Sep 2008 17:16:39 -0400 From: "Alexander Sack" <pisymbol@gmail.com> To: "Paul A. Procacci" <pprocacci@datapipe.com> Cc: freebsd-scsi@freebsd.org Subject: Re: Re[2]: kern/126866: [isp] [panic] kernel panic on card initialization Message-ID: <3c0b01820809301416v416460e5gc0b4689febcf0905@mail.gmail.com> In-Reply-To: <3c0b01820809251051q34a33fa5od5ec9fe9d853612@mail.gmail.com> References: <200809250910.m8P9A4MY047099@freefall.freebsd.org> <835218108.20080925113214@connection.ca> <3c0b01820809251051q34a33fa5od5ec9fe9d853612@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 25, 2008 at 1:51 PM, Alexander Sack <pisymbol@gmail.com> wrote: > On Thu, Sep 25, 2008 at 11:32 AM, Ross <westr@connection.ca> wrote: >> >> PAP> I am having the same exact problem you were having using the same >> PAP> device. I started receiving this error on FBSD7-RELEASE and thought it >> PAP> was specific to that version. Naturally I upgraded to FBSD7-Stable as >> PAP> of today (9/25/2008), but still haven't been able to resolve this error, >> PAP> even with the patch presented here. Like you had mentioned on >> PAP> freebsd-scsi, the machine panic's roughly 50% of the time during boot. >> >> Actually, going over the trap output, it looks different than the >> output I had, so it might be a different issue in the end. >> >> Which kernel are you running? (i386/amd64), and is it possible to get >> the output of a dmesg, so we know what chipset the driver thinks it is? >> (Are you running an HP Blade w QHM6432 like I am?) >> >> Also, if you can set 'hint.isp.[01].debug=0x11F' in your >> /boot/device.hints file, it'll hopefully give some additional output >> to help track the problem down. >> >> Obviously the best is to compile in the kernel debugger as that'll >> give the exact place it crashes. > > > Yea totally. If you can get a stack trace that would be great (just > compile in the debugger support, reboot, and when you hit the panic do > a trace and just give us the function output (again exact addresses > not so much)). Paul do you have any update with this issue? I have my patches ready and I want to try to resolve yours if it indeed turns out to be a similar bug. Please let me know, -aps
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3c0b01820809301416v416460e5gc0b4689febcf0905>