On Fri, Nov 16, 2001 at 09:50:02AM -0500, Justin S. Peavey wrote to To [email protected]: > On Thu, Nov 15, 2001 at 07:11:26PM -0500, Karl Heinz Kremer wrote to Cc > [email protected]: > > I read your post on the usb group, and your suspicion that this problem > > is caused by the USB subsystem is very likely correct. The scan times > > you are listing are definitely not right. You should get about the > > same times as you list for the Windows driver. I suspect that it has > > to do with your dual CPU setup. > > > > Sorry, but I can not help to solve this problem. > > > > Karl Heinz > > > > I'm going to try a non-SMP kernel tonight to see if that does > anything. The other thing that is tickling my mind is the shared > interrupts, USB, SCSI, and Network card all sharing the same one. I > understand this is much more common now, but the problem looks similar > to a slowly or mis-handled interrupt. Anyone know how to force USB to > it's own interrupt? > > -JSP >
On the nose Karl, the scanning works fine when I boot with a non-SMP kernel. I'll continue this on the linux-usb group. Thanks for your help! -JSP
