Bootup stops at "Loading UDev uevents"

When I boot my system there is a +/- 80% chance that the boot process stops at the message: "Loading UDev uevents... [busy]". This is not a big issue, because I can just reset the computer and try again. But it is annoying. When loading UDev uevents is successful (20% chance) everything works fine.
This problem started just a few days ago. I have a new SATA-II harddisk installed and I have moved some partitions to this new harddisk. I've build a new kernel (I compile the kernel myself) with SATA and SCSI capabilities built in. Like I've said above, when the boot process is successful, everything works fine.
Is there a solution for this?

I have this problem, with about 80% boot failure at "loading udev uevents", on a clean installation from Archlinux-x86_64-2007.08-Don't-Panic.current.iso. No dual boot, no fancy hardware: 1 SATA harddisk, 1 SATA optical drive. No USB devices.
Since this is the first machine I ever built myself I'm open to the possibility that I broke an important wire somewhere. Still, I'd like to be sure that that is the problem. Is there a way to find out?
I have experimented with mkinitcpio.conf by
1. getting a list of all loaded modules via mkinitcpio -m
2. adding them to the MODULES list in rc.conf
3. removing udev from the HOOKS defined in rc.conf
4. recompile the kernel image using mkinitcpio -p kernel26
However, this did not make a difference, since (if I read it correctly) rc.sysinit will call udev_start even if udev is not in HOOKS.
I've noticed that there are a number of print outs in the udev_start script that never make it to the boot screen, and I've also not found them in any log file. Is there a way to see them? I'd like to know if the problem is in udevsettle or in udevtrigger.

Similar Messages

Long waiting time during "Loading udev uevents" with P35-DS3R fixed

Hello folks,
I just bought a new computer with a new motherboard (GigaByte P35-DS3R), freshly installed Arch Linux and had problems during the boot process because "Loading udev uevents" took a very long time to finish (> 30 sec). In the BIOS both "USB Controller" and "USB 2.0 Controller" are enabled.
I spent a lot of time checking the autoloaded kernel modules and finally found out that the USB modul "uhci_hcd" caused the problems. I just added "uhci_hcd" to the module blacklist and now everything works as expected.
Cheers,
Yogi

Hello again,
ok, my post above does not show the whole truth... blacklisting uhci_hcd caused my good old logitech usb mouse to stop working.
My solution now is to add uhci_hcd to both MOD_BLACKLIST and MODULES so that the module is not loaded by udev but only manually.
Is there a better way?
Cheers,
Yogi

Udev uevents problem in kernel 2.6.27

(some people told me "change the subject crazy man")
ok i was in arch 32 but with the kernel 2.6.26 i got many problems with acpi, the kernel dont boot unless i keep pressing the power button of my laptop, so i go to arch64 with the same kernel and the problem goes away. But now with the new kernel (2.6.27) in arch64 the laptop just stop in loading "udev uevents" and dont continue loading unless i plug the power cable, same when im going to turn off the machine.
well my friends, what can i do ???
ftr ( hp pavilion dv6620la)
sorry for my english
Last edited by juancnb (2008-10-15 15:05:24)

Hi there !
I've exactly the same problem on my VAIO PCG-GRT815M.
I tried several things:
First, /sbin/udevadm monitor& as tavianator suggested. The problem is that messages are always different from one boot to another, so this output seems unusable there.
Next, I reproduced what juancnb said about pressing the power button : it allowed the system to continue its boot sequence for a few seconds. Repeating this operation, i managed to load gdm. At this stage, pressing keys has the same effect as pressing the power button (gui and tty).
Last thing i tried is to disable acpi modules (maybe), loaded just before UDev events are triggered. It changed nothing. At this stage, it must be either udev itself or some module it loads which is the source of the problem. I will try to get a list of loaded modules next time i try to boot, and starting to backlist them one by one to find the culprit.
I hope this issue will be solved soon.
vdust.

Install hangs at "Loaing Udev uevents" [solved]

Hi all,
I have been attempting to install Arch Linux on my old Compaq DeskPro EN (PIII 1GHz - 384MB RAM) since I am looking for a more lightweight distribution - it currently has Fedora 10 on it. I downloaded the Arch 2009.02 FTP ISO image and burnt it to CD however I cannot get past "Loading udev uevents" in the boot process. I have tried the pci=nosort, pci=nobios and noapic boot options to no avail.
Has anyone had a similar situation or does anyone have any idea what might be causing this?. Any ideas would be greatly appreciated.
Thanks,
oztrailrider
Last edited by oztrailrider (2009-03-18 22:34:59)

