From owner-freebsd-current@FreeBSD.ORG Fri Jan 7 23:03:18 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E895616A4CE; Fri, 7 Jan 2005 23:03:18 +0000 (GMT) Received: from vbook.fbsd.ru (user164.hovrino.net [82.179.232.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E93E43D3F; Fri, 7 Jan 2005 23:03:18 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1Cn38N-0000Nb-PT; Sat, 08 Jan 2005 02:03:07 +0300 From: Vladimir Grebenschikov To: Julian Elischer In-Reply-To: <41D67753.60202@elischer.org> References: <20041228010938.GA39686@freebsd3.cimlogic.com.au> <20041230.111631.13597845.imp@bsdimp.com> <1104542138.3084.9.camel@localhost> <41D67753.60202@elischer.org> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Sat, 08 Jan 2005 02:03:07 +0300 Message-Id: <1105138987.1401.5.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: Randy Bush cc: bluetooth cc: FreeBSD Current cc: "M. Warner Losh" Subject: Re: USB problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 23:03:19 -0000 =F7 =D3=C2, 01/01/2005 =D7 02:11 -0800, Julian Elischer =D0=C9=DB=C5=D4: > Vladimir Grebenschikov wrote: > > =F7 =D0=D4, 31/12/2004 =D7 05:05 -1000, Randy Bush =D0=C9=DB=C5=D4: > >=20 > >>possibly related? > >> > >>just so you know, on a thinkpad t41 with any current in the last > >>few weeks, i kernel panic on boot if a usb device is not plugged > >>in. turning off acpi also allows boot. see > >> > >> > >> > >>i can help debug if anyone is on the trail > >=20 > >=20 > > I have also problems with USB on recent current (previous was few weeks > > old). > >=20 >=20 > the most salient thiing you could do is find the date of the problem by c= hecking=20 > out sys/dev/usb on dec 9 and seeing if that fixes it (you said dec 9 was= ok) > and if so, gradually moving it forward using a binary search and narrowin= g in on=20 > the commit that broke it. So far I tracked it: it works on -D '2004-12-08 12:00' and does not works with -D '2004-12-09 00:00' I guess time is by MSK timezone (my local time). There are a lot of changes between these dates. > Is it an ohci or uhci (or ehci) usb inerface? I think both. It strikes when only ehci umass device attached or when uhci mouse or bluetooth dongle connected. usb0: on uhci0 usb0: USB revision 1.0 usb1: on uhci1 usb1: USB revision 1.0 usb2: on uhci2 usb2: USB revision 1.0 ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 ehci_pci_attach: companion usb2 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 Looks like it is not USB-only problem, I have revert only USB code and it does not helps. So I suppose it is some kind of locking problem. --=20 Vladimir B. Grebenchikov vova@fbsd.ru