Bug 1374679 - [abrt] BUG: unable to handle kernel NULL pointer dereference at 0000000000000250
Summary: [abrt] BUG: unable to handle kernel NULL pointer dereference at 0000000000000250
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:93e1f1a3969f781e7984e327de7...
: 1380640 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-09 12:03 UTC by Jeff Needle
Modified: 2017-08-08 17:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 17:12:55 UTC
Type: ---


Attachments (Terms of Use)
File: dmesg (61.54 KB, text/plain)
2016-09-09 12:03 UTC, Jeff Needle
no flags Details

Description Jeff Needle 2016-09-09 12:03:23 UTC
Description of problem:


Additional info:
reporter:       libreport-2.7.2
BUG: unable to handle kernel NULL pointer dereference at 0000000000000250
IP: [<ffffffff817e91ce>] __ww_mutex_lock+0x1e/0xa0
PGD 0 
Oops: 0002 [#1] SMP
Modules linked in: xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set_hash_net ccm fuse ip_set nfnetlink ebtable_broute bridge stp llc ebtable_nat ip6table_mangle ip6table_raw ip6table_security ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 iptable_mangle iptable_raw iptable_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables bnep arc4 iTCO_wdt iTCO_vendor_support intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iwlmvm mei_wdt kvm mac80211 irqbypass intel_cstate intel_uncore intel_rapl_perf uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 iwlwifi videobuf2_core
 btusb btrtl videodev btbcm cfg80211 joydev btintel bluetooth i2c_i801 media rtsx_pci_ms memstick snd_hda_codec_realtek snd_hda_codec_generic lpc_ich shpchp snd_hda_intel snd_hda_codec snd_hda_core wmi snd_hwdep snd_seq thinkpad_acpi snd_seq_device rfkill snd_pcm snd_timer mei_me mei snd soundcore tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt hid_logitech_hidpp hid_logitech_dj i915 rtsx_pci_sdmmc mmc_core crct10dif_pclmul crc32_pclmul crc32c_intel i2c_algo_bit drm_kms_helper ghash_clmulni_intel drm e1000e serio_raw rtsx_pci ptp pps_core fjes video
CPU: 0 PID: 1157 Comm: systemd-logind Not tainted 4.7.2-201.fc24.x86_64 #1
Hardware name: LENOVO 20ARS0LE00/20ARS0LE00, BIOS GJET77WW (2.27 ) 05/20/2014
task: ffff8803046f1e80 ti: ffff88030f2bc000 task.ti: ffff88030f2bc000
RIP: 0010:[<ffffffff817e91ce>]  [<ffffffff817e91ce>] __ww_mutex_lock+0x1e/0xa0
RSP: 0018:ffff88030f2bf928  EFLAGS: 00010246
RAX: 00000000ffffffff RBX: 0000000000000250 RCX: ffff8800367bc0e0
RDX: 0000000080000000 RSI: ffff88030cec9ac0 RDI: 0000000000000250
RBP: ffff88030f2bf940 R08: 0000000000000400 R09: 0000000000000698
R10: 0000000000000500 R11: 0000000000000698 R12: ffff88030cec9ac0
R13: ffff88030cc9d800 R14: ffff8802eb2d2000 R15: ffff8800c8e34000
FS:  00007fcd6e2e7900(0000) GS:ffff88031e200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000250 CR3: 000000030dd50000 CR4: 00000000001406f0
Stack:
 ffff88030cec9ac0 0000000000000250 ffff88030cc9d800 ffff88030f2bf970
 ffffffffc00b756e ffff88030c0b8000 0000000000000000 ffff8802eb2d2000
 ffff88030cc9d800 ffff88030f2bf9a8 ffffffffc00b8054 ffff8800364ca4c0
Call Trace:
 [<ffffffffc00b756e>] drm_modeset_lock+0x4e/0xd0 [drm]
 [<ffffffffc00b8054>] drm_atomic_get_connector_state+0x34/0x1c0 [drm]
 [<ffffffffc0110f90>] __drm_atomic_helper_set_config+0x2a0/0x360 [drm_kms_helper]
 [<ffffffffc01121da>] restore_fbdev_mode+0x22a/0x260 [drm_kms_helper]
 [<ffffffffc01145d4>] drm_fb_helper_restore_fbdev_mode_unlocked+0x34/0x80 [drm_kms_helper]
 [<ffffffffc011464d>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper]
 [<ffffffffc022181a>] intel_fbdev_set_par+0x1a/0x60 [i915]
 [<ffffffff81459016>] fb_set_var+0x236/0x460
 [<ffffffff8121f158>] ? kmem_cache_alloc+0x108/0x1d0
 [<ffffffff813597a7>] ? avc_alloc_node+0x27/0x120
 [<ffffffff813597a7>] ? avc_alloc_node+0x27/0x120
 [<ffffffff81359c46>] ? avc_compute_av+0x146/0x1e0
 [<ffffffff8144f0af>] fbcon_blank+0x30f/0x350
 [<ffffffff814d9a12>] do_unblank_screen+0xd2/0x1a0
 [<ffffffff814cf856>] vt_ioctl+0x4f6/0x1270
 [<ffffffff814c3cda>] tty_ioctl+0x35a/0xc50
 [<ffffffff8125e599>] ? dput+0xd9/0x260
 [<ffffffff8125a142>] do_vfs_ioctl+0xa2/0x5d0
 [<ffffffff810bd928>] ? task_work_run+0x88/0xb0
 [<ffffffff8125a6e9>] SyS_ioctl+0x79/0x90
 [<ffffffff817eb872>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Code: 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 49 89 f4 48 89 fb e8 f7 e5 ff ff b8 ff ff ff ff <f0> 0f c1 03 83 e8 01 78 29 41 83 44 24 10 01 4c 89 63 28 0f ae 
RIP  [<ffffffff817e91ce>] __ww_mutex_lock+0x1e/0xa0
 RSP <ffff88030f2bf928>
CR2: 0000000000000250

Potential duplicate: bug 1374643

Comment 1 Jeff Needle 2016-09-09 12:03:32 UTC
Created attachment 1199440 [details]
File: dmesg

Comment 2 argonym 2016-09-30 08:48:12 UTC
*** Bug 1380640 has been marked as a duplicate of this bug. ***

Comment 3 argonym 2016-10-06 16:55:57 UTC
This happens every time I shut down the system.

Comment 4 argonym 2016-10-09 13:38:38 UTC
More precisely, this happens every time I shut down the system, provided my HP 1020 G1 laptop was connected to the docking station when I turned it on and disconnected again before shutting it down.
(I use to disconnect it before shut down as otherwise the systems reboots - some ACPI wakeup issue.)

Comment 5 argonym 2016-10-11 07:48:48 UTC
Hm, this time it happened with the docking station still connected. But iirc it had never oopsed so far when the docking station was initially (at the time of boot) disconnected.

Comment 6 Yevgeny Zaspitsky 2016-10-27 14:35:18 UTC
Description of problem:
after hitting Ctrl+Alt+F7 the screen freezed

Version-Release number of selected component:
kernel-core-4.7.9-200.fc24

Additional info:
reporter:       libreport-2.7.2
cmdline:        BOOT_IMAGE=/vmlinuz-4.7.9-200.fc24.x86_64 root=/dev/mapper/fedora23-root ro rd.lvm.lv=fedora23/root rd.luks.uuid=luks-f7d30188-7f6d-41fc-9f5b-1e44a123408d rd.lvm.lv=fedora23/swap rhgb quiet LANG=en_US.UTF-8
kernel:         4.7.9-200.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           Kerneloops

Truncated backtrace:
#1 __ww_mutex_lock
#2 drm_modeset_lock in drm
#3 drm_atomic_get_connector_state in drm
#4 __drm_atomic_helper_set_config in drm_kms_helper
#5 restore_fbdev_mode in drm_kms_helper
#6 drm_fb_helper_restore_fbdev_mode_unlocked in drm_kms_helper
#7 drm_fb_helper_set_par in drm_kms_helper
#8 intel_fbdev_set_par in i915
#9 fb_set_var
#10 ? update_curr

Comment 7 Fedora End Of Life 2017-07-25 22:55:46 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2017-08-08 17:12:55 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.