[Kernel-packages] [Bug 1945289] Re: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver.
** Description changed: On 5.11.0 everything is OK. The GPU is AMD Carrizo APU. UPD: I have checked several kernels for presence of this bug Ubuntu: linux-image-5.13.0-35-generic/now 5.13.0-35.40~20.04.1 amd64 [installed,local] - BROKEN linux-image-5.14.0-1055-oem/now 5.14.0-1055.62 amd64 [installed,local] - OK linux-image-5.15.0-57-generic/now 5.15.0-57.63 amd64 [installed,local] - OK linux-image-5.17.0-1003-oem/now 5.17.0-1003.3 amd64 [installed,local] - OK linux-image-5.19.0-21-generic/now 5.19.0-21.21 amd64 [installed,local] - OK - Debian: linux-image-5.10.0-20-amd64/stable,now 5.10.158-2 amd64 [installed] - probably OK, haven't checked linux-image-5.18.0-0.deb11.4-amd64/bullseye-backports,now 5.18.16-1~bpo11+1 amd64 [installed] - OK linux-image-5.19.0-0.deb11.2-amd64/bullseye-backports,now 5.19.11-1~bpo11+1 amd64 [installed] - OK linux-image-6.0.0-6-amd64/testing,now 6.0.12-1 amd64 [installed] - OK + + Other people reports in this thread: + + + korta (Carrizo) + 5.13.0-21-generic - BROKEN + + Paweł Szmergała (Lucienne) + 5.13.0-27-generic - OK + 5.13.0-28-generic - BROKEN + 5.13.0-30-generic - BROKEN + 5.13.0-35-generic - BROKEN ** Tags added: lucienne ** Tags added: s3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1945289 Title: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver. Status in linux-meta package in Ubuntu: Fix Released Bug description: On 5.11.0 everything is OK. The GPU is AMD Carrizo APU. UPD: I have checked several kernels for presence of this bug Ubuntu: linux-image-5.13.0-35-generic/now 5.13.0-35.40~20.04.1 amd64 [installed,local] - BROKEN linux-image-5.14.0-1055-oem/now 5.14.0-1055.62 amd64 [installed,local] - OK linux-image-5.15.0-57-generic/now 5.15.0-57.63 amd64 [installed,local] - OK linux-image-5.17.0-1003-oem/now 5.17.0-1003.3 amd64 [installed,local] - OK linux-image-5.19.0-21-generic/now 5.19.0-21.21 amd64 [installed,local] - OK Debian: linux-image-5.10.0-20-amd64/stable,now 5.10.158-2 amd64 [installed] - probably OK, haven't checked linux-image-5.18.0-0.deb11.4-amd64/bullseye-backports,now 5.18.16-1~bpo11+1 amd64 [installed] - OK linux-image-5.19.0-0.deb11.2-amd64/bullseye-backports,now 5.19.11-1~bpo11+1 amd64 [installed] - OK linux-image-6.0.0-6-amd64/testing,now 6.0.12-1 amd64 [installed] - OK Other people reports in this thread: korta (Carrizo) 5.13.0-21-generic - BROKEN Paweł Szmergała (Lucienne) 5.13.0-27-generic - OK 5.13.0-28-generic - BROKEN 5.13.0-30-generic - BROKEN 5.13.0-35-generic - BROKEN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1945289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945289] Re: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver.
** Changed in: linux-meta (Ubuntu) Status: Confirmed => Fix Released ** Description changed: On 5.11.0 everything is OK. The GPU is AMD Carrizo APU. + + UPD: I have checked several kernels for presence of this bug + + Ubuntu: + linux-image-5.13.0-35-generic/now 5.13.0-35.40~20.04.1 amd64 [installed,local] - BROKEN + linux-image-5.14.0-1055-oem/now 5.14.0-1055.62 amd64 [installed,local] - OK + linux-image-5.15.0-57-generic/now 5.15.0-57.63 amd64 [installed,local] - OK + linux-image-5.17.0-1003-oem/now 5.17.0-1003.3 amd64 [installed,local] - OK + linux-image-5.19.0-21-generic/now 5.19.0-21.21 amd64 [installed,local] - OK + + + Debian: + linux-image-5.10.0-20-amd64/stable,now 5.10.158-2 amd64 [installed] - probably OK, haven't checked + linux-image-5.18.0-0.deb11.4-amd64/bullseye-backports,now 5.18.16-1~bpo11+1 amd64 [installed] - OK + linux-image-5.19.0-0.deb11.2-amd64/bullseye-backports,now 5.19.11-1~bpo11+1 amd64 [installed] - OK + linux-image-6.0.0-6-amd64/testing,now 6.0.12-1 amd64 [installed] - OK -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1945289 Title: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver. Status in linux-meta package in Ubuntu: Fix Released Bug description: On 5.11.0 everything is OK. The GPU is AMD Carrizo APU. UPD: I have checked several kernels for presence of this bug Ubuntu: linux-image-5.13.0-35-generic/now 5.13.0-35.40~20.04.1 amd64 [installed,local] - BROKEN linux-image-5.14.0-1055-oem/now 5.14.0-1055.62 amd64 [installed,local] - OK linux-image-5.15.0-57-generic/now 5.15.0-57.63 amd64 [installed,local] - OK linux-image-5.17.0-1003-oem/now 5.17.0-1003.3 amd64 [installed,local] - OK linux-image-5.19.0-21-generic/now 5.19.0-21.21 amd64 [installed,local] - OK Debian: linux-image-5.10.0-20-amd64/stable,now 5.10.158-2 amd64 [installed] - probably OK, haven't checked linux-image-5.18.0-0.deb11.4-amd64/bullseye-backports,now 5.18.16-1~bpo11+1 amd64 [installed] - OK linux-image-5.19.0-0.deb11.2-amd64/bullseye-backports,now 5.19.11-1~bpo11+1 amd64 [installed] - OK linux-image-6.0.0-6-amd64/testing,now 6.0.12-1 amd64 [installed] - OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1945289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945289] Re: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver.
On Debian unstable and testing, kernel version 6.0, resuming works fine on the same hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1945289 Title: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver. Status in linux-meta package in Ubuntu: Confirmed Bug description: On 5.11.0 everything is OK. The GPU is AMD Carrizo APU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1945289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956165] [NEW] Mere presence of WLAN_AKM_SUITE_PSK_SHA256 cipher suite disrupts connection
Public bug reported: I have tried to port support from brcm80211, but haven't succeed. Here is my draft. It is based on https://github.com/torvalds/linux/blob/fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c and https://github.com/torvalds/linux/blob/5bfc75d92efd494db37f5c4c173d3639d4772966/drivers/net/wireless/broadcom/brcm80211/include/brcmu_wifi.h It is likely that some code additions in other places are needed, but since I haven't found the analogous places, I guess they can be within chip firmware. ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Patch added: "it does not work" https://bugs.launchpad.net/bugs/1956165/+attachment/5550592/+files/0003-Trying-to-implement-cyphersuites-support.-Not-working.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1956165 Title: Mere presence of WLAN_AKM_SUITE_PSK_SHA256 cipher suite disrupts connection Status in bcmwl package in Ubuntu: New Bug description: I have tried to port support from brcm80211, but haven't succeed. Here is my draft. It is based on https://github.com/torvalds/linux/blob/fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c and https://github.com/torvalds/linux/blob/5bfc75d92efd494db37f5c4c173d3639d4772966/drivers/net/wireless/broadcom/brcm80211/include/brcmu_wifi.h It is likely that some code additions in other places are needed, but since I haven't found the analogous places, I guess they can be within chip firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1956165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956162] Re: Logic errors in error-reporting code cause a highly misleading message to be emitted: ERROR @wl_set_key_mgmt : invalid cipher group (1027076)
** Description changed:
>Problem: error `ERROR @wl_set_key_mgmt : invalid cipher group
(1027076)`
- Logic errors in error-reporting code cause a highly misleading message
- to be emitted. The problem is not within cipher group (that is supported
- WLAN_CIPHER_SUITE_CCMP).
+ 1. Logic errors in error-reporting code cause a highly misleading
+ message to be emitted. The problem is not within cipher group (that is
+ supported WLAN_CIPHER_SUITE_CCMP).
```patch
- WL_ERR(("invalid cipher group (%d)\n",
sme->crypto.cipher_group));
+ WL_ERR(("invalid akm suite (%d)\n",
sme->crypto.akm_suites[0]));
```
+
+ 2. Once we fix the error-reporting logic we get the correct error
+ message:
+
+ > ERROR @wl_set_key_mgmt : invalid akm suite (1027078)
+
+ It is because that case (WLAN_AKM_SUITE_PSK_SHA256) is not processed.
+ Even the mere presence of it in announced cipher suites is enough to
+ break wifi. Not only for this driver, but also for drivers for Windows.
+
+ I have ported processing of the cases from the open-source driver, but
+ it still doesn't work and causes errors in kernel. Likely it requires
+ some code in other places, maybe even in firmware.
+
+ `wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256` in `hostapd` config (currently it
+ is defaults on OpenWRT).
+
+ The OpenWRT wiki is incorrect, in `/etc/config/wireless` `ieee80211w=1`
+ is the default, which causes `wpa_key_mgmt` be generated so.
+
+ `wpa_key_mgmt=WPA-PSK SAE` in `hostapd` config works fine (if these
+ shitty crashing drivers can be called working fine).
+
+ To make it so, explicitly set `ieee80211w=0` in `/etc/config/wireless`.
+
+ So the second patch just gives the explanination to the user what
+ happens and the instructions on what to fix in his router configuration
+ as a workaround.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1956162
Title:
Logic errors in error-reporting code cause a highly misleading message
to be emitted: ERROR @wl_set_key_mgmt : invalid cipher group (1027076)
Status in bcmwl package in Ubuntu:
New
Bug description:
>Problem: error `ERROR @wl_set_key_mgmt : invalid cipher group
(1027076)`
1. Logic errors in error-reporting code cause a highly misleading
message to be emitted. The problem is not within cipher group (that is
supported WLAN_CIPHER_SUITE_CCMP).
```patch
- WL_ERR(("invalid cipher group (%d)\n",
sme->crypto.cipher_group));
+ WL_ERR(("invalid akm suite (%d)\n",
sme->crypto.akm_suites[0]));
```
2. Once we fix the error-reporting logic we get the correct error
message:
> ERROR @wl_set_key_mgmt : invalid akm suite (1027078)
It is because that case (WLAN_AKM_SUITE_PSK_SHA256) is not processed.
Even the mere presence of it in announced cipher suites is enough to
break wifi. Not only for this driver, but also for drivers for
Windows.
I have ported processing of the cases from the open-source driver, but
it still doesn't work and causes errors in kernel. Likely it requires
some code in other places, maybe even in firmware.
`wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256` in `hostapd` config (currently
it is defaults on OpenWRT).
The OpenWRT wiki is incorrect, in `/etc/config/wireless`
`ieee80211w=1` is the default, which causes `wpa_key_mgmt` be
generated so.
`wpa_key_mgmt=WPA-PSK SAE` in `hostapd` config works fine (if these
shitty crashing drivers can be called working fine).
To make it so, explicitly set `ieee80211w=0` in
`/etc/config/wireless`.
So the second patch just gives the explanination to the user what
happens and the instructions on what to fix in his router
configuration as a workaround.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1956162/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956162] Re: Logic errors in error-reporting code cause a highly misleading message to be emitted: ERROR @wl_set_key_mgmt : invalid cipher group (1027076)
** Patch added:
"0002-A-bit-more-useful-error-message-for-the-case-of-PSK-SHA256.patch"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1956162/+attachment/5550591/+files/0002-A-bit-more-useful-error-message-for-the-case-of-PSK-SHA256.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1956162
Title:
Logic errors in error-reporting code cause a highly misleading message
to be emitted: ERROR @wl_set_key_mgmt : invalid cipher group (1027076)
Status in bcmwl package in Ubuntu:
New
Bug description:
>Problem: error `ERROR @wl_set_key_mgmt : invalid cipher group
(1027076)`
1. Logic errors in error-reporting code cause a highly misleading
message to be emitted. The problem is not within cipher group (that is
supported WLAN_CIPHER_SUITE_CCMP).
```patch
- WL_ERR(("invalid cipher group (%d)\n",
sme->crypto.cipher_group));
+ WL_ERR(("invalid akm suite (%d)\n",
sme->crypto.akm_suites[0]));
```
2. Once we fix the error-reporting logic we get the correct error
message:
> ERROR @wl_set_key_mgmt : invalid akm suite (1027078)
It is because that case (WLAN_AKM_SUITE_PSK_SHA256) is not processed.
Even the mere presence of it in announced cipher suites is enough to
break wifi. Not only for this driver, but also for drivers for
Windows.
I have ported processing of the cases from the open-source driver, but
it still doesn't work and causes errors in kernel. Likely it requires
some code in other places, maybe even in firmware.
`wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256` in `hostapd` config (currently
it is defaults on OpenWRT).
The OpenWRT wiki is incorrect, in `/etc/config/wireless`
`ieee80211w=1` is the default, which causes `wpa_key_mgmt` be
generated so.
`wpa_key_mgmt=WPA-PSK SAE` in `hostapd` config works fine (if these
shitty crashing drivers can be called working fine).
To make it so, explicitly set `ieee80211w=0` in
`/etc/config/wireless`.
So the second patch just gives the explanination to the user what
happens and the instructions on what to fix in his router
configuration as a workaround.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1956162/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956162] [NEW] Logic errors in error-reporting code cause a highly misleading message to be emitted: ERROR @wl_set_key_mgmt : invalid cipher group (1027076)
Public bug reported:
>Problem: error `ERROR @wl_set_key_mgmt : invalid cipher group
(1027076)`
1. Logic errors in error-reporting code cause a highly misleading
message to be emitted. The problem is not within cipher group (that is
supported WLAN_CIPHER_SUITE_CCMP).
```patch
- WL_ERR(("invalid cipher group (%d)\n",
sme->crypto.cipher_group));
+ WL_ERR(("invalid akm suite (%d)\n",
sme->crypto.akm_suites[0]));
```
2. Once we fix the error-reporting logic we get the correct error
message:
> ERROR @wl_set_key_mgmt : invalid akm suite (1027078)
It is because that case (WLAN_AKM_SUITE_PSK_SHA256) is not processed.
Even the mere presence of it in announced cipher suites is enough to
break wifi. Not only for this driver, but also for drivers for Windows.
I have ported processing of the cases from the open-source driver, but
it still doesn't work and causes errors in kernel. Likely it requires
some code in other places, maybe even in firmware.
`wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256` in `hostapd` config (currently it
is defaults on OpenWRT).
The OpenWRT wiki is incorrect, in `/etc/config/wireless` `ieee80211w=1`
is the default, which causes `wpa_key_mgmt` be generated so.
`wpa_key_mgmt=WPA-PSK SAE` in `hostapd` config works fine (if these
shitty crashing drivers can be called working fine).
To make it so, explicitly set `ieee80211w=0` in `/etc/config/wireless`.
So the second patch just gives the explanination to the user what
happens and the instructions on what to fix in his router configuration
as a workaround.
** Affects: bcmwl (Ubuntu)
Importance: Undecided
Status: New
** Patch added:
"0001-Fixed-error-reporting-ported-from-the-recent-version.patch"
https://bugs.launchpad.net/bugs/1956162/+attachment/5550587/+files/0001-Fixed-error-reporting-ported-from-the-recent-version.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1956162
Title:
Logic errors in error-reporting code cause a highly misleading message
to be emitted: ERROR @wl_set_key_mgmt : invalid cipher group (1027076)
Status in bcmwl package in Ubuntu:
New
Bug description:
>Problem: error `ERROR @wl_set_key_mgmt : invalid cipher group
(1027076)`
1. Logic errors in error-reporting code cause a highly misleading
message to be emitted. The problem is not within cipher group (that is
supported WLAN_CIPHER_SUITE_CCMP).
```patch
- WL_ERR(("invalid cipher group (%d)\n",
sme->crypto.cipher_group));
+ WL_ERR(("invalid akm suite (%d)\n",
sme->crypto.akm_suites[0]));
```
2. Once we fix the error-reporting logic we get the correct error
message:
> ERROR @wl_set_key_mgmt : invalid akm suite (1027078)
It is because that case (WLAN_AKM_SUITE_PSK_SHA256) is not processed.
Even the mere presence of it in announced cipher suites is enough to
break wifi. Not only for this driver, but also for drivers for
Windows.
I have ported processing of the cases from the open-source driver, but
it still doesn't work and causes errors in kernel. Likely it requires
some code in other places, maybe even in firmware.
`wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256` in `hostapd` config (currently
it is defaults on OpenWRT).
The OpenWRT wiki is incorrect, in `/etc/config/wireless`
`ieee80211w=1` is the default, which causes `wpa_key_mgmt` be
generated so.
`wpa_key_mgmt=WPA-PSK SAE` in `hostapd` config works fine (if these
shitty crashing drivers can be called working fine).
To make it so, explicitly set `ieee80211w=0` in
`/etc/config/wireless`.
So the second patch just gives the explanination to the user what
happens and the instructions on what to fix in his router
configuration as a workaround.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1956162/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945289] [NEW] Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver.
Public bug reported: On 5.11.0 everything is OK. The GPU is AMD Carrizo APU. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: 5.13.0 amdgpu carrizo impish ** Summary changed: - Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16, amdgpu driver. + Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver. ** Tags added: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1945289 Title: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver. Status in linux-meta package in Ubuntu: New Bug description: On 5.11.0 everything is OK. The GPU is AMD Carrizo APU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1945289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
