On Mon, Feb 5, 2018 at 10:04 PM, Mark Kettenis wrote:
> It would help we if you could track
> down which function up the call chain return -ERESTARTSYS.
The call chain goes like this:
__i915_wait_request, which explicitly returns -ERESTARTSYS after
getting a non-zero
> From: Maximilian Pichler
> Date: Mon, 5 Feb 2018 21:29:11 +0100
>
> On Sat, Sep 23, 2017 at 6:56 AM, Niels Kobschaetzki
> wrote:
> > Sep 22 22:38:41 netcat /bsd: drm:pid71340:i915_drm_suspend *ERROR* GEM idle
> > failed, resume might fail
>
>
On Sat, Sep 23, 2017 at 6:56 AM, Niels Kobschaetzki
wrote:
> Sep 22 22:38:41 netcat /bsd: drm:pid71340:i915_drm_suspend *ERROR* GEM idle
> failed, resume might fail
Not sure if this helps, but since I'm seeing exactly the same thing on
a Zenbook 3 I added some logging to
On Mon, Feb 05, 2018 at 02:51:48PM +0100, Martin Pieuchot wrote:
> On 04/02/18(Sun) 11:28, Artturi Alm wrote:
> > Hi,
> >
> > machdep.forceukbd=1 feels broken to me, as i use "sv", and it doesn't
> > respect
> > /etc/kbdtype.
>
> If you unplug/replug your USB keyboard after having booted does
On 04/02/18(Sun) 11:28, Artturi Alm wrote:
> Hi,
>
> machdep.forceukbd=1 feels broken to me, as i use "sv", and it doesn't respect
> /etc/kbdtype.
If you unplug/replug your USB keyboard after having booted does it
respect /etc/kbdtype?