Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 12 Oct 2002 21:20:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 12 Oct 2002 21:20:17 -0400 Received: from ip68-4-86-174.oc.oc.cox.net ([68.4.86.174]:19182 "EHLO ip68-4-86-174.oc.oc.cox.net") by vger.kernel.org with ESMTP id ; Sat, 12 Oct 2002 21:20:16 -0400 Date: Sat, 12 Oct 2002 18:26:06 -0700 From: "Barry K. Nathan" To: Greg KH Cc: linux-kernel@vger.kernel.org Subject: Re: [BUG] pl2303 oops in 2.4.20-pre10 (and 2.5 too) Message-ID: <20021013012606.GB10921@ip68-4-86-174.oc.oc.cox.net> References: <20021009233624.GA17162@ip68-4-86-174.oc.oc.cox.net> <20021009235332.GA19351@kroah.com> <20021011023925.GA9142@ip68-4-86-174.oc.oc.cox.net> <20021011170623.GB4123@kroah.com> <20021012063036.GA10921@ip68-4-86-174.oc.oc.cox.net> <20021012205604.GB17162@ip68-4-86-174.oc.oc.cox.net> <20021013004938.GF12469@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021013004938.GF12469@kroah.com> User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1606 Lines: 35 (I didn't see this e-mail when I sent my [PATCH] that seems to work.) On Sat, Oct 12, 2002 at 05:49:39PM -0700, Greg KH wrote: > On Sat, Oct 12, 2002 at 01:56:04PM -0700, Barry K. Nathan wrote: > Ah, thanks for finding this. Yes this does help, a bit. Hm. What /dev > device are you trying to write to, ttyUSB0 or ttyUSB1? Yeah, I think we > need this kind of check back in to fix this problem, but I don't see off > the top of my head how to add it back... /dev/ttyUSB0 > And yes, the problem in 2.5 where you see the device register itself > twice is a known bug (to me at least), it goes away if you disable > CONFIG_USB_SERIAL_GENERIC. It's on my TODO list, which seems to be > getting longer every day... No, it doesn't go away in 2.5 if I disable CONFIG_USB_SERIAL_GENERIC (I just checked). > Any suggestions on how to fix this are appreciated. Basically we don't > want to claim the interface that only has the interrupt endpoint on it > for this device, as we kinda already did in the section entitled END > HORRIBLE HACK FOR PL2303. I guess we could just mark that interface as > claimed already, and then probe() would not get called again. Want to > throw a call to usb_driver_claim_interface() into that section, grabbing > that interface, and see if that works? If I have time today I'll try that. -Barry K. Nathan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/