BUG: unable to handle kernel NULL pointer dereference at 0000000000000068

[Alain RENARD]

Apparently alert when launching hamachi-gui

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: alain 2094 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 16'
   Mixer name : 'Realtek ALC660-VD'
   Components : 'HDA:10ec0660,10430000,00100001 HDA:15433155,10431335,00100700'
   Controls : 23
   Simple ctrls : 15
Date: Fri Oct 30 10:36:52 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=a2b2a104-5382-4132-9699-7b77163fef0c
MachineType: ASUSTeK Computer Inc. F3JC
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: root=UUID=3bc286eb-d078-4a37-8524-e1184d805a50 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
SourcePackage: linux
Tags: kernel-oops
Title: BUG: unable to handle kernel NULL pointer dereference at 0000000000000068
Uname: Linux 2.6.31-14-generic x86_64
WpaSupplicantLog:

dmi.bios.date: 01/25/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 304T00
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: F3JC
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr304T00:bd01/25/2007:svnASUSTeKComputerInc.:pnF3JC:pvr1.0:rvnASUSTeKComputerInc.:rnF3JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: F3JC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 437258, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.