Date: Wed, 18 Jul 2012 08:58:45 -0700 From: Trent Nelson <trent@snakebite.org> To: Matt Jacob <mjacob@freebsd.org>, "freebsd-scsi@freebsd.org" <freebsd-scsi@freebsd.org> Subject: Re: dev/isp panic (was Re: CAM Target Layer and dev/isp) Message-ID: <CC2C5408.32DAC%trent@snakebite.org> In-Reply-To: <5006C177.2090009@feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/18/12 10:00 AM, "Matthew Jacob" <mj@feral.com> wrote: >-------------- > >db> bt >Tracing pid 12 tid 100062 td 0xfffffe001c00f470 >acpi_timer_get_timecount() at 0xffffffff803ccfc6 =3D >acpi_timer_get_timecount+0x16 >DELAY() at 0xffffffff80ce68c3 =3D DELAY+0x83 >ns8250_putc() at 0xffffffff807a17ba =3D ns8250_putc+0x9a >uart_cnputc() at 0xffffffff807a3b85 =3D uart_cnputc+0x75 >cnputc() at 0xffffffff808e9cbc =3D cnputc+0x4c >cnputs() at 0xffffffff808ea0f5 =3D cnputs+0x35 >putbuf() at 0xffffffff8097400c =3D putbuf+0xac >kvprintf() at 0xffffffff80972643 =3D kvprintf+0x83 >vprintf() at 0xffffffff80973b15 =3D vprintf+0x85 >printf() at 0xffffffff80973be7 =3D printf+0x67 >isp_prt() at 0xffffffff805c15a0 =3D isp_prt+0xd0 >isp_async() at 0xffffffff805c6736 =3D isp_async+0x356 >isp_intr() at 0xffffffff805b854c =3D isp_intr+0x13ac >isp_platform_intr() at 0xffffffff805c1fd9 =3D isp_platform_intr+0x99 >intr_event_execute_handlers() at 0xffffffff80907214 =3D >intr_event_execute_handlers+0x104 >ithread_loop() at 0xffffffff809089a6 =3D ithread_loop+0xa6 >fork_exit() at 0xffffffff809038ef =3D fork_exit+0x11f >fork_trampoline() at 0xffffffff80c5139e =3D fork_trampoline+0xe >--- trap 0, rip =3D 0, rsp =3D 0xffffff9178bd3cf0, rbp =3D 0 --- >db> x/s panicstr >0xffffffff8130fd08 =3D panicstr: > > >------------- > >Hmm. No panic string because it wasn't a panic. isp driver is trying to >(successfully) print something and this blew up in the ACPI code. 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CC2C5408.32DAC%trent>