From nobody@FreeBSD.org Sat Mar 14 21:32:05 2009 Return-Path: Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1398106566B for ; Sat, 14 Mar 2009 21:32:05 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id C08E58FC16 for ; Sat, 14 Mar 2009 21:32:05 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n2ELW5dF088542 for ; Sat, 14 Mar 2009 21:32:05 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id n2ELW56U088541; Sat, 14 Mar 2009 21:32:05 GMT (envelope-from nobody) Message-Id: <200903142132.n2ELW56U088541@www.freebsd.org> Date: Sat, 14 Mar 2009 21:32:05 GMT From: Henry Karpatskij To: freebsd-gnats-submit@FreeBSD.org Subject: CURRENT as of 2009-03-14 panics on boot X-Send-Pr-Version: www-3.1 X-GNATS-Notify: >Number: 132641 >Category: sparc64 >Synopsis: [boot] [panic] CURRENT as of 2009-03-14 panics on boot >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-sparc64 >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Mar 14 21:40:00 UTC 2009 >Closed-Date: Fri Mar 20 13:48:14 UTC 2009 >Last-Modified: Fri Mar 20 13:48:14 UTC 2009 >Originator: Henry Karpatskij >Release: 8.0-CURRENT >Organization: >Environment: Sun Fire V210 >Description: I built the latest CURRENT and it panics on boot: da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz DT, offset 62, 16bit) da0: Command Queueing Enabled da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz DT, offset 62, 16bit) da1: Command Queueing Enabled da1: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) GEOM: da0: adding VTOC8 information. Trying to mount root from ufs:/dev/da0a panic: vm_fault: fault on nofault entry, addr: f35de000 cpuid = 0 KDB: enter: panic [thread pid 1 tid 100002 ] Stopped at kdb_enter+0x80: ta %xcc, 1 db> trace Tracing pid 1 tid 100002 td 0xfffff80001097b80 panic() at panic+0x20c vm_fault() at vm_fault+0x19c trap_pfault() at trap_pfault+0x340 trap() at trap+0x354 -- fast data access mmu miss tar=0xf35de000 %o7=0xc030244c -- exec_elf64_imgact() at exec_elf64_imgact+0x174 kern_execve() at kern_execve+0x464 execve() at execve+0x34 start_init() at start_init+0x2ec fork_exit() at fork_exit+0x9c fork_trampoline() at fork_trampoline+0x8 db> I understand it is possible on CURRENT that it might occassionally do this, but I just wanted to let you know. Looks like my best bet is to revert back to the 2008-12 snapshot, which boots fine. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: From: Marius Strobl To: Henry Karpatskij Cc: freebsd-gnats-submit@freebsd.org Subject: Re: sparc64/132641: CURRENT as of 2009-03-14 panics on boot Date: Thu, 19 Mar 2009 15:04:14 +0100 On Sat, Mar 14, 2009 at 09:32:05PM +0000, Henry Karpatskij wrote: > > I built the latest CURRENT and it panics on boot: > > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 160.000MB/s transfers (80.000MHz DT, offset 62, 16bit) > da0: Command Queueing Enabled > da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) > da1 at sym0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 160.000MB/s transfers (80.000MHz DT, offset 62, 16bit) > da1: Command Queueing Enabled > da1: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C) > GEOM: da0: adding VTOC8 information. > Trying to mount root from ufs:/dev/da0a > panic: vm_fault: fault on nofault entry, addr: f35de000 > cpuid = 0 > KDB: enter: panic > [thread pid 1 tid 100002 ] > Stopped at kdb_enter+0x80: ta %xcc, 1 > db> trace > Tracing pid 1 tid 100002 td 0xfffff80001097b80 > panic() at panic+0x20c > vm_fault() at vm_fault+0x19c > trap_pfault() at trap_pfault+0x340 > trap() at trap+0x354 > -- fast data access mmu miss tar=0xf35de000 %o7=0xc030244c -- > exec_elf64_imgact() at exec_elf64_imgact+0x174 > kern_execve() at kern_execve+0x464 > execve() at execve+0x34 > start_init() at start_init+0x2ec > fork_exit() at fork_exit+0x9c > fork_trampoline() at fork_trampoline+0x8 > db> > > I understand it is possible on CURRENT that it might occassionally do this, but I just wanted to let you know. Looks like my best bet is to revert back to the 2008-12 snapshot, which boots fine. Could you please try again with updates sources? I can't reproduce this problem but it was most likely introduced with r189771 and fixed again in r189919. Marius From: Henry Karpatskij To: Marius Strobl Cc: freebsd-gnats-submit@freebsd.org Subject: Re: sparc64/132641: CURRENT as of 2009-03-14 panics on boot Date: Fri, 20 Mar 2009 09:55:03 +0200 On 19.3.2009, at 16:04, Marius Strobl wrote: > Could you please try again with updates sources? I can't > reproduce this problem but it was most likely introduced > with r189771 and fixed again in r189919. Yes! This did the trick, thank you. I was already installing OpenBSD and got really annoyed by the RAIDFrame. Now I'm happily back with GEOM. :-) -- Henry Karpatskij http://ripe.net/fcgi-bin/whois?searchtext=HK1203-RIPE State-Changed-From-To: open->closed State-Changed-By: marius State-Changed-When: Fri Mar 20 13:45:02 UTC 2009 State-Changed-Why: Close; submitter confirms that the problem no longer exists with the backtrace indicating that it was caused by the bug fixed in r189919. http://www.freebsd.org/cgi/query-pr.cgi?pr=132641 >Unformatted: