All of lore.kernel.org
 help / color / mirror / Atom feed
* module is not unloaded when probe fails
@ 2004-03-22 21:08 Giuliano Pochini
  2004-03-22 23:11 ` Carl-Daniel Hailfinger
  0 siblings, 1 reply; 2+ messages in thread
From: Giuliano Pochini @ 2004-03-22 21:08 UTC (permalink / raw)
  To: Alsa-devel



When I try to load a module and it fails (snd-darla20 in this case) the
module is not unloaded. IIRC it didn't happen some months ago, but I have no
idea what is the cause because I changed a lot of stuff in the meantime
(kernel, compiler, modutils...). Is this the expected behaviour ?

[Giu@Jay Giu]$ uname -a
Linux Jay 2.6.3-ben2 #10 SMP Sun Mar 14 21:46:34 CET 2004 ppc unknown


[root@Jay Giu]# dmesg
[...]
PCI: Enabling device 0001:01:15.0 (0004 -> 0006)
[...]
Echoaudio: probe of 0001:01:15.0 failed with error -1
[root@Jay Giu]# lsmod
Module                  Size  Used by
snd_darla20            67908  0
snd_pcm               137692  1 snd_darla20
snd_timer              33000  1 snd_pcm
snd                    72800  3 snd_darla20,snd_pcm,snd_timer
snd_page_alloc         14436  2 snd_darla20,snd_pcm
therm_windtunnel        9748  0


--
Giuliano.



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: module is not unloaded when probe fails
  2004-03-22 21:08 module is not unloaded when probe fails Giuliano Pochini
@ 2004-03-22 23:11 ` Carl-Daniel Hailfinger
  0 siblings, 0 replies; 2+ messages in thread
From: Carl-Daniel Hailfinger @ 2004-03-22 23:11 UTC (permalink / raw)
  To: Giuliano Pochini; +Cc: Alsa-devel

Giuliano Pochini wrote:
> 
> When I try to load a module and it fails (snd-darla20 in this case) the
> module is not unloaded. IIRC it didn't happen some months ago, but I have no
> idea what is the cause because I changed a lot of stuff in the meantime
> (kernel, compiler, modutils...). Is this the expected behaviour ?

Yes, it's by design. If a module sees it can't drive the available
hardware, it *should* stay loaded so you either can
- add new hardware it can drive or
- tell it via /sys/bus/pci/drivers/tulip/new_id that it should drive dome
hardware with previously unknown pci id.


> [Giu@Jay Giu]$ uname -a
> Linux Jay 2.6.3-ben2 #10 SMP Sun Mar 14 21:46:34 CET 2004 ppc unknown

It's a new 2.6 feature.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-03-22 23:11 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-22 21:08 module is not unloaded when probe fails Giuliano Pochini
2004-03-22 23:11 ` Carl-Daniel Hailfinger

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.