Bug 14011 - Kernel paging request failed in kmem_cache_alloc
Summary: Kernel paging request failed in kmem_cache_alloc
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: i386 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_i386
URL:
Keywords:
Depends on:
Blocks: 13615
  Show dependency tree
 
Reported: 2009-08-19 22:09 UTC by Rafael J. Wysocki
Modified: 2009-08-26 21:01 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.31-rc5-git5
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description Rafael J. Wysocki 2009-08-19 22:09:24 UTC
Subject    : Oops w/ 2.6.31-rc5-git5
Submitter  : Matthias Dahl <ml_kernel@mortal-soul.de>
Date       : 2009-08-10 22:26
References : http://marc.info/?l=linux-kernel&m=124993603825082&w=4

This entry is being used for tracking a regression from 2.6.30.  Please don't
close it until the problem is fixed in the mainline.
Comment 1 Rafael J. Wysocki 2009-08-26 21:01:36 UTC
On Wednesday 26 August 2009, Pekka Enberg wrote:
> On Wed, Aug 26, 2009 at 5:01 PM, Matthias Dahl<ml_kernel@mortal-soul.de>
> wrote:
> >> Can you reproduce the bug without the proprietary nvidia module that
> >> seems to be loaded?
> >
> > I am sorry but I forgot to test that and right now I am not very keen on
> > trying again since this is my primary machine and I had quite some fs
> > corruption (ext4 on md raid5 -> no barriers) the last times. :-( But this
> also
> > happened w/o Xorg ever being run during that session (though naturally the
> > nvidia kernel module was still loaded).
> 
> Sure, I can understand that. The bug looks like regular slab
> corruption which could have been caused the nvidia blob. So I think
> the issue should be closed unless someone can reproduce it without the
> blob.

Note You need to log in before you can comment on or make changes to this bug.