failed to get tx report from firmware on RTL8723DU #246
Comments
|
Sadly Larry died this summer.
This is an old problem that only recently got an error message. A patch is available here: #205 (comment) For the random "failed to get tx report from firmware", try to load rtw_core with debug_mask=0x10. This may add some useful information to the log. |
|
I don't even notice Larry referring to lwfinger had passed away. I will give it a try and pass out some logs. Thanks again. |
|
No luck, the memory stress test immediately trigger the issue dmesg[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd040] |
|
Good news is that the driver didn't crash and ping can keep run after those fail reports. dmesgubuntu@briansune:~$ dmesg |
|
The timing here is interesting: C2H with id=0x03 is the TX report. "failed to get tx report from firmware" is a bit misleading. It's possible the firmware did send the TX report but the driver received it earlier than expected. I think this can happen with rtw_usb. We need more information: diff --git a/drivers/net/wireless/realtek/rtw88/tx.c b/drivers/net/wireless/realtek/rtw88/tx.c
index 215bfd731235..8994f316f367 100644
--- a/drivers/net/wireless/realtek/rtw88/tx.c
+++ b/drivers/net/wireless/realtek/rtw88/tx.c
@@ -181,11 +181,12 @@ void rtw_tx_report_purge_timer(struct timer_list *t)
struct rtw_dev *rtwdev = from_timer(rtwdev, t, tx_report.purge_timer);
struct rtw_tx_report *tx_report = &rtwdev->tx_report;
unsigned long flags;
+ u32 len = skb_queue_len(&tx_report->queue);
- if (skb_queue_len(&tx_report->queue) == 0)
+ if (len == 0)
return;
- rtw_warn(rtwdev, "failed to get tx report from firmware\n");
+ rtw_warn(rtwdev, "still have %u unprocessed tx report requests\n", len);
spin_lock_irqsave(&tx_report->q_lock, flags);
skb_queue_purge(&tx_report->queue);
@@ -214,6 +215,7 @@ void rtw_tx_report_enqueue(struct rtw_dev *rtwdev, struct sk_buff *skb, u8 sn)
/* pass sn to tx report handler through driver data */
drv_data = (u8 *)IEEE80211_SKB_CB(skb)->status.status_driver_data;
*drv_data = sn;
+pr_err("queueing tx report request with sn %d\n", sn);
spin_lock_irqsave(&tx_report->q_lock, flags);
__skb_queue_tail(&tx_report->queue, skb);
@@ -256,6 +258,7 @@ void rtw_tx_report_handle(struct rtw_dev *rtwdev, struct sk_buff *skb, int src)
sn = GET_CCX_REPORT_SEQNUM_V1(c2h->payload);
st = GET_CCX_REPORT_STATUS_V1(c2h->payload);
}
+pr_err("received tx report with sn %d\n", sn);
spin_lock_irqsave(&tx_report->q_lock, flags);
skb_queue_walk_safe(&tx_report->queue, cur, tmp) {
You don't need debug_mask anymore. |
|
It feels like the TX issue had gone, if I am understanding correctly the message is just a timing issue. After a very short test it feels like the "failed to allocate rx_skb #" still can trigger easily. How I am triggering this is undergo a system stress test on main-memory. The main-memory is: dmesgubuntu@briansune:~$ dmesg |
|
Bad news, I just discover a couples of TX issue. dmesgubuntu@briansune:~$ dmesg |
Yes, that's normal. The memory allocation sometimes fails, but it's retried. I will remove the message eventually. This latest log makes me think you're seeing the same bug I ran into and fixed recently. I haven't published the fix yet. But to confirm, you should apply that patch I gave you above and let it run for a while. |
|
Those two dmesg had already applied the patch you gave me from
|
|
I had run a longer test the log is attached here: dmesgubuntu@briansune:~$ dmesg <\details> |
|
But you didn't apply the patch with the extra logging. It changes "failed to get tx report from firmware" into a different message. |
|
Real sorry didn't notice the clean is missing at the beginning of the build and result in such situation. The new log is attached. dmesgubuntu@briansune:~$ dmesg <\details> |
|
Attaching a longer dmesg with stressapptest and memtester and ping running. dmesgubuntu@briansune:~$ dmesg |
|
Had successfully trigger the "still have error" message. dmesgubuntu@briansune:~$ dmesg |
|
As I suspected, that's the bug I fixed recently. The firmware can't always handle many TX report requests in a short time. I pushed the fix. |
|
Yes after the study on the log it feels like the get and give is out of order when messed up and even get lossed ordering. |
|
This is the log after modifying those area you had committed. But the "tw_8723du 1-1:1.2: failed to allocate rx_skb #" is still problematic. dmesgubuntu@briansune:~$ dmesg |
|
It's a buffer for the RX data. The problem seems to be that it's kinda large (32 KiB) and the system doesn't always have that much contiguous memory. So when the allocation fails it tries again a little later. |
|
Do you suggesting I need to increase the kernel cma settings? |
|
I guess this log explain a lot why it is happening Before driver load:
Once I boot the system and loaded the driver.
Do stressapptest
So the question now back to why the CMA memory is not locked by the driver and allowing other application to use more than it allows? Or at the state after the driver load it only use i.e. X size of memory and after other application is loaded Y size of memory is used. |
|
I don't think you need to do anything at this point. It's a problem in the driver. There is another problem which requires a small redesign of the RX code, so I will try to fix both at the same time. |
|
I pushed a fix for "failed to allocate rx_skb". I'm curious how it works with your stress tests. |
|
Appreciate the great works. See the comments. Again speed and great work. =] |
|
A quick compile shows:
|
|
Oh, I forgot to disable that INIT_WORK. I'll fix it tomorrow. |
|
Waiting on the instruction of the INIT_WORK. Thank you. |
|
I fixed it. |
|
Had successfully build t he driver. |
|
According to the previous repeatable fail skb behavior. As for the new push, Good result! Appreciate all the fixes. =] dmesg[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd040] |
|
I will try to make those message out. |
|
I had successfully compile the kernel with the debug message.
I am reading those debug message and waiting on the fail message. |
|
When the debug message is turned on and background is running ping the "failed to get tx report from firmware" not showing up at short test. It appears that 3 repeated id 0x03. dmesgubuntu@briansune:~/scripts$ dmesg | grep "id=0x03" |
|
Repeatable: dmesg[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd040] |
|
OK, I finally can grep it with a debug mask is turned on. $ dmesg | grep fail dmesg[ 6305.815233] rtw_8723du 1-1:1.2: send H2C content 01000020 00000c00 [ 6605.807317] rtw_8723du 1-1:1.2: send H2C content 01000020 00000c00 [ 6613.842990] rtw_8723du 1-1:1.2: send H2C content 00000058 00000213 [ 6649.835852] rtw_8723du 1-1:1.2: recv C2H, id=0x09, seq=0xe6, len=7 <\details> |
|
Okay, so my fix is not enough. I will report the problem and we'll see what happens. If you don't need to support roaming, you can disable the "bgscan" performed by wpa_supplicant. That will do a better job avoiding the problem than my fix did. |
|
Would it possible to explain what is happening behind this issue? |
|
Every five minutes wpa_supplicant triggers a scan, I assume to see if there are better APs available. During these scans mac80211 transmits many QoS Null frames in quick succession. Because these frames are marked with IEEE80211_TX_CTL_REQ_TX_STATUS, rtw88 asks the firmware to report the TX ACK status for each of these frames. Sometimes the firmware can't process the TX status requests quickly enough, they add up, it only processes some of them, and it permanently messes up the internal sequence number assigned to each TX status report. Then the firmware marks every subsequent TX status report with the wrong number, so rtw88 ignores them and prints a warning instead of reporting the TX status back to mac80211. If the device is going to be connected to just one AP, you can disable the "bgscan" in wpa_supplicant. |
|
Thank you for the explanation learn a lot =] I may not have good enough knowledge to understand all the theory behind. If my understand correctly: However, if the device using this driver is stationary and the same WIFI AP is the only one it is using. Then
is not needed and it is completely fine to remove it. Hope I am getting this correctly =] |
|
Yes, something like that. |
I changed my mind. The obvious solution was easier to implement than I first thought, so I just did it. You will still see "failed to get tx report from firmware" occasionally, but not every five minutes. You can safely ignore it. |
|
May I know the first thought about the firmware is that you are reporting back to realtek? Am I getting this correctly? |
|
Yes. |
|
Any appreciate all the works and assisting users and developers. But just a simple question to closeup the issue. |
I think the problem with the sequence numbers can cause unnecessary disconnections, for example during GTK rekeying. Nothing worse. |
|
Got it~ |
|
Hi, I'm testing with the "Scan" button on OpenWrt (triggering a scan every ~10 seconds), iperf3 -R for speed testing and using 8812au as a client on a far away AP (-70, -75 dbm). The old fix (140da49) solves the problem. Of course iperf3 slows down a little, but stopping the aggressive scan ramps up the speed. My thought is that the internal firmware corruption affects more than just the TX status number on 8812au. Will it be possible to retain the new & old patch, to prevent the firmware from becoming corrupted? With the old patch With the new patch: I can't see anything on dmesg. I definitely did not see the “failed to get tx report from firmware” error. |
|
Big question before people start debugging. Even you are unable to see any necessary message from the dmesg you still need to post it and give a good trace to developers to see the behind behaviors. Otherwise people could only make big guessing. |
|
@LuisMitaHL Let me see if I understood correctly: The RTL8812AU is plugged into the Cudy TR1200? This Travelmate software is also running on the Cudy? You are using the Cudy's internal wifi in AP mode, and the RTL8812AU in client mode, connected to another AP?
Did you have the problem before the old fix? With this commit: e9a6539 |
|
I tried his method on my side. It loss so many packet during server and client tests. Result as follows: PC (Ubuntu) iperf3iperf3 -c 192.168.1.9 -t 600 -R [ ID] Interval Transfer Bandwidth Custom Board (ARM 5.4.0) iperf3Server listening on 5201Accepted connection from 192.168.1.3, port 58606 [ ID] Interval Transfer Bandwidth Retr |
|
The repository branch I used is "Commit 22f2412" Custom board wifi dBm:
dmesg[ 139.049105] rtw_8723ds mmc1:0001:1: send H2C content 2b000042 00000000 <\details> |
Yes. Its a TP-Link Archer T4UHP
Exactly
Yes. But I run the tests using iperf3 installed directly on the Cudy, I am not passing any traffic on the internal wifi.
Reverting to the commit: Before: syslogBefore: iperf3 server logOne thing I have to mention is that the only stable thing here is the low speed of iperf3. Sometimes the interface crashes and iperf3 hangs, sometimes it doesn't and iperf3 works for 10+ minutes without problems, and sometimes Linux crash and stops working, needing to unplug and plug the power. The TR1200 comes with a 580 MHz MIPS CPU and 128 MB of RAM. Maybe that influences something. However, I can consistently reproduce the failure of the new fix by retrying the tests several times. One thing I just noticed, on one test after a certain time (30 min) it seems that the firmware is completely dead. New fix, more detailed logsNew fix: iperf3 |
|
In my case before I go back to use the RTW88. And even tried to clone proper firmware from a module chip into RTW88 still perform very badly. The DRIVER should undergo a check to see chip preprogrammed firmware or load back from the general settings from the driver. I can undergo a AP test like you and remove the router traffic on the old RTL8723DS driver and compare but I have very strong feeling that it will not drop or crash in any case. |
|
I had undergo the old RLT8723DS driver test with the same setup. PC (Ubuntu) iperf3iperf3 -c 192.168.1.12 -R -t 600 Custom Board (ARM) iperf3iperf3 -sServer listening on 5201Accepted connection from 192.168.1.3, port 60152 |
|
@LuisMitaHL "Before: syslog" shows some messages which did not exist in commit e9a6539 so I'm not sure what commit you tested. Maybe testing e9a6539 is not a good idea anyway because the driver can get stuck. A better idea is to use the latest code and apply the old fix on top: 140da49 The point is to check if your problems are caused by the new fix or by some other unrelated changes. |
|
Hi, I also tested again with a Cudy TR3000 (512MB RAM aarch64 router), where I was able to find the problems again. With this, I think that CPU arch is not a factor. rtw88 HEAD, syslog+iperf3 |
rtw88 HEAD+140da49 reapplied, syslog+iperf3At least in my case reapplying 140da49 solves the problem. |
I am using A53 ARM processor also with only 256MB RAM custom board. |
…TX patch Firmware TX patch reapplied (lwfinger/rtw88#246). Removing CONFIG_MAC80211_LEDS hack, it's not needed now.
|
The TR1200 comes with a 580 MHz MIPS CPU and 128 MB of RAM. Maybe that influences something. I discover that I didn't see this from beginning. How much swap space do both system had? I had very strong feeling when the memory got low it will trigger huge crash and system dead. Try:
or
|
@lwfinger
@dubhater
We are using RTL8723DU USB dongle on UBUNTU LTS 20.04.2 LTS
There are a lot of report on failed to get tx report from firmware.
How could we resolve this issue?
We do also see there are cases that the driver will crash.
What we had done to repeat the crash is undergo a memory stress test command.
While the fail to get tx report is randomly happened.
Attaching dmesg report below.
Thank you
dmesg
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd040]
[ 0.000000] Linux version 6.1.54-rt15 (tg5@tg5) (aarch64-linux-gnu-gcc (Linaro GCC 7.5-2019.12) 7.5.0, GNU ld (Linaro_Binutils-2019.12) 2.28.2.20170706) #8 SMP PREEMPT Thu Oct 31 07:04:49 HKT 2024
[ 0.000000] Machine model: Anlogic, DR1M90 FPSoc
[ 0.000000] earlycon: uart0 at MMIO32 0x00000000f8401000 (options '')
[ 0.000000] printk: bootconsole [uart0] enabled
[ 0.000000] efi: UEFI not found.
[ 0.000000] Reserved memory: created CMA memory pool at 0x0000000016400000, size 128 MiB
[ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv0.2 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] percpu: Embedded 21 pages/cpu s46248 r8192 d31576 u86016
[ 0.000000] pcpu-alloc: s46248 r8192 d31576 u86016 alloc=21*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: detected: GIC system register CPU interface
[ 0.000000] alternatives: applying boot alternatives
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 129024
[ 0.000000] Kernel command line: console=ttyS0,115200n8 earlycon=uart,mmio32,0xf8401000 loglevel=8 root=/dev/mmcblk0p2 rootwait rootfstype=ext4 rw
[ 0.000000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 366092K/524288K available (10048K kernel code, 1384K rwdata, 3168K rodata, 1536K init, 581K bss, 27124K reserved, 131072K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2.
[ 0.000000] Trampoline variant of Tasks RCU enabled.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] GICv3: 160 SPIs implemented
[ 0.000000] GICv3: 0 Extended SPIs implemented
[ 0.000000] Root IRQ handler: gic_handle_irq
[ 0.000000] GICv3: GICv3 features: 16 PPIs
[ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000dd040000
[ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000000] arch_timer: cp15 timer(s) running at 33.33MHz (virt).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x7b00c4bad, max_idle_ns: 440795202744 ns
[ 0.000000] sched_clock: 56 bits at 33MHz, resolution 30ns, wraps every 2199023255551ns
[ 0.008198] Console: colour dummy device 80x25
[ 0.012667] Calibrating delay loop (skipped), value calculated using timer frequency.. 66.66 BogoMIPS (lpj=133333)
[ 0.022986] pid_max: default: 32768 minimum: 301
[ 0.027761] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
[ 0.035057] Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
[ 0.044141] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.051376] cblist_init_generic: Setting shift to 1 and lim to 1.
[ 0.057515] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.064725] cblist_init_generic: Setting shift to 1 and lim to 1.
[ 0.070953] rcu: Hierarchical SRCU implementation.
[ 0.075743] rcu: Max phase no-delay instances is 1000.
[ 0.081236] EFI services will not be available.
[ 0.086013] smp: Bringing up secondary CPUs ...
[ 0.091020] Detected VIPT I-cache on CPU1
[ 0.091113] GICv3: CPU1: found redistributor 1 region 0:0x00000000dd060000
[ 0.091159] CPU1: Booted secondary processor 0x0000000001 [0x411fd040]
[ 0.091270] smp: Brought up 1 node, 2 CPUs
[ 0.112735] SMP: Total of 2 processors activated.
[ 0.117431] CPU features: detected: 32-bit EL0 Support
[ 0.122575] CPU features: detected: CRC32 instructions
[ 0.127769] CPU: All CPU(s) started at EL1
[ 0.131856] alternatives: applying system-wide alternatives
[ 0.138336] devtmpfs: initialized
[ 0.145713] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.155442] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.167006] DMI not present or invalid.
[ 0.171516] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.178488] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
[ 0.185604] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.193421] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.201378] audit: initializing netlink subsys (disabled)
[ 0.206938] audit: type=2000 audit(0.136:1): state=initialized audit_enabled=0 res=1
[ 0.207409] thermal_sys: Registered thermal governor 'fair_share'
[ 0.214666] thermal_sys: Registered thermal governor 'bang_bang'
[ 0.220741] thermal_sys: Registered thermal governor 'step_wise'
[ 0.227030] ASID allocator initialised with 65536 entries
[ 0.253509] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.260318] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[ 0.266570] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[ 0.273339] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[ 0.279589] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.286352] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[ 0.292600] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[ 0.299364] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[ 0.306597] dw_dmac f804d000.ahb_dma: WARN: Device release is not defined so it is not safe to unbind this driver while in use
[ 0.318459] dw_dmac f804d000.ahb_dma: DesignWare DMA Controller, 8 channels
[ 0.326107] SCSI subsystem initialized
[ 0.330081] usbcore: registered new interface driver usbfs
[ 0.335609] usbcore: registered new interface driver hub
[ 0.340940] usbcore: registered new device driver usb
[ 0.346791] pps_core: LinuxPPS API ver. 1 registered
[ 0.351747] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [email protected]
[ 0.360859] PTP clock support registered
[ 0.365157] FPGA manager framework
[ 0.369213] Bluetooth: Core ver 2.22
[ 0.372806] NET: Registered PF_BLUETOOTH protocol family
[ 0.378105] Bluetooth: HCI device and connection manager initialized
[ 0.384444] Bluetooth: HCI socket layer initialized
[ 0.389311] Bluetooth: L2CAP socket layer initialized
[ 0.394359] Bluetooth: SCO socket layer initialized
[ 0.399588] vgaarb: loaded
[ 0.402666] clocksource: Switched to clocksource arch_sys_counter
[ 0.417695] NET: Registered PF_INET protocol family
[ 0.422798] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.431140] tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 0.439564] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.447308] TCP established hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.455078] TCP bind hash table entries: 4096 (order: 5, 131072 bytes, linear)
[ 0.462403] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.468830] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.475363] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.482474] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.488501] RPC: Registered named UNIX socket transport module.
[ 0.494437] RPC: Registered udp transport module.
[ 0.499132] RPC: Registered tcp transport module.
[ 0.503824] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.510250] PCI: CLS 0 bytes, default 64
[ 0.515111] Initialise system trusted keyrings
[ 0.519684] workingset: timestamp_bits=62 max_order=17 bucket_order=0
[ 0.536571] NFS: Registering the id_resolver key type
[ 0.541703] Key type id_resolver registered
[ 0.545881] Key type id_legacy registered
[ 0.549898] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.556581] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[ 0.563977] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.625808] Key type asymmetric registered
[ 0.629902] Asymmetric key parser 'x509' registered
[ 0.634825] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 242)
[ 0.646524] dma-pl330 f8419000.dma-controller: WARN: Device release is not defined so it is not safe to unbind this driver while in use
[ 0.659173] dma-pl330 f8419000.dma-controller: Loaded driver for PL330 DMAC-341330
[ 0.666733] dma-pl330 f8419000.dma-controller: DBUFF-16x16bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.679517] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.686959] printk: console [ttyS0] disabled
[ 0.711463] f8401000.serial: ttyS0 at MMIO 0xf8401000 (irq = 28, base_baud = 3125000) is a U6_16550A
[ 0.720738] printk: console [ttyS0] enabled
[ 0.720740] printk: console [ttyS0] printing thread started
[ 0.720744] printk: bootconsole [uart0] disabled
[ 0.738139] brd: module loaded
[ 0.742204] loop: module loaded
[ 0.742372] at24 0-0050: supply vcc not found, using dummy regulator
[ 0.752209] at24 0-0050: 256 byte 24c02 EEPROM, writable, 32 bytes/write
[ 0.753198] dw_spi_mmio f8404000.spi: Synopsys DWC APB SSI v4.03
[ 0.753216] dw_spi_mmio f8404000.spi: Detected FIFO size: 32 bytes
[ 0.753224] dw_spi_mmio f8404000.spi: Detected 32-bits max data frame size
[ 0.753292] dw_dmac f804d000.ahb_dma: private_candidate: dma0chan0 filter said false
[ 0.753303] dmaengine: __dma_request_channel: success (dma0chan1)
[ 0.753327] dmaengine: __dma_request_channel: success (dma0chan0)
[ 0.753494] dw_spi_mmio f8404000.spi: registered master spi0
[ 0.753680] spi spi0.0: setup mode 0, 8 bits/w, 8000000 Hz max --> 0
[ 0.754043] dw_spi_mmio f8404000.spi: registered child spi0.0
[ 0.754248] dw_spi_mmio f8405000.spi: Synopsys DWC APB SSI v4.03
[ 0.754263] dw_spi_mmio f8405000.spi: Detected FIFO size: 32 bytes
[ 0.754271] dw_spi_mmio f8405000.spi: Detected 32-bits max data frame size
[ 0.754325] dw_dmac f804d000.ahb_dma: private_candidate: dma0chan0 busy
[ 0.754334] dw_dmac f804d000.ahb_dma: private_candidate: dma0chan1 busy
[ 0.754342] dw_dmac f804d000.ahb_dma: private_candidate: dma0chan2 filter said false
[ 0.754351] dmaengine: __dma_request_channel: success (dma0chan3)
[ 0.754375] dw_dmac f804d000.ahb_dma: private_candidate: dma0chan0 busy
[ 0.754383] dw_dmac f804d000.ahb_dma: private_candidate: dma0chan1 busy
[ 0.754390] dmaengine: __dma_request_channel: success (dma0chan2)
[ 0.754549] dw_spi_mmio f8405000.spi: registered master spi1
[ 0.754717] spi spi1.0: setup mode 0, 8 bits/w, 8000000 Hz max --> 0
[ 0.755075] dw_spi_mmio f8405000.spi: registered child spi1.0
[ 0.755537] al-qspi f804e000.spi: registered master spi2
[ 0.755650] spi_master spi2: Failed to power device: -13
[ 0.755659] al-qspi f804e000.spi: can't setup spi2.0, status -13
[ 0.755667] spi_master spi2: spi_device register error /soc/spi@f804e000/flash@0
[ 0.755691] spi_master spi2: Failed to create SPI device for /soc/spi@f804e000/flash@0
[ 0.757542] dwc-eth-dwmac f8100000.ethernet0: User ID: 0x10, Synopsys ID: 0x52
[ 0.757557] dwc-eth-dwmac f8100000.ethernet0: DWMAC4/5
[ 0.757566] dwc-eth-dwmac f8100000.ethernet0: DMA HW capability register supported
[ 0.757573] dwc-eth-dwmac f8100000.ethernet0: RX Checksum Offload Engine supported
[ 0.757580] dwc-eth-dwmac f8100000.ethernet0: TX Checksum insertion supported
[ 0.757586] dwc-eth-dwmac f8100000.ethernet0: TSO supported
[ 0.757593] dwc-eth-dwmac f8100000.ethernet0: Enable RX Mitigation via HW Watchdog Timer
[ 0.757601] dwc-eth-dwmac f8100000.ethernet0: Enabled RFS Flow TC (entries=10)
[ 0.757611] dwc-eth-dwmac f8100000.ethernet0: TSO feature enabled
[ 0.757618] dwc-eth-dwmac f8100000.ethernet0: Using 32/32 bits DMA host/device width
[ 0.760634] dwc2 f8180000.usb: supply vusb_d not found, using dummy regulator
[ 0.760774] dwc2 f8180000.usb: supply vusb_a not found, using dummy regulator
[ 0.761208] dwc2 f8180000.usb: DWC OTG Controller
[ 0.761230] dwc2 f8180000.usb: new USB bus registered, assigned bus number 1
[ 0.761257] dwc2 f8180000.usb: irq 33, io mem 0xf8180000
[ 0.761456] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[ 0.761469] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.761479] usb usb1: Product: DWC OTG Controller
[ 0.761486] usb usb1: Manufacturer: Linux 6.1.54-rt15 dwc2_hsotg
[ 0.761493] usb usb1: SerialNumber: f8180000.usb
[ 0.762013] hub 1-0:1.0: USB hub found
[ 0.762045] hub 1-0:1.0: 1 port detected
[ 0.763018] usbcore: registered new interface driver cdc_acm
[ 0.763026] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 0.763060] usbcore: registered new interface driver cdc_wdm
[ 0.763270] usbcore: registered new interface driver uas
[ 0.763340] usbcore: registered new interface driver usb-storage
[ 0.763424] usbcore: registered new interface driver usbserial_generic
[ 0.763450] usbserial: USB Serial support registered for generic
[ 0.763488] usbcore: registered new interface driver usb_serial_simple
[ 0.763511] usbserial: USB Serial support registered for carelink
[ 0.763533] usbserial: USB Serial support registered for flashloader
[ 0.763559] usbserial: USB Serial support registered for funsoft
[ 0.763581] usbserial: USB Serial support registered for google
[ 0.763602] usbserial: USB Serial support registered for hp4x
[ 0.763624] usbserial: USB Serial support registered for kaufmann
[ 0.763646] usbserial: USB Serial support registered for libtransistor
[ 0.763668] usbserial: USB Serial support registered for moto_modem
[ 0.763690] usbserial: USB Serial support registered for motorola_tetra
[ 0.763715] usbserial: USB Serial support registered for nokia
[ 0.763737] usbserial: USB Serial support registered for novatel_gps
[ 0.763759] usbserial: USB Serial support registered for siemens_mpi
[ 0.763781] usbserial: USB Serial support registered for suunto
[ 0.763807] usbserial: USB Serial support registered for vivopay
[ 0.763829] usbserial: USB Serial support registered for zio
[ 0.780586] rtc-ds1307 0-0068: SET TIME!
[ 0.800662] rtc-ds1307 0-0068: registered as rtc0
[ 0.812470] rtc-ds1307 0-0068: hctosys: unable to read the hardware clock
[ 0.812563] i2c_dev: i2c /dev entries driver
[ 0.812931] usbcore: registered new interface driver btusb
[ 0.813129] sdhci: Secure Digital Host Controller Interface driver
[ 0.813132] sdhci: Copyright(c) Pierre Ossman
[ 0.813136] sdhci-pltfm: SDHCI platform and OF driver helper
[ 0.813421] sdhci-dwcmshc f8049000.mmc: Got CD GPIO
[ 0.814344] usbcore: registered new interface driver usbhid
[ 0.814351] usbhid: USB HID core driver
[ 0.815063] ipip: IPv4 and MPLS over IPv4 tunneling driver
[ 0.815570] gre: GRE over IPv4 demultiplexor driver
[ 0.815576] ip_gre: GRE over IPv4 tunneling driver
[ 0.816858] IPv4 over IPsec tunneling driver
[ 0.817810] NET: Registered PF_INET6 protocol family
[ 0.819772] Segment Routing with IPv6
[ 0.819822] In-situ OAM (IOAM) with IPv6
[ 0.820488] NET: Registered PF_PACKET protocol family
[ 0.820505] NET: Registered PF_KEY protocol family
[ 0.820639] Bluetooth: RFCOMM TTY layer initialized
[ 0.820653] Bluetooth: RFCOMM socket layer initialized
[ 0.820699] Bluetooth: RFCOMM ver 1.11
[ 0.821029] Key type dns_resolver registered
[ 0.821576] Loading compiled-in X.509 certificates
[ 0.824375] Key type encrypted registered
[ 0.828964] of-fpga-region soc:base_fpga_region: FPGA Region probed
[ 0.830073] input: soc:keys as /devices/platform/soc/soc:keys/input/input0
[ 0.838582] of_cfs_init
[ 0.838716] of_cfs_init: OK
[ 0.850693] mmc0: SDHCI controller on f8049000.mmc [f8049000.mmc] using ADMA
[ 0.860218] Waiting for root device /dev/mmcblk0p2...
[ 1.007194] mmc0: new high speed SDHC card at address 0001
[ 1.007819] mmcblk0: mmc0:0001 00000 7.44 GiB
[ 1.014439] mmcblk0: p1 p2
[ 1.059656] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: disabled.
[ 1.059719] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 1.069609] usb 1-1: new high-speed USB device number 2 using dwc2
[ 1.073580] devtmpfs: mounted
[ 1.074397] Freeing unused kernel memory: 1536K
[ 1.087489] Checked W+X mappings: passed, no W+X pages found
[ 1.087515] Run /sbin/init as init process
[ 1.087521] with arguments:
[ 1.087524] /sbin/init
[ 1.087527] with environment:
[ 1.087529] HOME=/
[ 1.087532] TERM=linux
[ 1.280991] usb 1-1: New USB device found, idVendor=0bda, idProduct=d723, bcdDevice= 2.00
[ 1.281013] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.281023] usb 1-1: Product: 802.11n WLAN Adapter
[ 1.281030] usb 1-1: Manufacturer: Realtek
[ 1.281037] usb 1-1: SerialNumber: 00e04c000001
[ 1.306310] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000d lmp_ver=08 lmp_subver=8723
[ 1.325450] Bluetooth: hci0: RTL: rom_version status=0 version=2
[ 1.325465] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723d_fw.bin
[ 1.384425] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723d_config.bin
[ 1.391655] Bluetooth: hci0: RTL: cfg_sz 10, total sz 33266
[ 1.766629] Bluetooth: hci0: RTL: fw version 0x828a96f1
[ 1.992089] systemd[1]: System time before build time, advancing clock.
[ 2.024988] systemd[1]: Failed to look up module alias 'autofs4': Function not implemented
[ 2.078453] systemd[1]: systemd 245.4-4ubuntu3.24 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[ 2.078969] systemd[1]: Detected architecture arm64.
[ 2.135843] systemd[1]: Set hostname to .
[ 3.074687] random: crng init done
[ 3.081012] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
[ 3.081039] systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
[ 3.081951] systemd[1]: Created slice system-getty.slice.
[ 3.123399] systemd[1]: Created slice system-modprobe.slice.
[ 3.147265] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 3.171179] systemd[1]: Created slice User and Session Slice.
[ 3.191101] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 3.215035] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 3.238955] systemd[1]: Condition check resulted in Arbitrary Executable File Formats File System Automount Point being skipped.
[ 3.239127] systemd[1]: Reached target Local Encrypted Volumes.
[ 3.263275] systemd[1]: Reached target User and Group Name Lookups.
[ 3.286801] systemd[1]: Reached target Remote File Systems.
[ 3.306781] systemd[1]: Reached target Slices.
[ 3.327501] systemd[1]: Listening on fsck to fsckd communication Socket.
[ 3.351128] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ 3.375839] systemd[1]: Listening on Journal Audit Socket.
[ 3.399364] systemd[1]: Listening on Journal Socket (/dev/log).
[ 3.423389] systemd[1]: Listening on Journal Socket.
[ 3.443409] systemd[1]: Listening on udev Control Socket.
[ 3.463205] systemd[1]: Listening on udev Kernel Socket.
[ 3.499146] systemd[1]: Mounting Huge Pages File System...
[ 3.519313] systemd[1]: Condition check resulted in POSIX Message Queue File System being skipped.
[ 3.522615] systemd[1]: Mounting Kernel Debug File System...
[ 3.555323] systemd[1]: Condition check resulted in Kernel Trace File System being skipped.
[ 3.579532] systemd[1]: Starting Journal Service...
[ 3.591160] systemd[1]: Condition check resulted in Create list of static device nodes for the current kernel being skipped.
[ 3.594872] systemd[1]: Starting Load Kernel Module chromeos_pstore...
[ 3.623027] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
[ 3.626441] systemd[1]: Starting Load Kernel Module efi_pstore...
[ 3.654287] systemd[1]: Starting Load Kernel Module pstore_blk...
[ 3.687398] systemd[1]: Starting Load Kernel Module pstore_zone...
[ 3.714141] systemd[1]: Starting Load Kernel Module ramoops...
[ 3.728351] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[ 3.728546] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[ 3.734810] systemd[1]: Starting Load Kernel Modules...
[ 3.778316] systemd[1]: Starting Remount Root and Kernel File Systems...
[ 3.806464] systemd[1]: Starting udev Coldplug all Devices...
[ 3.824105] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: disabled.
[ 3.837972] systemd[1]: Started Journal Service.
[ 4.112396] Adding 1048572k swap on /swapfile. Priority:-2 extents:8 across:5857276k SS
[ 4.180988] systemd-journald[126]: Received client request to flush runtime journal.
[ 4.202283] systemd-journald[126]: File /var/log/journal/9855905ab2944be891538ff748241542/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 9.697463] Bluetooth: MGMT ver 1.22
[ 589.515117] systemd-journald[126]: Failed to set ACL on /var/log/journal/9855905ab2944be891538ff748241542/user-1000.journal, ignoring: Operation not supported
[ 596.319548] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 596.335817] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 598.118476] rtw_core: loading out-of-tree module taints kernel.
[ 598.514226] rtw_8723du 1-1:1.2: Firmware version 48.0.0, H2C version 0
[ 599.615333] usbcore: registered new interface driver rtw_8723du
[ 599.641064] rtw_8723du 1-1:1.2 wlx90de80882cf1: renamed from wlan0
[ 604.013322] wlx90de80882cf1: authenticate with f8:6f:b0:0e:ae:e5
[ 604.013393] wlx90de80882cf1: 80 MHz not supported, disabling VHT
[ 605.562628] wlx90de80882cf1: send auth to f8:6f:b0:0e:ae:e5 (try 1/3)
[ 605.564798] wlx90de80882cf1: authenticated
[ 605.568574] wlx90de80882cf1: associate with f8:6f:b0:0e:ae:e5 (try 1/3)
[ 605.601383] wlx90de80882cf1: RX AssocResp from f8:6f:b0:0e:ae:e5 (capab=0x1411 status=0 aid=3)
[ 605.619838] wlx90de80882cf1: associated
[ 605.800828] wlx90de80882cf1: Limiting TX power to 35 (35 - 0) dBm as advertised by f8:6f:b0:0e:ae:e5
[ 605.829046] IPv6: ADDRCONF(NETDEV_CHANGE): wlx90de80882cf1: link becomes ready
[ 1509.133062] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 1664.583324] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 1719.877242] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 1795.650412] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 1809.090427] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 2006.598908] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 2073.670997] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 2109.030857] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 2142.534606] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 2240.069397] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 2301.508398] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 2409.090217] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 2489.920359] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 2531.647357] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 2709.050804] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 3009.075705] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 3040.818943] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 3106.609413] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 3199.535200] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 3309.068523] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 3343.659618] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 3609.060794] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 3728.929580] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 3908.988718] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 3936.187982] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 4015.545827] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 4030.489414] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 4047.672947] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 4103.479423] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 4208.021498] rtw_8723du 1-1:1.2: failed to allocate rx_skb
[ 4208.095236] rtw_8723du 1-1:1.2: failed to allocate rx_skb
[ 4208.123961] rtw_8723du 1-1:1.2: failed to allocate rx_skb
[ 4208.156729] rtw_8723du 1-1:1.2: failed to allocate rx_skb
[ 4209.076586] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 4210.388549] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 4213.204760] wlx90de80882cf1: authenticate with f8:6f:b0:0e:ae:e5
[ 4213.204825] wlx90de80882cf1: 80 MHz not supported, disabling VHT
[ 4214.783981] wlx90de80882cf1: send auth to f8:6f:b0:0e:ae:e5 (try 1/3)
[ 4215.316386] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 4215.864583] wlx90de80882cf1: send auth to f8:6f:b0:0e:ae:e5 (try 2/3)
[ 4216.372322] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 4216.889058] wlx90de80882cf1: send auth to f8:6f:b0:0e:ae:e5 (try 3/3)
[ 4217.396288] rtw_8723du 1-1:1.2: failed to get tx report from firmware
[ 4217.876326] wlx90de80882cf1: authentication with f8:6f:b0:0e:ae:e5 timed out
The text was updated successfully, but these errors were encountered: