Attachment 125722 Details for Bug 97310 – kernel log

kernel log

i915-crash-20160809.txt (text/plain), 3.57 KB, created by gene on 2016-08-11 22:52:06 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: gene

Created: 2016-08-11 22:52:06 UTC

Size: 3.57 KB

patch

obsolete

>Aug 09 20:55:52 wise kernel: BUG: unable to handle kernel NULL pointer dereference at 00000000000000b0
>Aug 09 20:55:52 wise kernel: IP: [<ffffffffa08a19e0>] intel_fbdev_restore_mode+0x70/0xb0 [i915]
>Aug 09 20:55:52 wise kernel: PGD 8418db067 PUD 841bec067 PMD 0 
>Aug 09 20:55:52 wise kernel: Oops: 0000 [#1] PREEMPT SMP
>Aug 09 20:55:52 wise kernel: Modules linked in: joydev mousedev input_leds hid_logitech_hidpp hid_logitech_dj usbhid btusb btrtl arc4 ir_rc6_decoder iTCO_wdt iTCO_vendor_support evdev mac_hid intel_rapl x86_pkg_temp
>Aug 09 20:55:52 wise kernel:  battery rc_core pinctrl_sunrisepoint pinctrl_intel kfifo_buf tpm_tis tpm_tis_core video industrialio hid tpm acpi_pad button sch_fq_codel nfs nfsd auth_rpcgss oid_registry nfs_acl lockd
>Aug 09 20:55:52 wise kernel: CPU: 0 PID: 324 Comm: Xorg.wrap Not tainted 4.8.0-10-custom #1
>Aug 09 20:55:52 wise kernel: Hardware name:                  /NUC6i5SYB, BIOS SYSKLi35.86A.0045.2016.0527.1055 05/27/2016
>Aug 09 20:55:52 wise kernel: task: ffff880848836740 task.stack: ffff8808408cc000
>Aug 09 20:55:52 wise kernel: RIP: 0010:[<ffffffffa08a19e0>]  [<ffffffffa08a19e0>] intel_fbdev_restore_mode+0x70/0xb0 [i915]
>Aug 09 20:55:52 wise kernel: RSP: 0018:ffff8808408cfdd0  EFLAGS: 00010246
>Aug 09 20:55:52 wise kernel: RAX: 0000000000000000 RBX: ffff88084818a400 RCX: 00000000000d7100
>Aug 09 20:55:52 wise kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8808418c0068
>Aug 09 20:55:52 wise kernel: RBP: ffff8808408cfdd8 R08: 000000000001b2c0 R09: ffffffffa06391d6
>Aug 09 20:55:52 wise kernel: R10: ffffea002108b0c0 R11: 000000009fe6229b R12: ffff8808418c0000
>Aug 09 20:55:52 wise kernel: R13: ffff8808428d5ed8 R14: dead000000000200 R15: dead000000000100
>Aug 09 20:55:52 wise kernel: FS:  00007fcf48be8440(0000) GS:ffff88086ec00000(0000) knlGS:0000000000000000
>Aug 09 20:55:52 wise kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>Aug 09 20:55:52 wise kernel: CR2: 00000000000000b0 CR3: 0000000841bc2000 CR4: 00000000003406f0
>Aug 09 20:55:52 wise kernel: Stack:
>Aug 09 20:55:52 wise kernel:  ffff8808418c0000 ffff8808408cfde8 ffffffffa080305e ffff8808408cfe08
>Aug 09 20:55:52 wise kernel:  ffffffffa061e3ee ffff8808428d5e00 ffff8808418c0000 ffff8808408cfe60
>Aug 09 20:55:52 wise kernel:  ffffffffa061e748 0000000000000286 ffff8808418c01d8 ffff8808497371e0
>Aug 09 20:55:52 wise kernel: Call Trace:
>Aug 09 20:55:52 wise kernel:  [<ffffffffa080305e>] i915_driver_lastclose+0xe/0x20 [i915]
>Aug 09 20:55:52 wise kernel:  [<ffffffffa061e3ee>] drm_lastclose+0x2e/0x120 [drm]
>Aug 09 20:55:52 wise kernel:  [<ffffffffa061e748>] drm_release+0x268/0x380 [drm]
>Aug 09 20:55:52 wise kernel:  [<ffffffff811fabff>] __fput+0x9f/0x1e0
>Aug 09 20:55:52 wise kernel:  [<ffffffff811fad7e>] ____fput+0xe/0x10
>Aug 09 20:55:52 wise kernel:  [<ffffffff81098180>] task_work_run+0x80/0xa0
>Aug 09 20:55:52 wise kernel:  [<ffffffff8100366a>] exit_to_usermode_loop+0xba/0xc0
>Aug 09 20:55:52 wise kernel:  [<ffffffff81003b2e>] syscall_return_slowpath+0x4e/0x60
>Aug 09 20:55:52 wise kernel:  [<ffffffff815d0afa>] entry_SYSCALL_64_fastpath+0xa2/0xa4
>Aug 09 20:55:52 wise kernel: Code: 83 d0 00 00 00 00 00 00 00 48 89 df e8 8a 6e e5 ff 85 c0 75 d4 48 8b 43 08 48 8d 78 68 e8 09 ca d2 e0 48 8b 83 c8 00 00 00 31 f6 <48> 8b b8 b0 00 00 00 e8 64 59 ff ff 48 8b 7b 08 4
>Aug 09 20:55:52 wise kernel: RIP  [<ffffffffa08a19e0>] intel_fbdev_restore_mode+0x70/0xb0 [i915]
>Aug 09 20:55:52 wise kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
>Aug 09 20:55:52 wise kernel:  RSP <ffff8808408cfdd0>
>Aug 09 20:55:52 wise kernel: CR2: 00000000000000b0
>Aug 09 20:55:52 wise kernel: ---[ end trace 4f082bf9ec01934c ]---

Actions: View

Attachments on bug 97310: 125722

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.