Bug 1377568 - [abrt] BUG: unable to handle kernel NULL pointer dereference at (null)
Summary: [abrt] BUG: unable to handle kernel NULL pointer dereference at (null)
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:1ab5c207825438402895693ea6c...
: 1390990 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-20 06:30 UTC by Gwendal
Modified: 2017-08-08 17:29 UTC (History)
7 users (show)

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


Attachments (Terms of Use)
File: dmesg (58.22 KB, text/plain)
2016-09-20 06:30 UTC, Gwendal
no flags Details

Description Gwendal 2016-09-20 06:30:10 UTC
Additional info:
reporter:       libreport-2.7.2
BUG: unable to handle kernel NULL pointer dereference at           (null)
IP: [<ffffffff943f7dcb>] __list_add+0x1b/0xb0
PGD 0 
Oops: 0000 [#1] SMP
Modules linked in: rfcomm fuse ccm 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 nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_raw ip6table_mangle ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_security iptable_raw iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_security ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep arc4 intel_rapl x86_pkg_temp_thermal iwlmvm intel_powerclamp coretemp kvm_intel mac80211 iTCO_wdt iTCO_vendor_support kvm iwlwifi irqbypass intel_cstate intel_uncore intel_rapl_perf cfg80211 uvcvideo snd_hda_codec_realtek joydev snd_hda_codec_hdmi snd_hda_codec_generic
 videobuf2_vmalloc rtsx_pci_ms i2c_i801 videobuf2_memops snd_hda_intel memstick videobuf2_v4l2 videobuf2_core btusb snd_hda_codec btrtl btbcm btintel bluetooth lpc_ich videodev shpchp snd_hda_core mei_me media snd_hwdep mei snd_seq snd_seq_device snd_pcm wmi thinkpad_acpi snd_timer rfkill snd soundcore tpm_tis tpm nfsd binfmt_misc auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt i915 rtsx_pci_sdmmc mmc_core crct10dif_pclmul crc32_pclmul crc32c_intel i2c_algo_bit drm_kms_helper ghash_clmulni_intel e1000e drm serio_raw rtsx_pci ptp pps_core fjes video
CPU: 3 PID: 1108 Comm: systemd-logind Not tainted 4.7.3-200.fc24.x86_64 #1
Hardware name: LENOVO 20ARS2QF00/20ARS2QF00, BIOS GJET90WW (2.40 ) 08/15/2016
task: ffff8800c8259e80 ti: ffff88030e438000 task.ti: ffff88030e438000
RIP: 0010:[<ffffffff943f7dcb>]  [<ffffffff943f7dcb>] __list_add+0x1b/0xb0
RSP: 0018:ffff88030e43b978  EFLAGS: 00010246
RAX: ffff88030cdb2a58 RBX: ffff88030e43b9b0 RCX: 00000000c0000100
RDX: ffff88030cdb2a58 RSI: 0000000000000000 RDI: ffff88030e43b9b0
RBP: ffff88030e43b990 R08: 0000000000000000 R09: 0000000000000000
R10: 000014a90c724d05 R11: 0000000000000001 R12: 0000000000000000
R13: ffff88030cdb2a58 R14: 00000000ffffffff R15: ffff88030cdb2a50
FS:  00007feb02a05900(0000) GS:ffff88031f2c0000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000030e0d7000 CR4: 00000000001406e0
Stack:
 ffff8802ee0d4c80 ffff8800c8259e80 ffff88030cdb2a54 ffff88030e43ba00
 ffffffff947e90a2 dedededec03ab8a7 ffff88030cdb2a58 0000000000000000
 0000000000000000 3830317830323931 00000000a4ba969a 0000000000000000
Call Trace:
 [<ffffffff947e90a2>] __ww_mutex_lock_slowpath+0xb2/0x1c0
 [<ffffffff947e920b>] __ww_mutex_lock+0x5b/0xa0
 [<ffffffffc03ba56e>] drm_modeset_lock+0x4e/0xd0 [drm]
 [<ffffffffc03ba56e>] ? drm_modeset_lock+0x4e/0xd0 [drm]
 [<ffffffffc03bb054>] drm_atomic_get_connector_state+0x34/0x1c0 [drm]
 [<ffffffffc045df90>] __drm_atomic_helper_set_config+0x2a0/0x360 [drm_kms_helper]
 [<ffffffffc045f1da>] restore_fbdev_mode+0x22a/0x260 [drm_kms_helper]
 [<ffffffffc04615d4>] drm_fb_helper_restore_fbdev_mode_unlocked+0x34/0x80 [drm_kms_helper]
 [<ffffffffc055e712>] intel_fbdev_restore_mode+0x22/0x80 [i915]
 [<ffffffffc0589abe>] i915_driver_lastclose+0xe/0x20 [i915]
 [<ffffffffc039ee4e>] drm_lastclose+0x2e/0x120 [drm]
 [<ffffffffc039f1ce>] drm_release+0x28e/0x470 [drm]
 [<ffffffff942483af>] __fput+0xdf/0x1f0
 [<ffffffff942484fe>] ____fput+0xe/0x10
 [<ffffffff940bd903>] task_work_run+0x83/0xb0
 [<ffffffff940a37f2>] do_exit+0x2d2/0xb70
 [<ffffffff940a4117>] do_group_exit+0x47/0xb0
 [<ffffffff940af3cd>] get_signal+0x28d/0x630
 [<ffffffff94025f57>] do_signal+0x37/0x6c0
 [<ffffffff9425e769>] ? dput+0xd9/0x260
 [<ffffffff94267944>] ? mntput+0x24/0x40
 [<ffffffff9424844d>] ? __fput+0x17d/0x1f0
 [<ffffffff942484fe>] ? ____fput+0xe/0x10
 [<ffffffff940bd908>] ? task_work_run+0x88/0xb0
 [<ffffffff9400330c>] exit_to_usermode_loop+0x8c/0xd0
 [<ffffffff94003ce1>] syscall_return_slowpath+0xa1/0xb0
 [<ffffffff947eb8fa>] entry_SYSCALL_64_fastpath+0xa2/0xa4
Code: e8 1b 7a ca ff 66 2e 0f 1f 84 00 00 00 00 00 90 55 48 89 e5 41 55 41 54 53 4c 8b 42 08 48 89 fb 49 89 f4 49 89 d5 49 39 f0 75 29 <4d> 8b 04 24 4d 39 c5 75 47 49 39 dc 74 62 49 39 dd 74 5d 49 89 
RIP  [<ffffffff943f7dcb>] __list_add+0x1b/0xb0
 RSP <ffff88030e43b978>

Potential duplicate: bug 1376371

Comment 1 Gwendal 2016-09-20 06:30:19 UTC
Created attachment 1202715 [details]
File: dmesg

Comment 2 argonym 2016-09-30 16:21:01 UTC
Description of problem:
when removing power supply from the connected docking station

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

Additional info:
reporter:       libreport-2.7.2
cmdline:        BOOT_IMAGE=/vmlinuz-4.7.4-200.fc24.x86_64 root=UUID=823b5959-149f-4457-afff-beb21cf27950 ro resume=UUID=7df178e3-03b2-4f4f-8663-6b7be262b384 vconsole.font=latarcyrheb-sun16 rhgb quiet
kernel:         4.7.4-200.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           Kerneloops

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

Comment 3 Abhay Kadam 2016-11-02 11:11:09 UTC
*** Bug 1390990 has been marked as a duplicate of this bug. ***

Comment 4 Fedora End Of Life 2017-07-25 23:08: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 5 Fedora End Of Life 2017-08-08 17:29:24 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.