linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim McCloskey <mcclosk@ucsc.edu>
To: linux-hotplug@vger.kernel.org
Subject: FATAL error message
Date: Sun, 10 Oct 2004 15:48:46 +0000	[thread overview]
Message-ID: <20041010154846.GA19676@ohlone> (raw)


Hello. I hope it's OK to ask a help question here rather than a
developer's question.

kernel: 2.6.7
udev:  version 0.032 packaged for Debian testing

All was working very well for me. Then I had two hard shutdowns in a
row caused by power-failures. On the second re-boot, I got this message:

  FATAL: udev still active on /dev/

And it won't go away after several cycles of clean shutdown followed
by reboot.  I can't actually say that anything is broken. Device files
are still created:

Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcsa2'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcs4'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcsa4'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcs3'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcs5'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcsa5'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcsa6'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcs6'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcsa3'
Oct 10 08:03:45 lapdog udev: creating device node '/dev/vcs2'

I can mount and un-mount usb devices as needed, I can play
sound-files, use alsamixer, and so on. So far, the only source of
worry is the warning message itself.  But that big word FATAL all in
capital-letters is not reassuring.

I've looked for the error-message on Google and on various mailing
lists and not found anything. I've gone through the docs in
/usr/share/doc. I've stopped and re-started the udev init-script but
that had no more effect than re-booting and produces the same warning
message (unsurprisingly). I've also removed and re-installed the udev
package. The message persists through all of this.

My suspicion is that there is some temporary file that should have been
deleted in the course of a clean shutdown which has not been, but I
would really appreciate any advice that might be available here.

Thanks to all for a really great utility,

Jim McCloskey


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2004-10-10 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10 15:48 Jim McCloskey [this message]
2004-10-16 13:39 ` FATAL error message Jim McCloskey
2004-10-16 16:40 ` Kay Sievers

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=20041010154846.GA19676@ohlone \
    --to=mcclosk@ucsc.edu \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).