Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 00000000000000e4

Bug #1589837 reported by Kevin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Regarding the dmesg from the crashdump:

[ 2210.842592] BUG: unable to handle kernel NULL pointer dereference at 00000000000000e4
[ 2210.842631] IP: [<ffffffff816fead6>] sock_poll+0x26/0x120
[ 2210.842659] PGD 0
[ 2210.842670] Oops: 0000 [#1] SMP
[ 2210.842687] Modules linked in: drbg ansi_cprng cdc_ether usbnet r8152 mii nvram rfcomm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) xt_tcpudp bridge stp llc vboxdrv(OE) iptable_filter ip_tables x_tables msr bnep btusb btrtl btbcm btintel bluetooth input_leds joydev bcm5974 nls_iso8859_1 applesmc input_polldev brcmfmac snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic brcmutil cfg80211 thunderbolt bdc_pci intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd intel_pch_thermal lpc_ich snd_hda_intel snd_hda_codec snd_hda_core
[ 2210.843039] snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer mei_me snd mei shpchp soundcore sbs sbshc acpi_als kfifo_buf apple_bl industrialio mac_hid spi_pxa2xx_platform facetimehd(OE) videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media parport_pc ppdev lp parport autofs4 hid_generic hid_apple usbhid hid uas usb_storage i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci libahci drm fjes video
[ 2210.843180] CPU: 3 PID: 3991 Comm: Chrome_IOThread Tainted: G OE 4.4.0-22-generic #40-Ubuntu
[ 2210.843202] Hardware name: Apple Inc. MacBookPro12,1/Mac-E43C1C25D4880AD6, BIOS MBP121.88Z.0167.B14.1509281135 09/28/2015
[ 2210.843226] task: ffff8802611de040 ti: ffff880263a44000 task.ti: ffff880263a44000
[ 2210.843243] RIP: 0010:[<ffffffff816fead6>] [<ffffffff816fead6>] sock_poll+0x26/0x120
[ 2210.843264] RSP: 0018:ffff880263a47d68 EFLAGS: 00010246
[ 2210.843276] RAX: ffffffff81abcbe0 RBX: ffff88022dedf480 RCX: ffff88022c576918
[ 2210.843292] RDX: 0000000000000000 RSI: ffff880263a47db8 RDI: ffff880263c1cf00
[ 2210.843308] RBP: ffff880263a47d90 R08: 0000000000000000 R09: ffff880242c88c18
[ 2210.843324] R10: ffff880244293038 R11: ffff88025f54d8c0 R12: ffff880263a47db8
[ 2210.843340] R13: ffff880263c1cf00 R14: 0000000000000000 R15: 0000000000000000
[ 2210.843356] FS: 00007f4015e73700(0000) GS:ffff88026ecc0000(0000) knlGS:0000000000000000
[ 2210.843374] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2210.843388] CR2: 00000000000000e4 CR3: 00000000821fe000 CR4: 00000000003406e0
[ 2210.843404] Stack:
[ 2210.843409] ffff880263a47e18 0000000000000000 00001ed61c429c00 ffff880263a47ea0
[ 2210.843429] ffff880124d99d98 ffff880263a47df8 ffffffff81254a50 ffff8800821d98a0
[ 2210.843448] ffff880263a47f18 ffff8800821d9840 0000000000000000 0000000000000019
[ 2210.843467] Call Trace:
[ 2210.843476] [<ffffffff81254a50>] ep_send_events_proc+0xb0/0x1c0
[ 2210.843490] [<ffffffff812549a0>] ? ep_ptable_queue_proc+0xa0/0xa0
[ 2210.843505] [<ffffffff812553b9>] ep_scan_ready_list+0x99/0x1f0
[ 2210.843519] [<ffffffff81255718>] ep_poll+0x1d8/0x3d0
[ 2210.843532] [<ffffffff8120cad9>] ? vfs_write+0x149/0x1a0
[ 2210.843545] [<ffffffff81256ae8>] SyS_epoll_wait+0xb8/0xd0
[ 2210.843560] [<ffffffff818252f2>] entry_SYSCALL_64_fastpath+0x16/0x71
[ 2210.843574] Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 45 31 ff 53 48 8b 9f d0 00 00 00 49 89 fd 49 89 f4 4c 8b 73 20 <41> 8b 96 e4 00 00 00 85 d2 0f 84 c2 00 00 00 41 8b 86 e0 00 00
[ 2210.843662] RIP [<ffffffff816fead6>] sock_poll+0x26/0x120
[ 2210.843679] RSP <ffff880263a47d68>
[ 2210.843687] CR2: 00000000000000e4

the problem occurs since yesterday.
probably related to http://googlechromereleases.blogspot.ch/2016/06/stable-channel-update_6.html

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.40
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kevin 2371 F.... pulseaudio
 /dev/snd/controlC1: kevin 2371 F.... pulseaudio
