BUG: unable to handle kernel paging request at 80000000

[Ngassam Nkwenga]

this alert came when I updated my system: Lucid alpha 3( update from 16-03-2010).
I can not reproduce this bug.

ProblemType: KernelOops
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: cyrildz 1176 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xc0500000 irq 16'
   Mixer name : 'Realtek ALC861-VD'
   Components : 'HDA:10ec0862,173410fb,00100001 HDA:10573055,173410fb,00100700'
   Controls : 12
   Simple ctrls : 8
Date: Tue Mar 16 13:41:19 2010
DistroRelease: Ubuntu 10.04
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=UUID=1b5ad1c2-2776-46f4-a9ae-54e875e1326a
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100310)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 0930:0b03 Toshiba Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FUJITSU SIEMENS AMILO Li 1718
Package: linux-image-2.6.32-16-generic 2.6.32-16.25
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=17db952a-5fd0-4e17-a571-2c4f652efaae ro quiet splash nomodeset
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Regression: No
RelatedPackageVersions: linux-firmware 1.32
Reproducible: No
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
TestedUpstream: No
Title: BUG: unable to handle kernel paging request at 80000000
Uname: Linux 2.6.32-16-generic i686
WifiSyslog:
 Mar 16 13:50:50 cyrildz-laptop NetworkManager: <info> (wlan0): supplicant connection state: completed -> group handshake
 Mar 16 13:50:50 cyrildz-laptop NetworkManager: <info> (wlan0): supplicant connection state: group handshake -> completed
dmi.bios.date: 06/14/07
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.7
dmi.board.name: AMILO Li 1718
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: Rev.A
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: ATI
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvrV1.7:bd06/14/07:svnFUJITSUSIEMENS:pnAMILOLi1718:pvr-1:rvnFUJITSUSIEMENS:rnAMILOLi1718:rvrRev.A:cvnATI:ct1:cvrN/A:
dmi.product.name: AMILO Li 1718
dmi.product.version: -1
dmi.sys.vendor: FUJITSU SIEMENS

[Jeremy Foshee (jeremyfoshee)]

Hi Ngassam,

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 539554

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.]