lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue,  5 Oct 2021 14:26:51 +0000 (UTC)
From:   Kalle Valo <>
To:     Stephen Boyd <>
        Youghandhar Chintala <>,
        Abhishek Kumar <>,
        Steev Klimaszewski <>,
        Matthias Kaehlcke <>,
        Rakesh Pillai <>
Subject: Re: [PATCH v3] ath10k: Don't always treat modem stop events as

Stephen Boyd <> wrote:

> When rebooting on sc7180 Trogdor devices I see the following crash from
> the wifi driver.
>  ath10k_snoc 18800000.wifi: firmware crashed! (guid 83493570-29a2-4e98-a83e-70048c47669c)
> This is because a modem stop event looks just like a firmware crash to
> the driver, the qmi connection is closed in both cases. Use the qcom ssr
> notifier block to stop treating the qmi connection close event as a
> firmware crash signal when the modem hasn't actually crashed. See
> ath10k_qmi_event_server_exit() for more details.
> This silences the crash message seen during every reboot.
> Fixes: 3f14b73c3843 ("ath10k: Enable MSA region dump support for WCN3990")
> Cc: Youghandhar Chintala <>
> Cc: Abhishek Kumar <>
> Cc: Steev Klimaszewski <>
> Cc: Matthias Kaehlcke <>
> Cc: Rakesh Pillai <>
> Signed-off-by: Stephen Boyd <>
> Reviewed-by: Rakesh Pillai <>
> Tested-By: Youghandhar Chintala <>
> Signed-off-by: Kalle Valo <>

Patch applied to ath-next branch of ath.git, thanks.

747ff7d3d742 ath10k: Don't always treat modem stop events as crashes


Powered by blists - more mailing lists