From owner-freebsd-stable@FreeBSD.ORG Wed Jul 9 09:50:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D973D1065672 for ; Wed, 9 Jul 2008 09:50:31 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out0.tiscali.nl (smtp-out0.tiscali.nl [195.241.79.175]) by mx1.freebsd.org (Postfix) with ESMTP id 7A19C8FC1E for ; Wed, 9 Jul 2008 09:50:31 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [212.123.145.58] (helo=guido.klop.ws) by smtp-out0.tiscali.nl with smtp id 1KGWJh-0000u9-NB for ; Wed, 09 Jul 2008 11:50:29 +0200 Received: (qmail 1661 invoked from network); 9 Jul 2008 09:50:27 -0000 Received: from localhost (HELO guido.klop.ws) (127.0.0.1) by localhost with SMTP; 9 Jul 2008 09:50:27 -0000 Date: Wed, 09 Jul 2008 11:50:25 +0200 To: "Paul Schmehl" , "FreeBSD Stable" From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: User-Agent: Opera Mail/9.51 (FreeBSD) Cc: Subject: Re: UMASS problem on 7.0 STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 09:50:31 -0000 On Tue, 08 Jul 2008 20:27:26 +0200, Paul Schmehl wrote: > Ever since I upgraded this workstation to 7.0 STABLE, I have been unable > to reboot with my USB hard drive attached. During the boot sequence, > the device is properly detected and identified, but then I get an error > message, a crash dump and a reboot. I enabled /var/log/console.log in > the hope that I would catch the error message, but it doesn't appear in > the log. I also don't have any kernel dumps, so I can't trace those to > see what the problem might be. > > An additional problem that I have is that, during boot, the system says > there is no dump device available. This is despite the fact that swap > is twice the real memory size and /etc/defaults/rc.conf defines dumpdev > as auto. I even tried defining dumpdev as the swap partition (in > /etc/rc.conf), but nothing changed. > > I have to be doing something wrong, but I'm at a loss to know what it > is. I've rebuilt world and kernel nine times now, in the desparate hope > that something might have changed in the usb code that would solve this > problem. (Every time "#find /usr/src -newer /boot/kernel" returns > changes in the usb code, I rebuild kernel and world.) > > Is there something I can enable that will capture the boot sequence > during a failed boot while devices are still being detected? > > # grep -i umass /var/log/console.log > > > Any helpful hints would be gratefully appreciated. > > # uname -a > FreeBSD utd65257.utdallas.edu 7.0-STABLE FreeBSD 7.0-STABLE #8: Mon Jul > 7 10:41:03 CDT 2008 > root@utd65257.utdallas.edu:/usr/obj/usr/src/sys/GENERIC i386 > > # sysctl -a | grep hw.physmem > hw.physmem: 3474407424 > > # dmesg | grep -i umass > umass0: 2> on uhub5 > da0 at umass-sim0 bus 0 target 0 lun 0 > > # grep swap /etc/fstab > /dev/ad8s1b none swap sw 0 0 > > # swapctl -l > Device: 1024-blocks Used: > /dev/ad8s1b 8388608 0 > > # grep -i usb /var/run/dmesg.boot > uhci0: port 0xff20-0xff3f irq 16 at > device 26.0 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhci1: port 0xff00-0xff1f irq 17 at > device 26.1 on pci0 > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > ehci0: mem 0xfebd9c00-0xfebd9fff irq > 22 at device 26.7 on pci0 > usb2: waiting for BIOS to give up control > usb2: EHCI version 1.0 > usb2: wrong number of companions (3 != 2) > usb2: companion controllers, 2 ports each: usb0 usb1 > usb2: on ehci0 > usb2: USB revision 2.0 > uhub2: on usb2 > ums0: on > uhub3 > uhci2: port 0xff80-0xff9f irq 23 at > device 29.0 on pci0 > usb3: on uhci2 > usb3: USB revision 1.0 > uhub4: on usb3 > uhci3: port 0xff60-0xff7f irq 17 at > device 29.1 on pci0 > usb4: on uhci3 > usb4: USB revision 1.0 > uhub5: on usb4 > uhci4: port 0xff40-0xff5f irq 18 at > device 29.2 on pci0 > usb5: on uhci4 > usb5: USB revision 1.0 > uhub6: on usb5 > ehci1: mem 0xff980800-0xff980bff irq > 23 at device 29.7 on pci0 > usb6: waiting for BIOS to give up control > usb6: timed out waiting for BIOS > usb6: EHCI version 1.0 > usb6: companion controllers, 2 ports each: usb3 usb4 usb5 > usb6: on ehci1 > usb6: USB revision 2.0 > uhub7: on usb6 > It might be something else, but I had usb problems in 6-STABLE until I disabled usb support in the bios. FreeBSD still detects the usb hardware. In my case there was some sort of conflict between the usb detection of the bios and the detection FreeBSD. The symptoms where very weird, because it also depended on the connected usb devices on time of boot. Connecting theme after booting did work. Ronald.