* SIGSEGV on IWD 3.2
@ 2025-01-22 23:59 Bryce Johnson
2025-01-23 14:32 ` James Prestwood
0 siblings, 1 reply; 2+ messages in thread
From: Bryce Johnson @ 2025-01-22 23:59 UTC (permalink / raw)
To: iwd
Hi All,
Long shot here,
I was debugging a logs of a device from an SQA person that had
repeated IWD SIGSEGV and restarting probably after wifi driver went
out to lunch. Somewhat limited logs since I didn't get to it right
away and stuff started to roll over.
Also interesting, did not even have any wifi in use either in station
or AP (Nothing had been provisioned). This device had previously been
used for some wifi a week or 2 before, but all networks were cleared
out and device restarted.
We use s6-rc as our service manager. If a process (such as IWD) dies
it will repeatedly try and restart it.
Had what looked like wifi driver having issues - probably the start of
the whole issue.
[43459.804541] wfx-spi spi0.0: timeout while wake up chip
[43459.816453] wfx-spi spi0.0: timeout while wake up chip
[43459.830393] wfx-spi spi0.0: timeout while wake up chip
[43459.842357] wfx-spi spi0.0: max wake-up retries reached
[43460.803924] wfx-spi spi0.0: chip is abnormally long to answer
[43463.873992] wfx-spi spi0.0: chip did not answer
[43463.878627] wfx-spi spi0.0: hardware request
WRITE_MIB/TEMPLATE_FRAME (0x06) on vif 0 returned error -110
In some s6-rc logs, we have when it was restarted (continues on with
this and lost some info to rollover)
2025-01-21 07:12:08.808001808 signal SIGSEGV
2025-01-21 07:12:09.770742290 signal SIGSEGV
2025-01-21 07:12:10.806240896 signal SIGSEGV
2025-01-21 07:12:11.786297623 signal SIGSEGV
2025-01-21 07:12:12.760070244 signal SIGSEGV
2025-01-21 07:12:13.758235878 signal SIGSEGV
*** (Snip - repeated logs) ***
For IWD logs I have repeated restarts like this snipped log, but I
don't see an error. (I have the restarts from the same times as above
as well)
2025-01-21 02:21:25.344554377 Ciphers: BIP-CMAC-256 BIP-GMAC-256
BIP-GMAC-128 CCMP-256
2025-01-21 02:21:25.345014705 GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128
2025-01-21 02:21:25.347048046 TKIP
2025-01-21 02:21:25.347306057 Supported iftypes: ad-hoc station ap
2025-01-21 02:21:25.347473009 Wiphy phy0 will only use the default interface
2025-01-21 02:21:25.349009450 event: state, old: disconnected, new:
autoconnect_quick
2025-01-21 02:21:26.139899373 Wireless daemon version 3.2
2025-01-21 02:21:26.140155301 Loaded configuration from /etc/iwd/main.conf
2025-01-21 02:21:26.176308992 station: Network configuration is disabled.
2025-01-21 02:21:26.235244322 Wiphy: 0, Name: phy0
2025-01-21 02:21:26.239840939 Permanent Address: 70:54:64:3c:0e:be
2025-01-21 02:21:26.240499919 2.4GHz Band:
2025-01-21 02:21:26.241493513 Bitrates (non-HT):
2025-01-21 02:21:26.243046324 1.0 Mbps
2025-01-21 02:21:26.243289505 2.0 Mbps
2025-01-21 02:21:26.243446502 5.5 Mbps
2025-01-21 02:21:26.243590461 11.0 Mbps
2025-01-21 02:21:26.244386486 6.0 Mbps
2025-01-21 02:21:26.249855106 9.0 Mbps
2025-01-21 02:21:26.250142900 12.0 Mbps
2025-01-21 02:21:26.250309769 18.0 Mbps
2025-01-21 02:21:26.250451771 24.0 Mbps
2025-01-21 02:21:26.250588232 36.0 Mbps
2025-01-21 02:21:26.252128546 48.0 Mbps
2025-01-21 02:21:26.252323949 54.0 Mbps
2025-01-21 02:21:26.252475407 HT Capabilities:
2025-01-21 02:21:26.252615242 HT20
2025-01-21 02:21:26.252857840 Short GI for 20Mhz
2025-01-21 02:21:26.253010755 HT RX MCS indexes:
2025-01-21 02:21:26.253149883 0-7
2025-01-21 02:21:26.253285011 Ciphers: BIP-CMAC-256 BIP-GMAC-256
BIP-GMAC-128 CCMP-256
2025-01-21 02:21:26.253422847 GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128
2025-01-21 02:21:26.253550478 TKIP
2025-01-21 02:21:26.253761709 Supported iftypes: ad-hoc station ap
2025-01-21 02:21:26.253914166 Wiphy phy0 will only use the default interface
2025-01-21 02:21:26.288886191 event: state, old: disconnected, new:
autoconnect_quick
2025-01-21 02:21:27.138566070 Wireless daemon version 3.2
2025-01-21 02:21:27.143008147 Loaded configuration from /etc/iwd/main.conf
2025-01-21 02:21:27.175021883 station: Network configuration is disabled.
2025-01-21 02:21:27.237573107 Wiphy: 0, Name: phy0
2025-01-21 02:21:27.239996339 Permanent Address: 70:54:64:3c:0e:be
2025-01-21 02:21:27.241062954 2.4GHz Band:
2025-01-21 02:21:27.241968489 Bitrates (non-HT):
2025-01-21 02:21:27.242196175 1.0 Mbps
2025-01-21 02:21:27.245799489 2.0 Mbps
2025-01-21 02:21:27.246074536 5.5 Mbps
2025-01-21 02:21:27.246238990 11.0 Mbps
2025-01-21 02:21:27.246376451 6.0 Mbps
2025-01-21 02:21:27.246506539 9.0 Mbps
2025-01-21 02:21:27.246799664 12.0 Mbps
2025-01-21 02:21:27.246981113 18.0 Mbps
2025-01-21 02:21:27.247124406 24.0 Mbps
2025-01-21 02:21:27.247261409 36.0 Mbps
2025-01-21 02:21:27.247395204 48.0 Mbps
2025-01-21 02:21:27.249497818 54.0 Mbps
2025-01-21 02:21:27.249890707 HT Capabilities:
2025-01-21 02:21:27.250062117 HT20
2025-01-21 02:21:27.250200203 Short GI for 20Mhz
2025-01-21 02:21:27.250339205 HT RX MCS indexes:
2025-01-21 02:21:27.250470251 0-7
2025-01-21 02:21:27.250606671 Ciphers: BIP-CMAC-256 BIP-GMAC-256
BIP-GMAC-128 CCMP-256
2025-01-21 02:21:27.265473757 GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128
2025-01-21 02:21:27.266883150 TKIP
2025-01-21 02:21:27.267148201 Supported iftypes: ad-hoc station ap
2025-01-21 02:21:27.267466069 Wiphy phy0 will only use the default interface
2025-01-21 02:21:27.293290723 event: state, old: disconnected, new:
autoconnect_quick
*** (Snip - repeated logs) ***
Anything useful I could get out of this? I was thinking of enabling
iwd debug logs to hopefully have some more information if we can repo
this issue. Most likely it is on the driver side - we had been
fighting driver issues in the past...
Bryce
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: SIGSEGV on IWD 3.2
2025-01-22 23:59 SIGSEGV on IWD 3.2 Bryce Johnson
@ 2025-01-23 14:32 ` James Prestwood
0 siblings, 0 replies; 2+ messages in thread
From: James Prestwood @ 2025-01-23 14:32 UTC (permalink / raw)
To: Bryce Johnson, iwd
Hi Bryce,
On 1/22/25 3:59 PM, Bryce Johnson wrote:
> Hi All,
> Long shot here,
> I was debugging a logs of a device from an SQA person that had
> repeated IWD SIGSEGV and restarting probably after wifi driver went
> out to lunch. Somewhat limited logs since I didn't get to it right
> away and stuff started to roll over.
>
> Also interesting, did not even have any wifi in use either in station
> or AP (Nothing had been provisioned). This device had previously been
> used for some wifi a week or 2 before, but all networks were cleared
> out and device restarted.
>
> We use s6-rc as our service manager. If a process (such as IWD) dies
> it will repeatedly try and restart it.
>
> Had what looked like wifi driver having issues - probably the start of
> the whole issue.
> [43459.804541] wfx-spi spi0.0: timeout while wake up chip
> [43459.816453] wfx-spi spi0.0: timeout while wake up chip
> [43459.830393] wfx-spi spi0.0: timeout while wake up chip
> [43459.842357] wfx-spi spi0.0: max wake-up retries reached
> [43460.803924] wfx-spi spi0.0: chip is abnormally long to answer
> [43463.873992] wfx-spi spi0.0: chip did not answer
> [43463.878627] wfx-spi spi0.0: hardware request
> WRITE_MIB/TEMPLATE_FRAME (0x06) on vif 0 returned error -110
>
>
> In some s6-rc logs, we have when it was restarted (continues on with
> this and lost some info to rollover)
> 2025-01-21 07:12:08.808001808 signal SIGSEGV
> 2025-01-21 07:12:09.770742290 signal SIGSEGV
> 2025-01-21 07:12:10.806240896 signal SIGSEGV
> 2025-01-21 07:12:11.786297623 signal SIGSEGV
> 2025-01-21 07:12:12.760070244 signal SIGSEGV
> 2025-01-21 07:12:13.758235878 signal SIGSEGV
> *** (Snip - repeated logs) ***
>
> For IWD logs I have repeated restarts like this snipped log, but I
> don't see an error. (I have the restarts from the same times as above
> as well)
> 2025-01-21 02:21:25.344554377 Ciphers: BIP-CMAC-256 BIP-GMAC-256
> BIP-GMAC-128 CCMP-256
> 2025-01-21 02:21:25.345014705 GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128
> 2025-01-21 02:21:25.347048046 TKIP
> 2025-01-21 02:21:25.347306057 Supported iftypes: ad-hoc station ap
> 2025-01-21 02:21:25.347473009 Wiphy phy0 will only use the default interface
> 2025-01-21 02:21:25.349009450 event: state, old: disconnected, new:
> autoconnect_quick
> 2025-01-21 02:21:26.139899373 Wireless daemon version 3.2
> 2025-01-21 02:21:26.140155301 Loaded configuration from /etc/iwd/main.conf
> 2025-01-21 02:21:26.176308992 station: Network configuration is disabled.
> 2025-01-21 02:21:26.235244322 Wiphy: 0, Name: phy0
> 2025-01-21 02:21:26.239840939 Permanent Address: 70:54:64:3c:0e:be
> 2025-01-21 02:21:26.240499919 2.4GHz Band:
> 2025-01-21 02:21:26.241493513 Bitrates (non-HT):
> 2025-01-21 02:21:26.243046324 1.0 Mbps
> 2025-01-21 02:21:26.243289505 2.0 Mbps
> 2025-01-21 02:21:26.243446502 5.5 Mbps
> 2025-01-21 02:21:26.243590461 11.0 Mbps
> 2025-01-21 02:21:26.244386486 6.0 Mbps
> 2025-01-21 02:21:26.249855106 9.0 Mbps
> 2025-01-21 02:21:26.250142900 12.0 Mbps
> 2025-01-21 02:21:26.250309769 18.0 Mbps
> 2025-01-21 02:21:26.250451771 24.0 Mbps
> 2025-01-21 02:21:26.250588232 36.0 Mbps
> 2025-01-21 02:21:26.252128546 48.0 Mbps
> 2025-01-21 02:21:26.252323949 54.0 Mbps
> 2025-01-21 02:21:26.252475407 HT Capabilities:
> 2025-01-21 02:21:26.252615242 HT20
> 2025-01-21 02:21:26.252857840 Short GI for 20Mhz
> 2025-01-21 02:21:26.253010755 HT RX MCS indexes:
> 2025-01-21 02:21:26.253149883 0-7
> 2025-01-21 02:21:26.253285011 Ciphers: BIP-CMAC-256 BIP-GMAC-256
> BIP-GMAC-128 CCMP-256
> 2025-01-21 02:21:26.253422847 GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128
> 2025-01-21 02:21:26.253550478 TKIP
> 2025-01-21 02:21:26.253761709 Supported iftypes: ad-hoc station ap
> 2025-01-21 02:21:26.253914166 Wiphy phy0 will only use the default interface
> 2025-01-21 02:21:26.288886191 event: state, old: disconnected, new:
> autoconnect_quick
> 2025-01-21 02:21:27.138566070 Wireless daemon version 3.2
> 2025-01-21 02:21:27.143008147 Loaded configuration from /etc/iwd/main.conf
> 2025-01-21 02:21:27.175021883 station: Network configuration is disabled.
> 2025-01-21 02:21:27.237573107 Wiphy: 0, Name: phy0
> 2025-01-21 02:21:27.239996339 Permanent Address: 70:54:64:3c:0e:be
> 2025-01-21 02:21:27.241062954 2.4GHz Band:
> 2025-01-21 02:21:27.241968489 Bitrates (non-HT):
> 2025-01-21 02:21:27.242196175 1.0 Mbps
> 2025-01-21 02:21:27.245799489 2.0 Mbps
> 2025-01-21 02:21:27.246074536 5.5 Mbps
> 2025-01-21 02:21:27.246238990 11.0 Mbps
> 2025-01-21 02:21:27.246376451 6.0 Mbps
> 2025-01-21 02:21:27.246506539 9.0 Mbps
> 2025-01-21 02:21:27.246799664 12.0 Mbps
> 2025-01-21 02:21:27.246981113 18.0 Mbps
> 2025-01-21 02:21:27.247124406 24.0 Mbps
> 2025-01-21 02:21:27.247261409 36.0 Mbps
> 2025-01-21 02:21:27.247395204 48.0 Mbps
> 2025-01-21 02:21:27.249497818 54.0 Mbps
> 2025-01-21 02:21:27.249890707 HT Capabilities:
> 2025-01-21 02:21:27.250062117 HT20
> 2025-01-21 02:21:27.250200203 Short GI for 20Mhz
> 2025-01-21 02:21:27.250339205 HT RX MCS indexes:
> 2025-01-21 02:21:27.250470251 0-7
> 2025-01-21 02:21:27.250606671 Ciphers: BIP-CMAC-256 BIP-GMAC-256
> BIP-GMAC-128 CCMP-256
> 2025-01-21 02:21:27.265473757 GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128
> 2025-01-21 02:21:27.266883150 TKIP
> 2025-01-21 02:21:27.267148201 Supported iftypes: ad-hoc station ap
> 2025-01-21 02:21:27.267466069 Wiphy phy0 will only use the default interface
> 2025-01-21 02:21:27.293290723 event: state, old: disconnected, new:
> autoconnect_quick
> *** (Snip - repeated logs) ***
>
>
>
> Anything useful I could get out of this? I was thinking of enabling
> iwd debug logs to hopefully have some more information if we can repo
> this issue. Most likely it is on the driver side - we had been
> fighting driver issues in the past...
Yes debug logs will help. I agree it does seem like a weird driver issue
based on those wfx-spi logs, but regardless IWD shouldn't crash. If you
can get debug logs or better yet a stack trace with debug symbols that
would be great!
Thanks,
James
>
> Bryce
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-01-23 14:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-01-22 23:59 SIGSEGV on IWD 3.2 Bryce Johnson
2025-01-23 14:32 ` James Prestwood
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox