Date: Wed, 18 Jul 2012 10:24:42 -0700 From: Matthew Jacob <mj@feral.com> To: Trent Nelson <trent@snakebite.org> Cc: "freebsd-scsi@freebsd.org" <freebsd-scsi@freebsd.org> Subject: Re: dev/isp panic (was Re: CAM Target Layer and dev/isp) Message-ID: <5006F15A.5060709@feral.com> In-Reply-To: <CC2C5408.32DAC%trent@snakebite.org> References: <CC2C5408.32DAC%trent@snakebite.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/18/2012 8:58 AM, Trent Nelson wrote: > Hmm, just to clarify, do you mean "the isp tried to print something > that blew up ACPI", or "ACPI blew up whilst isp just happened to be > printing something"? Would knowing what isp was trying to print be of > any help? (I can poke around the *putc buffers if it happens again.) > I'm not surprised that ACPI is involved, though. This box has always > seemed to run into ACPI issues (HP ProLiant DL585 G1, quad dual-core > Opteron, 64GB RAM), like hanging on boot during the pci->bios probe > stuff from a kernel circa 2-3 months ago. Trent. I wouldn't know. Since there are a limited number of printfs from isp_async you could probably narrow it down. Try booting with ACPI disabled. Or upgrade f/w.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5006F15A.5060709>