mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Taylor Carpenter <taylorcc@codecafe.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops when accessing /dev/fd0 (kernel 2.4.7 and devfsd 1.3.11)
Date: Sat, 25 Aug 2001 11:28:12 -0500	[thread overview]
Message-ID: <20010825112812.A31755@pioneer.oftheInter.net> (raw)
In-Reply-To: <20010816222811.A1672@pioneer.oftheInter.net> <200108170419.f7H4J7c20693@vindaloo.ras.ucalgary.ca> <20010821223042.A30478@pioneer.oftheInter.net> <200108220507.f7M576q25412@vindaloo.ras.ucalgary.ca> <20010822191227.A11226@pioneer.oftheInter.net> <200108230505.f7N55sr05856@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200108230505.f7N55sr05856@vindaloo.ras.ucalgary.ca>; from rgooch@ras.ucalgary.ca on Wed, Aug 22, 2001 at 11:05:54PM -0600

On Wed, Aug 22, 2001 at 11:05:54PM -0600, Richard Gooch wrote:
> Taylor Carpenter writes:
> >
> You mean the floppy module gets loaded as a result of the mountall
> script being run?

As far as I can tell, when it runs mount -avt, the floppy module
is loaded if there is an entry in /etc/fstab for /dev/fd0 (even w/the noauto
option).
 
> Is the /etc/modules.devfs the one that ships with devfsd?
> Specifically, you need the following line:
> alias     /dev/floppy		floppy

I do not have a modules.devfs.  I do have a /etc/modutils/devfsd, but it does
not have an alias entry for the floppy.

I added the entry, and it now shows up in modules.conf.

> and of course the MODLOAD action in /etc/devfsd.conf.

I did not have anything specific to /dev/fd* in devfsd.conf, but I did have a
.* entry to load it.  I commented that out, after your other email.

I added /dev/fd0, and /dev/floppy MODLOAD but it is still not autoloading.
 
> Do you mean to say that the Oops happens during the boot sequence,
> before you can log in?

Yes, the oops happens during boot when it runs the mountall script, and then
right after when something else tries to access the device.  I did not mention
before, but devfsd will not run after I get this oops.  Or I should say it
dies, and then I can not run it again after logging in.  I get an oops
everytime I access the floppy device after this, but I only get an oops if I
get one during boot.

> You must have a bogus /etc/devfsd.conf or /etc/modules.devfs file for
> module autoloading not to work.

I had commented out the .* MODLOAD, it worked before that.  I uncommented the
.* and it still does not work, something else must have changed.

> I don't know what a "perms" file is. I know Debian uses some
> convoluted directory tree for devfsd configuration, but frankly, I
> don't want to know about that. If you have one of these monstrosities,
> please collapse them all into a single /etc/devfsd.conf file a report
> based on that.

OK.  I have nothing but REGISTER PERMISSIONS for floppy in devfsd.conf.

> > I have many LOOKUP entries.  I did not have any specific to
> > /dev/fd*, but that was caught by the .* LOOKUP entry.  I commented
> > that out, which is probably why mdir and other commands do not work
> > w/o manually loading floppy.o.
> 
> Oh! Well, duh!

I uncommented .* LOOKUP and it still did not autoload.

> Hm. Please try a virgin 2.4.9 kernel with CONFIG_DEVFS_FS=n and try
> again. I have this feeling that I'm chasing someone else's bug...

OK, done.  I did not get the oops with DEVFS turned off (in 2.4.9).


  reply	other threads:[~2001-08-25 16:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17  3:28 Taylor Carpenter
2001-08-17  4:19 ` Richard Gooch
2001-08-22  3:30   ` Taylor Carpenter
2001-08-22  9:00     ` Steve Hill
2001-08-22 10:47       ` Alan Cox
2001-08-22 10:48         ` Steve Hill
2001-08-22 10:53           ` Alan Cox
2001-08-22  5:07   ` Richard Gooch
2001-08-23  0:12     ` Taylor Carpenter
2001-08-23  5:05     ` Richard Gooch
2001-08-25 16:28       ` Taylor Carpenter [this message]
2001-09-03 23:07       ` Richard Gooch

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=20010825112812.A31755@pioneer.oftheInter.net \
    --to=taylorcc@codecafe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    /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®