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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 13 Jan 2018 01:38:19 +0100
From:   "Rafael J. Wysocki" <>
To:     Geert Uytterhoeven <>
Cc:     Linux PM <>,
        Ulf Hansson <>,
        LKML <>,
        Linux-Renesas <>
Subject: Re: [PATCH 0/2] PM / core: genpd fix and pm_runtime_force_suspend|resume() rework

On Friday, January 12, 2018 3:31:09 PM CET Geert Uytterhoeven wrote:
> Hi Rafael,
> On Fri, Jan 12, 2018 at 2:00 PM, Rafael J. Wysocki <> wrote:
> > This comes from the recent discussion/testing effort that ensued after my
> > pm_runtime_force_suspend|resume() changes proposal:
> >
> >
> >
> > Patch [1/2] basically is rebased
> > on top of the current linux-next branch of the linux-pm.git tree (the relevant
> > part should be there in the linux-next tree proper ATM).  It applies on top
> > of which should apply to the Linus'
> > tree cleanly.
> >
> > Patch [2/2] is a resend of with
> > a very minor changelog modification and the R-b tag from Ulf.
> >
> > Geert, if possible, please test this on the Renesas systems that had the
> > problem with previously and let
> > me know if you still see issues.
> I've tested this on two very similar systems: Salvator-XS with R-Car H3 ES2.0,
> and Salvator-X with R-Car M3-W ES1.0.
> On the M3-based system, everything seems to work fine.


> On the H3-based system, the serial console (the /dev/ttySC0 device, not kernel
> serial output) is dead after resume from s2ram, with and without
> no_console_suspend.
> With no_console_suspend, I see:
>     ttySC ttySC0: 1 input overrun(s)
> after typing on the serial console, so it looks like an interrupt problem.
> This issue seems to be caused by patch [1/2]. But I have no idea what's
> really happening, and why the two systems behave differently.

Well, that's not dramatic.

Let's make a deal that we'll fix this on top of [1/2].

Which driver is this BTW?  sh-sci?  That one doesn't even support runtime
PM, confusingly enough.

> Oh well, have a nice weekend!

Thanks, you too!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux - Powered by OpenVZ