RPi Feed - Internal Error

[Garry@lockyer.ca]

As indicated in another post, FR24 feed running on a headless Pi Zero W has been crashing lately. Here's the error messages I'm seeing:

"Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030504] Internal error: : 1 [#1] ARM

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030780] Process Xorg (pid: 1482, stack limit = 0x3412840d)

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030792] Stack: (0xdc955d90 to 0xdc956000)

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030805] 5d80: c02155e0 dc716dc0 00000000 00000001

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030820] 5da0: dc955dd4 dc955db0 c01a54f4 c02155ec 00000003 61c88647 e13b2580 00000003

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030837] 5dc0: 61c88647 d8a05025 dc955e2c dc955dd8 c01a6484 c01a542c de800000 00000000

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030853] 5de0: 00000000 00000007 dc955e0c c01a3670 dc955e70 d8a05010 dc955e2c 61583c28

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030868] 5e00: c01a3670 dc955e70 d8a05010 c0a27028 dc955f5c 00004040 dc955f5c 00000000

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030884] 5e20: dc955e6c dc955e30 c01a69c8 c01a641c c051df0c dc0a2800 dc0a2828 dc0a2830

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030899] 5e40: 00000008 61583c28 f301080e 00004000 d8a05000 c0a27028 dc955e70 00004000

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030915] 5e60: dc955f24 dc955e70 c01a900c c01a6940 dc8c4ef0 dc7403b8 41548c03 00000007

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030930] 5e80: d8a0501d c0a27028 dc8c4d30 dc7154c8 dc716dc0 00004010 00000000 0000083e

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030945] 5ea0: 00000000 00000000 00000000 dc955eb0 dc955ecc c0183d9c dc955ef4 dc955ec8

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030962] 5ec0: c0183d9c c018ff10 dc955f04 dc955ed8 00004000 bebbbae8 dc955f5c d8a05000

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030977] 5ee0: d8a05000 00000000 dc955f24 00000002 ffffff9c c03f7f00 dc955f5c 61583c28

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.030993] 5f00: 00004000 ffffff9c dc955f5c dc955f58 00ad6468 00001000 dc955f4c dc955f28

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.031008] 5f20: c01a9190 c01a8f70 00000000 c03f9fec 00000000 00004000 ffffff9c bebbbae8

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.031023] 5f40: dc955f94 dc955f50 c019e39c c01a914c dc955f58 dc955f60 00000000 c004e2b0

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.031039] 5f60: dc955f94 61583c28 0002aa2c 00001001 00ad6468 00001000 0000014c c00091a4

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.031054] 5f80: dc954000 00000000 dc955fa4 dc955f98 c019e5d8 c019e348 00000000 dc955fa8

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.031069] 5fa0: c0009000 c019e5cc 00001001 00ad6468 ffffff9c bebbbae8 00ad6468 00001000

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.031085] 5fc0: 00001001 00ad6468 00001000 0000014c bebbbae8 bebbbaa8 b6f17968 bebbbb5c

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.031100] 5fe0: b6e81ed0 bebbba84 b6e5b2d4 b6941b7c 20000010 ffffff9c 00000000 00000000

Message from syslogd@flightradar-T-CYYF2 at May 23 13:02:53 ...
kernel:[ 524.031364] Code: e59f002c eb13a04d e1a01004 e1a00006 (ebffff96)"

Everything is up to date according to apt-get upgrade.

Regards,

Garry

[Garry@lockyer.ca]

I swapped out the RPi Z and there have no errors for several days so it looks like this was a hardware fault.

Regards,

Garry