From owner-freebsd-current@FreeBSD.ORG Sat Aug 15 19:38:55 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE5E1106568D for ; Sat, 15 Aug 2009 19:38:55 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id 2A7608FC3F for ; Sat, 15 Aug 2009 19:38:54 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=ztB5IKwwM-XClAVvM08A:9 a=iL-M_UcLpLzaTi7DFysA:7 a=U6eVZ8IpzliUeIXAWma8Ahxn-6IA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe05.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1193709724; Sat, 15 Aug 2009 21:38:53 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sat, 15 Aug 2009 21:39:01 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-BETA2; KDE/4.2.4; i386; ; ) References: <791271c80908151025k344d906ar17cc585ae70927c7@mail.gmail.com> In-Reply-To: <791271c80908151025k344d906ar17cc585ae70927c7@mail.gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908152139.02493.hselasky@c2i.net> Cc: Deniz Subject: Re: unable to mount root from USB 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: Sat, 15 Aug 2009 19:38:55 -0000 On Saturday 15 August 2009 19:25:54 Deniz wrote: > Hello, > > today I updated my sources (CURRENT) and built a new system (world + > kernel). > But unfortunately, this action didn't end well 'cause I'm not able to boot > Freebsd > from my Maxtor One Touch USB HDD anymore. > Even booting from kernel.old doesnt't work anymore (tried everything: > normal, single user mode, acpi disabled/enabled). > > Here is a short part of the boot messages (copied it manually): > > ################################## > > usbus0: 12Mbps Full Speed USB v1.0 > usbus1: 12Mbps Full Speed USB v1.0 > usbus2: 12Mbps Full Speed USB v1.0 > usbus3: 12Mbps Full Speed USB v1.0 > usbus4: 480Mbps High Speed USB v2.0 > SMP: AP CPU #1 Launched! > Root mount wainting for: usbus4 usbus3 usbus2 usbus1 usbus0 > ugen0.1: at usbus0 > uhub0: on usbus0 > uhub0: 2 ports with 2 removable, self powered > ugen1.1: at usbus0 > uhub1: on usbus1 > uhub1: 2 ports with 2 removable, self powered > ugen4.1: at usbus4 > uhub2: on usbus 4 > Root mount wainting for: usbus4 usbus3 usbus2 > Root mount wainting for: usbus4 usbus3 usbus2 > Root mount wainting for: usbus4 usbus3 usbus2 > uhub2: 8 ports with 8 removable, self powered > ugen2.1: at usbus2 > uhub3: on usbus2 > uhub3: 2 ports with 2 removable, self powered > ugen3.1: at usbus3 > uhub4: on usbus3 > uhub4: 2 ports with 2 removable, self powered > Root mount waiting for: usbus4 > usb_alloc_device:1626: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT! > Root mount wainting for: usbus4 > Root mount wainting for: usbus4 > usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT! > Root mount wainting for: usbus4 > Root mount wainting for: usbus4 > usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed, > USB_ERR_TIMEOUT! > ugen4.2: <(null)> at usbus4 (disconnected) > uhub_reattach_port:440: could not allocate new device! > Trying to mount root from ufs:/dev/da0s4a > > ######## [and the HDD suddenly shuts down] ########## > > ROOT MOUNT ERROR: > If you have invalid mount options, rebott, and first try the following from > the loader prompt: > > set vfs.root.mountfrom.options=rw > > and the remove invalid mount options from /etc/fstab. > > Loader variables: > vfs.root.mountfrom=ufs:/dev/da0s4a > vfs.root.mountform.options=rw > > [manual boot prompt] > mountroot> ? > > List of GEOM managed disk devices: > > Loader variables: > .... > > ################################## > > I hope this problem wasn't reported already, but I did not found > everything. This was not reported as a PR, 'cause I don't know if this is a > real bug or just my fault. You could try setting the following sysctl: hw.usb.ehci.no_hs=1 --HPS