Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#26911 - [udev] watchdog timer causes boot failure with udev-175-1
Attached to Project:
Arch Linux
Opened by Steffen (thieste) - Wednesday, 16 November 2011, 05:29 GMT
Last edited by Tom Gundersen (tomegun) - Friday, 25 November 2011, 11:15 GMT
Opened by Steffen (thieste) - Wednesday, 16 November 2011, 05:29 GMT
Last edited by Tom Gundersen (tomegun) - Friday, 25 November 2011, 11:15 GMT
|
DetailsDescription: After the upgrade to udev-175 the following message appears for approx. 10s while start-process:
"iTCO_wdt: Unexpected close not stopping, watchdog" after that the start-process aborted and reboots ... Additional info: * udev-175 * HOTFIX: downgrade to version 174-1 Steps to reproduce: simple upgrade to version 175-1 and reboot |
This task depends upon
Closed by Tom Gundersen (tomegun)
Friday, 25 November 2011, 11:15 GMT
Reason for closing: Not a bug
Additional comments about closing: Seems like the problem is caused by broken rules. Not udev's fault.
Friday, 25 November 2011, 11:15 GMT
Reason for closing: Not a bug
Additional comments about closing: Seems like the problem is caused by broken rules. Not udev's fault.
You could probably temporarily blacklist iTCO_wdt to make things continue working.
The underlying problem is not clear though, as the error message just says that the watchdog timer found a problem and rebooted.
Do you use the stock arch kernel? Anything else non-standard about your setup? Do you make sure to recreate the initarmfs whenever you change the udev version? Are you absolutely sure that only the udev version is different between tries and that the problem is 100% reproducible?
today i find the time to reproduce the error/failure.. Well, i updated to current version of udev an reboot my system. The error was nearly the same, but this time the following message appears while loading User specified modules
udevd[243]: unknown key 'ERNEL' in /etc/udev/rules.d/11-media-by-label-with-pmount.rules
After "Waiting for UDev uevents to be processes" i ve got the error-message:
udevd[243]: süecified group 'pcscd' unknown
iTCO_wdt: Unexpected close not stopping, watchdog
These messages appears for some seconds and then the system reboots.
Well, with the use of chroot and an archlinux live cd, i could login into my arch-system, removed the udev rule and reboot the pc.
The error message regarding to /etc/udev/rules.d/11-media-by-label-with-pmount.rules was gone. Only the message with the unknown group 'pcscd' appears, but my installed arch-system is working again.
Conclusion
there seem to be no bug in the current udev version, it was something wrong on my system.. sorry for the wrong bug report.. but the first time i updated to the current udev version. there were no error messages ...
Thanks for getting back to it. The rule probably should have been 'KERNEL' rather than 'ERNEL', which you might have guessed ;-) Please file a bug report if this is from an Arch package.
Whatever installed the rule referencing the pcscd group should either stop doing that or make sure the rule exists (again, if this is an Arch package please file a report).
The missing error message is a bit annoying, if you are able to consistently reproduce it, and can explain to me a simple way to do it I'd be interested to try and sort it out. If so, please open a new bug report about that.