| > So maybe the cause triggering this oops is somewhere else.
|
| yes, probably. sorry - i didn`t tell or maybe i didn`t know when writing
| my first mail to module authors and forget to add that before forwarding here.
|
| for me , the problem does not happen with suse kernel of the day
| (2.6
| > >> the easiest way to reproduce is:
| > >>
| > >> while true;do modprobe dccp_ccid2/3;modprobe -r dccp_ccid2/3;done
| > >> after short time, the kernel oopses (messages below)
| > >>
|
| Gerrit, the control socket isn't attached to any CCID module, so the
| CCID modules should be safe to re
Em Wed, Jan 09, 2008 at 12:28:27PM +, Gerrit Renker escreveu:
> Roland, -
>
> >> apparently, i got crashes when loading/unloading other driver modules just
> >> after ccid2 or ccid3 had been loaded/unloaded _once_ (have not used them at
> >> all, just modprobe module;modprobe -r module) >
> >>
Roland, -
>> apparently, i got crashes when loading/unloading other driver modules just
>> after ccid2 or ccid3 had been loaded/unloaded _once_ (have not used them at
>> all, just modprobe module;modprobe -r module) >
>>
>> the easiest way to reproduce is:
>>
>> while true;do modprobe dccp_ccid
Hello !
as suggested by Ian McDonald, i`m forwarding this to dccp and netdev mailing
lists.
> hi !
>
> i know dccp_ccid2 and ccid3 modules are considered experimental, but i`m
> unsure if i probably triggered a bug inside or outside that modules here (i`m
> no kernel developer)
>
> apparently
