Created attachment 13493 [details]
make log from failed build

I just recently reinstalled the dkms-rtl8192eu package. Not sure how long it's
been since it built properly.

Reassigning to Philippe, the registered maintainer.

Assignee: kernel => makowski.mageia
CC: (none) => kernel

We need recent commits from https://github.com/Mange/rtl8192eu-linux-driver/

At least https://github.com/Mange/rtl8192eu-linux-driver/commit/ec5c2446db5f3380d7468b1e71fe9db67cbc8a8b for 6.0 and we should add at least https://github.com/Mange/rtl8192eu-linux-driver/commit/563780d2ebe722384c10d9185055edd9905828de to avoid a future update.

I would probably just switch to a more recent git snapshot.

I have updated cauldron with a 20221105 snapshot and the sources build with the 6.0.8 kernel but make prepare (called by dkms) is currently broken in cauldron so I didn't properly test the package.

(In reply to Pascal Terjan from comment #4)
> I have updated cauldron with a 20221105 snapshot and the sources build with
> the 6.0.8 kernel but make prepare (called by dkms) is currently broken in
> cauldron so I didn't properly test the package.

Fix coming in next kernel build


--
Thomas

I have uploaded it to 8/updates_testing and can confirm it built fine with kernel 6.0.8-desktop-3.mga8 and detected the adaptor:

[   51.238405] usb 2-1: new high-speed USB device number 2 using xhci_hcd
[   51.426825] usb 2-1: New USB device found, idVendor=2357, idProduct=0109, bcdDevice= 2.00
[   51.426838] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   51.426842] usb 2-1: Product: 802.11n NIC 
[   51.426844] usb 2-1: Manufacturer: Realtek 
[   51.426847] usb 2-1: SerialNumber: 00e04c000001
[   51.650932] usbcore: registered new interface driver rtl8192eu
[   51.662039] rtl8192eu 2-1:1.0 wlp1s0u1: renamed from wlan0

