From owner-freebsd-current@FreeBSD.ORG Sun Aug 5 16:30:02 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CC7916A41A for ; Sun, 5 Aug 2007 16:30:02 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.bluestop.org (muon.bluestop.org [80.68.94.188]) by mx1.freebsd.org (Postfix) with ESMTP id 0944F13C46E for ; Sun, 5 Aug 2007 16:30:01 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from [10.0.10.23] (dyn-62-56-85-40.dslaccess.co.uk [62.56.85.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTP id EF0D930122; Sun, 5 Aug 2007 16:54:40 +0100 (BST) Message-ID: <46B5F38D.8090806@cran.org.uk> Date: Sun, 05 Aug 2007 16:58:05 +0100 From: Bruce Cran User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Michel Talon References: <20070805100429.GA29553@lpthe.jussieu.fr> In-Reply-To: <20070805100429.GA29553@lpthe.jussieu.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Panic with current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Aug 2007 16:30:02 -0000 Michel Talon wrote: > Hello, > > i have tried the following recent snapshot of CURRENT on my laptop: > http://snapshots.us.freebsd.org/snapshots/2007-08-03/7.0-20070803-SNAP-i386-bootonly.iso > it boots OK but panics when probing hardware. Very strangely at this > point it says "Going nowhere without my init!" while it has already > found sysinstall as init. It then drops to the debugger, the backtrace > says it was in kern_exit after a syscall, and no more. Sorry the laptop > has nos serial port so i don't have a better trace. > > The laptop is a Sony VGN-C1, with a Core 2 Duo. It works with > FreeBSD-6.2. The boot messages appear normal, in particular the hardware > seems detected except the wifi, and acpi seems to work. The same above > iso works OK on another machine. > I get the same panic with the June i386 snapshot on my Dell Inspirpon 1501 (which has a dual core AMD Turion TL52 CPU). It doesn't have a serial port or firewire, so I can't capture a complete log of the boot and crash. However, I've copied the last boot messages and the backtrace below. I also tried booting with ACPI disabled, but the system paniced much earlier during the boot process with a GPF. ... acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 GEOM: new disk ad4 GEOM_LABEL: Label for provider ad4s3 is msdosfs/NEW VOLUME. Trying to mount root from ufs:/dev/md0 start_init: trying /sbin/init start_init: trying /sbin/oinit start_init: trying /sbin/init.bak start_init: trying /rescue/init start_init: trying /stand/sysinstall /stand/sysinstall running as init on vty0 acpi0_check: nexus0 attached acpi0_check: apic0 attached acpi0_check: legacy0 not-present acpi0_check: ram0 attached acpi0_check: nxp0 attached acpi0_check: acpi0 attached [The screen goes blue] BARF 148 <86> panic: Going nowhere without my init! cpuid = 1 KDB: enter: panic [thread pid 1 tid 100006 ] Stopped at kdb_enter+0x32: leave db> tr Tracing pid 1 tid 100006 td 0xc40bb400 kdb_enter ... panic ... exit1 ... sys_exit ... syscall(dfaf7d38) at syscall+0x288 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x814f2cb, esp = 0xbfbfdd9c, ebp = 0xbfbfdda8 --- db> ps ... ... 11 0 0 0 RL CPU 0 [idle: cpu0] 10 0 0 0 RL [idle: cpu1] 1 0 1 0 RLs+ CPU 1 [sysinstall] 0 0 0 0 WLs [swapper] db> -- Bruce Cran