Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simultaneous playback and capture will cause IPC timed out #266

Closed
mengdonglin opened this issue Nov 9, 2018 · 22 comments
Closed

Simultaneous playback and capture will cause IPC timed out #266

mengdonglin opened this issue Nov 9, 2018 · 22 comments
Assignees
Labels
APL Applies to ApolloLake platform bug Something isn't working GLK Applies to Gemini Lake P2 Critical bugs or normal features

Comments

@mengdonglin
Copy link
Collaborator

This issue happens when running playback and capture at same time. Possibility: 5%~10%.

How to reproduce:

  1. repeat run: aplay -Dhw:0,1 test.wav -d 5 & arecord -Dhw:0,1 -f dat -c 2 test9.wav -d 5

Error log:
chronos@localhost ~ $ aplay -Dhw:0,1 /root/100sine.wav -d 5 & arecord -Dhw:0,1 -f dat -c 2 test9.wav -d 5
[1] 2489
Recording WAVE 'test9.wav' : Signed 16 bit Little Endian, Playing WAVE '/root/100sine.wav' : Rate 48000 Hz, Signed 16 bit Little Endian, StereoRate 48000 Hz,
Stereo
overrun!!! (at least 0.111 ms long)
aplay: pcm_write:2051: write error: Input/output error
[1]+ Exit 1 aplay -Dhw:0,1 /root/100sine.wav -d 5

@mengdonglin mengdonglin added bug Something isn't working P2 Critical bugs or normal features GLK Applies to Gemini Lake labels Nov 9, 2018
@mengdonglin
Copy link
Collaborator Author

Comments by Jakub:
"we always are missing FW traces from faulty iteration and there are no more traces afterwards.
Look at attached fw trace and dmesg logs and count ipc_glb_stream_message trigger start and ipc_glb_stream_message trigger stop pairs – there are two starts and two stops per iteration and in logs attached there were 10 iterations (tenth being faulty) but start and stop trigger pairs count is 9.

You can find fw build I used attached in zip (it has clearer ipc triger presentation in fw logs so counting is easier). "
log_trace_fw.txt
log_trace_dmsg.txt
sof-apl.zip

@dabekjakub
Copy link
Member

Comment to missing traces - @keqiaozhang did not see this issue and provided fw traces.
In traces provided by him there was no timeout on FW side and every ipc was handled and responded to in time.

Kernel side log on the other hand states that ipc replay was not sent in time. (inline)

[ 92.037887] sof-audio sof-audio: pcm: trigger stream 1 dir 1 cmd 1
[ 92.038044] sof-audio sof-audio: ipc tx succeeded: 0x60010000: GLB_STREAM_MSG: PCM_PARAMS
[ 92.038115] sof-audio sof-audio: ipc tx: 0x60040000: GLB_STREAM_MSG: TRIG_START
[ 92.039410] sof-audio sof-audio: ipc tx succeeded: 0x60040000: GLB_STREAM_MSG: TRIG_START
[ 92.040194] sof-audio sof-audio: pcm: trigger stream 1 dir 0 cmd 1
[ 92.040217] sof-audio sof-audio: ipc tx: 0x60040000: GLB_STREAM_MSG: TRIG_START - ipc sent on kernel side
[ 92.344431] sof-audio sof-audio: error: ipc timed out for 0x60040000 size 0xc
[ 92.344460] sof-audio sof-audio: status: fw entered - code 00000005
[ 92.344606] sof-audio sof-audio: error: unexpected fault 0x00000000 trace 0x00004000
[ 92.344611] sof-audio sof-audio: error: waking up any trace sleepers
[ 92.344643] Headset: ASoC: trigger FE failed -110
[ 92.344672] sof-audio sof-audio: pcm: trigger stream 1 dir 0 cmd 0
[ 92.344758] sof-audio sof-audio: error: rx list empty but received 0x0 fw response recived for the ipc that timed out
[ 92.344763] sof-audio sof-audio: error: can't find message header 0x60040000

@keyonjie
Copy link

I can still see this issue with latest codes.

@keyonjie
Copy link

@dabekjakub from the logs you pasted, looks FW received the trigger start msg, but handle/schedule too late?

@libinyang
Copy link

Interesting bug.
Let me keep an eye on it...
BTW: Do you guys know how to watch an issue without send any message to others? Sorry for the garbage message.

@dabekjakub
Copy link
Member

