iwd 2.19 segfault?

iwd 2.19 segfault?

[Mogens Jensen]

Hi,

I'm using iwd 2.19 on kernel 6.6.40. Yesterday, after booting the
system, no wlan interface was found. I have never experienced this
situation before, system had not been updated recently and no recent
configuration changes.

Following was found in kernel message buffer:

[   13.585766] wlan0: send auth to 00:16:3e:21:cf:ab (try 1/3)
[   13.585997] traps: iwd[2446] general protection fault ip:55c8166f5107 sp:7ffde5888d90 error:0 in iwd[55c8166c8000+ea000]
[   13.613989] wlan0: aborting authentication with 00:16:3e:21:cf:ab by local choice (Reason: 3=DEAUTH_LEAVING)

Rebooting system and wlan interface was missing again. This time
the message was different:

[   11.623212] wlan0: send auth to 00:16:3e:21:cf:ab (try 1/3)
[   11.623519] iwd[2443]: segfault at 1411 ip 0000000000001411 sp 00007ffc64376348 error 14 in iwd[55e26592f000+3000] likely on CPU 2 (core 2, socket 0)
[   11.623558] Code: Unable to access opcode bytes at 0x13e7.
[   11.657372] wlan0: aborting authentication with 00:16:3e:21:cf:ab by local choice (Reason: 3=DEAUTH_LEAVING)

Rebooting system again and problem still persists:

[   11.981208] wlan0: send auth to 00:16:3e:21:cf:ab (try 1/3)
[   11.981515] traps: iwd[2442] general protection fault ip:558bac8fe107 sp:7ffdab42aca0 error:0 in iwd[558bac8d1000+ea000]
[   11.997438] wlan0: aborting authentication with 00:16:3e:21:cf:ab by local choice (Reason: 3=DEAUTH_LEAVING)

After a third reboot, the wlan interface was available again and
everything works as normal. I have rebooted many times since, but the
problem has not occured again.

Any ideas on why this occured out of nowhere? Have you seen something
like this before?

Thanks in advance.


Regards,
Mogens Jensen

Re: iwd 2.19 segfault?

[James Prestwood]

Hi Mogens,

On 7/19/24 10:45 PM, Mogens Jensen wrote:
> Hi,
>
> I'm using iwd 2.19 on kernel 6.6.40. Yesterday, after booting the
> system, no wlan interface was found. I have never experienced this
> situation before, system had not been updated recently and no recent
> configuration changes.
>
> Following was found in kernel message buffer:
>
> [   13.585766] wlan0: send auth to 00:16:3e:21:cf:ab (try 1/3)
> [   13.585997] traps: iwd[2446] general protection fault ip:55c8166f5107 sp:7ffde5888d90 error:0 in iwd[55c8166c8000+ea000]
> [   13.613989] wlan0: aborting authentication with 00:16:3e:21:cf:ab by local choice (Reason: 3=DEAUTH_LEAVING)
>
> Rebooting system and wlan interface was missing again. This time
> the message was different:
>
> [   11.623212] wlan0: send auth to 00:16:3e:21:cf:ab (try 1/3)
> [   11.623519] iwd[2443]: segfault at 1411 ip 0000000000001411 sp 00007ffc64376348 error 14 in iwd[55e26592f000+3000] likely on CPU 2 (core 2, socket 0)
> [   11.623558] Code: Unable to access opcode bytes at 0x13e7.
> [   11.657372] wlan0: aborting authentication with 00:16:3e:21:cf:ab by local choice (Reason: 3=DEAUTH_LEAVING)
>
> Rebooting system again and problem still persists:
>
> [   11.981208] wlan0: send auth to 00:16:3e:21:cf:ab (try 1/3)
> [   11.981515] traps: iwd[2442] general protection fault ip:558bac8fe107 sp:7ffdab42aca0 error:0 in iwd[558bac8d1000+ea000]
> [   11.997438] wlan0: aborting authentication with 00:16:3e:21:cf:ab by local choice (Reason: 3=DEAUTH_LEAVING)
>
> After a third reboot, the wlan interface was available again and
> everything works as normal. I have rebooted many times since, but the
> problem has not occured again.
>
> Any ideas on why this occured out of nowhere? Have you seen something
> like this before?

This really isn't much to go on. Are there any IWD logs? A stack trace? 
Core dump? etc.

Thanks,

James

>
> Thanks in advance.
>
>
> Regards,
> Mogens Jensen
>

Re: iwd 2.19 segfault?

[Mogens Jensen]

On Mon, Jul 22, 2024, at 11:25, James Prestwood wrote:
> Hi Mogens,
>
> This really isn't much to go on. Are there any IWD logs? A stack trace? 
> Core dump? etc.
>
> Thanks,
>
> James

Hi James,

Unfortunately not and the error has not occured since, which I find quite strange. That is also why I started this thread, to find out if anyone else have ever seen something like this.

However, I now run iwd with debugging enabled and that will hopefully reveal some more information, if the error occurs again.

Regards,
Mogens Jensen