Bug 1374197 - [abrt] BUG: unable to handle kernel NULL pointer dereference at 00000000000007a4
Summary: [abrt] BUG: unable to handle kernel NULL pointer dereference at 00000000000007a4
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 25
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:a2b32eeb5aa9a8fe4346417ba9e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-08 08:46 UTC by Kamil Páral
Modified: 2017-12-12 10:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:16:44 UTC
Type: ---


Attachments (Terms of Use)
File: dmesg (99.44 KB, text/plain)
2016-09-08 08:46 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2016-09-08 08:46:22 UTC
Description of problem:
Happened during playing a video.

Additional info:
reporter:       libreport-2.7.2
BUG: unable to handle kernel NULL pointer dereference at 00000000000007a4
IP: [<ffffffff82805f82>] _raw_spin_lock_irqsave+0x22/0x3d
PGD 0 
Oops: 0002 [#1] SMP
Modules linked in: nfsv3 rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache vhost_net vhost macvtap macvlan ccm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun fuse 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_security ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 iptable_raw iptable_mangle iptable_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep vfat fat arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iwlmvm mac80211 mei_wdt iTCO_wdt iTCO_vendor_support irqbypass intel_cstate intel_uncore iwlwifi
 intel_rapl_perf cfg80211 snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic uvcvideo joydev btusb btrtl snd_hda_intel i2c_i801 btbcm i2c_smbus rtsx_pci_ms intel_pch_thermal videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_hda_codec memstick videobuf2_core btintel snd_seq bluetooth shpchp lpc_ich snd_hda_core snd_seq_device videodev snd_hwdep snd_pcm media mei_me mei snd_timer wmi thinkpad_acpi snd soundcore rfkill tpm_tis tpm_tis_core tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt i915 rtsx_pci_sdmmc mmc_core i2c_algo_bit drm_kms_helper crct10dif_pclmul drm crc32_pclmul crc32c_intel ghash_clmulni_intel e1000e serio_raw rtsx_pci ptp pps_core fjes video
CPU: 2 PID: 895 Comm: systemd-logind Not tainted 4.8.0-0.rc4.git0.1.fc25.x86_64 #1
Hardware name: LENOVO 20BWS1KY0H/20BWS1KY0H, BIOS JBET49WW (1.14 ) 05/21/2015
task: ffff9709026d5b80 task.stack: ffff97090e060000
RIP: 0010:[<ffffffff82805f82>]  [<ffffffff82805f82>] _raw_spin_lock_irqsave+0x22/0x3d
RSP: 0018:ffff97090e063888  EFLAGS: 00010046
RAX: 0000000000000000 RBX: 0000000000000246 RCX: ffff97090b345d00
RDX: 0000000000000001 RSI: 0000000000000003 RDI: 00000000000007a4
RBP: ffff97090e063890 R08: 0000000000000438 R09: 0000000000000898
R10: 0000000000000780 R11: 0000000000000898 R12: 00000000000007a4
R13: 0000000000000000 R14: ffff97086f031000 R15: 0000000000000000
FS:  00007f661f4fd300(0000) GS:ffff97091dc80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000000007a4 CR3: 0000000342742000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Stack:
 0000000000000000 ffff97090e0638f0 ffffffff820cc7b0 0000000000000000
 0000000000000000 3830317800000003 0000000000000030 000000008604586f
 ffff97090a090a58 ffffea000d281080 ffff97090a090a60 ffff97086f031000
Call Trace:
 [<ffffffff820cc7b0>] try_to_wake_up+0x40/0x3c0
 [<ffffffff820ccb45>] wake_up_process+0x15/0x20
 [<ffffffff82803502>] __ww_mutex_lock+0x82/0xa0
 [<ffffffffc03115ae>] drm_modeset_lock+0x4e/0xd0 [drm]
 [<ffffffff828034db>] ? __ww_mutex_lock+0x5b/0xa0
 [<ffffffffc0311dc2>] drm_atomic_get_connector_state+0x32/0x180 [drm]
 [<ffffffffc036babe>] __drm_atomic_helper_set_config+0x29e/0x360 [drm_kms_helper]
 [<ffffffffc036dcfe>] restore_fbdev_mode+0x13e/0x270 [drm_kms_helper]
 [<ffffffffc036f884>] drm_fb_helper_restore_fbdev_mode_unlocked+0x34/0x80 [drm_kms_helper]
 [<ffffffffc036f8fd>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper]
 [<ffffffffc04528ca>] intel_fbdev_set_par+0x1a/0x60 [i915]
 [<ffffffff82469116>] fb_set_var+0x236/0x460
 [<ffffffff820e57b4>] ? __wake_up+0x44/0x50
 [<ffffffff82803b32>] ? down_write+0x12/0x40
 [<ffffffff824d75d0>] ? tty_unthrottle+0x50/0x60
 [<ffffffff8245ef3f>] fbcon_blank+0x30f/0x350
 [<ffffffff824e7f72>] do_unblank_screen+0xd2/0x1a0
 [<ffffffff824ddafc>] vt_ioctl+0x52c/0x1360
 [<ffffffff824d8639>] ? n_tty_ioctl_helper+0x29/0x120
 [<ffffffff824d1e71>] tty_ioctl+0x381/0xc80
 [<ffffffff824cf06d>] ? __tty_fasync+0x5d/0xe0
 [<ffffffff824dab19>] ? tty_unlock+0x29/0x50
 [<ffffffff82266083>] do_vfs_ioctl+0xa3/0x620
 [<ffffffff82266679>] SyS_ioctl+0x79/0x90
 [<ffffffff82003c57>] do_syscall_64+0x67/0x160
 [<ffffffff828060e1>] entry_SYSCALL64_slow_path+0x25/0x25
Code: 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 9c 58 0f 1f 44 00 00 48 89 c3 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00 <f0> 0f b1 17 85 c0 75 06 48 89 d8 5b 5d c3 89 c6 e8 39 85 8e ff 
RIP  [<ffffffff82805f82>] _raw_spin_lock_irqsave+0x22/0x3d
 RSP <ffff97090e063888>

Comment 1 Kamil Páral 2016-09-08 08:46:31 UTC
Created attachment 1198953 [details]
File: dmesg

Comment 2 Kamil Páral 2016-10-06 10:47:36 UTC
Description of problem:
I tried to reboot after dnf update. Black screen, had to use sysrq.

Version-Release number of selected component:
kernel-core-4.8.0-0.rc8.git0.1.fc25

Additional info:
reporter:       libreport-2.8.0
cmdline:        BOOT_IMAGE=/vmlinuz-4.8.0-0.rc8.git0.1.fc25.x86_64 root=/dev/mapper/dryad-root ro rd.lvm.lv=dryad/root rd.lvm.lv=dryad/swap rd.luks.uuid=luks-f7c876f1-4497-42fd-9cc1-c60c38d2f2a0 rd.luks.options=discard resume=/dev/mapper/dryad-swap audit=0 rhgb quiet LANG=en_US.UTF-8
kernel:         4.8.0-0.rc8.git0.1.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       unknown
type:           Kerneloops

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

Comment 3 Fedora End Of Life 2017-11-16 14:11:39 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 4 Fedora End Of Life 2017-12-12 10:16:44 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.