On Fri, Nov 16, 2018 at 07:16:23PM +0100, Francois Tigeot wrote:
>
> I have a Broadwell laptop on hand; I will try to reproduce and fix
> whatever is going wrong.
Commit c9f83a72b5c7c2f29b40b404aa63767b20a7422c definitely introduced
instability on broadwell but I am not getting consistent
Hi,
On Fri, Nov 16, 2018 at 04:07:32PM +0100, Daniel Bilik wrote:
> On Fri, 16 Nov 2018 16:29:15 +0200
> "karu.pruun" wrote:
>
> > Can you specify what graphics hw are you using?
>
> vgapci0@pci0:0:2:0: class=0x03 card=0x222617aa chip=0x16168086 rev=0x09
> hdr=0x00
> vendor =
On Fri, 16 Nov 2018 16:29:15 +0200
"karu.pruun" wrote:
> Can you specify what graphics hw are you using?
Sure...
vgapci0@pci0:0:2:0: class=0x03 card=0x222617aa chip=0x16168086 rev=0x09
hdr=0x00
vendor = 'Intel Corporation'
device = 'HD Graphics 5500'
class =
On Fri, Nov 16, 2018 at 3:35 PM Daniel Bilik wrote:
>
> On Fri, 16 Nov 2018 10:49:33 +
> Antonio Huete Jiménez wrote:
>
> > Would you mind pin pointing the commit that may be causing the problems?
> > You can use 'git bisect' for it.
>
> Done, bisect pointed me to commit c9f83a7+:
>
>
On Fri, 16 Nov 2018 10:49:33 +
Antonio Huete Jiménez wrote:
> Would you mind pin pointing the commit that may be causing the problems?
> You can use 'git bisect' for it.
Done, bisect pointed me to commit c9f83a7+:
Author: Francois Tigeot
Date: Mon Nov 5 22:15:18 2018 +0100
As of 8 Nov (d1dbb0fb), I can't see these issues. This suggests the
need to bisect between 8 and 16 Nov.
Cheers
Peeter
--
On Fri, Nov 16, 2018 at 12:49 PM Antonio Huete Jiménez
wrote:
>
> Hi Daniel,
>
> Would you mind pin pointing the commit that may be causing the problems?
> You can use
Hi Daniel,
Would you mind pin pointing the commit that may be causing the problems?
You can use 'git bisect' for it.
Regards,
Antonio Huete
Daniel Bilik escribió:
Hi.
After updating to current 5.3-DEVELOPMENT (21b2a00+), chromium started to
fall on me. Well, not really chromium itself, but
Hi.
After updating to current 5.3-DEVELOPMENT (21b2a00+), chromium started to
fall on me. Well, not really chromium itself, but "just" extensions are
crashing during browser activity, taking down chromium child processes,
with kernel reporting something like this:
pid 1123 (chrome), uid 1001:
