The bug was that the shell code used to find the udev process run from
the initramfs was not reliable... we replaced it with pkill
--
boot process interrupted by "could not kill pid 1984"
https://launchpad.net/bugs/81395
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
"Already fixed in feisty"
Nice! but what was then the actual bug? Was it certainly in udev? Should
I still try to catch a snapshot of the screen when the pc hangs or the
problem is solved?
--
boot process interrupted by "could not kill pid 1984"
https://launchpad.net/bugs/81395
--
ubuntu-bugs
Already fixed in feisty
** Changed in: udev (Ubuntu)
Status: Unconfirmed => Fix Released
--
boot process interrupted by "could not kill pid 1984"
https://launchpad.net/bugs/81395
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bu
Not an upstream bug
** Changed in: udev (upstream)
Status: Unconfirmed => Rejected
--
boot process interrupted by "could not kill pid 1984"
https://launchpad.net/bugs/81395
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Andrea: It would be nice if you could boot the /other/ Ubuntu entry in
your boot menu in the future (rescue or whatever it's called, that
produces more messages), and in case it hangs, post another picture.
Thank you.
--
boot process interrupted by "could not kill pid 1984"
https://launchpad.net/
You're not supposed to know. :-)
Blaming on udev package for now.
** Changed in: malone (upstream)
Product: Malone => udev
Status: Rejected => Unconfirmed
** Changed in: Ubuntu
Sourcepackagename: None => udev
--
boot process interrupted by "could not kill pid 1984"
https://launchp
Sorry I don't know what a "race condition" is.
--
boot process interrupted by "could not kill pid 1984"
https://launchpad.net/bugs/81395
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I forgot to say that before that screenshot there is a filesystem check,
which usually ends with "The filesystem is clean [ok]". This is also
mentioned in some of the Google hits.
It's not so easy to take a screenshot while the filesystem check is
going on because when it ends the screen is refres
All of these systems seem to have reiserfs as root partition.
--
boot process interrupted by "could not kill pid 1984"
https://launchpad.net/bugs/81395
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Directly after the GRUB boot script:
readlink:/proc/1915/exe: No such file or directory
[: /sbin/udevd: unknown operand
kill: could not kill pid '1915': no such process
Maybe a race condition in the udev init script?
--
boot process interrupted by "could not kill pid 1984"
https://launchpad.ne
1. Yes, the machine hangs and I have to turn it off.
2. I attach here a screenshot of the error message.
3. The Google search `ubuntu boot "could not kill pid"` gives 11 hits,
among them:
http://ubuntuforums.org/showthread.php?t=346020
http://ubuntuforums.org/showthread.php?t=346436
https://answ
Can you comment on
1. What happens when this message appears (I presume the machine hangs
because you have to turn it off)?
2. Please provide the 4-5 lines of text prior to this message for
context.
Also, if you have Google hits for this bug, it would be convenient to
include them here (although
** Changed in: malone (upstream)
Status: Unconfirmed => Rejected
--
boot process interrupted by "could not kill pid 1984"
https://launchpad.net/bugs/81395
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I am using kernel 2.6.17.
--
boot process interrupted by "could not kill pid 1984"
https://launchpad.net/bugs/81395
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
14 matches
Mail list logo
