BUG: unable to handle kernel NULL pointer dereference at 0000000000000068

[Roosh Ak]

Description: Ubuntu 14.04 LTS
Release: 14.04

----------------------
> HSPA Stick doesn't work
> Can't Restart/Shutdown
----------------------

dmesg.log is attached
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rooshan 2212 F.... pulseaudio
 /dev/snd/controlC0: rooshan 2212 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=b9bd7bf4-27a2-4615-a015-f51dfd3b1ca1
InstallationDate: Installed on 2014-05-28 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: TOSHIBA Satellite L655
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=49d4c839-9bf6-453b-b5b2-18c4399f095b ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-27-generic N/A
 linux-backports-modules-3.13.0-27-generic N/A
 linux-firmware 1.127.2
Tags: trusty
Uname: Linux 3.13.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/23/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.30
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr2.30:bd03/23/2011:svnTOSHIBA:pnSatelliteL655:pvrPSK2JL-00C001:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L655
dmi.product.version: PSK2JL-00C001
dmi.sys.vendor: TOSHIBA

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1324742

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[Roosh Ak (rooshan)]

apport information

[penalvch (penalvch)]

Roosh Ak, thank you for reporting this and helping make Ubuntu better. Could you please provide the full computer model as noted on the sticker (ex. Satellite L655-S5150)?

[Roosh Ak (rooshan)]

Toshiba Satellite L655 PSK2JL-00C001

[penalvch (penalvch)]

Roosh Ak, could you please test the latest upstream kernel available (3.15-rc7) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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-3.15-rc7

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.

[Roosh Ak (rooshan)]

Bug is vanished. checked for 12 hours.

> there was a new bug in the upstream kernel. after waking up from the sleep and opening a file upload dialog lead my computer screen to flash for 3-4 times. there were no errors or whatsoever.

[penalvch (penalvch)]

Roosh Ak, the next step is to fully reverse commit bisect the kernel in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

[Roosh Ak (rooshan)]

I tried this and failed.

> git bisect bad v3.13-trusty

    fatal: Needed a single revision
    Bad rev input: v3.13-trusty

[penalvch (penalvch)]

Roosh Ak, v3.13 would be the revision input, not v3.13-trusty as -trusty is a downstream naming construct.

[Roosh Ak (rooshan)]

Bisecting: 108 revisions left to test after this (roughly 7 steps)
[e2bc44706faa1852471cc101f3c5cdd757dddcd0] Merge tag 'xfs-for-linus-v3.13-rc8' of git://oss.sgi.com/xfs/xfs

done !

[penalvch (penalvch)]

Roosh Ak, the following indicates you have approximately 7 more kernels to test to identify the offending commit:
 Bisecting: 108 revisions left to test after this (roughly 7 steps)
[e2bc44706faa1852471cc101f3c5cdd757dddcd0] Merge tag 'xfs-for-linus-v3.13-rc8' of git://oss.sgi.com/xfs/xfs

[Roosh Ak (rooshan)]

How do I do that ?

I tired bisecting v3.13-rc-8

[9b6c4ea95ff87464e012f70b119601de9e94deac] Merge branch 'core-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

I don't understand how it works. if you could explain on this, It would be helpful me to do this.

[penalvch (penalvch)]

Roosh Ak, you would need to read https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_bisect_the_upstream_kernel.3F .

[Darek (ddarek-ch)]

For casual users I can propose kernel which is free from this bug.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]