linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Dodge <dododge@dododge.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug *seems* to hang during boot]
Date: Mon, 04 Oct 2004 19:55:31 +0000	[thread overview]
Message-ID: <20041004195531.GA20448@basmati> (raw)
In-Reply-To: <4161A0FF.9010509@ntlworld.com>

On Mon, Oct 04, 2004 at 07:14:07PM +0000, Richard Wild wrote:
> Some other information noticed: it seems (to me) quite likely that the 
> message "cardmgr[953]: no sockets found!" is related to the problem, 
> because when I boot the 2.4 kernel is says instead "cardmgr[80]: no 
> pcmcia driver in /proc/devices".

cardmgr is a bit strange in how it accesses devices.  Here's a quick
explanation in case it's relevant to the problem.

"no pcmcia driver in /proc/devices":

That means just what it says.  cardmgr wants the major device number for
the pcmcia driver, so it reads through /proc/devices looking for it.
This error message indicates that it did not find a "pcmcia" line,
presumably because no driver was loaded.

"no sockets found!":

This indicates that it _did_ find "pcmcia" listed in /proc/devices,
and it tried to access the driver.  Here's where things get a bit
unusual.  After obtaining the major device number from /proc/devices,
cardmgr uses mknod(2) to create device files of its own.  It starts
with minor device 0 and continues in a one-up loop until it fails.
For each minor number, it creates a device file with a name of the
form "cm-PID-COUNTER", opens the file, and then immediately unlinks
the file while holding it open.  There are a number of directories
where it might try to do this, usually in this order:

  /var/lib/pcmcia, /var/run, /dev, /tmp

The "no sockets found" message indicates that it managed to do the
mknod for minor device 0, but got an ENODEV when it then tried to open
the resulting file.

So what this seems to be saying is that:

  - your 2.4 kernel has no PCMCIA stuff loaded at all.

  - your 2.6 kernel has at least the "ds" driver, which
    creates the "pcmcia" /proc/devices entry, but it has no
    card sockets.

I don't know if this is part of your problem or not, but since cardmgr
does do some device file manipulation, it might be worth investigating.

                                                  -Dave Dodge


-------------------------------------------------------
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-04 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 18:52 Hotplug *seems* to hang during boot] Richard Wild
2004-10-04 19:55 ` Dave Dodge [this message]
2004-10-04 20:44 ` Richard Wild
2004-10-04 21:16 ` Simone Gotti
2004-10-04 22:35 ` Richard Wild

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=20041004195531.GA20448@basmati \
    --to=dododge@dododge.net \
    --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).