Udev worker error during boot "worker [XX] did not accept message -1 (Connection refused), kill it

Bug #647404 reported by Elias Julkunen
694
This bug affects 139 people
Affects Status Importance Assigned to Milestone
udev
Confirmed
Undecided
Unassigned
udev (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: udev

I'm using Ubuntu 10.10 with latest updates. I guess you see all necessary information from attachments.
During boot, I get error message:
"udevd[80]: worker [XXX] did not accept message -1 (Connection refused), kill it"
XXX is number around 240, see the picture.
I didn't find any information about that in logs, so I took a picture. I tried to google for similar bugs too but I didn't find any – I'm sorry if there are.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: udev 162-1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sat Sep 25 11:10:28 2010
MachineType: Gateway AOA110
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=378e3c34-d70a-40a8-b977-f1e751ad7db5 ro quiet splash
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: udev
dmi.bios.date: 12/09/2008
dmi.bios.vendor: Gateway
dmi.bios.version: v0.3103
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Gateway
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnGateway:bvrv0.3103:bd12/09/2008:svnGateway:pnAOA110:pvrLU.S030A.079:rvnGateway:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AOA110
dmi.product.version: LU.S030A.079
dmi.sys.vendor: Gateway

Revision history for this message
Elias Julkunen (eliasj) wrote :
Revision history for this message
Elias Julkunen (eliasj) wrote :
Revision history for this message
talent03 (talent03) wrote :

I have had this same problem as well. I have been trying to figure what is causing it, but I just can't figure it out. I am running a stock eee pc 1000.

Revision history for this message
Elias Julkunen (eliasj) wrote :

I tried the newest mainline kernel (just in case) and this error happens with it too.

This bug makes the boot experience very bad because the beautiful Ubuntu boot screen starts after this and it takes ~3 seconds.

Changed in udev (Ubuntu):
status: New → Confirmed
Revision history for this message
ingolf.schaefer (ingolf-schaefer) wrote :

I think the bug is specific to netbook hardware. I see it to on my Aspire AOA 110, too. That is the very same model as Elias, same specs but newer BIOS 3309.

Revision history for this message
Mikhail Polianski (mnpol) wrote :

same problem here: fresh install on Asus EeePc 901

Revision history for this message
Mike G (grcmptrnrd) wrote :

same here, EeePc 1000HEB occurs on roughly half of boots.

Revision history for this message
Keith Allcock (keith-allcock) wrote :

Same here, eee 901 ...

Any good ideas to help pinpoint ?

Revision history for this message
Mikhail Polyanskiy (mpolyanskiy) wrote :

apparently this only appears on netbooks... So is it hardware-related or Unity-related issue? Did anyone try generic (not netbook edition) Maverick on the same machine?

Revision history for this message
James Grieve (jamesagrieve) wrote :

I can confirm this bug for the AA1 too, but using the desktop RC for Maverick.

Revision history for this message
Elias Julkunen (eliasj) wrote :

I'm using normal Ubuntu too, so this is not Unity related error.

Revision history for this message
Arjen Douma (a-douma) wrote :

I have the same issue on my AA1 110L with de Ubuntu RC NBR 10.10

Revision history for this message
Dmitry Murat (dmitry-murat) wrote :

One more @ eee 901 with 10.10 final.

Revision history for this message
Mike (mike-summersault) wrote :

And another netbook with that same error.

Dell Inspiron Mini 910 (atom n270, 1gb RAM, 8gb SSD)

Have tried with both Desktop and Netbook editions of 10.10 final (tried them both this morning) booting and installing from a USB stick.

Revision history for this message
Riptr (riptr) wrote :

I have the same issue on my Acer Aspire 1, running Ubuntu 10.10

Revision history for this message
greywolf (timcraig) wrote :

I have the same error on my EeePC 900a. Occurs every time during boot up.

Revision history for this message
Chap (eric-chaperon) wrote :

I have the same problem with fresh install Ubuntu 10.10 on Asus EeePc 901

Revision history for this message
Uwe Geercken (uwe-geercken) wrote :

I have a desktop: Core2 Duo, E8400, 2GB memory and have the same message runint 10.10

Revision history for this message
Vytautas (vytautasjc) wrote :

Same on Eee 1000 (Ubuntu 10.10)

Revision history for this message
Chap (eric-chaperon) wrote :

Click on the link "This bug affects you and 15 other people" on top of this page to alert the developpers ;-)

