public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Mogens Jensen <mogj@fastmail.com>, iwd@lists.linux.dev
Subject: Re: iwd 2.19 segfault?
Date: Mon, 22 Jul 2024 04:25:34 -0700	[thread overview]
Message-ID: <d571910b-77c8-4e47-8741-01867c535398@gmail.com> (raw)
In-Reply-To: <3554030d-7309-459c-8e91-ee34a0fe677b@app.fastmail.com>

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
>

  reply	other threads:[~2024-07-22 11:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-20  5:45 iwd 2.19 segfault? Mogens Jensen
2024-07-22 11:25 ` James Prestwood [this message]
2024-08-09  2:21   ` Mogens Jensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d571910b-77c8-4e47-8741-01867c535398@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=mogj@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox