From owner-freebsd-questions@FreeBSD.ORG Fri Sep 28 14:38:02 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 695DC106566B for ; Fri, 28 Sep 2012 14:38:02 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 21E5B8FC15 for ; Fri, 28 Sep 2012 14:38:01 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1THbhW-0006uB-66 for freebsd-questions@freebsd.org; Fri, 28 Sep 2012 16:37:58 +0200 Received: from 79-139-19-75.prenet.pl ([79.139.19.75]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Sep 2012 16:37:58 +0200 Received: from jb.1234abcd by 79-139-19-75.prenet.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 Sep 2012 16:37:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: jb Date: Fri, 28 Sep 2012 14:37:39 +0000 (UTC) Lines: 58 Message-ID: References: <5065A533.1030103@intersonic.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 79.139.19.75 (Mozilla/5.0 (X11; FreeBSD i386; rv:15.0) Gecko/20100101 Firefox/15.0.1) Subject: Re: boot error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2012 14:38:02 -0000 Per olof Ljungmark intersonic.se> writes: > ... > Try a verbose boot. I forgot to mention: $ uname -a FreeBSD localhost.localdomain 9.1-RC1 FreeBSD 9.1-RC1 #0: Tue Aug 14 03:56:40 UTC 2012 root@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 I set Verbose ON and put hw.usb.ugen.debug="1" in /boot/loader.conf as originally ugen(4) driver followed the point of lockup. This time the log sequence was a little different - the ata(4) driver followed the point of lockup. If I understand it correctly, these log messages may be recorded in somewhat random sequence, so the dmesg output sequence in not 100% reliable. Anyway, here it is: $ dmesg -a ... usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 usbus6: 480Mbps High Speed USB v2.0 < HERE THE BOOT LOCKUP HAPPENED <===================================== ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x10000 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 ugen6.1: at usbus6 uhub6: on usbus6 ahcich0: AHCI reset... ... More ideas what to look for or catch ? jb