BUG: unable to handle kernel NULL pointer dereference at 0000000000000068

[Benjamin Halbrock]

openvpn and hamachi interference

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: benjamin 1934 F.... pulseaudio
 /dev/snd/seq: timidity 2194 F.... timidity
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6500000 irq 21'
   Mixer name : 'Nvidia MCP78 HDMI'
   Components : 'HDA:10ec0888,1025013f,00100202 HDA:11c11040,11c10001,00100200 HDA:10de0006,10de0101,00100000'
   Controls : 38
   Simple ctrls : 20
Date: Sun Sep 27 15:12:10 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=09561e77-fd09-4549-8deb-94e260267001
MachineType: Acer Aspire 5930
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-11-generic 2.6.31-11.36
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=bbbba41a-a725-42ff-af65-0afbfe3db43f ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
RelatedPackageVersions: linux-firmware 1.19
SourcePackage: linux
Tags: kernel-oops
Title: BUG: unable to handle kernel NULL pointer dereference at 0000000000000068
Uname: Linux 2.6.31-11-generic x86_64
WpaSupplicantLog:

dmi.bios.date: 10/28/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.23
dmi.board.name: Eiger
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.23:bd10/28/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5930
dmi.product.version: 0100
dmi.sys.vendor: Acer

[Steven Harms (sharms)]

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.

[Benjamin Halbrock (kontakt-bennis-blog)]

I have a fully updated karmic

[Rookcifer (rookcifer)]

I also am getting this kerneloops. Apport gives me the same bug title as this one. However, I am not using vpn or hamachi like the OP.

My bug report is attached.

[Boiler (boiler)]

Still in 9.10 RC when try to launch hamachi

[Alex Forencich (alex-alexelectronics)]

I just got this problem with the latest version of karmic, upgraded from jaunty.

[Gavin Chappell (g-a-c)]

This appears to be related to the UPX compression used by Hamachi (/usr/bin/hamachi is a UPX-compressed executable). A workaround (although not really a fix, as this shouldn't be necessary) is:

1) sudo aptitude install upx-ucl
2) sudo upx -d /usr/bin/hamachi

This will restore Hamachi to its working state in Karmic. However, LogMeIn have recently updated the Windows client and I've emailed them about Linux support, they assure me that Linux support is continuing and they're working on a Linux client to match the features of the Windows version, whether this fix will still be needed and/or valid in the new version I have no idea.

I haven't submitted this bug report to LogMeIn as I'm not sure where it should go; LogMeIn's product worked in previous Ubuntu releases with no problems, and still does when decompressed, so I don't think it's their issue, it sounds more like a Ubuntu/kernel upstream issue to me?

Credit to curtlee2002 on the Ubuntu Forums for finding this fix, linked here - http://ubuntuforums.org/showpost.php?s=1735b54634bd163bbc9313d2647c9162&p=8037569&postcount=8

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