Date: Wed, 28 Dec 2011 17:00:23 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: Chris Rees <utisoft@gmail.com> Cc: hackers@freebsd.org Subject: Re: Checking for other kernel modules on load Message-ID: <20111228150023.GY50300@deviant.kiev.zoral.com.ua> In-Reply-To: <CADLo83-OBNWzY_r_oFmUBjkNoCpifJ0_u9dYN52YTZ69X06o4Q@mail.gmail.com> References: <CADLo838QjrUunABB=3R_d6NO9bnNAcKXM%2BZt3DRam3RnOGnxGw@mail.gmail.com> <B8D5A1B2-4790-48CA-AAC3-D4333D52ECEB@gsoft.com.au> <CADLo8382uPC6YmreCz8irVuiOhSwc2axJTgQRpVJk-%2B0Win8rQ@mail.gmail.com> <20111228135641.GV50300@deviant.kiev.zoral.com.ua> <CADLo83-OBNWzY_r_oFmUBjkNoCpifJ0_u9dYN52YTZ69X06o4Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--b10Qt5W+7gVLGshn
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Dec 28, 2011 at 02:53:42PM +0000, Chris Rees wrote:
> 2011/12/28 Kostik Belousov <kostikbel@gmail.com>:
> > On Wed, Dec 28, 2011 at 12:23:58PM +0000, Chris Rees wrote:
> >> On 28 December 2011 12:21, Daniel O'Connor <doconnor@gsoft.com.au> wro=
te:
> >> >
> >> > On 28/12/2011, at 22:07, Chris Rees wrote:
> >> >> Is there a simple way to check for existence of a driver? =9AI could
> >> >> even check for /dev/sndstat, though that doesn't seem elegant to me=
...
> >> >
> >> > kldstat -v, but really /dev/sndstat seems simpler and just as effect=
ive.
> >> >
> >>
> >> Cheers-- I was thinking of a kernel-level function though.
> >>
> >> cognet@ suggested using modfind("sound"), I'll go with that.
> > Obvious question is what the panic is. Checking for modules loaded is
> > papering over some issue.
>=20
> True, although I figured that it was a simple conflict, possibly to do
> with sndstat.
>=20
> Also, I'm getting panics with the following patch, whether sound is
> loaded or not :)
>=20
> + if (modfind("sound") >=3D 0)
> + {
> + cmn_err (CE_WARN, "A conflicting sound driver is already loaded");
> + return EBUSY;
> + }
> +
>=20
> Is there a better way to handle such conflicts?
You have missed the point. There is some bug in oss driver that causing
the panic. Presumed 'conflict' cannot cause the harm itself, besides not
allowing second driver to attach to the same device, and should not result
in panic. Trying to implement a half-measure that only covers the problem
you do a mis-service.
And you still did not provided the panic message.
--b10Qt5W+7gVLGshn
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)
iEYEARECAAYFAk77LwcACgkQC3+MBN1Mb4g8JQCePyY1CYPa2sp/3ACnW3jgMmTh
syQAn27MIo0wDRz7LFcDEbr7rW7OjyTO
=wfmT
-----END PGP SIGNATURE-----
--b10Qt5W+7gVLGshn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111228150023.GY50300>