From owner-freebsd-current Sun Oct 31 21:52: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 3CE6314E6F for ; Sun, 31 Oct 1999 21:52:04 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id AAA27583; Mon, 1 Nov 1999 00:51:55 -0500 (EST) Message-ID: <19991101005154.A27488@netmonger.net> Date: Mon, 1 Nov 1999 00:51:55 -0500 From: Christopher Masto To: Nick Hibma , Garrett Wollman Cc: usb-bsd@egroups.com, current@freebsd.org Subject: Re: VESA module breaks USB? References: <199910291505.LAA95902@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Nick Hibma on Sun, Oct 31, 1999 at 09:39:33PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Oct 31, 1999 at 09:39:33PM -0700, Nick Hibma wrote: > > > ohci0: irq 9 at device 11.0 on pci0 > > > +ohci_waitintr: timeout > > > > IRQ 9 is shared with the VGA controller. Perhaps calling the VESA > > BIOS caused it to do something strange that interfered with the > > delivery of this interrupt on your motherboard. > > No, this has something to do with soft resetting vs. hard > resetting. It might be that this is related to soft rebooting out of > Windows. Try switching off and on your machine. I don't have Windows, but I can try a hard boot at some point and see if it helps. I can also try to fiddle with the IRQs just in case, but they are after all being assigned by FreeBSD. For now I've just turned off VESA, but I think it is going to become non-optional at some point and I'd hate to see my USB go away. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message