From mboxrd@z Thu Jan 1 00:00:00 1970 From: mans@mansr.com (=?iso-8859-1?Q?M=E5ns_Rullg=E5rd?=) Date: Mon, 31 Jul 2017 12:59:03 +0100 Subject: [RFC PATCH v1] net: ethernet: nb8800: Reset HW block in ndo_open In-Reply-To: (Mason's message of "Mon, 31 Jul 2017 13:49:45 +0200") References: <823b1540-b528-bbd7-7f99-5dc39a08868a@sigmadesigns.com> <446e3a95-80c3-0742-9cb1-69a8dfc9b1ae@free.fr> <4ff343de-41c7-c309-04dc-983b5fe3e066@gmail.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Mason writes: > On 29/07/2017 17:18, Florian Fainelli wrote: > >> On 07/29/2017 05:02 AM, Mason wrote: >> >>> I have identified a 100% reproducible flaw. >>> I have proposed a work-around that brings this down to 0 >>> (tested 1000 cycles of link up / ping / link down). >> >> Can you also try to get help from your HW resources to eventually help >> you find out what is going on here? > > The patch I proposed /is/ based on the feedback from the HW team :-( > "Just reset the HW block, and everything will work as expected." Nobody is saying a reset won't recover the lockup. The problem is that we don't know what caused it to lock up in the first place. How do we know it can't happen during normal operation? If we knew the cause, it might also be possible to avoid the situation entirely. -- M?ns Rullg?rd