On Fri, Feb 01, 2019 at 12:01:19PM +0100, Miquel Raynal wrote:

Hi Vivien,

Vivien Didelot [off-list ref] wrote on Wed, 30 Jan 2019
19:46:08 -0500:

quoted

Hi Miquèl,

On Wed, 30 Jan 2019 10:46:06 +0100, Miquel Raynal [off-list ref] wrote:

quoted

quoted

quoted

quoted

Today, there is no S2RAM support for switches. First, I proposed to add
suspend/resume callbacks to the mv88e6xxx driver - just enough to avoid
crashing the kernel.    

Then i would suggest the mv88e6xxx refuses the suspend. Actually that
probably is the first correct step. We don't have suspend support, so
stop the suspend happening, so preventing the kernel crash.    

Actually can you show me the crash that is happening?

Sure, here it is: http://code.bulix.org/swwb11-569137

Actually it is a silent crash but the platform never resumes. I am
pretty sure this is due to the kthread_queue_delayed_work() loop which
might access registers before it is allowed to do so.

Hi Miquel

That sounds like it is an MDIO driver problem, or at least, a resume
ordering problem. You need to ensure that the MDIO bus driver is
resumed before the switch driver. Also, that the switch is suspended
before the MDIO bus driver is suspended.

       Andrew