Revision history for this message
Chris Jutting (amdinside624) wrote :

I am also experiencing this, also on an Acer Aspire One AOA 110 with a 32GB SSD.

It seems like this issue is mostly affecting SSD based systems.

Revision history for this message
Coprophiliac (coprophiliac) wrote :

Also seen this on a Dell Inspiron 910 Netbook with the Netbook Edition of Ubuntu 10.10 installed.
Nothing in dmesg or /varl/log/messages

Revision history for this message
Victor Maryama (victor-maryama) wrote :

I have this same bug on a Acer Aspire One with 8GB SSD and Ubuntu Netbook Remix 10.10.

Revision history for this message
lotus49 (lotus-49) wrote :

I too have this on my Acer Aspire One running Ubuntu Desktop.

Revision history for this message
peet llort (troll-dionysos) wrote :

+1
eeepc 901 ubuntu 10.10 reinstall after format all

Revision history for this message
Leap Frog Group, Inc. (leapfrog-support) wrote :

One more.
Ubuntu Desktop, dual boot with 10.04 and 10.10 on separate hard drives. All updates applied.

Revision history for this message
Druid (druid99999) wrote :

+1

Fresh install of UNE 10.10 on a Dell Inspiron Mini 910 (atom n270, 512mg RAM, 4gb SSD)

Revision history for this message
Eric Svärd (eric-svard) wrote :

Same on my Eee 901 with a fresh install of Xubuntu 10.10.

Revision history for this message
Pham Gia Liem (liempg) wrote :

One more on Dell Inspiron Mini 910 after a fresh install of Ubuntu 10.10 (8 gig SSD).
Need quick focus on this bug. Thanks.

Revision history for this message
Andrew Wright (andrew-wright) wrote :

Another Acer Aspire One here, the ZG5. Happens every boot. Not using the original SSD any more, replaced with a CompactFlash through an IDE interface. Fresh install of 10.10 final Netbook Edition on an ext2 partition. Can provide any logs on request.

Revision history for this message
watkin5 (robert-watkin5) wrote :

Me too ....
UNR 10.10 on my Eee PC 1000 with ext4 file system on a 8 Gb SSD.

Revision history for this message
Will Laws (whlspacedude) wrote :

Me too.
HP mini 110-1030NR
16gb sdd
Ubuntu 10.10 desktop

Revision history for this message
MaxNegro (maxnegro) wrote :

I used to have my system (10.10 netbook) installed with / in xfs, and never experienced this problem. Today I switched to ext4 and started seeing this. Don't know if this may cast some light on the problem...

I have a Dell mini-9.

Revision history for this message
Hans (hans-vandeveire) wrote :

+1
Kubuntu 10.10 Plasma Netbook
ACER ASPIRE ONE 16 GB SSD

Revision history for this message
Samizdata (samizdata) wrote :

AOA 110, current BIOS, ext4, 8 Gb SSD, installed via upgrade, Maverick 10.10 Netbook.

Revision history for this message
miho (cst372000) wrote :

 I get error message "udevd[80]: worker [XXX] did not accept message -1 (Connection refused), kill it" too. How I solve this problem. AOA 110

miho (cst372000)
description: updated
Revision history for this message
ingolf.schaefer (ingolf-schaefer) wrote :

I have no additional insight in fixing this bug, but at least it is possible to just hide it.

I repeat: The following does not fix anything, just hides the error message.

In Terminal enter:

