From owner-freebsd-sparc64@FreeBSD.ORG Tue Aug 12 19:37:13 2014 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2FAF9F73 for ; Tue, 12 Aug 2014 19:37:13 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0857825CF for ; Tue, 12 Aug 2014 19:37:13 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E6639B9A5; Tue, 12 Aug 2014 15:37:11 -0400 (EDT) From: John Baldwin To: freebsd-sparc64@freebsd.org, mexas@bris.ac.uk Subject: Re: isp driver causes panic in 10-stable Date: Tue, 12 Aug 2014 13:54:58 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <201407131437.s6DEbDuP005266@mech-cluster241.men.bris.ac.uk> In-Reply-To: <201407131437.s6DEbDuP005266@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201408121354.58355.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 12 Aug 2014 15:37:12 -0400 (EDT) X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2014 19:37:13 -0000 On Sunday, July 13, 2014 10:37:13 am Anton Shterenlikht wrote: > isp0: port 0x300-0x3ff mem 0x100000-0x100fff at device 3.0 on pci1 > > I used this card for years on ia64, from 8-current > to 11-current. Now that ia64 is not supported, > I wanted to move it into sparc64 10-stable box > (SunBlade 1500 silver workstation). The card is > recognised, see above, but shortly after I get > this panic (single user mode): > > isp0: port 0x300-0x3ff mem 0x100000-0x100fff at device 3.0 on pci1 > nexus0: mem 0x4000fc64000-0x4000fc6400f type i2c (no driver attached) > nexus0: type unknown (no driver attached) > rtc0: at port 0x70-0x71 on isa0 > uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 44 on isa0 > uart0: console (9600,n,8,1) > uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 44 on isa0 > WITNESS: unable to allocate a new witness object > Timecounter "tick" frequency 1503000000 Hz quality 1000 > Timecounter "stick" frequency 12000000 Hz quality 1000 > Event timer "tick" frequency 1503000000 Hz quality 1000 > Timecounters tick every 1.000 msec > usbus0: 12Mbps Full Speed USB v1.0 > usbus1: 12Mbps Full Speed USB v1.0 > panic: trap: memory address not aligned (kernel) > KDB: stack backtrace: > vpanic() at vpanic+0xfc > panic() at panic+0x20 > trap() at trap+0x5cc > -- memory address not aligned sfar=0x1001ee021 sfsr=0x40029 %o7=0xc0137bac -- > userland() at isp_get_ridacq+0x118 Can you run gdb against the kernel.debug file from this kernel and do 'l *isp_get_ridacq+0x118'? -- John Baldwin