general protection fault: 0000 [#1] SMP

[Ertan Günay]

after booted and logged in system gave an error.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-7-generic 4.2.0-7.7
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: egtaroot 1814 F.... pulseaudio
 /dev/snd/controlC1: egtaroot 1814 F.... pulseaudio
Date: Sat Sep 12 15:06:51 2015
Failure: oops
HibernationDevice: RESUME=UUID=1f126905-ef92-4f88-a1c9-de5d23389d16
InstallationDate: Installed on 2015-08-16 (27 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150815.1)
IwConfig:
 enp3s0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=40ffe8ef-a968-42ab-9e9a-d648e8a9fb4c ro quiet splash video=uvesafb:mode_option=1400x900-24,mtrr=3,scroll=ywrap vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
RfKill:

SourcePackage: linux
Title: general protection fault: 0000 [#1] SMP
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0603
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5G41-M LX
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.:bvr0603:bd06/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.3 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc1-unstable/

[Ertan Günay (ergunay)]

Hi Joseph
This problem happened once
I don't get this error anymore.

Thanks
Ertan

[Ertan Günay (ergunay)]

Hi Joseph
I have some problems with PulseAudio.
I noticed that
If I listen music from online radio in Rhythmbox,
And meanwhile if I check my twitter page
And there is a video in twitter page,
Rhythmbox crashs on very video on twitter page.

Radio Station:
http://windows.showradyo.com.tr

Browser:
Mozilla Firefox v41.0.2

Error:
Couldn't start playback
Failed to open output device: pa_stream_writable_size() failed: Connection terminated

Thanks
Ertan

[Ertan Günay (ergunay)]

I haven't seen this problem again.

[Joel Barnes (joel-s-barnes)]

I can recreate this consistently on a new installation of 15.10. See this thread. After I log in, I get between 0-5 occurrences of this exact error and similar errors about unable to access memory addresses.

I have NOT had the system destabilize on me yet, but I've also avoided carrying out any meaningful work while I try to resolve my boot issues. Other than browsing the web and researching linux errors, not much to be done.

[Joel Barnes (joel-s-barnes)]

The (possibly related) issue I referenced above: http://askubuntu.com/questions/707971/must-boot-through-recovery-mode-new-nvidia-drivers-installed