Skip to contentSkip to conversation

rt-tester testcase t4-l2-pi-deboost.tst failed

DISCUSSION Yao Zhao 2 participants 3 messages Feb 27, 2013 – Feb 28, 2013

lore
Share & tools
lore

Yao Zhao

author
#0 lore raw

Hi,

I tested rt-tester with mainline 3.8.0 kernel and the kernel scripts/rt-tester/t4-l2-pi-deboost.tst failed at

# Verify prio of T0 (still pending owner,

# but T2 is enqueued due to the previous boost by T3
T: prioeq:              0:      82

The current T0's prio is -21 so it failed.

Reading source code, it should be 82 as T2 is at prio 82 and T0 owns the L1 and T2 is waiting for the L1.

Can I ask
1.is the rt-tester test only for preempt-rt kernel? 2.any idea why it failed?

thanks,
yao

#1 lore raw
Quoted 9 lines · Yao Zhao

Hi,

I tested rt-tester with mainline 3.8.0 kernel and the kernel scripts/rt-tester/t4-l2-pi-deboost.tst failed at

# Verify prio of T0 (still pending owner,

# but T2 is enqueued due to the previous boost by T3
T: prioeq:              0:      82
Quoted 7 lines

The current T0's prio is -21 so it failed.

Reading source code, it should be 82 as T2 is at prio 82 and T0 owns the L1 and T2 is waiting for the L1.

Can I ask
1.is the rt-tester test only for preempt-rt kernel?

No

Quoted 1 line

2.any idea why it failed?

No

It would be nice if you could figure out whether that's a failure of the test case or a failure in the kernel.

Thanks

tglx

author
#2 lore raw
Quoted 18 lines · Thomas Gleixner
Quoted 9 lines · Yao Zhao

Hi,

I tested rt-tester with mainline 3.8.0 kernel and the kernel scripts/rt-tester/t4-l2-pi-deboost.tst failed at

# Verify prio of T0 (still pending owner,

# but T2 is enqueued due to the previous boost by T3
T: prioeq:              0:      82
Quoted 7 lines

The current T0's prio is -21 so it failed.

Reading source code, it should be 82 as T2 is at prio 82 and T0 owns the L1 and T2 is waiting for the L1.

Can I ask
1.is the rt-tester test only for preempt-rt kernel?

Quoted 7 lines

No

Quoted 1 line

2.any idea why it failed?

No

It would be nice if you could figure out whether that's a failure of the test case or a failure in the kernel.

For the whole check-all.sh t4-l2-pi-deboost.tst is the first test case which failed and in t4-l2-pi-deboost.tst: that line is the first "test" failed.
I didn't see any failures in the kernel.

But I will spend some time to debug around and get familiar with the rt-mutex code.

thanks,
yao

Quoted 3 lines

Thanks

tglx