From owner-freebsd-current  Sun Oct 31 21:40: 2 1999
Delivered-To: freebsd-current@freebsd.org
Received: from bamboo.verinet.com (bamboo.verinet.com [204.144.246.5])
	by hub.freebsd.org (Postfix) with ESMTP id EDE0514BC4
	for <current@freebsd.org>; Sun, 31 Oct 1999 21:40:00 -0800 (PST)
	(envelope-from hibma@skylink.it)
Received: from henny (cherry41.verinet.com [207.174.160.230])
	by bamboo.verinet.com (8.9.3/8.9.3) with SMTP id WAA29023;
	Sun, 31 Oct 1999 22:39:47 -0700
Date: Sun, 31 Oct 1999 21:39:33 -0700 (MST)
From: Nick Hibma <hibma@skylink.it>
X-Sender: n_hibma@henny
Reply-To: Nick Hibma <hibma@skylink.it>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: Christopher Masto <chris@netmonger.net>, usb-bsd@egroups.com,
	current@freebsd.org
Subject: Re: VESA module breaks USB?
In-Reply-To: <199910291505.LAA95902@khavrinen.lcs.mit.edu>
Message-ID: <Pine.BSF.3.96.991031213640.200D-100000@henny>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> >  ohci0: <OPTi 82C861 (FireLink) USB controller> 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've seen this before but not yet spent the time to fix it.

Nick



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message