teh wrote:
Hi, i have this problem while i'm trying to load Archlinux to install it.
I don't know how to add that line into the kernel. Should i build my own cd with that line in the kernel?
I was trying in the grub command line ('C' in the GRUB menu) but i fail.
Sorry for being a newbie and for my baaaad english.
when the iso boots and you see the grub menu, press 'e' to edit, then add that string to the end of the command line. press enter, then 'b' to boot
For me this did not help the crashes I'm having with Virtualbox btw

Keyboard after UDev uevents stops responding.

Hello.
I have just installed (well, a few times now..) Arch Duke (not Panic because of arch-addons/NTFS issue). Selected only Basic packages, changed hostname and dhcp settings, selected en_US.utf8 locale.
At kernel installation I got warning that "current locale is invalid, using default "C" locale".
After installation, on booting, at "UDev uevents" my simple PS/2 keyboard (MS Natural without any multimedia-stuff) stoped responding ( I was pushing "Num Lock" repeatedly to check that). I can't login, or anything...
Any suggestions?
Thanks in advance.
Last edited by Talkless (2007-08-15 18:10:39)

What happens when you try a USB keyboard (if you have one handy)?
I actually had something similar happen on an IBM NetVista box that I found in my dad's scrapheap (guess that's why it was in the scrapheap); the PS/2 port basically accepted one keystroke and then stopped working... but that was for all OS's, and even CMOS setup. I'm guessing that's not what's happened to you?
- Try booting the -fallback image; see if that does anything.
- Linux seems able to take a PS/2 keyboard hot plug-in (I was always told you couldn't do that with PS/2 devices) -- try unplugging it and plugging it back in, then try booting with it not plugged in at all and plug it in at the login screen. If I boot with no keyboard or a USB keyboard and then plug my PS/2 in, it detects it and I see a line about it in my dmesg.
~Felix.

[SOLVED] Waiting for udev uevents to be processed - Black Screen

Hi, after upgrading my kernel to the latest from abs I'm having trouble booting.
When "Waiting for udev uevents to be processed" comes my screen turns black and the monitor starts searching for a new signal.
I've tried adding vga=775 and i915.modeset=0 without any success
My server has a Intel p4 3,0ghz with HT and a ATI HD card.
This is kernel version 2.6.33(.4?) something
How can I fix this?
This is how my bootup looks like: http://www.youtube.com/watch?v=It9Ao1s55ns
Last edited by XAM (2010-06-11 10:37:51)

tomk wrote:i915 is the Intel DRM driver - you say you have an ATI card...
I just tested it out since it was marked as a solution in a different thread.
Do you know why this happens? I actually managed to boot 1 time before, and the font was übersmall
I had this problem with the default kernel, which I managed to boot after several restarts. I'm still rebooting it over and over without any success.
Last edited by XAM (2010-06-11 10:00:09)

PIII Celeron hangs or reboots when "Waiting for UDev uevents to be..."

Hello
I want to mention that the only way I can boot a Linux kernel on this machine is adding "no-hlt" option. Additionally the Arch installation image reboots shortly after the boot loader's menu is printed, perhaps due to requesting the "no_hlt" instruction.
So I placed the contents of Arch installation LiveCD on the hard drive and installed GRUB using Knoppix.
The problem is that when Arch installation image boots the system hangs or reboots on this stage: "Waiting for UDev uevents to be prcessed", or here with debug option. Sometimes it hangs 3 lines earlier, but more often it reboots.
So it's hard to recognize the exact reason of the issue.
May be I need to bypass some uevents? Or there are some failsafe boot options of Arch installation image?
What can you recommend?
Last edited by AleXoundOS (2011-11-25 18:51:01)

AleXoundOS wrote:
Hello
I want to mention that the only way I can boot a Linux kernel on this machine is adding "no-hlt" option. Additionally the Arch installation image reboots shortly after the boot loader's menu is printed, perhaps due to requesting the "no_hlt" instruction.
So I placed the contents of Arch installation LiveCD on the hard drive and installed GRUB using Knoppix.
The problem is that when Arch installation image boots the system hangs or reboots on this stage: "Waiting for UDev uevents to be prcessed", or here with debug option. Sometimes it hangs 3 lines earlier, but more often it reboots.
So it's hard to recognize the exact reason of the issue.
May be I need to bypass some uevents? Or there are some failsafe boot options of Arch installation image?
What can you recommend?
can someone help with this?

What happens during the "Waiting for UDev uevents to be processed"?

Hello dear archers,
I have arch installed on my laptop, working great, I really love it.
Only one thing bother me and I would like to solve it: at boot time, the system waits for about 15s on the stage "Waiting for UDev uevents to be processed".
Is it normal? What is it doing exactly during this stage: loading modules?
I try to see in my logs but I can't find anything related to this. How can I know if there is not some kind of issue which make him takes so long ? How can I improve this ?

Thank you for all your answers.
Well, according to the man page and rc.sysinit, udevadm command in the rc.sysinit script does:
/sbin/udevadm settle
/sbin/udevadm control --property=STARTUP=
I assume this is the settle command which takes time.
But how can I list the uevents in the queue the udevadm settle command is waiting for ? If possible, with the delay of treatment of each of these uevents during the boot...
I have nothing related to this in my logs.
Regarding my hardware, I have one toshiba laptop P300-220 with two internal hard drives (and many partitions on them). But no external drive.
Last edited by Laserpithium (2010-07-20 08:35:36)

Hangs on Waiting for UDev uevents to be processed

On startup it hangs on "Waiting for UDev uevents to be processed". Sometimes an extra row saying "[ 6.423351] firewire_ohci: Failed to set Link Power Status" is shown, and sometimes the screen goes all black before it hang.
Last time I was logged in I made some upgrades (pacman -Syu), so I guess that could have caused this problem but I'm not sure how to fix it.
What should I do?

This is most probably a kernel bug. More specifically, a problem in a module that is being loaded on boot by udev. You can boot into your system by appending "init=/bin/bash" to your kernel commandline (in GRUB). First of all I'd uninstall any third-party (unsupported) kernel modules that you might have installed. If that does not work I'd revert to a previous kernel version and file a bug.

Waiting for udev uevents to be processed hangs for 30s. |SOLVED|

Hello. This is my first post.
Just installed ArchLinux with KDE 4.7,everything is working perfectly but something is really annoying.
When booting up the laptop (toshiba satellite) it takes too much loading this "waiting for udev uevents to be processed", like 30 or 40 secs,and after that all is fine.
i have tried a lot of things with DAEMONS AND MODULES, also tried blacklisting some modules just like this post said.
https://bbs.archlinux.org/viewtopic.php?id=133032
But nothing has worked.
Maybe this could help or at least be related:
dmesg | grep fail
[ 0.496066] pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
[ 0.499488] pci0000:3f: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
It looks just like the same thing that happened to TuxLyn in the post i showed before.
I have an ATI card HD5400 so the other solutions in the Forum like this:
https://bbs.archlinux.org/viewtopic.php?id=92189 didn't work at all.
Btw, ArchLinux rules!, i really liked it so decided to leave Debian!
Greets!
Last edited by imJorgeMerinoS (2012-01-25 02:51:04)

Welcome to arch. Great first post - all the right info, and it shows you've looked around for your own answer.
However, it seems you did miss the one thread you needed to find. The title was something like "Udev hangs for 30 seconds on boot." If you google that (with site:bbs.archlinux.org) you should find it quickly.
The gist of it is that there are certain modules that need to be added to the MODULES line in rc.conf for now. It seems that the vast majority (if not all) of these are the wireless modules - brcmsmac in my case, but it would be different in yours.
If you don't know your wireless module you can find it in the output of "lspci -v" and look for the line "kernel driver in use" under your wireless card.

[SOLVED] Endless UDev uevents from DVD Drive

After a recent (large) update, I seem to be getting nonstop UDev uevents from my DVD Drive. The first thing I noticed after performing the update and rebooting was that the "Waiting for UDev uevents to be processed" message timed out and failed. Everything else seemed fine, so I used udevadm to see if I could find anything:
$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
UDEV [1307739081.593903] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
KERNEL[1307739081.602768] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
UDEV [1307739081.620546] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
KERNEL[1307739081.629459] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
UDEV [1307739081.647213] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
KERNEL[1307739081.656111] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
UDEV [1307739081.673838] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
KERNEL[1307739081.682778] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
UDEV [1307739081.700991] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
KERNEL[1307739081.709447] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
UDEV [1307739081.727307] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
KERNEL[1307739081.736115] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
UDEV [1307739081.753807] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
KERNEL[1307739081.762773] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
UDEV [1307739081.780494] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
KERNEL[1307739081.789424] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
UDEV [1307739081.807156] change /devices/pci0000:00/0000:00:1c.4/0000:03:00.1/ide1/1.0/block/hdc (block)
Which goes on forever, with dozens of lines per second. hdc is my DVD drive, but nothing has changed there (I've had it for a few years now). Something is definitely wrong, though, as
a) another machine I have with Arch does not show so many messages when running udevadm monitor
and
b) when I open my DVD drive, the messages stop briefly, but it promptly closes itself and the messages continue
UDev was one of the almost 70 packages I updated (from 168 to 171). I suspect something may have gone wrong in updating UDev, otherwise I can post my pacman.log later.
Thoughts?
Last edited by Mystal (2011-06-11 17:18:58)

