Hide Forgot
Description of problem: System froze up several times in a row during booting, this report is from one of those. Once it froze after the mouse pointer appeared but before gdm loaded fully. Next several times, I hit escape to show text while booting, and it froze just after "Starting switch root". After a few tries, it booted successfully. Additional info: reporter: libreport-2.6.4 BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 IP: [<ffffffff81244ec2>] dput+0x132/0x200 PGD 0 Oops: 0000 [#1] SMP Modules linked in: ccm nf_log_ipv4 nf_log_ipv6 nf_log_common xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 xt_limit ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 xt_recent ip6table_filter xt_conntrack ip6_tables nf_conntrack bnep arc4 vfat fat ath9k_htc ath9k_common ath9k_hw ath mac80211 cfg80211 nls_utf8 hfsplus uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media btusb btrtl btbcm btintel bluetooth intel_rapl rfkill iosf_mbi bcm5974 x86_pkg_temp_thermal coretemp kvm_intel iTCO_wdt joydev kvm iTCO_vendor_support snd_hda_codec_hdmi applesmc input_polldev irqbypass snd_hda_codec_cirrus snd_hda_codec_generic acpi_als snd_hda_intel snd_hda_codec bcma kfifo_buf i2c_i801 snd_hda_core industrialio sbs snd_hwdep snd_seq snd_seq_device snd_pcm mei_me shpchp apple_gmux sbshc lpc_ich apple_bl snd_timer snd soundcore mei tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc dm_crypt i915 crct10dif_pclmul crc32_pclmul crc32c_intel i2c_algo_bit drm_kms_helper sdhci_pci hid_appleir sdhci firewire_ohci drm hid_apple tg3 mmc_core firewire_core ptp crc_itu_t pps_core fjes video CPU: 0 PID: 1712 Comm: gdbus Not tainted 4.4.5-300.fc23.x86_64 #1 Hardware name: Apple Inc. MacBookPro8,1/Mac-94245B3640C91C81, BIOS MBP81.88Z.0047.B2C.1510261540 10/26/15 task: ffff88043ce01e00 ti: ffff88043cec4000 task.ti: ffff88043cec4000 RIP: 0010:[<ffffffff81244ec2>] [<ffffffff81244ec2>] dput+0x132/0x200 RSP: 0018:ffff88043cec7be8 EFLAGS: 00010202 RAX: 0000000000000000 RBX: ffff88008842f0c0 RCX: ffffffff00000000 RDX: 0000000000000001 RSI: ffff88044355f500 RDI: ffff88008842f0c0 RBP: ffff88043cec7c10 R08: 0000000000000000 R09: 0000000000000246 R10: ffff88044816bc50 R11: ffff88044355f510 R12: ffff88008842f118 R13: ffff880449b6ccb0 R14: ffff88045d58a920 R15: ffff88008842f0c0 FS: 00007fd8076e7700(0000) GS:ffff88046fa00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000020 CR3: 0000000451d63000 CR4: 00000000000406f0 Stack: ffff88044355f500 0000000000000008 ffff880449b6ccb0 ffff88045d58a920 ffff88008842f0c0 ffff88043cec7c58 ffffffff8122fcd2 ffff880449b6ccb0 ffff88044355f510 ffffffff81f2ef60 ffff88043ce02510 ffff88043ce01e00 Call Trace: [<ffffffff8122fcd2>] __fput+0x172/0x1e0 [<ffffffff8122fd7e>] ____fput+0xe/0x10 [<ffffffff810c0b13>] task_work_run+0x73/0x90 [<ffffffff810a6d02>] do_exit+0x2d2/0xac0 [<ffffffff81241f30>] ? poll_select_copy_remaining+0x140/0x140 [<ffffffff810a7577>] do_group_exit+0x47/0xb0 [<ffffffff810b29f4>] get_signal+0x294/0x610 [<ffffffff81017277>] do_signal+0x37/0x6b0 [<ffffffff8127927c>] ? eventfd_read+0x5c/0x90 [<ffffffff8122d6b7>] ? __vfs_read+0x37/0x100 [<ffffffff81337440>] ? security_file_permission+0xa0/0xc0 [<ffffffff8100320c>] exit_to_usermode_loop+0x8c/0xd0 [<ffffffff81003d31>] syscall_return_slowpath+0xa1/0xb0 [<ffffffff817a068c>] int_ret_from_sys_call+0x25/0x8f Code: 85 c0 0f 84 94 00 00 00 48 89 df e8 39 fd ff ff 4d 85 ed 0f 84 26 ff ff ff 4d 89 fc 4c 89 eb e9 f3 fe ff ff 48 8b 43 60 48 89 df <ff> 50 20 85 c0 75 98 8b 03 e9 3d ff ff ff a9 00 04 08 00 0f 85 RIP [<ffffffff81244ec2>] dput+0x132/0x200 RSP <ffff88043cec7be8> CR2: 0000000000000020
Created attachment 1138172 [details] File: dmesg
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those.
The issue seemed to have stopped happening on the hardware while I was still running 23. I have now upgraded it to 24 and have not experienced this problem there either.