BUG: unable to handle kernel NULL pointer dereference at (null)

Bug #525198 reported by Higany
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Invalid
Medium
linux (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

 2.6.32-14-generic #20-Ubuntu SMP Sat Feb 20 05:18:19 UTC 2010 x86_64 GNU/Linux
Lucid

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: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: higany 1528 F.... pulseaudio
 /dev/snd/controlC1: higany 1528 F.... pulseaudio
CRDA: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfce78000 irq 20'
   Mixer name : 'Nvidia MCP78 HDMI'
   Components : 'HDA:1106e721,10438345,00100100 HDA:10de0002,10de0101,00100000'
   Controls : 38
   Simple ctrls : 19
Card1.Amixer.info:
 Card hw:1 'SAA7134'/'saa7134[0] at 0xfcfff800 irq 16'
   Mixer name : 'SAA7134 Mixer'
   Components : ''
   Controls : 6
   Simple ctrls : 3
Date: Sat Feb 20 17:17:21 2010
DistroRelease: Ubuntu 10.04
Failure: oops
Frequency: Once a day.
HibernationDevice: RESUME=UUID=29b72926-69c7-438c-8f0e-5eabae1edb39
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux-image-2.6.32-14-generic 2.6.32-14.20
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-14-generic root=UUID=a6c24a15-cc02-40db-8efe-b0eb020b3123 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.30
Reproducible: No
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
TestedUpstream: Yes
Title: BUG: unable to handle kernel NULL pointer dereference at (null)
Uname: Linux 2.6.32-14-generic x86_64
dmi.bios.date: 09/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1309
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3N78-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1309:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-VM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Higany (higany-mailbox) wrote :
Revision history for this message
Chase Douglas (chasedouglas) wrote :

I'm following this bug upstream, so if there's any fixes found there I will report on them here.

Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Changed in linux:
status: Unknown → Confirmed
Changed in linux:
importance: Unknown → Medium
tags: removed: regression-potential
Changed in linux:
status: Confirmed → Invalid
Revision history for this message
penalvch (penalvch) wrote :

Higany, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.