Closed bkallyat closed 7 months ago
This looks like some upstream iwlwifi issue. By searching the string Microcode SW error detected. Restarting 0x0.
this problem seems to happen also on other operating systems at times. What some people suggest is to set iwlwifi options, specifically 11n_disable=1
and bt_coex_active=0
. You can set such options by editing cmdline.txt
on the boot partition (/mnt/boot
). Currently you have to edit this file directly on the OS shell (which you can access by using login
on the terminal).
Thanks. Will set those options and update if this workaround works.
Didn't work. Crashed in few hours.
Any other ideas anyone have to resolve this? This crash is basically making my Home Assistant setup useless. All my automation is dead 😖
@agners Can the HAOS be updated to include the new Intel Wifi firmwares? It may possibly resolve this bug. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Describe the issue you are experiencing
Hi, The HAOS crashes with error message saying "microcode SW error detected, Restarting 0x0." However, the system does not reboot and is stuck. The HA is currently running on AMD Mini PC. When the system is unreachable, I would connect this miniPC to a monitor to check the state. I would see a lot of iwlwifi errors post that microcode SW error. Have uploaded a pic of the error.
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
Home Assistant OS 10.5
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | October 6, 2023 at 11:00 AM relayer_connected | true relayer_region | ap-southeast-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | true remote_server | ap-southeast-1-0.ui.nabu.casa certificate_status | ready can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 10.5 -- | -- update_channel | stable supervisor_version | supervisor-2023.09.2 agent_version | 1.5.1 docker_version | 23.0.6 disk_total | 1833.1 GB disk_used | 9.5 GB healthy | true supported | true board | generic-x86-64 supervisor_api | ok version_api | ok installed_addons | Studio Code Server (5.11.0), Home Assistant Google Drive Backup (0.111.1), Matter Server (4.9.0), Silicon Labs Multiprotocol (2.3.2), Advanced SSH & Web Terminal (15.0.8)Dashboards
dashboards | 1 -- | -- resources | 0 views | 1 mode | storageRecorder
oldest_recorder_run | September 20, 2023 at 5:33 PM -- | -- current_recorder_run | October 1, 2023 at 10:52 PM estimated_db_size | 13.94 MiB database_engine | sqlite database_version | 3.41.2Spotify
api_endpoint_reachable | ok -- | --Additional information