Bug 820638

Summary: kernel/udevadm/haldaemon crash
Product: [Fedora] Fedora Reporter: Henrique Martins <fedora>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-11 14:53:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
kernel crash log in /var/log/messages
none
kernel crash log in /var/log/messages
none
crash log without vbox (not tainted kernel) none

Description Henrique Martins 2012-05-10 14:51:03 UTC
Created attachment 583600 [details]
kernel crash log in /var/log/messages

Description of problem:
My system runs haldaemon.service daily invoked by systemd.  This in turn causes a kernel/udevadm crash that is splashed on the console and logged on messages.
I'll attach the crash report.  

First crash was around 3:30 am on 2012/05/08 after I rebooted with kernel-3.3.4-3.fc16.x86_64

Version-Release number of selected component (if applicable):
kernel-3.3.4-3.fc16.x86_64
udev-173-3.fc16.x86_64
hal-0.5.14-6.fc15.x86_64

How reproducible:
Happened every night for the last three nights, doesn't bring the system down.

Steps to Reproduce:
1. No steps, just running the system
  
Actual results:
daily annoying crash report splashed on screen

Expected results:
no crash

Additional info:

Comment 1 Henrique Martins 2012-05-10 14:54:01 UTC
Created attachment 583601 [details]
kernel crash log in /var/log/messages

changing attachment type to text/plain

Comment 2 Dave Jones 2012-05-10 15:08:11 UTC
this isn't the first bug that was hit (Tainted:B indicates a 'bad page' was found earlier).

Can you reproduce this without vbox ?

Comment 3 Henrique Martins 2012-05-10 16:20:18 UTC
I don't think I ever fired vbox after reboot, only ran the setup for the new kernel, but do have the modules loaded.  I'll make sure they are not loaded and reboot sometime today.

Comment 4 Henrique Martins 2012-05-11 13:42:39 UTC
Still crashes without vbox. The "Tainted:B" is no longer there, that line containing "Not tainted".  I run this kernel on another (very different) machine with no problems, but on this one I do have a Hauppage video capture card.
I'll attach the new crash message.

Comment 5 Henrique Martins 2012-05-11 13:43:34 UTC
Created attachment 583851 [details]
crash log without vbox (not tainted kernel)

Comment 6 Dave Jones 2012-05-11 14:53:59 UTC
RAX: ffefffff81c8bca0

that 'e' should be an 'f'. You had a single bit flip from 1 to 0.
This is usually a sign of a hardware problem such as bad memory.

Comment 7 Henrique Martins 2012-05-13 18:27:45 UTC
That could be it, though I don't think anything else crashes on my system (other that Adobe's flash, but that's another story).  I'll run memtest soon.

Comment 8 Henrique Martins 2012-05-16 01:05:04 UTC
memtest did show up a bad memory (but interestingly no crashes with kernel 3.3.5-2.fc16.x86_64).  I'll need to find my old 4 GB stick before RMAing the 3x4 now on the system :-(