Still not entirely sure what was the initial cause, but after today's kernel upgrade (2.6.38.8 -> 2.6.39.1), all the messages are gone and UDev starts normally once more. I guess this is solved.

[Solved]Black screen after "waiting for udev uevents to be processed"

Hello friends,
Starting from late Dec., my laptop goes black screen after "waiting for udev uevents to be processed", after updating kernel to 2.26.32.*. The strange thing is that even the screen is black, the keyboard is working. For example, I can turn on/off the status lights of capslock and others. I guess something might be wrong with udev uevents configuration with regard to the latest kernel. I've noticed that in the new kernel, there are two drivers for intel integrated graphics. My laptop has a 855G, which is supposed to be functional by both drivers, at least according to the kernel description. Maybe because the udev is configured to use the second driver (for newer graphic chips), rather than the first driver, which caused the problem?
Regards,
Wen
Last edited by Wen (2010-01-28 13:14:28)

Have a look here: http://bbs.archlinux.org/viewtopic.php? … 70#p695670

Stop A Loader From Loading?

I am creating an image gallery where the user can select from several thumbnail images. Once selected, the thumbnails will enlarge and load the full sized image. My problem is that while the user is waiting for the full sized image to load, he may decide to close that image and view another image. I am trying to find a way to stop a loader from loading. Here is the code I have used. My problem is that even though the user has clicked on the unloadBtn, the loader continues to load the file. Is there a way to disable that?
import flash.net.URLRequest;
import flash.display.Loader;
import flash.events.Event;
import flash.events.ProgressEvent;
loadBtn.buttonMode = true;
loadBtn.addEventListener(MouseEvent.CLICK, loadStuff);
unloadBtn.buttonMode = true;
unloadBtn.addEventListener(MouseEvent.CLICK, unloadStuff);
var mLoader:Loader = new Loader();
function loadStuff(e:MouseEvent){
     var mRequest:URLRequest = new URLRequest('a.swf');
     mLoader.contentLoaderInfo.addEventListener(Event.COMPLETE, onCompleteHandler);
     mLoader.contentLoaderInfo.addEventListener(ProgressEvent.PROGRESS, onProgressHandler);
        mLoader.load(mRequest);
function onCompleteHandler(loadEvent:Event){
     addChild(loadEvent.currentTarget.content);
        loadEvent.currentTarget.content.x = 0;
     loadEvent.currentTarget.content.y = 0;
function onProgressHandler(mProgress:ProgressEvent){
     var percent:Number = mProgress.bytesLoaded/mProgress.bytesTotal;
     trace('Percent Loaded: ' + percent);
function unloadStuff(e:MouseEvent):void{
     mLoader.unload();
     mLoader.close();
     trace('Unloading....');

I have tried placing the close() before calling unload() so my code looks like:
     mLoader.close();
     mLoader.unload();
It still has no effect.

When ever I click on a page in Firefox, I get the message that Firefox has stopped the loading of that page, with an "allow" box in the upper right corner of th

When ever i try to migrate to another page, the browser puts up a blank page with the message that Firefox stopped the loading of the page, and there is an allow button in the upper right corner of the blank page, which i have to click on, to get to the page i want to travel to.
is this normal, and how do i fix it?

can you try restarting Firefox in safe mode.
[[Troubleshoot Firefox issues using Safe Mode]]
Reply back to us.

Waiting for Udev uevents to be proccessed forever

After a clean install from cd arch booted properly.
After updating everything and rebooting, boot hanged at waiting for Udev uevents to be proccessed for too long.
I reinstalled arch but this time I updated only udev and i have the same problem.
I dont know where to look for the error logs in order to find the problematic hardware (if there is one) or the incorrect configuration.

marios4 wrote:Solved by blacklisting sr_mod.
I found out it was problematic by trial and error.
I don't even know what this module does, if anyone knows I would apreciate a reply.
It's for CD and DVD drives. They won't work without it.

Bootup stops at "Loading UDev uevents"

Similar Messages

Maybe you are looking for