Bug 1303327

Summary: [abrt] BUG: unable to handle kernel NULL pointer dereference at 0000000000000060
Product: [Fedora] Fedora Reporter: Ray <ray>
Component: xorg-x11-drv-mgaAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: edgar.hoch, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, ray, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4a4c774c85144844f7a9480022fa669f411f2c79
Whiteboard: abrt_hash:7a2b9ea6b2b64ede39df6ad51d68326a18018efb;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-22 13:17:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description Ray 2016-01-30 20:28:32 UTC 
Description of problem:
clean install of fedora 23 XFCE spin earlier this month (~Jan 03,2016). dnf updated.
shut down until today Jan 30, 2016. booted up fine
dnf update; dnf install docker-io
After update and docker intstall. I rebooted to (4.3.3-303) a forever blank screen.
old -300 kernel also no longer boots unless choosing Fedora (0-rescue) grub2 boot option
-300 kernel showed a login repeat loop where plymouth may have been the issue.

Hardware:
There is a LSI 9620-4i installed, but not used and has 0 virtual disks defined. (shouldn't be an issue)
directly attached sata: 3 samsung evo 850 series 250GB ssds
/boot == raid5 (md)
/ == raid0 (md)

Additional info:
reporter:       libreport-2.6.3
BUG: unable to handle kernel NULL pointer dereference at 0000000000000060
IP: [<ffffffff817813ec>] _raw_spin_lock+0xc/0x30
PGD 0 
Oops: 0002 [#1] SMP 
Modules linked in: enclosure lpc_ich tpm_tis ioatdma tpm dca i7core_edac edac_core i5500_temp shpchp acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace sunrpc raid456 hid_logitech_hidpp async_raid6_recov async_memcpy async_pq async_xor xor async_tx hid_logitech_dj raid6_pq raid0 mgag200 i2c_algo_bit drm_kms_helper ttm drm e1000e serio_raw ptp pps_core megaraid_sas fjes
CPU: 1 PID: 443 Comm: plymouthd Not tainted 4.3.3-303.fc23.x86_64 #1
Hardware name: Supermicro X8DT6/X8DT6, BIOS 2.0b    08/30/2011
task: ffff881806999cc0 ti: ffff880c05bfc000 task.ti: ffff880c05bfc000
RIP: 0010:[<ffffffff817813ec>]  [<ffffffff817813ec>] _raw_spin_lock+0xc/0x30
RSP: 0018:ffff880c05bff938  EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000001
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000060
RBP: ffff880c05bff958 R08: 0000000000000000 R09: ffff8800bb0b0440
R10: ffff8800bb0b0440 R11: 0000000000000000 R12: 0000000000000000
R13: ffff880c04fb2828 R14: ffff880c04fb1800 R15: 0000000000000001
FS:  00007fedab698700(0000) GS:ffff880c0fa40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000060 CR3: 0000000c05be4000 CR4: 00000000000006e0
Stack:
 ffffffffa00ab6bf 0000000000000141 ffff880c05b42400 0000000000000000
 ffff880c05bffa48 ffffffffa00fe60c ffff881806999cc0 0000000000000000
 ffffffff82002a48 ffff881806de9a40 ffff880c05bffab8 ffff880c05b42400
Call Trace:
 [<ffffffffa00ab6bf>] ? drm_gem_object_lookup+0x1f/0xa0 [drm]
 [<ffffffffa00fe60c>] mga_crtc_cursor_set+0xdc/0xab0 [mgag200]
 [<ffffffff813bab85>] ? find_next_bit+0x15/0x20
 [<ffffffff813a5fe1>] ? cpumask_next_and+0x31/0x50
 [<ffffffff8177f2b9>] ? __ww_mutex_lock+0x19/0xa0
 [<ffffffffa00c6011>] ? drm_modeset_lock+0x81/0xd0 [drm]
 [<ffffffffa01808b6>] restore_fbdev_mode+0xf6/0x110 [drm_kms_helper]
 [<ffffffffa0182735>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper]
 [<ffffffffa01827ad>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper]
 [<ffffffff8141cfe6>] fb_set_var+0x236/0x460
 [<ffffffff81238a56>] ? do_sys_poll+0x146/0x560
 [<ffffffff8141318f>] fbcon_blank+0x30f/0x350
 [<ffffffff81497cd3>] do_unblank_screen+0xd3/0x1a0
 [<ffffffff8148d41a>] vt_ioctl+0x50a/0x12e0
 [<ffffffffa00c5ce1>] ? drm_modeset_unlock_crtc+0x31/0x50 [drm]
 [<ffffffffa00ba605>] ? drm_mode_getcrtc+0xd5/0x140 [drm]
 [<ffffffff81480a2a>] tty_ioctl+0x35a/0xbf0
 [<ffffffff8133572c>] ? ioctl_has_perm+0xbc/0xf0
 [<ffffffff81236bd5>] do_vfs_ioctl+0x295/0x470
 [<ffffffff813357b0>] ? selinux_file_ioctl+0x50/0xd0
 [<ffffffff813298e3>] ? security_file_ioctl+0x43/0x60
 [<ffffffff81236e29>] SyS_ioctl+0x79/0x90
 [<ffffffff81003c35>] ? syscall_return_slowpath+0x55/0x150
 [<ffffffff8178176e>] entry_SYSCALL_64_fastpath+0x12/0x71
Code: 00 00 f0 0f b1 17 85 c0 75 01 c3 55 89 c6 48 89 e5 e8 c9 7c 96 ff 5d c3 0f 1f 80 00 00 00 00 66 66 66 66 90 31 c0 ba 01 00 00 00 <f0> 0f b1 17 85 c0 75 01 c3 55 89 c6 48 89 e5 e8 a0 7c 96 ff 5d 
RIP  [<ffffffff817813ec>] _raw_spin_lock+0xc/0x30
 RSP <ffff880c05bff938>
Comment 1 Ray 2016-01-30 20:28:39 UTC 
Created attachment 1119674 [details]
File: dmesg
Comment 2 Josh Boyer 2016-02-17 17:22:08 UTC 
Please test this scratch build when it completes and let me know if it resolves the issue.

http://koji.fedoraproject.org/koji/taskinfo?taskID=13022511
Comment 3 Ray 2016-02-18 16:05:23 UTC 
Thanks Josh,

I suspect the issue was due to 3xSSD mdraid0 and unconfirmed data corruption. What was odd is subsequent fedora 23-xfce reinstall (with possibly different f23 live image revision) was not booting either.

I no longer have the exact configuration to repeat the kernel error I was seeing in this bug report. I'll attempt to reproduce it over this weekend, otherwise unless you have other evidence I will continue to believe this was due to disk/hardware issues.
Comment 4 Josh Boyer 2016-02-18 16:08:28 UTC 
The backtrace included in the bug matches identically to three other bug reports.  I would be surprised if this specific issue is related to your RAID corruption.  However, if it is inconvenient for you to test, I can just duplicate your bug against one of the others that have confirmed the fix.
Comment 5 Ray 2016-02-20 19:26:24 UTC 
Hi Josh,

I wasn't able to reproduce the NULL pointer dereference error again, but I was not able to boot either. I was stuck in a infite loop of systemd attempting to start services. I moved the array to other (desktop) hardware I was able to successfully boot from to it. I then installed the ..-301 kernel (http://koji.fedoraproject.org/koji/taskinfo?taskID=13022511), moved it back to original supermicro (server) hardware and it booted!

After realizing my onboard GPU (Matrox G200eW) had 16MB of DDR2, I upgraded to Geforce GT 730 2GB DDR3--which seems to be the best performance option within the limitations of my motherboard (Supermicro X8-D2F) and the PCIe x8 slot.

..but the 4.3.5-301.fc23.x86_64 build works on the G200!

Thanks!!

-Ray
Comment 6 Josh Boyer 2016-02-22 13:17:29 UTC 

*** This bug has been marked as a duplicate of bug 1305181 ***