> 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.24-rc6-git7-20080102160500-default, .config attached) but it happens with vanilla 2.6.24-rc6 (mostly allmodconfig, also attached) regards roland ----- Original Message ----- From: "Gerrit Renker" <gerrit@xxxxxxxxxxxxxx> To: "Arnaldo Carvalho de Melo" <acme@xxxxxxxxxx>; <devzero@xxxxxx>; <dccp@xxxxxxxxxxxxxxx>; <netdev@xxxxxxxxxxxxxxx> Sent: Wednesday, January 09, 2008 3:17 PM Subject: Re: FW: ccid2/ccid3 oopses >| > >> 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) > | > >> > <snip> > | > | Gerrit, the control socket isn't attached to any CCID module, so the > | CCID modules should be safe to remove, and IIRC they were safe to > | unload. > | > Ah, right. I have misread the email. And can confirm the above: running > the for-loop at the top of the message (60 seconds uninterrupted for > CCID2,3 each) brought no oopses. > So maybe the cause triggering this oops is somewhere else. _________________________________________________________________________ In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114
Attachment:
working_config.gz
Description: GNU Zip compressed data
Attachment:
config_where_problem_exists.gz
Description: GNU Zip compressed data