(In reply to Dave Hodgins from comment #1)
> Created attachment 13493 [details]
> make log from failed build
> 
> I just recently reinstalled the dkms-rtl8192eu package. Not sure how long
> it's
> been since it built properly.

I just updated to the 5.19.16 desktop kernel on a system I haven't touched in months, and it didn't build properly here, either. It did build properly with the 5.18 series kernel in August. (Bug 30737) That fix was supposed to work for the 5.19 series as well, but I couldn't test it when the 5.19 series was backported.

CC: (none) => andrewsfarm

Can you try with dkms-rtl8192eu from updates_testing?

That one appears to build with the 5.19.16 desktop kernel, but the device doesn't work with the net_applet. It fails to connect on the first try, and trying to connect again just goes into some kind of endless loop.

Thank you, I didn't test more than seeing the device was detected, I'll have a look.

It is indeed badly broken:

Nov 15 18:48:43 pn50 systemd-udevd[712]: wlan0: Worker [5387] processing SEQNUM=4560 is taking a long time
Nov 15 18:48:43 pn50 systemd-udevd[5387]: wlan0: Spawned process 'net_action' [5399] is taking longer than 59s to complete
Nov 15 18:48:43 pn50 kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
Nov 15 18:48:43 pn50 kernel: rcu:         12-....: (1 GPs behind) idle=8f8c/1/0x4000000000000000 softirq=250691/250693 fqs=13702
Nov 15 18:48:43 pn50 kernel:         (t=60001 jiffies g=1100337 q=2288 ncpus=16)
Nov 15 18:48:43 pn50 kernel: NMI backtrace for cpu 12
Nov 15 18:48:43 pn50 kernel: CPU: 12 PID: 5434 Comm: iwconfig Tainted: G           O       6.0.8-desktop-3.mga8 #1
Nov 15 18:48:43 pn50 kernel: Hardware name: ASUSTeK COMPUTER INC. MINIPC PN50/PN50, BIOS 0611 12/17/2020
Nov 15 18:48:43 pn50 kernel: Call Trace:
Nov 15 18:48:43 pn50 kernel:  <IRQ>
Nov 15 18:48:43 pn50 kernel:  dump_stack_lvl+0x45/0x5e
Nov 15 18:48:43 pn50 kernel:  nmi_cpu_backtrace.cold+0x32/0x79
Nov 15 18:48:43 pn50 kernel:  dump_stack_lvl+0x45/0x5e
Nov 15 18:48:43 pn50 kernel:  nmi_cpu_backtrace.cold+0x32/0x79
Nov 15 18:48:43 pn50 kernel:  ? lapic_can_unplug_cpu+0x80/0x80
Nov 15 18:48:43 pn50 kernel:  nmi_trigger_cpumask_backtrace+0xd8/0xf0
Nov 15 18:48:43 pn50 kernel:  rcu_dump_cpu_stacks+0xc3/0xfe
Nov 15 18:48:43 pn50 kernel:  rcu_sched_clock_irq.cold+0xfa/0x497
Nov 15 18:48:43 pn50 kernel:  ? update_load_avg+0x714/0x750
Nov 15 18:48:43 pn50 kernel:  ? reweight_entity+0x14c/0x160
Nov 15 18:48:43 pn50 kernel:  update_process_times+0x5b/0x90
Nov 15 18:48:43 pn50 kernel:  tick_sched_handle+0x34/0x50
Nov 15 18:48:43 pn50 kernel:  tick_sched_timer+0x65/0x80
Nov 15 18:48:43 pn50 kernel:  ? tick_sched_do_timer+0xa0/0xa0
Nov 15 18:48:43 pn50 kernel:  __hrtimer_run_queues+0x12a/0x2c0
Nov 15 18:48:43 pn50 kernel:  hrtimer_interrupt+0xfc/0x210
Nov 15 18:48:43 pn50 kernel:  __sysvec_apic_timer_interrupt+0x5f/0x110
Nov 15 18:48:43 pn50 kernel:  sysvec_apic_timer_interrupt+0x6d/0x90
Nov 15 18:48:43 pn50 kernel:  </IRQ>
Nov 15 18:48:43 pn50 kernel:  <TASK>
Nov 15 18:48:43 pn50 kernel:  asm_sysvec_apic_timer_interrupt+0x16/0x20
Nov 15 18:48:43 pn50 kernel: RIP: 0010:rtw_wx_set_essid+0x192/0x290 [8192eu]
Nov 15 18:48:43 pn50 kernel: Code: b5 c8 00 00 00 4c 89 e8 eb 0d 4c 39 6d 70 75 4d 48 8b 85 90 00 00 00 48 89 45 70 8b 54 24 04 48 89 de 4c 89 f7 e8 5e 89 ff ff <83> f8 01 75 db 8b 44 24 04 39 85 c4 00 00 00 75>
Nov 15 18:48:43 pn50 kernel: RSP: 0018:ffffa7de82b9bd28 EFLAGS: 00000286
Nov 15 18:48:43 pn50 kernel: RAX: 0000000000000000 RBX: ffffa7de82b9bd30 RCX: 0000000000000042
Nov 15 18:48:43 pn50 kernel: RDX: 00000000ffffffbe RSI: 0000000000000007 RDI: ffffa7de8011b0c8
Nov 15 18:48:43 pn50 kernel: RBP: ffffa7de8011b000 R08: ffffa7de82b9bd30 R09: ffffa7de82b9be4c
Nov 15 18:48:43 pn50 kernel: R10: ffffffffc1f13f80 R11: 00007ffcfa4649f0 R12: 0000000000000000
Nov 15 18:48:43 pn50 kernel: R13: ffffa7de8011b090 R14: ffffa7de8011b0c8 R15: ffffa7de8011b0a0
Nov 15 18:48:43 pn50 kernel:  ? rtw_wx_set_rate+0x190/0x190 [8192eu]
Nov 15 18:48:43 pn50 kernel:  ? rtw_wx_set_essid+0x192/0x290 [8192eu]
Nov 15 18:48:43 pn50 kernel:  ioctl_standard_iw_point+0x2e5/0x3b0
Nov 15 18:48:43 pn50 kernel:  ? rtw_wx_set_rate+0x190/0x190 [8192eu]
Nov 15 18:48:43 pn50 kernel:  ? __inode_wait_for_writeback+0x7e/0xf0
Nov 15 18:48:43 pn50 kernel:  ioctl_standard_call+0xa5/0xd0
Nov 15 18:48:43 pn50 kernel:  wext_handle_ioctl+0x133/0x170
Nov 15 18:48:43 pn50 kernel:  ? mntput_no_expire+0x4a/0x240
Nov 15 18:48:43 pn50 kernel:  sock_ioctl+0x1cc/0x2f0
Nov 15 18:48:43 pn50 kernel:  __x64_sys_ioctl+0x8b/0xc0
Nov 15 18:48:43 pn50 kernel:  do_syscall_64+0x3b/0x90
Nov 15 18:48:43 pn50 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
Nov 15 18:48:43 pn50 kernel: RIP: 0033:0x7fb20dc05aa7
Nov 15 18:48:43 pn50 kernel: Code: 3c 1c 48 f7 d8 4c 39 e0 77 a9 e8 04 ff ff ff 85 c0 78 b7 4c 89 e0 5b 5d 41 5c c3 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 91 53 0d 00>
Nov 15 18:48:43 pn50 kernel: RSP: 002b:00007ffcfa4649a8 EFLAGS: 00000202 ORIG_RAX: 0000000000000010
Nov 15 18:48:43 pn50 kernel: RAX: ffffffffffffffda RBX: 00007ffcfa464c20 RCX: 00007fb20dc05aa7
Nov 15 18:48:43 pn50 kernel: RDX: 00007ffcfa4649d0 RSI: 0000000000008b1a RDI: 0000000000000003
Nov 15 18:48:43 pn50 kernel: RBP: 0000000000000003 R08: 0000000000000007 R09: 003175307331706c
Nov 15 18:48:43 pn50 kernel: R10: fffffffffffff945 R11: 0000000000000202 R12: 00007ffcfa465aa1
Nov 15 18:48:43 pn50 kernel: R13: 00007ffcfa4649d0 R14: 00007ffcfa4649f0 R15: 0000000000000001
Nov 15 18:48:43 pn50 kernel:  </TASK>

I have submitted dkms-rtl8192eu-4.4.1-2.20210403.1.mga8 which goes back to the 20210403 snapshot and just adds the patchs for 6.0 and 6.1.

I have tested it here (with "2357:0109 TP-Link TL-WN823N v2/v3") and it is working fine for me.

Qarepo says it hasn't made it to the princeton mirror yet - all it has is the one we just tested. I will wait a while and try again. Will yours be able to build with the 5.19.16 kernel? I don't have the 6.x kernel yet.

I have booted into the 5.18.x kernel and downgraded back to the old driver so that it will update properly. I checked it out to be sure, and it does work with my device. It does not build with the 5.19.16 kernel.

BTW, my device carries the inspiring brand name of "Zowietek." But, it does work...

Got it this morning, and it built with the 5.19.16 kernel and works. Using it now. There was some finagling necessary with the settings in Network Center before it would connect, but that has always been the way.

I have not tried it with a 6.x kernel. I tend to avoid installing new kernels from various testing repos until TMB says they are ready for QA.

Thomas (tmb), should I remove this one from updates_testing and move it to backports_testing?

Not my decision, but let me check to see if it builds and works with the present 5.15.74 kernel. 

If it does, then our past practice has been to keep it as an update.

As I expected, it does build and function properly, as far as *I* can tell, with the 5.15.74 kernel.

(In reply to Pascal Terjan from comment #15)
> Thomas (tmb), should I remove this one from updates_testing and move it to
> backports_testing?

Nope, updates_testting -> updates path is preferred.

we  try to keep driver updates as normal updates (even if they add support for backports kernels) as that is easier to manage for endusers

The only exception so far is the nvidia-current driver in backports as that  one drops older hw support so it would cause regressions

obviously they need to be tested with both updates and backports kernels,

and I both are done, so that's covered for this update

I just tried this with the 6.0.9 kernel from backports_testing, and it builds and functions perfectly.

If someone could do whatever still needs to be done to get this ready for QA, I could OK it and validate almost immediately...

Advisory:

The dkms-rtl8192eu package has been updated to support recent versions of the
Linux kernel.

Updated packages in core/updates_testing:
========================
dkms-rtl8192eu-4.4.1-2.20210403.1.mga8

Source RPMs: 
dkms-rtl8192eu-4.4.1-2.20210403.1.mga8.src.rpm

OKing and validating. Advisory in comment 21.

Whiteboard: (none) => MGA8-64-OK
CC: (none) => sysadmin-bugs
Keywords: (none) => validated_update

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2022-0146.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED