From: "Captain Wiggum" <captwiggum@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Linux kernel 2.6.16.14 boot errors: udevd-event: udev_make_node and find_free_number
Date: Fri, 12 May 2006 13:29:52 -0500 [thread overview]
Message-ID: <3d78499d0605121129m3fe0951fy68e55ec1dce13397@mail.gmail.com> (raw)
My 2.6.15.4 booted without any errors or warnings. Now with 2.6.16.14 I
get the below errors. I have also installed 2.6.16.14 on another
computer, and it works great there. I stepped through every kernel
config option and everything is in place.
Any ideas? All suggestions appreciated.
Gentoo, gcc 3.4.4-r1, P4-1.5GHz, 512MB RAM, hp pavilion 7955.
-------------------------
BOOT, CONSOLE MESSAGES:
...<snip>...
* Populating /dev with saved device nodes ... [ ok ]
* Seeding /dev with needed nodes ...
cp: cannot create special file `/dev/null': File exists
cp: cannot create special file `/dev/zero': File exists [ ok ]
* Setting up proper hotplug agent ...
* Using netlink for hotplug events... [ ok ]
* Starting udevd ... [ ok ]
* Populating /dev with existing devices through uevents ...
udevd-event[1462]: udev_make_node: mknod(/dev/ttyS0, 020660, 4, 64)
failed: File exists
udevd-event[1463]: udev_make_node: mknod(/dev/ttyS1, 020660, 4, 65)
failed: File exists
udevd-event[1464]: udev_make_node: mknod(/dev/ttyS2, 020660, 4, 66)
failed: File exists
udevd-event[1465]: udev_make_node: mknod(/dev/ttyS3, 020660, 4, 67)
failed: File exists
[ ok ]
* Letting udev process events ...
udevd-event[1984]: find_free_number: %e is deprecated, will be removed
and is unlikey to work correctly. Don't use it.
udevd-event[1986]: find_free_number: %e is deprecated, will be removed
and is unlikey to work correctly. Don't use it.
[ ok ]
* Finializing udev configuration ... [ ok ]
...<snip>...
next reply other threads:[~2006-05-12 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 18:29 Captain Wiggum [this message]
2006-05-12 20:54 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d78499d0605121129m3fe0951fy68e55ec1dce13397@mail.gmail.com \
--to=captwiggum@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®