Re: ARM board lockups/hangs triggered by locks and mutexes

2024-05-25 Thread Rafał Miłecki
On 18.08.2023 22:23, Rafał Miłecki wrote: On 14.08.2023 11:04, Geert Uytterhoeven wrote: Hi Rafal, On Mon, Aug 7, 2023 at 1:11 PM Rafał Miłecki wrote: On 4.08.2023 13:07, Rafał Miłecki wrote: I triple checked that. Dropping a single unused function breaks kernel / device stability on

Re: ARM board lockups/hangs triggered by locks and mutexes

2024-05-25 Thread Rafał Miłecki
On 14.08.2023 11:04, Geert Uytterhoeven wrote: Hi Rafal, On Mon, Aug 7, 2023 at 1:11 PM Rafał Miłecki wrote: On 4.08.2023 13:07, Rafał Miłecki wrote: I triple checked that. Dropping a single unused function breaks kernel / device stability on BCM53573! AFAIK the only thing below diff

Re: ARM board lockups/hangs triggered by locks and mutexes

2024-05-25 Thread Rafał Miłecki
On 7.08.2023 20:34, Florian Fainelli wrote: On 8/7/23 04:10, Rafał Miłecki wrote: On 4.08.2023 13:07, Rafał Miłecki wrote: I triple checked that. Dropping a single unused function breaks kernel / device stability on BCM53573! AFAIK the only thing below diff actually affects is location of

Re: ARM board lockups/hangs triggered by locks and mutexes

2024-05-25 Thread Rafał Miłecki
On 4.08.2023 13:07, Rafał Miłecki wrote: I triple checked that. Dropping a single unused function breaks kernel / device stability on BCM53573! AFAIK the only thing below diff actually affects is location of symbols (I actually verified that by comparing System.map before and after - over

Re: ARM board lockups/hangs triggered by locks and mutexes

2024-05-25 Thread Rafał Miłecki
On 2.08.2023 00:10, Rafał Miłecki wrote: Unfortunately enabling *any* of following options: CONFIG_DEBUG_RT_MUTEXES=y CONFIG_DEBUG_SPINLOCK=y CONFIG_DEBUG_MUTEXES=y seems to make locksup/hangs go away. I tried for few hours. I decided to find out why enabling CONFIG_DEBUG_MUTEXES "fixes"

Re: ARM board lockups/hangs triggered by locks and mutexes

2024-05-25 Thread Rafał Miłecki
On 2.08.2023 00:10, Rafał Miłecki wrote: Reverting that extra commit from v5.4.238 allows me to run Linux for hours again (currently 3 devices x 6 hours and counting). So I need in total 10+1 reverts from 5.4 branch to get a stable kernel. I switched back to OpenWrt's kernel 5.4 and applied

ARM board lockups/hangs triggered by locks and mutexes

2024-05-25 Thread Rafał Miłecki
Hi, Years ago I added support for Broadcom's BCM53573 SoCs. We released firmwares based on Linux 4.4 (and later on 4.14) that worked almost fine. There was one little issue we couldn't debug or fix: random hangs and reboots. They were too rare to deal with (most devices worked fine for weeks or

Re: ARM board lockups/hangs triggered by locks and mutexes

2024-05-25 Thread Rafał Miłecki
On 2.08.2023 00:21, Russell King (Oracle) wrote: On Wed, Aug 02, 2023 at 12:10:24AM +0200, Rafał Miłecki wrote: Years ago I added support for Broadcom's BCM53573 SoCs. We released firmwares based on Linux 4.4 (and later on 4.14) that worked almost fine. There was one little issue we couldn't

Re: ARM board lockups/hangs triggered by locks and mutexes

2024-05-25 Thread Rafał Miłecki
On 2.08.2023 00:25, Florian Fainelli wrote: Hi Rafal, On 8/1/23 15:10, Rafał Miłecki wrote: Hi, Years ago I added support for Broadcom's BCM53573 SoCs. We released firmwares based on Linux 4.4 (and later on 4.14) that worked almost fine. There was one little issue we couldn't debug or fix:

Re: ARM board lockups/hangs triggered by locks and mutexes

2024-05-25 Thread Rafał Miłecki
On 2.08.2023 09:00, Rafał Miłecki wrote: With your comment I decided to try CONFIG_PROVE_LOCKING anyway / again and this time on 1 of my BCM53573 devices I got something very interesting on the first boot. FWIW following error: Broadcom B53 (2) bcma_mdio-0-0:1e: failed to register switch: -517

Re: ARM board lockups/hangs triggered by locks and mutexes

2024-05-25 Thread Geert Uytterhoeven
Hi Rafal, On Mon, Aug 7, 2023 at 1:11 PM Rafał Miłecki wrote: > On 4.08.2023 13:07, Rafał Miłecki wrote: > > I triple checked that. Dropping a single unused function breaks kernel / > > device stability on BCM53573! > > > > AFAIK the only thing below diff actually affects is location of symbols