I investigated the FW logs and every trigger was handled in the same time @keyonjie and there were no indications of timeout on FW side that is why i need someone from kernel to look at it. I am 99.99% sure that we write response correctly and in time.

@keyonjie
Copy link

it looks there is extra delay on some part:
[ 92.040217] sof-audio sof-audio: ipc tx: 0x60040000: GLB_STREAM_MSG: TRIG_START - ipc sent on kernel side

[ 92.344758] sof-audio sof-audio: error: rx list empty but received 0x0 fw response recieved for the ipc that timed out

the response is too late, longer than 300ms.

@keyonjie
Copy link

it is not easy for me to reduplicate it now, with SOF glk-004-drop-stable and linux topic/cros-sof-v4.14-rebase, I tried the step #1 for more than 100 times, but no ipc timeout or xrun happens.

@dabekjakub
Copy link
Member

As i said before - i know that there is a timeout in log that points to fw. But when it comes to FW ipc handling i saw no delay in response in fw traces. So FW handled ipc (we handle it as IRQ) as fast as it was possible it was not even close to 300ms. That is why i ask for kernel dev to check it out. Maybe the response is already there but system has some kind of hickup on reading the memory window. So simply trace time between sending and reading response. If You try to read it many times during this 300ms then it means that fw either didn't recive or respond to in time and i can continiue.
Overal really inprobable since in our python tests we never had a timeout issue on ipc.

@keyonjie
Copy link

we miss an interrupt here on driver side, under investigation about why this happens.

@keyonjie
Copy link

0      1          DAI          44637303.177083      1983.802124                dai.c:114 	dai_buffer_process() error: Insufficient free bytes for next period. comp_overrun()
0      1          DAI          44637319.322917        16.145834                dai.c:98  	dai_buffer_process() error: Insufficient bytes for next period. comp_underrun()
0      1          DAI          44639303.125000      1983.802124                dai.c:114 	dai_buffer_process() error: Insufficient free bytes for next period. comp_overrun()
0      1          DAI          44639319.375000        16.250000                dai.c:98  	dai_buffer_process() error: Insufficient bytes for next period. comp_underrun()
0      1         PIPE 3.18     44640223.541667       904.166687           pipeline.c:1221	pipeline_xrun_recover()
0      1          DAI          44640388.125000       164.583328                dai.c:98  	dai_buffer_process() error: Insufficient bytes for next period. comp_underrun()
0      1         PIPE 2.12     44640442.291667        54.166668           pipeline.c:1221	pipeline_xrun_recover()

@keyonjie
Copy link

keyonjie commented Dec 7, 2018

