Jetson Orin VI timeout when ext4 abnormal

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
, ,
1

Hi,
I found syslog will print: “uncorr_err: request timed out after 2500 ms”, when ext4 abnormal.
Reproduce step:

  1. Insert U disk;
  2. mount /dev/sda1 /mnt
  3. cp large file to /mnt
  4. Before file tranferring stop, pull out U disk
  5. vi print “uncorr_err: request timed out after 2500 ms”
  6. ext4 print: "EXT4-fs (sdc1): failed to convert unwritten extents to written extents – potential data loss! "

Jetpack sdk 5.1.2, L4T version 35.4.1
I tried to read max9296 register on I2C bus, but every return is 0;
And VI also print: “capture control message timed out”. I think Orin is abnormal now.
syslog print below:
syslog.zip (403.7 KB)

What I hope is VI works always fine even filesystem has problems. Can anyone can help me to fix it?
Thanks!
BR/Tim

3

I don’t think this message cause by ext4 abnormal.
You should confirm it without enable camera.

4

Hi ShaneCCC
“capture control message timed out” only happen when vi recovery, please refer log:“attempting to reset the capture channel”.
If I disable camera, this recovery will not happen. So how can I confirm that?
Thanks.

5

Why do you want to disable it?
You can modify the timeout to try.

6

Hi ShaneCCC
You mean I make timeout longer than 2.5s? But I can’t understand what this modify for? Even I make timeout longer than 1min, then no error report, I still lost my camera frame.

7

That’s tell could be the sensor output have problem.

8

Sorry ShaneCCC
How you make this conclusion? And sensor output problem will make “capture control message timed out”?
I tried to abort sensor output, and it print: “successfully reset the capture channel”.

9

While the VI driver didn’t receive FS during 2500ms will print timeout message and try to recover and print the reset channel message.

So, the root cause is didn’t get FS from sensor druing 2500ms

10

Could it be sensor already send frame, but VI can’t receive since IVC channel goes wrong?
Otherwise how to explain"capture control message timed out"?

11

You can check the vi5_fops.c for the detail.

Thanks

12

Will, interesting. I thought this forums can tell me the detail(or fix bug) directly.
Anyway I checked vi5_fops.c and it real shows IVC channel goes wrong, but for ext4 relations need dig more deeper, and cost time…

14

Suppose the bug is in sensor side need to match the capture conditions.

15

Hi,
Anyother suggestions?
Thanks!

16

Get the trace log if further information.

https://elinux.org/Jetson/l4t/Camera_BringUp#Steps_to_enable_more_debug_messages

17

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.