From owner-freebsd-scsi@FreeBSD.ORG Thu Jul 19 05:55:38 2012 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 67860106564A; Thu, 19 Jul 2012 05:55:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8041C8FC0A; Thu, 19 Jul 2012 05:55:34 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id IAA08015; Thu, 19 Jul 2012 08:55:26 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Srjht-00094P-QJ; Thu, 19 Jul 2012 08:55:25 +0300 Message-ID: <5007A14B.5020703@FreeBSD.org> Date: Thu, 19 Jul 2012 08:55:23 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120620 Thunderbird/13.0.1 MIME-Version: 1.0 To: Matt Jacob References: <5006C177.2090009@feral.com> In-Reply-To: <5006C177.2090009@feral.com> X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@FreeBSD.org, Matthew Jacob Subject: Re: dev/isp panic (was Re: CAM Target Layer and dev/isp) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jul 2012 05:55:38 -0000 on 18/07/2012 17:00 Matthew Jacob said the following: > -------------- > > db> bt > Tracing pid 12 tid 100062 td 0xfffffe001c00f470 > acpi_timer_get_timecount() at 0xffffffff803ccfc6 = > acpi_timer_get_timecount+0x16 > DELAY() at 0xffffffff80ce68c3 = DELAY+0x83 > ns8250_putc() at 0xffffffff807a17ba = ns8250_putc+0x9a > uart_cnputc() at 0xffffffff807a3b85 = uart_cnputc+0x75 > cnputc() at 0xffffffff808e9cbc = cnputc+0x4c > cnputs() at 0xffffffff808ea0f5 = cnputs+0x35 > putbuf() at 0xffffffff8097400c = putbuf+0xac > kvprintf() at 0xffffffff80972643 = kvprintf+0x83 > vprintf() at 0xffffffff80973b15 = vprintf+0x85 > printf() at 0xffffffff80973be7 = printf+0x67 > isp_prt() at 0xffffffff805c15a0 = isp_prt+0xd0 > isp_async() at 0xffffffff805c6736 = isp_async+0x356 > isp_intr() at 0xffffffff805b854c = isp_intr+0x13ac > isp_platform_intr() at 0xffffffff805c1fd9 = isp_platform_intr+0x99 > intr_event_execute_handlers() at 0xffffffff80907214 = > intr_event_execute_handlers+0x104 > ithread_loop() at 0xffffffff809089a6 = ithread_loop+0xa6 > fork_exit() at 0xffffffff809038ef = fork_exit+0x11f > fork_trampoline() at 0xffffffff80c5139e = fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff9178bd3cf0, rbp = 0 --- > db> x/s panicstr > 0xffffffff8130fd08 = 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. 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"). -- Andriy Gapon