OpenWRT x86 23.05, IO Freezes randomly and then recovers after plugging a USB device

Hi I'm having a weird issue after upgrading to OpenWRT x86 23.05, the IO (SSD) is freezing randomly and what's really weird is after inserting any USB device in the computer, may it be a keyboard or flash drive, the system magically responds again, also only the IO is frozen, I still have routing, internet and pppoe enabled and connected, luci is still also responsive except those function requiring IO like viewing the system logs (as it requires reading from IO in tmpfs), it's just that the file system is inaccessible, even logread won't load the logs, SSH is also inaccessible and existing SSH connections are frozen.

Kernel logs are still accessible and this is the part where it recovers from a frozen IO. I couldn't retrieve the system logs from logread as after the system recovers from a frozen state, the system logs are wiped out, but I will try to change to persistent logging.

My suspect is there is a bug in the kernel interrupts, I don't have irqbalance installed, just packet steering enabled, also using the stock x86 kernel.

[40146.294809] br-49c181f3cd08: port 24(veth204b9d7) entered disabled state
[40180.307091] usb 1-1.4: new high-speed USB device number 4 using ehci-pci
[40180.520002] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[40180.526654] scsi host6: usb-storage 1-1.4:1.0
[40181.573675] scsi 6:0:0:0: Direct-Access     Generic- SD/MMC           1.00 PQ: 0 ANSI: 0 CCS
[40181.588656] scsi 6:0:0:1: Direct-Access     Generic- MS/MS-Pro        1.00 PQ: 0 ANSI: 0 CCS
[40183.447778] usb 1-1.4: USB disconnect, device number 4
[40183.487157] sd 6:0:0:0: [sdc] Test Unit Ready failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
[40183.496041] sd 6:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
[40183.496084] sd 6:0:0:1: [sdd] Test Unit Ready failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
[40183.505054] sd 6:0:0:0: [sdc] Sense not available.
[40183.514036] sd 6:0:0:1: [sdd] Read Capacity(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
[40183.518723] sd 6:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
[40183.518725] sd 6:0:0:0: [sdc] 0-byte physical blocks
[40183.527714] sd 6:0:0:1: [sdd] Sense not available.
[40183.533925] sd 6:0:0:0: [sdc] Write Protect is off
[40183.538924] sd 6:0:0:1: [sdd] 0 512-byte logical blocks: (0 B/0 B)
[40183.543739] sd 6:0:0:0: [sdc] Mode Sense: 00 00 00 00
[40183.548560] sd 6:0:0:1: [sdd] 0-byte physical blocks
[40183.548584] sd 6:0:0:1: [sdd] Test WP failed, assume Write Enabled
[40183.554776] sd 6:0:0:0: [sdc] Asking for cache data failed
[40183.559892] sd 6:0:0:1: [sdd] Asking for cache data failed
[40183.564848] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[40183.571058] sd 6:0:0:1: [sdd] Assuming drive cache: write through
[40183.576689] sd 6:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK
[40183.582242] sd 6:0:0:1: [sdd] Test Unit Ready failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
[40183.586326] sd 6:0:0:1: [sdd] Test Unit Ready failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
[40183.588203] sd 6:0:0:0: [sdc] Sense not available.
[40183.588216] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[40183.594324] sd 6:0:0:1: [sdd] Attached SCSI removable disk
[40555.176936] br-49c181f3cd08: port 24(vetha9037c9) entered blo

I've also checked the SSD drive SMART Statistics and all passed.
CPU: Intel i7 2600k
System Unit: Dell Optiplex 790, Intel Q65 chipset

=== START OF INFORMATION SECTION ===
Device Model:     BR 128GB
Serial Number:    YS20230405615480
LU WWN Device Id: 0 000000 000000000
Firmware Version: HPS2818E
User Capacity:    128,035,676,160 bytes [128 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available
Device is:        Not in smartctl database 7.3/5319
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Nov  3 22:10:59 2023 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x00) 	Offline data collection not supported.
SMART capabilities:            (0x0000)	Automatic saving of SMART data		is not implemented.
Error logging capability:        (0x00)	Error logging supported.
					General Purpose Logging supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0032   100   100   050    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0032   100   100   050    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   100   100   050    Old_age   Always       -       819
 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       55
160 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       0
161 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       100
163 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       0
164 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       151
165 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       142
166 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       3
167 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       69
168 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       0
169 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       100
175 Program_Fail_Count_Chip 0x0032   100   100   050    Old_age   Always       -       83886080
176 Erase_Fail_Count_Chip   0x0032   100   100   050    Old_age   Always       -       628622
177 Wear_Leveling_Count     0x0032   100   100   050    Old_age   Always       -       3942414
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   050    Old_age   Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   050    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   050    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       24
194 Temperature_Celsius     0x0032   100   100   050    Old_age   Always       -       40
195 Hardware_ECC_Recovered  0x0032   100   100   050    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   100   100   050    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0032   100   100   050    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   050    Old_age   Always       -       0
232 Available_Reservd_Space 0x0032   100   100   050    Old_age   Always       -       100
241 Total_LBAs_Written      0x0032   100   100   050    Old_age   Always       -       26416
242 Total_LBAs_Read         0x0032   100   100   050    Old_age   Always       -       21016

Encountered a random freeze again today here are the system logs stored in ssd, same situation, i was able to unfreeze it by plugging a usb device, frozen in between Sat Nov 4 18:25:26 2023 - Sat Nov 4 19:42:15 2023

Sat Nov  4 18:25:26 2023 daemon.info ipsec: 15[CFG] joining forecast multicast groups: 224.0.0.1,224.0.0.22,224.0.0.251,224.0.0.252,239.255.255.250
Sat Nov  4 18:25:26 2023 daemon.err dockerd[6215]: time="2023-11-04T10:25:26.453200781Z" level=error msg="failed to enable controllers ([cpuset cpu io memory hugetlb pids rdma])" error="failed to write subtree controllers [cpuset cpu io memory hugetlb pids rdma] to \"/sys/fs/cgroup/docker/cgroup.subtree_control\": write /sys/fs/cgroup/docker/cgroup.subtree_control: no such file or directory"
Sat Nov  4 18:25:26 2023 daemon.err dockerd[6215]: time="2023-11-04T10:25:26.498516755Z" level=warning msg="cleaning up after shim disconnected" id=218f8bacbeb9358d99fdfb826aaa6fabf7a18b11578817aa7d91a2feeae69a1e namespace=moby
Sat Nov  4 18:25:26 2023 daemon.info avahi-daemon[4338]: Interface veth543003f.IPv6 no longer relevant for mDNS.
Sat Nov  4 18:25:26 2023 daemon.info avahi-daemon[4338]: Leaving mDNS multicast group on interface veth543003f.IPv6 with address fe80::5ca6:5ff:fe99:41c.
Sat Nov  4 18:25:26 2023 daemon.info ipsec: 10[KNL] interface veth543003f deactivated
Sat Nov  4 18:25:26 2023 daemon.notice ttyd[7753]: [2023/11/04 18:25:26:8492] N: rops_handle_POLLIN_netlink: DELADDR
Sat Nov  4 18:25:26 2023 daemon.info ipsec: 12[KNL] fe80::5ca6:5ff:fe99:41c disappeared from veth543003f
Sat Nov  4 18:25:26 2023 daemon.info ipsec: 10[KNL] interface vethc66e8b8 deleted
Sat Nov  4 19:42:15 2023 kern.info kernel: [39710.883276] usb 1-1.3: new high-speed USB device number 3 using ehci-pci
Sat Nov  4 19:42:15 2023 daemon.info ipsec: 13[KNL] interface veth543003f deleted
Sat Nov  4 19:42:15 2023 daemon.notice netifd: bridge 'docker0' link is down
Sat Nov  4 19:42:15 2023 daemon.notice netifd: Interface 'docker' has link connectivity loss
Sat Nov  4 19:42:15 2023 daemon.info avahi-daemon[4338]: Withdrawing address record for fe80::5ca6:5ff:fe99:41c on veth543003f.
Sat Nov  4 19:42:15 2023 daemon.info ipsec: 15[NET] using forecast interface br-lan
Sat Nov  4 19:42:15 2023 daemon.info ipsec: 15[CFG] joining forecast multicast groups: 224.0.0.1,224.0.0.22,224.0.0.251,224.0.0.252,239.255.255.250
Sat Nov  4 19:42:15 2023 daemon.info avahi-daemon[4338]: Joining mDNS multicast group on interface vethdb8539e.IPv6 with address fe80::8b8:c8ff:fe99:314d.
Sat Nov  4 19:42:15 2023 daemon.info ipsec: 11[KNL] fe80::8b8:c8ff:fe99:314d appeared on vethdb8539e
Sat Nov  4 19:42:15 2023 daemon.info avahi-daemon[4338]: New relevant interface vethdb8539e.IPv6 for mDNS.
Sat Nov  4 19:42:15 2023 daemon.info avahi-daemon[4338]: Registering new address record for fe80::8b8:c8ff:fe99:314d on vethdb8539e.*.
Sat Nov  4 19:42:15 2023 daemon.info ipsec: 12[NET] using forecast interface br-lan
Sat Nov  4 19:42:15 2023 daemon.info ipsec: 12[CFG] joining forecast multicast groups: 224.0.0.1,224.0.0.22,224.0.0.251,224.0.0.252,239.255.255.250
Sat Nov  4 19:42:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Sat Nov  4 19:42:15 2023 daemon.err uhttpd[4082]: [info] luci: accepted login on / for root from 127.0.0.1
Sat Nov  4 19:42:15 2023 authpriv.notice sudo:  vincejv : TTY=pts/0 ; PWD=/home/vincejv ; USER=root ; COMMAND=/sbin/logread
Sat Nov  4 19:42:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Sat Nov  4 19:42:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Sat Nov  4 19:42:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Sat Nov  4 19:42:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Sat Nov  4 19:42:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52

I would first try an active-powered USB hub, to check, whether it is not an USB power issue.

But when downgrading to 22.03.5 no issue

I've had issues with 23.05 on x86 too, but for me, it simply freezes during boot. Rolled back, just as you did.

so much weird problems for me too in 23.05.0... squid crash issues, wifi performance issues; staying on 22.03 for now

The last thing I got on the log before reboot was this

Tue Nov 28 10:30:21 2023 kern.alert kernel: [ 632.608660] CPU 0 Unable to handle kernel paging request at virtual address 00000000, epc == 8016cc5c, ra == 8016f51c

on searching I found the following link, will look into it further ...

I'm still encountering this on 23.05.2, and apparently only the main disk or /dev/sda is affected, my other mounts are perfect responsive in /dev/sdb through FTP, but any IO operation against /dev/sda just cause the service to hang including FTP

I hardly think this is a hardware issue, as the IO Freeze can simply be fixed by plugging a new USB Device (USB Keyboard, Flashdrive, Card reader), after plugging everything in /dev/sda magically responds again. What comes to mind when plugging a new usb is it trigger a kernel interrupt, so likely a kernel interrupt bug.

Kernel Logs (before and after the freeze)

[  +0.086481] br-23f6a949a670: port 19(vethd59145d) entered blocking state
[  +0.007997] br-23f6a949a670: port 19(vethd59145d) entered disabled state
[  +0.008072] device vethd59145d entered promiscuous mode
[  +0.006594] br-23f6a949a670: port 19(vethd59145d) entered blocking state
[  +0.007481] br-23f6a949a670: port 19(vethd59145d) entered forwarding state
[  +0.190794] eth0: renamed from vethe6f88bf
[  +0.059764] IPv6: ADDRCONF(NETDEV_CHANGE): vethd59145d: link becomes ready
[Dec13 01:34] TCP: request_sock_TCP: Possible SYN flooding on port 5000. Sending cookies.  Check SNMP counters.
[Dec13 03:10] usb 1-1.4: new low-speed USB device number 3 using ehci-pci
[  +0.158902] input: USB usb keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:C0F4:07C0.0001/input/input7
[  +0.081203] hid-generic 0003:C0F4:07C0.0001: input,hidraw0: USB HID v1.10 Keyboard [USB usb keyboard] on usb-0000:00:1a.0-1.4/input0
[  +0.016169] input: USB usb keyboard Consumer Control as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:C0F4:07C0.0002/input/input8
[  +0.083995] input: USB usb keyboard System Control as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:C0F4:07C0.0002/input/input9
[  +0.015220] hid-generic 0003:C0F4:07C0.0002: input,hidraw1: USB HID v1.10 Device [USB usb keyboard] on usb-0000:00:1a.0-1.4/input1

Syslog

Wed Dec 13 01:33:00 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 01:33:00 2023 user.notice nft-qos-monitor: ACTION=update, MACADDR=3c:19:cb:01:28:6d, IPADDR=172.16.0.58, HOSTNAME=Pictor
Wed Dec 13 01:33:00 2023 user.notice nft-qos-dynamic: ACTION=update, MACADDR=3c:19:cb:01:28:6d, IPADDR=172.16.0.58, HOSTNAME=Pictor
Wed Dec 13 03:10:49 2023 kern.info kernel: [12486.710062] usb 1-1.4: new low-speed USB device number 3 using ehci-pci
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 94:17:00:20:a3:1d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.43 94:17:00:20:a3:1d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.43 94:17:00:20:a3:1d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.43 94:17:00:20:a3:1d M2006C3LG-Redmi9A
Wed Dec 13 03:10:49 2023 user.notice nft-qos-monitor: ACTION=add, MACADDR=94:17:00:20:a3:1d, IPADDR=172.16.0.43, HOSTNAME=M2006C3LG-Redmi9A
Wed Dec 13 03:10:49 2023 user.notice nft-qos-dynamic: ACTION=add, MACADDR=94:17:00:20:a3:1d, IPADDR=172.16.0.43, HOSTNAME=M2006C3LG-Redmi9A
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 user.notice nft-qos-monitor: ACTION=update, MACADDR=0a:97:77:02:ce:64, IPADDR=172.16.0.42, HOSTNAME=OPPO-A52
Wed Dec 13 03:10:49 2023 user.notice nft-qos-dynamic: ACTION=update, MACADDR=0a:97:77:02:ce:64, IPADDR=172.16.0.42, HOSTNAME=OPPO-A52
Wed Dec 13 03:10:49 2023 authpriv.notice sudo:     root : TTY=pts/6 ; PWD=/root ; USER=root ; COMMAND=/bin/ping 185.148.1.127
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.err uhttpd[4151]: [info] luci: accepted login on / for root from 127.0.0.1
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.58 3c:19:cb:01:28:6d
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.16.0.42 0a:97:77:02:ce:64
Wed Dec 13 03:10:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.16.0.42 0a:97:77:02:ce:64 OPPO-A52
Wed Dec 13 03:10:49 2023 user.notice nft-qos-monitor: ACTION=update, MACADDR=3c:19:cb:01:28:6d, IPADDR=172.16.0.58, HOSTNAME=Pictor
Wed Dec 13 03:10:50 2023 user.notice nft-qos-monitor: ACTION=update, MACADDR=3c:19:cb:01:28:6d, IPADDR=172.16.0.58, HOSTNAME=Pictor
Wed Dec 13 03:10:50 2023 kern.info kernel: [12487.065551] hid-generic 0003:C0F4:07C0.0002: input,hidraw1: USB HID v1.10 Device [USB usb keyboard] on usb-0000:00:1a.0-1.4/input1
Wed Dec 13 03:10:50 2023 user.notice nft-qos-dynamic: ACTION=update, MACADDR=3c:19:cb:01:28:6d, IPADDR=172.16.0.58, HOSTNAME=Pictor
Wed Dec 13 03:10:50 2023 user.notice nft-qos-monitor: ACTION=update, MACADDR=3c:19:cb:01:28:6d, IPADDR=172.16.0.58, HOSTNAME=Pictor
Wed Dec 13 03:10:50 2023 user.notice nft-qos-dynamic: ACTION=update, MACADDR=3c:19:cb:01:28:6d, IPADDR=172.16.0.58, HOSTNAME=Pictor
Wed Dec 13 03:10:50 2023 user.notice nft-qos-monitor: ACTION=update, MACADDR=3c:19:cb:01:28:6d, IPADDR=172.16.0.58, HOSTNAME=Pictor
Wed Dec 13 03:10:50 2023 user.notice nft-qos-dynamic: ACTION=update, MACADDR=3c:19:cb:01:28:6d, IPADDR=172.16.0.58, HOSTNAME=Pictor
Wed Dec 13 03:10:50 2023 user.notice nft-qos-monitor: ACTION=update, MACADDR=3c:19:cb:01:28:6d, IPADDR=172.16.0.58, HOSTNAME=Pictor

As you can see from syslog, DHCP was unresponsive during the freeze (as the lease file is saved in /dev/sda2), but after plugging in a keyboard, DHCP spams the logs with lease requests as IO starts to recover, then DHCP magically works again.

Just to provide a more updated info, experimenting the scenarios of when the system will unfreeze (didn't use the USB method), the IO magically unfreezed after a couple of hours, here are the logs (notice the long time gap between the logs), smart stats are clean.

logread

Wed Jan 17 22:35:52 2024 daemon.err dockerd[6420]: time="2024-01-17T14:35:52.863293270Z" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Wed Jan 17 22:35:52 2024 daemon.err dockerd[6420]: time="2024-01-17T14:35:52.863311545Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Wed Jan 17 22:35:52 2024 daemon.err dockerd[6420]: time="2024-01-17T14:35:52.863390429Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.pause\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Wed Jan 17 22:35:52 2024 daemon.info ipsec: 12[NET] using forecast interface br-lan
Wed Jan 17 22:35:52 2024 daemon.info ipsec: 12[CFG] joining forecast multicast groups: 224.0.0.1,224.0.0.22,224.0.0.251,224.0.0.252,239.255.255.250
Wed Jan 17 22:35:53 2024 daemon.info ipsec: 10[KNL] interface veth2e621c5 deleted
Wed Jan 17 22:35:53 2024 kern.info kernel: [609739.225027] eth0: renamed from veth2e621c5
Wed Jan 17 22:35:53 2024 daemon.info ipsec: 10[KNL] interface veth707f6ba deleted
Thu Jan 18 18:56:04 2024 kern.err kernel: [682949.757885] ata4.00: irq_stat 0x40000008
Thu Jan 18 18:56:04 2024 daemon.info ipsec: 11[NET] using forecast interface br-lan
Thu Jan 18 18:56:04 2024 daemon.info ipsec: 11[CFG] joining forecast multicast groups: 224.0.0.1,224.0.0.22,224.0.0.251,224.0.0.252,239.255.255.250
Thu Jan 18 18:56:04 2024 daemon.info ipsec: 05[NET] using forecast interface br-lan
Thu Jan 18 18:56:04 2024 daemon.info ipsec: 05[CFG] joining forecast multicast groups: 224.0.0.1,224.0.0.22,224.0.0.251,224.0.0.252,239.255.255.250
Thu Jan 18 18:56:04 2024 daemon.info avahi-daemon[4521]: Joining mDNS multicast group on interface vethc7a8a0d.IPv6 with address fe80::108d:d3ff:febc:45ed.
Thu Jan 18 18:56:04 2024 daemon.info ipsec: 14[KNL] fe80::108d:d3ff:febc:45ed appeared on vethc7a8a0d
Thu Jan 18 18:56:04 2024 daemon.info avahi-daemon[4521]: New relevant interface vethc7a8a0d.IPv6 for mDNS.
Thu Jan 18 18:56:04 2024 daemon.info avahi-daemon[4521]: Registering new address record for fe80::108d:d3ff:febc:45ed on vethc7a8a0d.*.
Thu Jan 18 18:56:04 2024 daemon.info ipsec: 13[NET] using forecast interface br-lan
Thu Jan 18 18:56:04 2024 daemon.info ipsec: 13[CFG] joining forecast multicast groups: 224.0.0.1,224.0.0.22,224.0.0.251,224.0.0.252,239.255.255.250
Thu Jan 18 18:56:04 2024 daemon.info avahi-daemon[4521]: Joining mDNS multicast group on interface veth2bd4c67.IPv6 with address fe80::7c41:28ff:fe15:3607.
Thu Jan 18 18:56:04 2024 daemon.info ipsec: 15[KNL] fe80::7c41:28ff:fe15:3607 appeared on veth2bd4c67
Thu Jan 18 18:56:04 2024 daemon.info avahi-daemon[4521]: New relevant interface veth2bd4c67.IPv6 for mDNS.

dmesg

[36633.202233] eth0: renamed from veth3af5989
[36633.292088] IPv6: ADDRCONF(NETDEV_CHANGE): veth2f6374e: link becomes ready
[36633.300352] br-23f6a949a670: port 22(veth2f6374e) entered blocking state
[36633.308330] br-23f6a949a670: port 22(veth2f6374e) entered forwarding state
[42300.391275] ata4.00: exception Emask 0x0 SAct 0xd020003e SErr 0x0 action 0x0
[42300.399215] ata4.00: irq_stat 0x40000008

Anyways, I managed to fix the issue by forking the code and cherry-picking patches to upgrade to kernel 5.15.147, and the freezing issue seems to have been fixed, I have tried going for 6.1.71 as well (cherry-pick commit method), it also didn't have the same freezing issue. So I guess I'll wait for the team to release OpenWRT with a more updated Kernel, and I think there aren't any other reports regarding this as I have a fairly complex setup with my OpenWRT x86 system which includes docker + lxc + btrfs raid + etc, the installed packages probably triggered a kernel bug which a regular user won't notice.

And as per the latest logs provided the IO Unfreezed after encountering this log Thu Jan 18 18:56:04 2024 kern.err kernel: [682949.757885] ata4.00: irq_stat 0x40000008 which leads me to believe that it was an interrupt issue after all which may have been fixed on a later kernel version.


For parting words, I just wished the Kernel was less tightly integrated to the OpenWRT build system, as issues like these can simply be fixed by upgrading kernels + kmods, no need to wipe the rootfs. It's a lot of work to cherry pick + forking code which a casual user would find as a huge hassle.

1 Like

I'm having similar issues using an ASUS TUF-AX4200 (ARMv8 mediatek/filogic) with a USB pendrive attached to it as storage. Never tried adding another USB device to unfreeze it, usually I just reboot the router through luci to get it working again. The router has OpenWrt 23.05.2 with all the package updates installed, and after a couple of days uptime clients cannot connect to it anymore through wifi, and just as you described "still have routing, internet and pppoe enabled and connected, luci is still also responsive [...], SSH is also inaccessible". I have a dumb-AP connected to one of the local ethernet ports of the TUF-AX4200, and I can still log into luci through the dumb-AP. I would say this issue is not x86 specific.

Try that plugging/replugging the USB pendrive attached and see if it unfreezes it, or plugin a USB hub and attach a separate usb device and let us know what you see.

Yes, we have the same issue, new clients can't connect because the DHCP server may be storing the lease file in the disk, so DHCP won't function temporarily as the IO is frozen.

Anyways it's been a couple of days now on Kernel 6.1.71, no freezing issues so far...

Also a lot of EXT4/BTRFS fixes from 5.15.137 to .147, given this a disk io related issue, might have been fixed between those versions. I'm using both btrfs & ext4, it's the ext4 disk that's freezing.

The file system on my USB pendrive is exfat. I've switched back to my previous Linksys EA8300 (ARMv7 ipq40xx/generic) router, installed a clean 23.05.2 and then all the latest software updates, and a lot of additional packages my configuration uses but this time I haven't added the USB pendrive to the router (and haven't installed the kmod-usb* packages either), and this freeze still occurred. The last entry in the system log was a mac flush kernel info from the ath10k module, and after that no more hostapd entries. New clients were unable to connect through wifi, ssh was not accepting connections, but luci is still up and accepting connections. I guess I see the same behavior but the root cause may be different on my routers.

With opkg upgrade or LuCI -> System -> Software -> Updates?
I do hope not.
If yes, on OpenWrt, that's a good way to brick your device.

With the commands

opkg update
opkg list-upgradable | cut -f 1 -d ' ' | xargs opkg upgrade

I thought the package updates are safe to use.

As you might know, OpenWrt is no full-fledged, multi-purpose linux distribution.
So while it's normal and recommended for a standard linux distribution to do updates on a regular basis, which is often only a few updated libraries or a new kernel, this is not true for OpenWrt.
Please refer to this for further information.

1 Like

Oh my, I didn't know about it, but now I learned it the hard way! Thank you for taking the time and pointing this out for me, I am going to "firstboot" my router right now.

It's definitely okay to upgrade packages in OpenWRT, but not the base packages like busybox, the details are here: To upgrade or not to upgrade packages - #11 by jow

Also upgrade maybe required if it's a security issue/fix listed here: https://openwrt.org/advisory/start

Well, that's jows opinion. I think he's right, but other people in the mentioned thread seem to have different opinions.
I think, i should be safe for single packages.

You might agree that it's not the best idea to upgrade all installed packages by just executing opkg upgrade or similar.

And of course, all these are recommendations.
People tend to have their own thoughts about other people's recommendations. :face_with_peeking_eye:

These are quite old (at least 15 months) and should've been fixed by a new release quite soon at that time.
But for a new security issue: I agree with that.

Another thing to think about:
All these updates would be installed into the overlay. If the router's memory is already sparse, it would worsen the situation. Or make it even impossible to install the updates.

I had the firstboot and the reconfiguration 3 days ago and there was no IO freeze for me since then. Neither on the ASUS TUF-AX4200 nor on the Linksys EA8300. Maybe it is too early to be 100% sure, 3 days uptime is not that much when usually I got the IO freeze in 1-2 days, but in my case it is highly likely that the package upgrade caused the issue. Right now opkg list-upgradable shows the following list:

luci-theme-bootstrap - git-23.306.39416-c86c256 - git-23.338.81541-94798fc
netifd - 2023-11-10-35facc83-1.1 - 2024-01-04-c18cc79d-1
luci-mod-status - git-23.306.52197-bdcd3e0 - git-23.351.85404-a962261
luci-app-firewall - git-23.306.38853-a0466cd - git-24.008.46353-971459d
luci-base - git-23.306.39416-c86c256 - git-24.006.68745-9128656
luci-proto-ipv6 - git-21.148.48881-79947af - git-23.355.78874-80140aa
luci-app-upnp - git-22.297.83017-2877753 - git-24.025.85485-89a9b58
luci-mod-network - git-23.313.56166-6da284d - git-24.025.85485-c30d85b
jsonfilter - 2018-02-04-c7e938d6-1 - 2024-01-23-594cfa86-1

So one or more of these are not recommended for upgrade. I guess the luci packages are for the web interface, the jsonfilter is quite new, so that netifd package is what I would consider, but this is just a guess, I have no proof.