sudo -s
echo FRAMEBUFFER=y >>/etc/initramfs-tools/conf.d/splash
update-initramfs -u

This loads the framebuffer at start which hides the errors. Taken from: http://www.ubuntugeek.com/quick-tipplymouth-themes-in-ubuntu-10-04-lucid-lynx.html

Revision history for this message
Michael Davidson (talinus) wrote :

I receive the same error on nearly all boots.

Fresh install Ubuntu 10.10 final release
Asus EEE PC 1000
Stock: Atom 1.6 N270, 1GB, 8GB SSD X 2

Since I can't find info in /var/log and am unfamiliar with debian distros, Is someone going to take on this problem?

Thank you,
Mike D

Revision history for this message
Mike Reynolds (sleepy8765) wrote :

Re: Ingolf.schaefer's suggestion:

In Terminal enter:

sudo -s
echo FRAMEBUFFER=y >>/etc/initramfs-tools/conf.d/splash
update-initramfs -u

Makes no difference for me on a HP mini 110 running ubuntu 10.10 with unity.

Pity - I'd be happy with a solution that simply hid it.

Revision history for this message
Jose Maria Tagarro Marti (chema92) wrote :

Same on fresh install of full Desktop edition on 1st SSD disk (4GB, the other one 16GB) on EEE PC 901.

tags: added: apport-collected
40 comments hidden view all 120 comments
Revision history for this message
Elias Julkunen (eliasj) wrote :

Ian: If 9.10 works fine, then use it, but this bug affects nothing in your system, it is just an error message. That's what I think.

And I still wonder why no developer has commented this...

Revision history for this message
Juan E Munoz Oca (juaneduardo11) wrote :

mini hp 1000 with ubuntu netbook 10.10. same problem.

Revision history for this message
Dylan Wimp (defdylan) wrote :

HP Mini 110- 1000, Ubuntu Netbook Remix 10.10. Same error. Can nobody fix this?

Revision history for this message
RandyF (randyfrisch) wrote :

...apparently not. I have a fresh install of 10.10, and get this error as well. Dell Mini 9.

Revision history for this message
Rikard Larsson (rikard-larsson) wrote :

I have the same problem with fresh install Ubuntu 10.10 (Desktop Edition) on Asus EeePc 901

Revision history for this message
Keith Allcock (keith-allcock) wrote :

The acpi=off change is not recommended :-)

Revision history for this message
Keith Allcock (keith-allcock) wrote :

Playing with trying to get udev to log something with the following result:

Changing /etc/udev/udev.conf to log debug info and changing /etc/default/grub to not have quiet on the default boot options, shows the errors come before this line:
usb 1-8: configuration #1 chosen from 1 choice

... but there is too much info on screen and nothing is in any log files (specifically the worker lines we all see)

Without the logging option, I can then tell that the errors should be between these two entries;
kernel: [ 1.394993] EXT4-fs (sda1): mounted filesystem with ordered data mode
kernel: [ 1.528061] usb 1-8: configuration #1 chosen from 1 choice

and when udev is in debug you can see these parts are run
/scripts/local-bottom

Unfortunately when the grub option has the quiet removed you don't get the error lines showing so I can't see any more details.

Does anyone know how to switch on some logging to show what happens between the two logged lines?

Revision history for this message
Phil (devilofsky) wrote :

Booting 10.10 netbook today, I got a message like this for several seconds:

http://img99.imageshack.us/img99/1593/p1020880g.jpg

Revision history for this message
Phoenixie (secure-pho) wrote :

I get exactly the same message as @Phill on my MSI Wind U100 Netbook running Ubuntu 10.10 with latest updates.

Revision history for this message
Peterson Silva (petersonsilva) wrote :

Look out for updates, people! I no longer see this here in my aspire one! (I booted up a few minutes ago and plymouth appeared right away)

Revision history for this message
PeterNR (peternybor) wrote :

