Bug 575580

Summary: With udev-151-5.fc14.x86_64 fedora 14 doesn't start
Product: [Fedora] Fedora Reporter: Wolfgang Ulbrich <fedora>
Component: udevAssignee: Harald Hoyer <harald>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: fedora, harald, jonathan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-22 09:55:24 UTC Type: ---
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
messages log none

Description Wolfgang Ulbrich 2010-03-21 15:33:14 UTC 
Description of problem:
After updating to new udev packages fedora rawhide (14) doesn't start anymore.
On the screen i see this message when udev starts:
iTCO_wdt: unexpected close , not stoping watchdog 
After some seconds watchdog stop the boot and restart the system.
I had no chance to boot in runlevel 1 or 3 or 5, everytime i get the same error.
And no logs were writen.
Then i edit /etc/udev/udev.conf, changing 'udev_log="err" ' in 'udev_log="debug"'.
Now the system boots, but it takes a long time.
Ok after back in system, i downgrade udev and the libs packages to udev-151-3.fc13.x86_64 from the fc13alpha original installation. Than everthing is fine and fc14 starts normal again.
Version-Release number of selected component (if applicable):
udev-151-5.fc14.x86_64
libgudev1-151.5.fc14.x86_64
libgudev1-devel-151.5.fc14.x86_64
libudev-151.5.fc14.x86_64
libudev-devel-151.5.fc14.x86_64

How reproducible:
Everytime system starts

Steps to Reproduce:
1.
2.
3.
  
Actual results:
iTCO_wdt: unexpected close , not stoping watchdog
system reboot

Expected results:
normal system start

Additional info:
Comment 1 Wolfgang Ulbrich 2010-03-21 16:38:54 UTC 
Created attachment 401572 [details]
messages log
Comment 2 Wolfgang Ulbrich 2010-03-21 16:42:02 UTC 
The messages log is from starting with changing udev.conf 'udev_log="debug"'.
The last part is starting with the old udev version.
Comment 3 Harald Hoyer 2010-03-22 09:55:24 UTC 

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