BUG: unable to handle kernel paging request at 0000000031325f38 (sys_getdents)

[Nicolás Lichtmaier]

[27952.368812] <#DF> <0> [<ffffffff80215ace>] show_registers+0xee/0x280
[27952.368816] [<ffffffff8069fa91>] __die+0xb1/0x120
[27952.368821] [<ffffffff80215ca3>] die+0x43/0x90
[27952.368824] [<ffffffff8021406a>] do_double_fault+0x6a/0x70
[27952.368827] [<ffffffff80213bd0>] double_fault+0xa0/0xd0
[27952.368830] [<ffffffff802f70c5>] ? sys_getdents+0x45/0xe0

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
DistroRelease: Ubuntu 9.04
Failure: oops
HibernationDevice: RESUME=UUID=514c3239-8cd1-42c1-b55f-3cc6f8498d7b
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
ProcCmdLine: root=UUID=1c8b6b97-3d59-4fbc-a959-b53a69e45285 ro i8042.nomux=1 e quiet splash
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: linux
Tags: kernel-oops
Title: BUG: unable to handle kernel paging request at 0000000031325f38

[Leann Ogasawara (leannogasawara)]

Hi Nicolas,

Can you comment how reproducible this issue is or how often does it occur? Could you try the latest upstream mainline kernel build to try and reproduce the oops? https://wiki.ubuntu.com/KernelMainlineBuilds . Please try 2.6.30-rc7 and let us know your results. Thanks.

[Jim Lieb (lieb)]

Can you also confirm this issue exists with the most recent Karmic Koala 9.10 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . If the issue remains with Karmic it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Thanks in advance.

[Jim Lieb (lieb)]

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Karmic Koala 9.10. To reopen the bug, click on the current status, under the Status column, and change the status back to "New". Thanks.