Subject : Kernel v2.6.36 trouble on USB disconnect Submitter : Ketil Froyn <ketil@froyn.name> Date : 2010-10-29 8:05 Message-ID : AANLkTik5qVxkEGVAA1PSOGk2KTW+ekHpSwttsQEWzWj+@mail.gmail.com References : http://marc.info/?l=linux-kernel&m=128833956503607&w=2 This entry is being used for tracking a regression from 2.6.35. Please don't close it until the problem is fixed in the mainline.
This bug is misclassified. It is a problem with the block layer (or possibly the SCSI layer) and has nothing to do with USB. It should be reassigned.
reassigning...
On Sunday, December 19, 2010, Heinz Diehl wrote: > On 19.12.2010, Rafael J. Wysocki wrote: > > > This message has been generated automatically as a part of a report > > of regressions introduced between 2.6.35 and 2.6.36. > > > > The following bug entry is on the current list of known regressions > > introduced between 2.6.35 and 2.6.36. Please verify if it still should > > be listed and let the tracking team know (either way). > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=22092 > > Subject : Kernel v2.6.36 trouble on USB disconnect > > Submitter : Ketil Froyn <ketil@froyn.name> > > Date : 2010-10-29 8:05 (52 days old) > > Message-ID : > <AANLkTik5qVxkEGVAA1PSOGk2KTW+ekHpSwttsQEWzWj+@mail.gmail.com> > > References : http://marc.info/?l=linux-kernel&m=128833956503607&w=2 > > I guess this may be a duplicate of this one: > http://bugzilla.kernel.org/show_bug.cgi?id=24722
Closing as a duplicate. *** This bug has been marked as a duplicate of bug 24722 ***
On Sun, 19 Dec 2010 bugzilla-daemon@bugzilla.kernel.org wrote: > --- Comment #4 from Rafael J. Wysocki <rjw@sisk.pl> 2010-12-19 14:48:12 --- > Closing as a duplicate. > > *** This bug has been marked as a duplicate of bug 24722 *** Are you sure about this? The error messages don't look at all similar. The error for bug #24722 is a WARN_ONCE in ehci_endpoint_reset(), whereas the error in this bug report is some unspecified problem in disk_replace_part_tbl(). Alan Stern
Not at all, I wanted someone more familiar with the code in question to speak up. :-)
Is this still a problem on 2.6.38.y?
*ping*