[Xenomai-help] xeno-test failed to open benchmark device, code -19 at t1 and t2 # latency

[Xenomai-help] xeno-test failed to open benchmark device, code -19 at t1 and t2 # latency

[Dennis Nguyen]

Hi,

I built 2.6.22.10 linux kernel -i386 with xenomai 2.4-rc4 and
adeos-ipipe-2.6.22-i386-1.10-09.patch.

I checked enable SMI workaround, uncheck frequency scaling, uncheck ACPI
and uncheck APM.

I ran xeno-test and get the following failed message:

Thu Oct 25 13:17:02 PDT 2007
running: ./run -- -sh -T 120 -t1 # latency
*
*
* Type ^C to stop this application.
*
*
== Sampling period: 100 us
== Test mode: in-kernel periodic task
== All results in microseconds
latency: failed to open benchmark device, code -19
(modprobe xeno_timerbench?)

Thu Oct 25 13:17:04 PDT 2007
running: ./run -- -sh -T 120 -t2 # latency
*
*
* Type ^C to stop this application.
*
*
== Sampling period: 100 us
== Test mode: in-kernel timer handler
== All results in microseconds
latency: failed to open benchmark device, code -19
(modprobe xeno_timerbench?)

Could you help me to solve the issue?

Thank you,
Dennis

Re: [Xenomai-help] xeno-test failed to open benchmark device, code -19 at t1 and t2 # latency

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]

Dennis Nguyen wrote:
> Hi,
> 
> I built 2.6.22.10 linux kernel -i386 with xenomai 2.4-rc4 and
> adeos-ipipe-2.6.22-i386-1.10-09.patch.
> 
> I checked enable SMI workaround, uncheck frequency scaling, uncheck ACPI
> and uncheck APM.
> 
> I ran xeno-test and get the following failed message:
> 
> Thu Oct 25 13:17:02 PDT 2007
> running: ./run -- -sh -T 120 -t1 # latency
> *
> *
> * Type ^C to stop this application.
> *
> *
> == Sampling period: 100 us
> == Test mode: in-kernel periodic task
> == All results in microseconds
> latency: failed to open benchmark device, code -19
> (modprobe xeno_timerbench?)
> 
> Thu Oct 25 13:17:04 PDT 2007
> running: ./run -- -sh -T 120 -t2 # latency
> *
> *
> * Type ^C to stop this application.
> *
> *
> == Sampling period: 100 us
> == Test mode: in-kernel timer handler
> == All results in microseconds
> latency: failed to open benchmark device, code -19
> (modprobe xeno_timerbench?)
> 
> Could you help me to solve the issue?

What does the kernel log say (=>dmesg) when you manually insert the
module (=>modprobe xeno_timerbench)? Do you still have versioning
conflicts with your modules (as reported on rtnet-users)?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] xeno-test failed to open benchmark device, code -19 at t1 and t2 # latency

[Dennis Nguyen]

Jan Kiszka wrote:
> Dennis Nguyen wrote:
>   
>> Hi,
>>
>> I built 2.6.22.10 linux kernel -i386 with xenomai 2.4-rc4 and
>> adeos-ipipe-2.6.22-i386-1.10-09.patch.
>>
>> I checked enable SMI workaround, uncheck frequency scaling, uncheck ACPI
>> and uncheck APM.
>>
>> I ran xeno-test and get the following failed message:
>>
>> Thu Oct 25 13:17:02 PDT 2007
>> running: ./run -- -sh -T 120 -t1 # latency
>> *
>> *
>> * Type ^C to stop this application.
>> *
>> *
>> == Sampling period: 100 us
>> == Test mode: in-kernel periodic task
>> == All results in microseconds
>> latency: failed to open benchmark device, code -19
>> (modprobe xeno_timerbench?)
>>
>> Thu Oct 25 13:17:04 PDT 2007
>> running: ./run -- -sh -T 120 -t2 # latency
>> *
>> *
>> * Type ^C to stop this application.
>> *
>> *
>> == Sampling period: 100 us
>> == Test mode: in-kernel timer handler
>> == All results in microseconds
>> latency: failed to open benchmark device, code -19
>> (modprobe xeno_timerbench?)
>>
>> Could you help me to solve the issue?
>>     
>
> What does the kernel log say (=>dmesg) when you manually insert the
> module (=>modprobe xeno_timerbench)? Do you still have versioning
> conflicts with your modules (as reported on rtnet-users)?
>
> Jan
>
>   

I could not find xeno_timerbench. How to include the xeno_timerbench 
when it is built?
I got:
[root@domain.hid bin]# modprobe xeno_timerbench
FATAL: Module xeno_timerbench not found.

I don't know about the versioning conflicts.

Thanks,
Dennis

Re: [Xenomai-help] xeno-test failed to open benchmark device, code -19 at t1 and t2 # latency

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]

Dennis Nguyen wrote:
> Jan Kiszka wrote:
>> Dennis Nguyen wrote:
>>  
>>> Hi,
>>>
>>> I built 2.6.22.10 linux kernel -i386 with xenomai 2.4-rc4 and
>>> adeos-ipipe-2.6.22-i386-1.10-09.patch.
>>>
>>> I checked enable SMI workaround, uncheck frequency scaling, uncheck ACPI
>>> and uncheck APM.
>>>
>>> I ran xeno-test and get the following failed message:
>>>
>>> Thu Oct 25 13:17:02 PDT 2007
>>> running: ./run -- -sh -T 120 -t1 # latency
>>> *
>>> *
>>> * Type ^C to stop this application.
>>> *
>>> *
>>> == Sampling period: 100 us
>>> == Test mode: in-kernel periodic task
>>> == All results in microseconds
>>> latency: failed to open benchmark device, code -19
>>> (modprobe xeno_timerbench?)
>>>
>>> Thu Oct 25 13:17:04 PDT 2007
>>> running: ./run -- -sh -T 120 -t2 # latency
>>> *
>>> *
>>> * Type ^C to stop this application.
>>> *
>>> *
>>> == Sampling period: 100 us
>>> == Test mode: in-kernel timer handler
>>> == All results in microseconds
>>> latency: failed to open benchmark device, code -19
>>> (modprobe xeno_timerbench?)
>>>
>>> Could you help me to solve the issue?
>>>     
>>
>> What does the kernel log say (=>dmesg) when you manually insert the
>> module (=>modprobe xeno_timerbench)? Do you still have versioning
>> conflicts with your modules (as reported on rtnet-users)?
>>
>> Jan
>>
>>   
> 
> I could not find xeno_timerbench. How to include the xeno_timerbench
> when it is built?
> I got:
> [root@domain.hid bin]# modprobe xeno_timerbench
> FATAL: Module xeno_timerbench not found.
> 
> I don't know about the versioning conflicts.

Did you enable the timer benchmark in the kernel configuration (Xenomai
menu -> drivers -> testing -> timer benchmark)ß

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]