Messages in this thread | | | Date | Mon, 17 Jun 2002 17:47:46 +0200 | From | Kristian Peters <> | Subject | Re: isdn oops with 2.4.19-pre10 |
| |
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de> wrote: > Okay, I think I can see what is happening. > > Can you confirm that you get the oops if you unload the modules in the > same order that you loaded them, but not if you use the reverse order? > > I.e. > > insmod capidrv; insmod hisax; rmmod hisax; rmmod capidrv > > should be okay, > > insmod capidrv; insmod hisax; rmmod capidrv; rmmod hisax > > oopses?
No. ;-) But it's another issue. I'm loading the hisax drivers first:
hisax 492836 1 isdn 119072 1 [hisax] slhc 4624 0 [isdn] [...]
And after them (and the ippp-related programs..) the drivers for avmb1:
ppp_deflate 40928 0 (unused) bsd_comp 4056 0 (unused) ppp_synctty 4768 0 (unused) ppp_generic 18240 0 [ppp_deflate bsd_comp ppp_synctty] b1isa 3740 1 b1 17152 0 [b1isa] capidrv 25716 1 capi 17344 0 capifs 3712 1 [capi] kernelcapi 29796 4 [b1isa capidrv capi] capiutil 22368 0 [capidrv kernelcapi] [...]
I'm connecting with the avmb1-card to a provider via pppd and starting my iptables firewall (with qos scheduling). While connected or after shutting down the connection unloading the hisax or isdn modules produces that oops. I haven't tried it without the sched-modules loaded. Should I ? It seems that they could be responsible too.
Please note that the avmb1 (b1isa) card is active and hisax a passive one.
Hope that helps.
*Kristian
:... [snd.science] ...: :: _o) :: http://www.korseby.net /\\ :: http://gsmp.sf.net _\_V :.........................: - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |