On Wed, May 27, 2015 at 07:08:41PM +0200, Tom Gundersen wrote:
> This should be fixed by 86c3bece38bcf55da6387d20c6f01da9ad0284dc.
> Thanks for the help in debugging this, and sorry for the
> inconvenience.
Also this fixes a bug where 'udevadm settle' would go into a loop for
a few minutes after y
Hey Tom,
Tom Gundersen [2015-05-27 19:08 +0200]:
> This should be fixed by 86c3bece38bcf55da6387d20c6f01da9ad0284dc.
> Thanks for the help in debugging this, and sorry for the
> inconvenience.
Works like a charm. Great work, thanks!
Martin
--
Martin Pitt| http://www.piwa
On Wed, May 27, 2015 at 10:08 AM, Tom Gundersen wrote:
> This should be fixed by 86c3bece38bcf55da6387d20c6f01da9ad0284dc.
> Thanks for the help in debugging this, and sorry for the
> inconvenience.
And I can confirm the timeout is gone.
Thanks for fixing it quickly Tom! Glad to help you isolate
On Wed, May 27, 2015 at 6:23 PM, Tom Gundersen wrote:
> On Wed, May 27, 2015 at 6:16 PM, Filipe Brandenburger
> wrote:
>> Hi Tom,
>>
>> On Wed, May 27, 2015 at 8:45 AM, Tom Gundersen wrote:
>>> It appears a few people see this, but I was not able to reproduce. If
>>> anyone could reproduce with
On Wed, May 27, 2015 at 6:16 PM, Filipe Brandenburger
wrote:
> Hi Tom,
>
> On Wed, May 27, 2015 at 8:45 AM, Tom Gundersen wrote:
>> It appears a few people see this, but I was not able to reproduce. If
>> anyone could reproduce with this patch applied [0], it would be most
>> helpful (and post th
Hi Tom,
On Wed, May 27, 2015 at 8:45 AM, Tom Gundersen wrote:
> It appears a few people see this, but I was not able to reproduce. If
> anyone could reproduce with this patch applied [0], it would be most
> helpful (and post the output of "journalctl -b -u systemd-udevd").
Done.
Console output
On Tue, May 26, 2015 at 5:11 PM, Martin Pitt wrote:
> Hello Tom, all,
>
> with 220 I get a severe boot time regression:
>
> $ systemd-analyze
> Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s
>
> which used to be
>
> $ systemd-analyze
> Startup finished in 703ms (kerne
On Tue, May 26, 2015 at 9:04 PM, Christian Hesse wrote:
> Martin Pitt on Tue, 2015/05/26 17:11:
>> Hello Tom, all,
>>
>> with 220 I get a severe boot time regression:
>>
>> $ systemd-analyze
>> Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s
>>
>> which used to be
>>
>>
On Tue, May 26, 2015 at 9:04 PM, Christian Hesse wrote:
> Martin Pitt on Tue, 2015/05/26 17:11:
>> Hello Tom, all,
>>
>> with 220 I get a severe boot time regression:
>>
>> $ systemd-analyze
>> Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s
>>
>> which used to be
>>
>>
Martin Pitt on Tue, 2015/05/26 17:11:
> Hello Tom, all,
>
> with 220 I get a severe boot time regression:
>
> $ systemd-analyze
> Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s
>
> which used to be
>
> $ systemd-analyze
> Startup finished in 703ms (kernel) + 890ms
On Tue, May 26, 2015 at 5:11 PM, Martin Pitt wrote:
> Hello Tom, all,
>
> with 220 I get a severe boot time regression:
>
> $ systemd-analyze
> Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s
>
> which used to be
>
> $ systemd-analyze
> Startup finished in 703ms (kerne
Hello Tom, all,
with 220 I get a severe boot time regression:
$ systemd-analyze
Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s
which used to be
$ systemd-analyze
Startup finished in 703ms (kernel) + 890ms (userspace) = 1.593s
(this is a VM)
It seems udevd --daemo
12 matches
Mail list logo
