Date: Thu, 19 Jul 2012 05:22:21 -0700 From: Trent Nelson <trent@snakebite.org> To: Andriy Gapon <avg@FreeBSD.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: <CC2D73DE.338ED%trent@snakebite.org> In-Reply-To: <5007A14B.5020703@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/19/12 1:55 AM, "Andriy Gapon" <avg@FreeBSD.org> wrote: >on 18/07/2012 17:00 Matthew Jacob said the following: >> -------------- >>=20 >> 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: >>=20 >>=20 >> ------------- >>=20 >> 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. If >>there was a >> bad string it would have blown up in kvprintf. At least that's my read >>of this. > >I think that the vague reference to ACPI is unnecessarily too vague, >given the >quite obvious stack trace (hint: DELAY) and both simplicity and utility of >acpi_timer_get_timecount (essentially an I/O read operation). >But there is no indication in the above stack trace that something blew >up at >all (no magic words like "panic", "trap"). Hrm. What else would cause 'db>' to show up on the console? Ctrl-Alt-Esc and hitting a breakpoint are all I can think of at the moment -- and neither of those are applicable here. Trent.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CC2D73DE.338ED%trent>