Date: Thu, 25 Sep 2003 20:37:11 -0700 From: Brandon Fosdick <bfoz@terrandev.com> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: Andrew Atrens <atrens@nortelnetworks.com> Subject: Re: fix/workaround for usb probe lockups on nForce2 mbs Message-ID: <3F73B467.5080500@terrandev.com> In-Reply-To: <200309251850.aa69426@salmon.maths.tcd.ie> References: <200309251850.aa69426@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
Ian Dowse wrote: > In message <3F72659E.8090809@nortelnetworks.com>, Andrew Atrens writes: > >>The attached patch fixes the boot lockups I've been experiencing on my >>nForce2 (A7N8X-Deluxe) motherboards when usb devices are on the bus at >>boot time. >> >>Looks like something in usb_explore is (inadvertently?) enabling >>interrupts if it detects a device on a port. The fix is, during hub >>attach, to not assume that interrupts are off when we access the hub in >>'polling' mode. > > > Great, thanks for tracking it down! It sounds very similar to a > problem people were having before with FAST_IPSEC where interrupts > were being enabled and confusing the USB code. You have a "uhci" > rather than an "ohci" controller I assume? If so, coould you try > the following patch instead? Unfortunately I don't have anything > to test this on, but it in theory it should work around this class > of problems by backporting from -CURRENT some logic for avoiding > interrupts in polling mode. My A7N8X-Deluxe has an ohci, not a uhci. I haven't tried either patch yet, but I will in a minute.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F73B467.5080500>