WARNING: at /build/buildd/linux-2.6.31/mm/page_alloc.c:1751 __alloc_pages_slowpath+0x41b/0x4e0()

[hyperandy]

Right after boot up upper right hand corner displayed a crash

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: hyperandy 4898 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,1458a102,00100101'
   Controls : 37
   Simple ctrls : 20
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdffc000 irq 19'
   Mixer name : 'ATI RS690/780 HDMI'
   Components : 'HDA:1002791a,00791a00,00100000'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [off]
Date: Mon Oct 12 16:03:29 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=050aff5c-d19d-4d78-b2bd-01000d97629f
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 vboxnet0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H
NonfreeKernelModules: fglrx
Package: linux-image-2.6.31-13-generic 2.6.31-13.44
ProcCmdLine: root=UUID=3559023e-0473-4569-924c-a5fb423144cb ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-13-generic N/A
 linux-firmware 1.21
RfKill:

SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/mm/page_alloc.c:1751 __alloc_pages_slowpath+0x41b/0x4e0()
Uname: Linux 2.6.31-13-generic x86_64
WpaSupplicantLog:

dmi.bios.date: 05/18/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3a
dmi.board.name: GA-MA790GP-UD4H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF3a:bd05/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA790GP-UD4H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Eric Firing (efiring)]

Looking more closely, I don't think this is the same bug; I am on an Atom processor, and after the first line, the traces look quite different.

[felipe (fegutiva09)]

not sure its the same bug

[Jeremy Foshee (jeremyfoshee)]

Hi hyperandy,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 449819

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]