Date: Tue Jun 7 09:38:44 2016
InstallationDate: Installed on 2016-03-01 (97 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Apple Inc. MacBookPro12,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=18e90ec4-bbea-4061-aa6a-a7a46445929d ro quiet splash crashkernel=384M-:128M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-06 (61 days ago)
dmi.bios.date: 09/28/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0167.B14.1509281135
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B14.1509281135:bd09/28/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Kevin (kevinhaefeli) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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.7-rc1 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.7-rc1-yakkety/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key
Revision history for this message
Kevin (kevinhaefeli) wrote :

yes, the issue started happening after an upgrade from 15.10
but there were 2-3 weeks without problems (after the upgrade)
so I think it's probably not directly related to the upgrade.

I'll test the new upstream kernel and update the tag.

Revision history for this message
Kevin (kevinhaefeli) wrote :

actually I can't boot with RC1.
With RC2 the device crashes shortly after the login screen appears.

Revision history for this message
penalvch (penalvch) wrote :

Kevin, does 4.6.2 provide a test to this issue? If not, please test successively earlier kernels to see if a newer version may be tested against.

Revision history for this message
Kevin (kevinhaefeli) wrote : Re: [Bug 1589837] Re: Kernel oops - BUG: unable to handle kernel NULL pointer dereference at 00000000000000e4
Download full text (6.7 KiB)

yes, I can test the issue with 4.6.2 and I can confirm that it still
happens.
Christopher M. Penalver <email address hidden> schrieb am Do.,
9. Juni 2016 um 06:41 Uhr:

> Kevin, does 4.6.2 provide a test to this issue? If not, please test
> successively earlier kernels to see if a newer version may be tested
> against.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1589837
>
> Title:
> Kernel oops - BUG: unable to handle kernel NULL pointer dereference at
> 00000000000000e4
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> Regarding the dmesg from the crashdump:
>
> [ 2210.842592] BUG: unable to handle kernel NULL pointer dereference at
> 00000000000000e4
> [ 2210.842631] IP: [<ffffffff816fead6>] sock_poll+0x26/0x120
> [ 2210.842659] PGD 0
> [ 2210.842670] Oops: 0000 [#1] SMP
> [ 2210.842687] Modules linked in: drbg ansi_cprng cdc_ether usbnet r8152
> mii nvram rfcomm xt_CHECKSUM iptable_mangle ipt_MASQUERADE
> nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4
> nf_nat_ipv4 nf_nat nf_conntrack pci_stub vboxpci(OE) vboxnetadp(OE)
> vboxnetflt(OE) xt_tcpudp bridge stp llc vboxdrv(OE) iptable_filter
> ip_tables x_tables msr bnep btusb btrtl btbcm btintel bluetooth input_leds
> joydev bcm5974 nls_iso8859_1 applesmc input_polldev brcmfmac
> snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic brcmutil
> cfg80211 thunderbolt bdc_pci intel_rapl x86_pkg_temp_thermal
> intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul
> crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper
> cryptd intel_pch_thermal lpc_ich snd_hda_intel snd_hda_codec snd_hda_core
> [ 2210.843039] snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event
> snd_rawmidi snd_seq snd_seq_device snd_timer mei_me snd mei shpchp
> soundcore sbs sbshc acpi_als kfifo_buf apple_bl industrialio mac_hid
> spi_pxa2xx_platform facetimehd(OE) videobuf2_dma_sg videobuf2_memops
> videobuf2_v4l2 videobuf2_core v4l2_common videodev media parport_pc ppdev
> lp parport autofs4 hid_generic hid_apple usbhid hid uas usb_storage i915
> i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops
> ahci libahci drm fjes video
> [ 2210.843180] CPU: 3 PID: 3991 Comm: Chrome_IOThread Tainted: G
> OE 4.4.0-22-generic #40-Ubuntu
> [ 2210.843202] Hardware name: Apple Inc.
> MacBookPro12,1/Mac-E43C1C25D4880AD6, BIOS MBP121.88Z.0167.B14.1509281135
> 09/28/2015
> [ 2210.843226] task: ffff8802611de040 ti: ffff880263a44000 task.ti:
> ffff880263a44000
> [ 2210.843243] RIP: 0010:[<ffffffff816fead6>] [<ffffffff816fead6>]
> sock_poll+0x26/0x120
> [ 2210.843264] RSP: 0018:ffff880263a47d68 EFLAGS: 00010246
> [ 2210.843276] RAX: ffffffff81abcbe0 RBX: ffff88022dedf480 RCX:
> ffff88022c576918
> [ 2210.843292] RDX: 0000000000000000 RSI: ffff880263a47db8 RDI:
> ffff880263c1cf00
> [ 2210.843308] RBP: ffff880263a47d90 R08: 0000000000000000 R09:
> ffff880242c88c18
> [ 2210.843324] R10: ffff880244293038 R11: ffff88025f54d8c0 R12:
> ffff880263a47db8
> [ 2210.843340] R13: ffff880263c1cf00 R14: 0000000000000000...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

Kevin, to keep this relevant to upstream, could you please test the latest mainline kernel (4.7-rc5) and advise to the results?

tags: added: kernel-bug-exist-upstream kernel-bug-exist-upstream-4.6.2 regression-release
tags: added: needs-bisect
Revision history for this message
Kevin (kevinhaefeli) wrote :

Hi,

Im working now with 4.7.0-040700rc5-generic on Ubuntu 16.04 LTS.

no crashes since 4 days. Hurray!

Cheers,
Kevin

Revision history for this message
penalvch (penalvch) wrote :

Kevin, to clarify, how often would the kernel crash occur when using the default Ubuntu kernel?

Revision history for this message
Kevin (kevinhaefeli) wrote :

the kernel crash occured 3-5x in a working day (8.5 hours)

Revision history for this message
penalvch (penalvch) wrote :

Kevin, the next step is to fully reverse commit bisect from kernel 4.4 to 4.7-rc5 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your help.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.