Date: Tue, 25 Aug 1998 11:57:20 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Andrzej Bialecki <abial@nask.pl> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic with DEVFS Message-ID: <Pine.BSF.3.95.980825115443.1236E-100000@current1.whistle.com> In-Reply-To: <Pine.BSF.4.00.9808251906160.8821-100000@korin.warman.org.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
is it possible to find out which device it is?
disabled devices should not show up in devfs as they
should not be probed and the probe routine should be responsible for
adding the devfs entries..
(actually the attach routine but...)
except for devices that do not probe, (e.g. /dev/mem)
which do it in their init routine.
On Tue, 25 Aug 1998, Andrzej Bialecki wrote:
> Hi,
>
> It was pointed to me that it's very easy to panic -current system running
> DEVFS on /dev, with / on MFS.
>
> The problem manifested itself with picobsd floppy. The following scenario
> causes panic with "mfs_strategy: bad dev":
>
> 1. boot with -c
> 2. disable at least one device
> 3. log in
> 4. cd /dev
> 5. ls -l
>
> What's funny is that when I do 'ls' (without -l) in step 5., everything is
> ok.
>
> My guess is that DEVFS doesn't like these devices which are present in
> kernel, but are disabled...
>
> Andrzej Bialecki
>
> +---------------------+------------------------+--------------------------+
> | <abial@nask.pl> | When in problem or in | if(halt_per_mth > 0) { |
> | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); |
> | Network in Poland | scream and shout. | } |
> + --------------------+------------------------+--------------------------+
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.980825115443.1236E-100000>