[arch-dev-public] blacklisting issue, perhaps initscripts or kernel 3.0 related

[Dave Reisner]

On Mon, Aug 01, 2011 at 05:37:56PM +0200, Thomas Bächler wrote:
> Am 01.08.2011 17:23, schrieb Dave Reisner:
> > It's also not recommended by upstream, as per modprobe.conf(5). We
> > shouldn't make any guarantees about module load order. What's the
> > problem we're trying to solve with this juggling? Is this bandaiding and
> > issue that should be taken upstream to the kernel folk? Or, is this some
> > pre-emptive attack against hardware being claimed by the wrong module,
> > in which case we should be leaving it up the user to figure out which
> > module they want to use...
> 
> Apparently, it is recommended upstream to load ehci before uhci or ohci
> (which userspace cannot safely guarantee) and actual bugs are caused if
> we don't. I don't like this, but we couldn't think of another solution.
> 

Oh, absolutely...

https://bugzilla.redhat.com/show_bug.cgi?id=464908
https://bugzilla.redhat.com/show_bug.cgi?id=154008
https://bugs.archlinux.org/task/12009

and every distro does this, similar to the way we do it. This seems like
an edge case though -- you might want ohci _and_ ehci for different
devices. On the other hand, you definitely don't want (incoming
contrived example) b43 being loaded for your wifi card that can use
brcmsmac instead. There's no use case for both being loaded. In the
case of sound modules, we shouldn't enforce order -- leave it up to the
user to order the devices via modprobe config.

dave