Subject : latest -git: suspend: unable to handle kernel paging request Submitter : "Vegard Nossum" <vegard.nossum@gmail.com> Date : 2008-08-21 17:28 References : http://marc.info/?l=linux-kernel&m=121933974928881&w=4 Handled-By : "Rafael J. Wysocki" <rjw@sisk.pl> Handled-By : "Pekka Enberg" <penberg@cs.helsinki.fi> Handled-By : Pavel Machek <pavel@suse.cz> This entry is being used for tracking a regression from 2.6.26. Please don't close it until the problem is fixed in the mainline.
On Friday, 12 of September 2008, Vegard Nossum wrote: > On Fri, Sep 12, 2008 at 9:06 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote: > > This message has been generated automatically as a part of a report > > of recent regressions. > > > > The following bug entry is on the current list of known regressions > > from 2.6.26. Please verify if it still should be listed and let me know > > (either way). > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11407 > > Subject : suspend: unable to handle kernel paging request > > Submitter : Vegard Nossum <vegard.nossum@gmail.com> > > Date : 2008-08-21 17:28 (23 days old) > > References : http://marc.info/?l=linux-kernel&m=121933974928881&w=4 > > Handled-By : Rafael J. Wysocki <rjw@sisk.pl> > > Pekka Enberg <penberg@cs.helsinki.fi> > > Pavel Machek <pavel@suse.cz> > > I'm sorry for not replying sooner. This is current status: Problem was > never resolved. I tried to bisect, but I only ran into other problems > with either config not being supported for my machine prior to certain > date while trying to find a good bisection point. It's been a while > now, so I don't remember everything exactly, but I may try to > reproduce it tomorrow on the latest -git and see what comes up. > > Will report back as soon as I have more info. Thanks,
The first reported oops is here: static inline int lock_and_freeze_slab(struct kmem_cache_node *n, struct page *page) { if (slab_trylock(page)) { =====> list_del(&page->lru); n->nr_partial--; __SetPageSlubFrozen(page); return 1; } return 0; } I'm guessing the page isn't on an lru list, or the list is corrupted.
Second reported oops could be one of several list_add() operations; they all operate on &page->lru.
This problem seems not to be reproducible any more. Closing.