*** This bug is a duplicate of bug 1680904 ***
https://bugs.launchpad.net/bugs/1680904
bleh, whatever gets this bug fixed.
** This bug has been marked a duplicate of bug 1680904
zesty unable to handle kernel NULL pointer dereference
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677673
Title:
System soft-freezes, BUG: unable to handle kernel NULL pointer
dereference at 0000000000000018 in journalctl at
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250
Status in linux package in Ubuntu:
Confirmed
Bug description:
I just upgraded to 17.04. It appears that now leaving the system
locked for long enough now makes it unable to respond to any input but
SysRq.
This apepars to be the only relevant bit in `journalctl --boot -1`:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
PGD 0
Oops: 0002 [#1] SMP
Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE)
vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4
iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek
snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress
ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel
pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci
i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100
CPU: 3 PID: 3826 Comm: chrome Tainted: G OE 4.10.0-14-generic
#16-Ubuntu
Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015
task: ffff99ddb372da00 task.stack: ffffb0ec037dc000
RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
RSP: 0018:ffffb0ec037df880 EFLAGS: 00010246
RAX: ffff99dd0367b880 RBX: 0000000000000003 RCX: 0000000000000003
RDX: 0000000000000000 RSI: ffff99ddb737e000 RDI: ffff99de4ad90000
RBP: ffffb0ec037df8d8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: ffff99ddc994a000
R13: ffff99dcd02e2bf0 R14: 00000000fffdf000 R15: 0000000000008000
FS: 00007fd3a0fa7b00(0000) GS:ffff99de5e580000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000018 CR3: 0000000174607000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
? __alloc_pages_nodemask+0xff/0x260
gen8_alloc_va_range+0x23d/0x470 [i915]
i915_vma_bind+0x7e/0x170 [i915]
__i915_vma_do_pin+0x2a5/0x450 [i915]
i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
? radix_tree_lookup_slot+0x22/0x50
? shmem_getpage_gfp+0xf9/0xc10
i915_gem_execbuffer2+0xa1/0x1e0 [i915]
drm_ioctl+0x21b/0x4c0 [drm]
? i915_gem_execbuffer+0x310/0x310 [i915]
? __seccomp_filter+0x67/0x250
do_vfs_ioctl+0xa3/0x610
? __secure_computing+0x3f/0xd0
? syscall_trace_enter+0xcd/0x2e0
SyS_ioctl+0x79/0x90
do_syscall_64+0x5b/0xc0
entry_SYSCALL64_slow_path+0x25/0x25
RIP: 0033:0x7fd39a33a907
RSP: 002b:00007ffff6323818 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000018a20a505000 RCX: 00007fd39a33a907
RDX: 00007ffff6323860 RSI: 00000000c0406469 RDI: 000000000000000e
RBP: 00007ffff6323860 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000038 R11: 0000000000000246 R12: 00000000c0406469
R13: 000000000000000e R14: 0000000000000000 R15: 0000000000000000
Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8
ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab
08 0f 1f 44 00
RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP:
ffffb0ec037df880
CR2: 0000000000000018
---[ end trace 2a4103476767c23b ]---
I walked to my computer 12 minutes later, finding it soft-locked as
described above.
I realize that this appears somewhat far removed from the real cause
of the problem, so please let me know what other data I can provide to
facilitate the debugging process.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-14-generic 4.10.0-14.16
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: sraffa 2780 F.... pulseaudio
/dev/snd/controlC0: sraffa 2780 F.... pulseaudio
CurrentDesktop: Unity:Unity7
Date: Thu Mar 30 17:44:00 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640
InstallationDate: Installed on 2015-11-02 (514 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. Latitude E7250
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.10.0-14-generic N/A
linux-backports-modules-4.10.0-14-generic N/A
linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-03-29 (0 days ago)
dmi.bios.date: 11/18/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0V8RX3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA09:bd11/18/2015:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0V8RX3:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7250
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
