On Thu, 22 Dec 2011 16:28:19 +0530 "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx> wrote: > On 12/21/2011 05:24 AM, Rafael J. Wysocki wrote: > > > [Evidently, vger has blocked the previous attempts to post this message > > for some reason. I wonder why?] > > > > This message contains a list of some regressions from 3.0 and 3.1 > > for which there are no fixes in the mainline known to the tracking team. > > If any of them have been fixed already, please let us know. > > > > If you know of any other unresolved regressions from 3.0 and 3.1, please let us > > know either and we'll add them to the list. Also, please let us know if any of > > the entries below are invalid. > > > > The entries below are simplified and the statistics are not present due to the > > continuing Bugzilla outage. > > > > [...] > > > > > Subject : Freezing of tasks failed after 20.01 seconds in kernel 3.2.0-rc2 > > Submitter : Belisko Marek <marek.belisko@xxxxxxxxx> > > Date : 2011-11-22 21:20 > > Message-ID : > > CAAfyv36nxYq1EA2pcHi5WR1BdWYHp2sQTY1mMA4Q3JjcOG5RDw@xxxxxxxxxxxxxx > > References : http://marc.info/?l=linux-kernel&m=132199691706100&w=2 > > > > > > > I believe we already have a fix for this, but not yet in mainline: > http://thread.gmane.org/gmane.linux.nfs/45336 > I don't believe this is a regression at all. As far as I know, It's always been the case that these sleeps weren't freezable. I even have a similar bug open for RHEL6 which has a 2.6.32-based kernel... If people are seeing this more now, then it might be some subtle difference in timing or differences in what userspace is doing at the time the freezer runs. In any case, the final fix didn't make 3.2, but should go in early for 3.3. -- Jeff Layton <jlayton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
