On Thu, Apr 26, 2018 at 10:51 AM, Thomas Gleixner wrote:
> On Thu, 26 Apr 2018, Rafael J. Wysocki wrote:
>
>> On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote:
>> > On Thu, 26 Apr 2018, Mike Galbraith wrote:
>> >> On Wed, 2018-04-25 at 15:03 +0200,
On Thu, Apr 26, 2018 at 10:51 AM, Thomas Gleixner wrote:
> On Thu, 26 Apr 2018, Rafael J. Wysocki wrote:
>
>> On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote:
>> > On Thu, 26 Apr 2018, Mike Galbraith wrote:
>> >> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote:
>> >> > Right, it
On Thu, 26 Apr 2018, Rafael J. Wysocki wrote:
> On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote:
> > On Thu, 26 Apr 2018, Mike Galbraith wrote:
> >> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote:
> >> > Right, it does not matter. The real interesting one is
On Thu, 26 Apr 2018, Rafael J. Wysocki wrote:
> On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote:
> > On Thu, 26 Apr 2018, Mike Galbraith wrote:
> >> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote:
> >> > Right, it does not matter. The real interesting one is d6ed449afdb3.
> >>
>
On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote:
> On Thu, 26 Apr 2018, Mike Galbraith wrote:
>> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote:
>> > Right, it does not matter. The real interesting one is d6ed449afdb3.
>>
>> FWIW, three boxen here
On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote:
> On Thu, 26 Apr 2018, Mike Galbraith wrote:
>> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote:
>> > Right, it does not matter. The real interesting one is d6ed449afdb3.
>>
>> FWIW, three boxen here suspend/resume fine, but
On Thu, 26 Apr 2018, Mike Galbraith wrote:
> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote:
> > Right, it does not matter. The real interesting one is d6ed449afdb3.
>
> FWIW, three boxen here suspend/resume fine, but repeatably exhibit the
> below after a very few minute suspend, and a
On Thu, 26 Apr 2018, Mike Galbraith wrote:
> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote:
> > Right, it does not matter. The real interesting one is d6ed449afdb3.
>
> FWIW, three boxen here suspend/resume fine, but repeatably exhibit the
> below after a very few minute suspend, and a
On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote:
> Right, it does not matter. The real interesting one is d6ed449afdb3.
FWIW, three boxen here suspend/resume fine, but repeatably exhibit the
below after a very few minute suspend, and a short bisect fingered your
suspect. Distro is
On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote:
> Right, it does not matter. The real interesting one is d6ed449afdb3.
FWIW, three boxen here suspend/resume fine, but repeatably exhibit the
below after a very few minute suspend, and a short bisect fingered your
suspect. Distro is
On Wed, 25 Apr 2018, Rafael J. Wysocki wrote:
> On Wednesday, April 25, 2018 10:52:18 AM CEST Rafael J. Wysocki wrote:
> > On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote:
> > > On Mon, 23 Apr 2018, John Stultz wrote:
> > >
> > > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky
On Wed, 25 Apr 2018, Rafael J. Wysocki wrote:
> On Wednesday, April 25, 2018 10:52:18 AM CEST Rafael J. Wysocki wrote:
> > On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote:
> > > On Mon, 23 Apr 2018, John Stultz wrote:
> > >
> > > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky
On Wednesday, April 25, 2018 10:52:18 AM CEST Rafael J. Wysocki wrote:
> On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote:
> > On Mon, 23 Apr 2018, John Stultz wrote:
> >
> > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote:
> > > > Quoting Genki Sky (2018/04/23
On Wednesday, April 25, 2018 10:52:18 AM CEST Rafael J. Wysocki wrote:
> On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote:
> > On Mon, 23 Apr 2018, John Stultz wrote:
> >
> > > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote:
> > > > Quoting Genki Sky (2018/04/23 20:40:36
On Wednesday, April 25, 2018 8:50:15 AM CEST Pavel Machek wrote:
>
> --ReaqsoxgOBHFXBhH
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Tue 2018-04-24 10:09:28, Thomas Gleixner wrote:
> > On Mon, 23 Apr 2018, John
On Wednesday, April 25, 2018 8:50:15 AM CEST Pavel Machek wrote:
>
> --ReaqsoxgOBHFXBhH
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Tue 2018-04-24 10:09:28, Thomas Gleixner wrote:
> > On Mon, 23 Apr 2018, John
On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote:
> On Mon, 23 Apr 2018, John Stultz wrote:
>
> > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote:
> > > Quoting Genki Sky (2018/04/23 20:40:36 -0400)
> > >> I came across this thread for same reason as [0]: Daemons
On Tuesday, April 24, 2018 10:09:28 AM CEST Thomas Gleixner wrote:
> On Mon, 23 Apr 2018, John Stultz wrote:
>
> > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote:
> > > Quoting Genki Sky (2018/04/23 20:40:36 -0400)
> > >> I came across this thread for same reason as [0]: Daemons getting
> > >>
On Tue 2018-04-24 10:09:28, Thomas Gleixner wrote:
> On Mon, 23 Apr 2018, John Stultz wrote:
>
> > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote:
> > > Quoting Genki Sky (2018/04/23 20:40:36 -0400)
> > >> I came across this thread for same reason as [0]: Daemons getting
> > >>
On Tue 2018-04-24 10:09:28, Thomas Gleixner wrote:
> On Mon, 23 Apr 2018, John Stultz wrote:
>
> > On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote:
> > > Quoting Genki Sky (2018/04/23 20:40:36 -0400)
> > >> I came across this thread for same reason as [0]: Daemons getting
> > >> killed by
On Tue, 24 Apr 2018, Genki Sky wrote:
> Sorry to have been the bearer of bad news :(.
No problem. We're not shooting the messengers
> Again, I just have my user hat on here. It does seem like this unifying
> would have been nice to have. And even, more compliant with the POSIX
> definition of
On Tue, 24 Apr 2018, Genki Sky wrote:
> Sorry to have been the bearer of bad news :(.
No problem. We're not shooting the messengers
> Again, I just have my user hat on here. It does seem like this unifying
> would have been nice to have. And even, more compliant with the POSIX
> definition of
Sorry to have been the bearer of bad news :(. Again, I just have my
user hat on here. It does seem like this unifying would have been nice
to have. And even, more compliant with the POSIX definition of
MONOTONIC...
On that note, maybe it is still worth introducing MONOTONIC_ACTIVE,
but just as an
Sorry to have been the bearer of bad news :(. Again, I just have my
user hat on here. It does seem like this unifying would have been nice
to have. And even, more compliant with the POSIX definition of
MONOTONIC...
On that note, maybe it is still worth introducing MONOTONIC_ACTIVE,
but just as an
On Mon, 23 Apr 2018, John Stultz wrote:
> On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote:
> > Quoting Genki Sky (2018/04/23 20:40:36 -0400)
> >> I came across this thread for same reason as [0]: Daemons getting
> >> killed by systemd on resume (after >WatchdogSec seconds of
> >>
On Mon, 23 Apr 2018, John Stultz wrote:
> On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote:
> > Quoting Genki Sky (2018/04/23 20:40:36 -0400)
> >> I came across this thread for same reason as [0]: Daemons getting
> >> killed by systemd on resume (after >WatchdogSec seconds of
> >> suspending).
On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote:
> Quoting Genki Sky (2018/04/23 20:40:36 -0400)
>> I came across this thread for same reason as [0]: Daemons getting
>> killed by systemd on resume (after >WatchdogSec seconds of
>> suspending). I'm using master branch of systemd
On Mon, Apr 23, 2018 at 7:45 PM, Genki Sky wrote:
> Quoting Genki Sky (2018/04/23 20:40:36 -0400)
>> I came across this thread for same reason as [0]: Daemons getting
>> killed by systemd on resume (after >WatchdogSec seconds of
>> suspending). I'm using master branch of systemd and the kernel.
Quoting Genki Sky (2018/04/23 20:40:36 -0400)
> I came across this thread for same reason as [0]: Daemons getting
> killed by systemd on resume (after >WatchdogSec seconds of
> suspending). I'm using master branch of systemd and the kernel. As
> mentioned, systemd uses CLOCK_MONOTONIC, originally
Quoting Genki Sky (2018/04/23 20:40:36 -0400)
> I came across this thread for same reason as [0]: Daemons getting
> killed by systemd on resume (after >WatchdogSec seconds of
> suspending). I'm using master branch of systemd and the kernel. As
> mentioned, systemd uses CLOCK_MONOTONIC, originally
Hello,
I came across this thread for same reason as [0]: Daemons getting
killed by systemd on resume (after >WatchdogSec seconds of
suspending). I'm using master branch of systemd and the kernel. As
mentioned, systemd uses CLOCK_MONOTONIC, originally expecting it to
not include suspend time.
Hello,
I came across this thread for same reason as [0]: Daemons getting
killed by systemd on resume (after >WatchdogSec seconds of
suspending). I'm using master branch of systemd and the kernel. As
mentioned, systemd uses CLOCK_MONOTONIC, originally expecting it to
not include suspend time.
Hi
On Fri, Apr 20, 2018 at 7:44 AM, Sergey Senozhatsky
wrote:
> On (04/20/18 06:37), David Herrmann wrote:
>>
>> I get lots of timer-errors on Arch-Linux booting current master, after
>> a suspend/resume cycle. Just a selection of errors I see on resume:
>
>
Hi
On Fri, Apr 20, 2018 at 7:44 AM, Sergey Senozhatsky
wrote:
> On (04/20/18 06:37), David Herrmann wrote:
>>
>> I get lots of timer-errors on Arch-Linux booting current master, after
>> a suspend/resume cycle. Just a selection of errors I see on resume:
>
> Hello David,
> Any chance you can
On (04/20/18 06:37), David Herrmann wrote:
>
> I get lots of timer-errors on Arch-Linux booting current master, after
> a suspend/resume cycle. Just a selection of errors I see on resume:
Hello David,
Any chance you can revert the patches in question and test? I'm running
ARCH
On (04/20/18 06:37), David Herrmann wrote:
>
> I get lots of timer-errors on Arch-Linux booting current master, after
> a suspend/resume cycle. Just a selection of errors I see on resume:
Hello David,
Any chance you can revert the patches in question and test? I'm running
ARCH
Hey
On Tue, Mar 13, 2018 at 7:11 PM, John Stultz wrote:
> On Mon, Mar 12, 2018 at 11:36 PM, Ingo Molnar wrote:
>> Ok, I have edited all the changelogs accordingly (and also flipped around the
>> 'clock MONOTONIC' language to the more readable 'the
Hey
On Tue, Mar 13, 2018 at 7:11 PM, John Stultz wrote:
> On Mon, Mar 12, 2018 at 11:36 PM, Ingo Molnar wrote:
>> Ok, I have edited all the changelogs accordingly (and also flipped around the
>> 'clock MONOTONIC' language to the more readable 'the MONOTONIC clock'
>> variant),
>> the resulting
On Mon, Mar 12, 2018 at 11:36 PM, Ingo Molnar wrote:
>
> * Linus Torvalds wrote:
>
>> On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote:
>> >
>> > This really needs lot of testing, documentation updates and more input from
On Mon, Mar 12, 2018 at 11:36 PM, Ingo Molnar wrote:
>
> * Linus Torvalds wrote:
>
>> On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote:
>> >
>> > This really needs lot of testing, documentation updates and more input from
>> > userspace folks to make a final decision.
>>
>> Honestly, I
* Linus Torvalds wrote:
> On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote:
> >
> > This really needs lot of testing, documentation updates and more input from
> > userspace folks to make a final decision.
>
> Honestly, I don't think
* Linus Torvalds wrote:
> On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote:
> >
> > This really needs lot of testing, documentation updates and more input from
> > userspace folks to make a final decision.
>
> Honestly, I don't think we'd get the testing this kind of change needs
>
On Thu, 1 Mar 2018, Thomas Gleixner wrote:
> On Thu, 1 Mar 2018, Linus Torvalds wrote:
> > On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote:
> > >
> > > This really needs lot of testing, documentation updates and more input
> > > from
> > > userspace folks to make a
On Thu, 1 Mar 2018, Thomas Gleixner wrote:
> On Thu, 1 Mar 2018, Linus Torvalds wrote:
> > On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote:
> > >
> > > This really needs lot of testing, documentation updates and more input
> > > from
> > > userspace folks to make a final decision.
> >
> >
On Thu, 1 Mar 2018 19:41:35 +0100 (CET)
Thomas Gleixner wrote:
> I'm old enough to have learned that conflate means unify or combine, but
> I'm still not old enough to be stubborn about it :)
You need to watch more American Cable News channels to know what
"conflate" means
On Thu, 1 Mar 2018 19:41:35 +0100 (CET)
Thomas Gleixner wrote:
> I'm old enough to have learned that conflate means unify or combine, but
> I'm still not old enough to be stubborn about it :)
You need to watch more American Cable News channels to know what
"conflate" means today.
-- Steve
On Thu, 1 Mar 2018, Linus Torvalds wrote:
> On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote:
> >
> > This really needs lot of testing, documentation updates and more input from
> > userspace folks to make a final decision.
>
> Honestly, I don't think we'd get the
On Thu, 1 Mar 2018, Linus Torvalds wrote:
> On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote:
> >
> > This really needs lot of testing, documentation updates and more input from
> > userspace folks to make a final decision.
>
> Honestly, I don't think we'd get the testing this kind of
On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote:
>
> This really needs lot of testing, documentation updates and more input from
> userspace folks to make a final decision.
Honestly, I don't think we'd get the testing this kind of change needs
except by just trying it.
On Thu, Mar 1, 2018 at 8:33 AM, Thomas Gleixner wrote:
>
> This really needs lot of testing, documentation updates and more input from
> userspace folks to make a final decision.
Honestly, I don't think we'd get the testing this kind of change needs
except by just trying it.
I'm willing to
While working through the melted spectrum induced backlog I found that last
years discussion about unifying clock MONOTONIC and clock BOOTTIME has died
out and obviously nobody had time to do testing on that half baken RFC patch:
While working through the melted spectrum induced backlog I found that last
years discussion about unifying clock MONOTONIC and clock BOOTTIME has died
out and obviously nobody had time to do testing on that half baken RFC patch:
52 matches
Mail list logo