with the latest code base, I can't find interrupt missing issue. Here summarize what I found:

  1. most of this IPC timeout happens after a FW Xrun in my observation, the Xrun auto recovery make debugging difficult, as it will keep doing things which actually never recover, and keep printing massive logs which expand the trace workload.
  2. removing DMA trace will decrease the rate of IPC timeout happen, e.g. from 3% -> 0.5%, but I still see error with DMA trace removed(don't initial it in driver side).
  3. I see DMA trace error log like "number of dropped logs = 379" happens when IPC timeout happens.
  4. I make some scripts to make the error happen more easily:
# cat sim
aplay -Dhw:0,1 -f dat -c 2 /dev/zero -d 5 & arecord -Dhw:0,1 -f dat -c 2 /dev/null -d 5 & aplay -Dhw:0,0 -f dat -c 2 /dev/zero -d 5
# cat stress_sim.sh 
i=0
MAXLOOPS=1000
while [ $i -lt $MAXLOOPS ]; do
	echo "iterate $i ..."
	./sim
	if [ $? -eq 0 ]; then
           let i+=1
	else
	   exit 1
	fi
done

I believe CoE friends can do similar slim driver scripts to duplicate the same issue(if not, please contact with me).

So, to resolve this kind of issues thoroughly, IMO, we need to:

  1. revisit our xrun recover part, best to add flag to disable xrun recover for debug purpose.
  2. add an option to disable DMA trace in driver side, it will benefit debugging of this kind of issues, and production release also.
  3. add IPC unit stress test to verify and make sure IPC itself can handle duplex(dual-direction) multi-thread communication, this can narrow down the problem positioning for this kind of issues.

@dabekjakub @lgirdwood @plbossart @mmaka1 any comments?

@keyonjie keyonjie added the APL Applies to ApolloLake platform label Dec 7, 2018
@dabekjakub
Copy link
Member

I haven't seen any xruns in fw when debugging this issue. However , @slawblauciak has uncovered reason for xruns and proposed a fix thesofproject/sof#645. We should recheck this issue after proposed fix will be implemented.

@ranj063
Copy link
Collaborator

ranj063 commented Dec 8, 2018

@keyonjie can you please check this issue with thesofproject/sof#692

@keyonjie
Copy link

@ranj063 so for this kind of ipc timeout, we need to confirm what stage we actually failed:
host not sent?
host sent but fw not recieved?
host sent, fw recieved, fw handled but not acked?
host sent, fw recieved, fw handled and acked, but host didn't get the ack?

@keyonjie
Copy link

I found that sometimes scheduler crash before Xrun happens(looks like copy task is not scheduled then xrun happens), there might be scheduler bug.

@keyonjie
Copy link

I have done several optimizations, now it can pass 200 (2playback+1capture+1dma-trace) iterations.

Still hit several corner cases after long enough try, e.g. 300 or 500 iterations, one classical one as below:

[ 2418.681877] sof-audio sof-audio: ipc tx: 0x60050000: GLB_STREAM_MSG: TRIG_STOP
[ 2418.682348] sof-audio sof-audio: ipc: firmware response, msg:0x60050000, msg_ext:0x0
[ 2418.682450] sof-audio sof-audio: ipc tx succeeded: 0x60050000: GLB_STREAM_MSG: TRIG_STOP
[ 2418.682510] sof-audio sof-audio: pcm: free stream 1 dir 1
[ 2418.682540] sof-audio sof-audio: ipc tx: 0x60030000: GLB_STREAM_MSG: PCM_FREE
[ 2418.682636] sof-audio sof-audio: ipc: firmware initiated, msg:0xdead00a, msg_ext:0x40800
[ 2418.682644] sof-audio sof-audio: error : DSP panic!
[ 2418.682658] sof-audio sof-audio: panic: dsp_oops_offset 788480 offset 788480
[ 2418.682665] sof-audio sof-audio: status: fw entered - code 00000005
[ 2418.682810] sof-audio sof-audio: error: invalid wait state
[ 2418.682816] sof-audio sof-audio: error: trace point 00004000
[ 2418.682823] sof-audio sof-audio: error: panic happen at /home/keyon/hdd/github/keyonjie/soun:1853190003
[ 2418.682829] sof-audio sof-audio: error: DSP Firmware Oops
[ 2418.682836] sof-audio sof-audio: error: Exception Cause: Level1InterruptCause, Level-1 interrupt as indicated by set level-1 bits in the INTERRUPT register
[ 2418.682844] sof-audio sof-audio: EXCCAUSE 0x00000004 EXCVADDR 0x00000000 PS       0x00060122 SAR     0x00000000
[ 2418.682852] sof-audio sof-audio: EPC1     0xbe012630 EPC2     0xbe012625 EPC3     0xbe01a8c6 EPC4    0x00000000
[ 2418.682859] sof-audio sof-audio: EPC5     0xbe02a444 EPC6     0x00000000 EPC7     0x00000000 DEPC    0x00000000
[ 2418.682866] sof-audio sof-audio: EPS2     0x00060720 EPS3     0x00060022 EPS4     0x00000000 EPS5    0x00050023
[ 2418.682873] sof-audio sof-audio: EPS6     0x00000000 EPS7     0x00000000 INTENABL 0x00010198 INTERRU 0x0000023a
[ 2418.682879] sof-audio sof-audio: stack dump from 0xbe07ef10
[ 2418.682887] sof-audio sof-audio: 0xbe07ef10: 0x00000000 0x0000000a 0x6d6f682f 0x656b2f65
[ 2418.682895] sof-audio sof-audio: 0xbe07ef14: 0x2f6e6f79 0x2f646468 0x68746967 0x6b2f6275
[ 2418.682902] sof-audio sof-audio: 0xbe07ef18: 0x6e6f7965 0x2f65696a 0x6e756f73 0x706f2d64
[ 2418.682910] sof-audio sof-audio: 0xbe07ef1c: 0x662d6e65 0x776d7269 0x2f657261 0x2f637273
[ 2418.682917] sof-audio sof-audio: 0xbe07ef20: 0x68637261 0x6574782f 0x2f61736e 0x6c636e69
[ 2418.682924] sof-audio sof-audio: 0xbe07ef24: 0x2f656475 0x68637261 0x6961772f 0x00682e74
[ 2418.682932] sof-audio sof-audio: 0xbe07ef28: 0xbe01209b 0xbe07efa0 0xbe04c250 0x00000001
[ 2418.682940] sof-audio sof-audio: 0xbe07ef2c: 0x08020006 0x00003200 0x00004180 0x00000080
[ 2418.682948] sof-audio sof-audio: error: waking up any trace sleepers
[ 2418.999751] sof-audio sof-audio: error: ipc timed out for 0x60030000 size 0xc
[ 2418.999770] sof-audio sof-audio: status: fw entered - code 00000005
[ 2418.999915] sof-audio sof-audio: error: invalid wait state
[ 2418.999921] sof-audio sof-audio: error: trace point 00004000
[ 2418.999928] sof-audio sof-audio: error: panic happen at /home/keyon/hdd/github/keyonjie/soun:1853190003
[ 2418.999935] sof-audio sof-audio: error: DSP Firmware Oops
[ 2418.999942] sof-audio sof-audio: error: Exception Cause: Level1InterruptCause, Level-1 interrupt as indicated by set level-1 bits in the INTERRUPT register
[ 2418.999950] sof-audio sof-audio: EXCCAUSE 0x00000004 EXCVADDR 0x00000000 PS       0x00060122 SAR     0x00000000
[ 2418.999957] sof-audio sof-audio: EPC1     0xbe012630 EPC2     0xbe012625 EPC3     0xbe01a8c6 EPC4    0x00000000
[ 2418.999964] sof-audio sof-audio: EPC5     0xbe02a444 EPC6     0x00000000 EPC7     0x00000000 DEPC    0x00000000
[ 2418.999971] sof-audio sof-audio: EPS2     0x00060720 EPS3     0x00060022 EPS4     0x00000000 EPS5    0x00050023
[ 2418.999978] sof-audio sof-audio: EPS6     0x00000000 EPS7     0x00000000 INTENABL 0x00010198 INTERRU 0x0000023a
[ 2418.999985] sof-audio sof-audio: stack dump from 0xbe07ef10
[ 2418.999993] sof-audio sof-audio: 0xbe07ef10: 0x00000000 0x0000000a 0x6d6f682f 0x656b2f65
[ 2419.000000] sof-audio sof-audio: 0xbe07ef14: 0x2f6e6f79 0x2f646468 0x68746967 0x6b2f6275
[ 2419.000008] sof-audio sof-audio: 0xbe07ef18: 0x6e6f7965 0x2f65696a 0x6e756f73 0x706f2d64
[ 2419.000016] sof-audio sof-audio: 0xbe07ef1c: 0x662d6e65 0x776d7269 0x2f657261 0x2f637273
[ 2419.000023] sof-audio sof-audio: 0xbe07ef20: 0x68637261 0x6574782f 0x2f61736e 0x6c636e69
[ 2419.000031] sof-audio sof-audio: 0xbe07ef24: 0x2f656475 0x68637261 0x6961772f 0x00682e74
[ 2419.000038] sof-audio sof-audio: 0xbe07ef28: 0xbe01209b 0xbe07efa0 0xbe04c250 0x00000001
[ 2419.000046] sof-audio sof-audio: 0xbe07ef2c: 0x08020006 0x00003200 0x00004180 0x00000080
[ 2419.000052] sof-audio sof-audio: error: waking up any trace sleepers
[ 2419.000195] sof-audio sof-audio: pcm: close stream 1 dir 1
[ 2419.640430] sof-audio sof-audio: pcm: open stream 1 dir 1
[ 2419.640434] sof-audio sof-audio: period min 192 max 16384 bytes
[ 2419.640436] sof-audio sof-audio: period count 2 max 16
[ 2419.640438] sof-audio sof-audio: buffer max 65536 bytes
[ 2419.640602] sof-audio sof-audio: rate_min: 48000 rate_max: 48000
[ 2419.640605] sof-audio sof-audio: channels_min: 2 channels_max: 2
[ 2419.640608] sof-audio sof-audio: rate_min: 48000 rate_max: 48000
[ 2419.640610] sof-audio sof-audio: channels_min: 2 channels_max: 2
[ 2419.640612] sof-audio sof-audio: rate_min: 48000 rate_max: 48000
[ 2419.640614] sof-audio sof-audio: channels_min: 2 channels_max: 2
[ 2419.640617] sof-audio sof-audio: pcm: hw params stream 1 dir 1
[ 2419.640621] sof-audio sof-audio: generating page table for 0000000060aab561 size 0xff00 pages 16
[ 2419.640641] sof-audio sof-audio: period_bytes:0xfc0
[ 2419.640643] sof-audio sof-audio: periods:16
[ 2419.640675] sof-audio sof-audio: stream_tag 2
[ 2419.959745] sof-audio sof-audio: error: ipc timed out for 0x60010000 size 0x6c
[ 2419.959766] sof-audio sof-audio: status: fw entered - code 00000005
[ 2419.959913] sof-audio sof-audio: error: invalid wait state
[ 2419.959920] sof-audio sof-audio: error: trace point 00004000
[ 2419.959928] sof-audio sof-audio: error: panic happen at /home/keyon/hdd/github/keyonjie/soun:1853190003
[ 2419.959935] sof-audio sof-audio: error: DSP Firmware Oops
[ 2419.959943] sof-audio sof-audio: error: Exception Cause: Level1InterruptCause, Level-1 interrupt as indicated by set level-1 bits in the INTERRUPT register
[ 2419.959952] sof-audio sof-audio: EXCCAUSE 0x00000004 EXCVADDR 0x00000000 PS       0x00060122 SAR     0x00000000
[ 2419.959961] sof-audio sof-audio: EPC1     0xbe012630 EPC2     0xbe012625 EPC3     0xbe01a8c6 EPC4    0x00000000
[ 2419.959968] sof-audio sof-audio: EPC5     0xbe02a444 EPC6     0x00000000 EPC7     0x00000000 DEPC    0x00000000
[ 2419.959976] sof-audio sof-audio: EPS2     0x00060720 EPS3     0x00060022 EPS4     0x00000000 EPS5    0x00050023
[ 2419.959985] sof-audio sof-audio: EPS6     0x00000000 EPS7     0x00000000 INTENABL 0x00010198 INTERRU 0x0000023a
[ 2419.959992] sof-audio sof-audio: stack dump from 0xbe07ef10

@keyonjie
Copy link

as this issue mostly happens in FW side now(e.g. FW hang, FW panic, FW can't get IPC interrupts, ...), let me duplicate this in sof issue.

@plbossart
Copy link
Member

@mengdonglin is this still open or can we close?

@plbossart
Copy link
Member

last call @mengdonglin I will close at the end of the week if there is no update.

@keqiaozhang
Copy link
Collaborator

Confirmed that this issue is fixed on GLK.
@stevyan ,please help to check on APL and close it if you cannot reproduce it.

@stevyan
Copy link

stevyan commented Mar 28, 2019

Summary
Issue cannot be reproduced with daily build version after executed more than 800 times based on APL UP2 nocodec.

Test Env
sof master: 742f83b
kernel sof-dev: 0367002
tplg: sof-apl-nocodec.tplg

@stevyan stevyan closed this as completed Mar 28, 2019
aiChaoSONG pushed a commit to aiChaoSONG/linux that referenced this issue May 24, 2021
…om-kernel-result

rust/kernel: move from_kernel_result! macro to error.rs
wenliangwu pushed a commit that referenced this issue Oct 30, 2023
Add various tests to check maximum number of supported programs
being attached:

  # ./vmtest.sh -- ./test_progs -t tc_opts
  [...]
  ./test_progs -t tc_opts
  [    1.185325] bpf_testmod: loading out-of-tree module taints kernel.
  [    1.186826] bpf_testmod: module verification failed: signature and/or required key missing - tainting kernel
  [    1.270123] tsc: Refined TSC clocksource calibration: 3407.988 MHz
  [    1.272428] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x311fc932722, max_idle_ns: 440795381586 ns
  [    1.276408] clocksource: Switched to clocksource tsc
  #252     tc_opts_after:OK
  #253     tc_opts_append:OK
  #254     tc_opts_basic:OK
  #255     tc_opts_before:OK
  #256     tc_opts_chain_classic:OK
  #257     tc_opts_chain_mixed:OK
  #258     tc_opts_delete_empty:OK
  #259     tc_opts_demixed:OK
  #260     tc_opts_detach:OK
  #261     tc_opts_detach_after:OK
  #262     tc_opts_detach_before:OK
  #263     tc_opts_dev_cleanup:OK
  #264     tc_opts_invalid:OK
  #265     tc_opts_max:OK              <--- (new test)
  #266     tc_opts_mixed:OK
  #267     tc_opts_prepend:OK
  #268     tc_opts_replace:OK
  #269     tc_opts_revision:OK
  Summary: 18/0 PASSED, 0 SKIPPED, 0 FAILED

Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Link: https://lore.kernel.org/bpf/20230929204121.20305-2-daniel@iogearbox.net
wenliangwu pushed a commit that referenced this issue Oct 30, 2023
Add a new test case which performs double query of the bpf_mprog through
libbpf API, but also via raw bpf(2) syscall. This is testing to gather
first the count and then in a subsequent probe the full information with
the program array without clearing passed structs in between.

  # ./vmtest.sh -- ./test_progs -t tc_opts
  [...]
  ./test_progs -t tc_opts
  [    1.398818] tsc: Refined TSC clocksource calibration: 3407.999 MHz
  [    1.400263] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x311fd336761, max_idle_ns: 440795243819 ns
  [    1.402734] clocksource: Switched to clocksource tsc
  [    1.426639] bpf_testmod: loading out-of-tree module taints kernel.
  [    1.428112] bpf_testmod: module verification failed: signature and/or required key missing - tainting kernel
  #252     tc_opts_after:OK
  #253     tc_opts_append:OK
  #254     tc_opts_basic:OK
  #255     tc_opts_before:OK
  #256     tc_opts_chain_classic:OK
  #257     tc_opts_chain_mixed:OK
  #258     tc_opts_delete_empty:OK
  #259     tc_opts_demixed:OK
  #260     tc_opts_detach:OK
  #261     tc_opts_detach_after:OK
  #262     tc_opts_detach_before:OK
  #263     tc_opts_dev_cleanup:OK
  #264     tc_opts_invalid:OK
  #265     tc_opts_max:OK
  #266     tc_opts_mixed:OK
  #267     tc_opts_prepend:OK
  #268     tc_opts_query:OK            <--- (new test)
  #269     tc_opts_replace:OK
  #270     tc_opts_revision:OK
  Summary: 19/0 PASSED, 0 SKIPPED, 0 FAILED

Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Link: https://lore.kernel.org/r/20231006220655.1653-4-daniel@iogearbox.net
Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org>
wenliangwu pushed a commit that referenced this issue Oct 30, 2023
Add a new test case to query on an empty bpf_mprog and pass the revision
directly into expected_revision for attachment to assert that this does
succeed.

  ./test_progs -t tc_opts
  [    1.406778] tsc: Refined TSC clocksource calibration: 3407.990 MHz
  [    1.408863] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x311fcaf6eb0, max_idle_ns: 440795321766 ns
  [    1.412419] clocksource: Switched to clocksource tsc
  [    1.428671] bpf_testmod: loading out-of-tree module taints kernel.
  [    1.430260] bpf_testmod: module verification failed: signature and/or required key missing - tainting kernel
  #252     tc_opts_after:OK
  #253     tc_opts_append:OK
  #254     tc_opts_basic:OK
  #255     tc_opts_before:OK
  #256     tc_opts_chain_classic:OK
  #257     tc_opts_chain_mixed:OK
  #258     tc_opts_delete_empty:OK
  #259     tc_opts_demixed:OK
  #260     tc_opts_detach:OK
  #261     tc_opts_detach_after:OK
  #262     tc_opts_detach_before:OK
  #263     tc_opts_dev_cleanup:OK
  #264     tc_opts_invalid:OK
  #265     tc_opts_max:OK
  #266     tc_opts_mixed:OK
  #267     tc_opts_prepend:OK
  #268     tc_opts_query:OK
  #269     tc_opts_query_attach:OK     <--- (new test)
  #270     tc_opts_replace:OK
  #271     tc_opts_revision:OK
  Summary: 20/0 PASSED, 0 SKIPPED, 0 FAILED

Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Link: https://lore.kernel.org/r/20231006220655.1653-6-daniel@iogearbox.net
Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
APL Applies to ApolloLake platform bug Something isn't working GLK Applies to Gemini Lake P2 Critical bugs or normal features
Projects
None yet
Development

No branches or pull requests

8 participants