[Click] Queue element BUG ?!?!

[Eddie Kohler]

David,

When I run a configuration like:

make && sudo ./click -e 'TimedSource -> Print(A) -> Queue -> Print(b) -> 
ToDevice(eth1)'

I see:

A:   69 | 52616e64 6f6d2062 756c6c73 68697420 696e2061 20706163
b:   69 | 52616e64 6f6d2062 756c6c73 68697420 696e2061 20706163
A:   69 | 52616e64 6f6d2062 756c6c73 68697420 696e2061 20706163
b:   69 | 52616e64 6f6d2062 756c6c73 68697420 696e2061 20706163
A:   69 | 52616e64 6f6d2062 756c6c73 68697420 696e2061 20706163
b:   69 | 52616e64 6f6d2062 756c6c73 68697420 696e2061 20706163

...Perhaps there is a bug in the Notifier code.
* Are you running x86 linux?
* Can you alter Queue and ToDevice in the following ways?
   - Add to fullnotequeue::initialize() the line: (right before returning)
     click_chatter("Q %s / %s", _empty_note.signal().unparse().c_str(), 
_full_note.signal().unparse().c_str());

   - Add to todevice::initialize() the line: (right before returning)
     click_chatter("TD %s", _signal.unparse().c_str());

The TD should equal one of the Qs.

Eddie


dfuste at ac.upc.edu wrote:
> Eddie,
> 
> I have tried with the current CVS version of Click and the problem persists :(
> And sorry but when I wrote "click crashes", I meant that Click does not work
> fine (packets enter but never leave the Queue), but there isn't any
> Segmentation fault or something like that. So, I think in this case the
> debugger can not help me. Right?
> 
> Do you have new suggestions?
> david
> 
> Quoting Eddie Kohler <kohler at cs.ucla.edu>:
> 
>> David,
>>
>> Can you try with the current CVS version of Click, and see whether that 
>> works??  If it does not work, then maybe run user-level Click in a debugger
>> so 
>> you can see where the crash happens.
>>
>> Eddie
>>
>>
>> David Fuste wrote:
>>> Thanks Thomas!
>>>
>>> OK,
>>> so, the only thing I can conclude is that my PC is bewitched :)
>>>
>>> No, I'm being serious now. I compiled the linux-2.4.28 and 
>>> linux-2.6.16.13 kernels in a Debian "etch" with the click patch without 
>>> errors, I compiled the click-1.5.0 without errors (enabling all elements 
>>> in the configure), I compiled the madwifi-ng without errors...and with 
>>> all configurations which not imply the Queue element, click works 
>>> perfectly (in both user level and kernel mode). Only when I use the 
>>> Queue element (or SimpleQueue,...) click crashes (regardless if I use 
>>> the ethernet device (SiS) or the wireless device (Atheros)).
>>>
>>> Could it be a PC hardware (not network device) problem? I doubt but...
>>> Am I the only one which have this problem with the Queue element? If it 
>>> is true, the only thing I can try is to change of PC :(
>>>
>>> Thank you very much again,
>>> david
>>>
>>>> -----Original Message-----
>>>> From: click-bounces at pdos.csail.mit.edu
>> [mailto:click-bounces at pdos.csail.mit.edu] On Behalf Of dfuste at ac.upc.edu
>>>> Sent: Wednesday, December 13, 2006 10:34 AM
>>>> To: click at pdos.csail.mit.edu
>>>> Subject: [Click] Queue element BUG ?!?!
>>>>
>>>> OK,
>>>> this is my new situation (see my previous mails). I have installed
>> click-1.5.0 in a linux-2.6.16.13 kernel.
>>>> Why does the config
>>>> "InfiniteSource(...)->Print(ok)->ToDevice(eth0);"
>>>> work fine and the config
>>>>
>> "InfiniteSource(...)->Print(before)->Queue->Print(after)->ToDevice(eth0);"
>>>> only prints "before : ..."?
>>>> The packet never leaves the queue and so, it is never sent!
>>>>
>>>> There is no more things I can try...I need your help :) Thanks!
>>>> _______________________________________________
>>>> click mailing list
>>>> click at amsterdam.lcs.mit.edu
>>>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>>>>   
>>> _______________________________________________
>>> click mailing list
>>> click at amsterdam.lcs.mit.edu
>>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>