Latest updates did not help me :-(
Still getting lots of "udevd[80]: worker [XXX] did not accept message -1 (Connection refused), kill it" on my ASUS Eee S101, Ubuntu 10.10 Netbook Edition, latest updates as of today.

Revision history for this message
Andreas Ruprecht (rupran) wrote :

Same problem here, getting these messages since yesterday on 10.10 on my desktop (Intel C2Q 9400, 4GiB RAM, Radeon graphics). In the attachment is a part of the dpkg.log with the updates I installed yesterday and the day before.

Revision history for this message
Andreas Ruprecht (rupran) wrote :

Just seeing: Also getting this message on the 2.6.32-25.44 kernel. And on the 2.6.35-22 I'm left with the "modprobe fatal"... make by boot screen look good again...

Revision history for this message
jon-paul clark (jon-paul-clark) wrote :

i've had this problem for several months, running maverick netbook on an eeepc 901. Gave up waiting for a fix and went to work on it yesterday. Try this: 'sudo udevadm trigger --type failed' in terminal
It doesn't boot any quicker but it is a clean boot and reboot.

Revision history for this message
jon-paul clark (jon-paul-clark) wrote :

scrub that it's back!

Revision history for this message
jon-paul clark (jon-paul-clark) wrote :

echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash

sudo update-initramfs -u

these 2 commands run in terminal should get plymouth running properly and hide the errors

Revision history for this message
Keith Allcock (keith-allcock) wrote :

Excellent .... this has hidden the error for me!

Revision history for this message
Andrew Wright (andrew-wright) wrote :

Same here - error is suppressed. Thanks!

Revision history for this message
Peterson Silva (petersonsilva) wrote :

It worked for me too =) Thanks!

Revision history for this message
codejumper (jumperpro) wrote :

the same for me

Revision history for this message
nordicnurse (nordicnurse) wrote :

Another Acer Aspire One a110 here. Clean install of Lubuntu 10.10. 2.6.35.24-generic.

Revision history for this message
Oleg A. (dude1phoenix) wrote :

@jon-paul clark Can you explain what this means?

This bug in plymouth or in it config?

Revision history for this message
Oleg A. (dude1phoenix) wrote :

@jon-paul clark wrote on 2010-12-21: #96
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash

sudo update-initramfs -u

these 2 commands run in terminal should get plymouth running properly and hide the errors

Work 4 me. Thx.

Revision history for this message
Charlie Kravetz (charlie-tca) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in udev (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Revision history for this message
Valery Kondakoff (strauss) wrote :

This bug is still reproducible in Natty Narwhal Alpha 3.

Revision history for this message
Lawrence H. Bulk (lhbcomm) wrote :

It's disappointing that this 'bug' hasn't been corrected in 'Natty' (at least as yet). I certainly hope that someone can introduce a fix for the anomaly. Does anyone know WHY it occurs?

It appears to be more of an annoyance than a real problem. At least so far I have not seen it affecting anything I try to do on my Asus Eee PC 1000/Linux (running 10.10, network update from 10.04 clean install).

I have noticed that when I begin the boot, the background shown is that of 10.04; once I enter the login information, the background immediately changes to that of 10.10. Has anyone else noticed this? And does it occur with computers which have had a clean install of 10.10?

Again I hope that someone can come up with a fix.

Revision history for this message
Dmitry Mn (progscrt) wrote :

one more

Same error when i add max_loop=1300 for kernel cmd.

(/boot/vmlinuz-2.6.32-29-generic root=UUID=a60346eb-7611-449e-a9b8-2121d60ddd33 ro quiet splash max_loop=1300)

For sample, max_loop=1024 without this error.

Ubuntu 10.04.2 LTS
Linux 2.6.32-29-generic #58-Ubuntu SMP Fri Feb 11 20:52:10 UTC 2011 x86_64 GNU/Linux

Revision history for this message
resonant . interval (resonant-interval) wrote :

i get --> udevd[79] instead of [80]

Xubuntu 10.10 desktop on acer aspire one 110L (8gb SD) installed from usb

Revision history for this message
bamjammer (bamjammer) wrote :

Same problem with udevd as others. I have seen udevd[79], udevd[80], or udevd[81] at startup of my HP Mini 1000 (16gb sd).

xaav (xaav)
Changed in udev:
status: New → Confirmed
Revision history for this message
Erik1984 (erik1984) wrote :

Just happened to me too. However after a reboot the messages did not show up anymore. Where can I find these messages in the logs?

Revision history for this message
Oleg A. (dude1phoenix) wrote :

Bug back after update natty to beta.

Revision history for this message
bamjammer (bamjammer) wrote :

Problem still there after update to 11.04 from 10.10. Now error message begins "udevd [67]:" but the rest is the same. Usually fills a screen and a half of incremental workers being killed. Then something about a cache page not found. Once the machine gets going everything else seems OK.

Revision history for this message
slegrand (legrand-simon) wrote :

It started happening after I updated to 11.04, however I also at the same time replaced my old HDD with and SSD. Could it be a Solid state drive problem? Since all other users seem to be experiencing it with netbooks it could be a possibility.

Revision history for this message
Lawrence H. Bulk (lhbcomm) wrote : Re: [Bug 647404] Re: Udev worker error during boot "worker [XX] did not accept message -1 (Connection refused), kill it

A few weeks before the release of 11.04, there was evidently an update which
caused at least part of the problem to cease. I still saw the 10.04
background on the login screen (which switched immediately to the 10.10
background once I had logged in), but the udev message no longer appeared.

I won't go into my reasons for doing this but, rather than try a network
upgrade on this particular computer (Asus Eee PC 1000/Linux, formerly with
Asus' proprietary distro but replaced with Ubuntu last year), I decided to
'wipe' (with DBAN) and completely reinstall Ubuntu (with 11.04).

I have very few programs on this computer; my wife and I use it when
traveling to get e-mail, listen to internet radio stations, and so forth.

It has two hard drives, both SSDs - 8 GB (primary) and 32 GB (secondary).
(Why Asus made it this way I cannot understand; until you really get to
understand how to coordinate the two drives, it can be a real pain.)

The 'wiping' process took a couple of hours; reinstallation of Ubuntu took
only a half-hour and the configuration to our tastes took another hour.

Now everything works perfectly. I recommend that anyone who is annoyed by
this udev message (or who is having some other problems) consider wiping and
reinstalling.

It has certainly worked for me.

Revision history for this message
Peter Hansen (peter-launchpad-engcorp) wrote :

I see various comments that this may affect only Netbooks. Not the case. I just set up a new headless server, quad core Xeon X3430, with a 500GB SATA drive, and am getting the same errors at startup with an Ubuntu 11.04 install. I don't know whether this occurred with the fresh install... I think not... but I did just notice it immediately after going through a root filesystem resize (shrinking it from the full drive to 100GB) using the Rescue CD (actually a USB flash drive).

If there's any connection to solid state drives here, it's that I installed this from a USB key and did the resizing just now from a USB key in Rescue mode. Hope that helps...

Revision history for this message
sctechlaw (sctechlaw) wrote :

Ubuntu 11.04 upgraded from 10.10 on an iMac (powerpc). After the messages finish scrolling by I am dumped at a TTY login prompt. Can log in, but no GUI, am stuck in terminal. This machine has 1 GB of ram and a 7 GB hard drive. It has both Ubuntu and Lubuntu on it. Tried the commands above:
sudo -s
echo FRAMEBUFFER=y >>/etc/initramfs-tools/conf.d/splash
update-initramfs -u

but no help so far.

Revision history for this message
sctechlaw (sctechlaw) wrote :

Re message #116: Was able to get a GUI by changing to the 2.6.35.30 kernel from the 2.6.38 version, and no more pesky messages.

Revision history for this message
Alec Ellsworth (ellsworth-alec) wrote :

newish addition to the bug:
I tried running a virtual machine through virtual box. The virtual OS is Fedora, and when I tried to start the machine I got the udev kill it message, and then got kicked into the root terminal for the virtual appliance. I don't know how or if I can get to the GUI from there. I have attached a screenshot

Revision history for this message
unmacaque (unmacaque) wrote :

I have got a similar problem as #118.

I install Arch Linux as a VirtualBox guest system. Once up and running, I install systemd to replace the default initscripts startup system. After restarting, I am thrown into 'emergency mode' and am greeted by random modprobe messages (see the attached screenshot). Going from there, I can login as root but all mounts save for the system partition seem to have failed. If I press Ctrl+D twice or try "systemctl default" as suggested, I get multiple "worker [XXX] did not accept message -1" lines.

If I switch back to the initscripts system, the system boots fine. Most curiously, the host system is also running Arch Linux with systemd and it never failed during boot.

Revision history for this message
xaav (xaav) wrote :

This problem is not occurring for me any more upon upgrading to Ubuntu
11.10.

2011/11/27 unmacaque <email address hidden>

> I have got a similar problem as #118.
>
> I install Arch Linux as a VirtualBox guest system. Once up and running,
> I install systemd to replace the default initscripts startup system.
> After restarting, I am thrown into 'emergency mode' and am greeted by
> random modprobe messages (see the attached screenshot). Going from
> there, I can login as root but all mounts save for the system partition
> seem to have failed. If I press Ctrl+D twice or try "systemctl default"
> as suggested, I get multiple "worker [XXX] did not accept message -1"
> lines.
>
> If I switch back to the initscripts system, the system boots fine. Most
> curiously, the host system is also running Arch Linux with systemd and
> it never failed during boot.
>
> ** Attachment added: "archlinux-systemd-udev.png"
>
> https://bugs.launchpad.net/ubuntu/+source/udev/+bug/647404/+attachment/2610682/+files/archlinux-systemd-udev.png
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/647404
>
> Title:
> Udev worker error during boot "worker [XX] did not accept message -1
> (Connection refused), kill it
>
> Status in udev - /dev/ management daemon:
> Confirmed
> Status in “udev” package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: udev
>
> I'm using Ubuntu 10.10 with latest updates. I guess you see all necessary
> information from attachments.
> During boot, I get error message:
> "udevd[80]: worker [XXX] did not accept message -1 (Connection refused),
> kill it"
> XXX is number around 240, see the picture.
> I didn't find any information about that in logs, so I took a picture. I
> tried to google for similar bugs too but I didn't find any – I'm sorry if
> there are.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: udev 162-1
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
> Uname: Linux 2.6.35-22-generic i686
> Architecture: i386
> Date: Sat Sep 25 11:10:28 2010
> MachineType: Gateway AOA110
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic
> root=UUID=378e3c34-d70a-40a8-b977-f1e751ad7db5 ro quiet splash
> ProcEnviron:
> LANG=en_GB.utf8
> SHELL=/bin/bash
> SourcePackage: udev
> dmi.bios.date: 12/09/2008
> dmi.bios.vendor: Gateway
> dmi.bios.version: v0.3103
> dmi.board.asset.tag: Base Board Asset Tag
> dmi.board.vendor: Gateway
> dmi.board.version: Base Board Version
> dmi.chassis.type: 1
> dmi.chassis.vendor: Chassis Manufacturer
> dmi.chassis.version: Chassis Version
> dmi.modalias:
> dmi:bvnGateway:bvrv0.3103:bd12/09/2008:svnGateway:pnAOA110:pvrLU.S030A.079:rvnGateway:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
> dmi.product.name: AOA110
> dmi.product.version: LU.S030A.079
> dmi.sys.vendor: Gateway
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/udev/+bug/647404/+subscriptions
>

Displaying first 40 and last 40 comments. View all 120 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.