Comment 109 for bug 1705099

Revision history for this message
In , rjw (rjw-linux-kernel-bugs) wrote :

(In reply to Patrik Kullman from comment #98)
> (In reply to Rafael J. Wysocki from comment #97)
> > (In reply to Patrik Kullman from comment #96)
> > > Actually it doesn't seem to suspend properly, I get a lot of these while
> > > suspended:
> >
> > Well, that's how the platform works, unfortunately.
> >
> > The EC needs to be enabled to wake up the system for the power button
> wakeup
> > to work, but if the EC is enabled to wake up the system, it will wake it up
> > every once a while, so either-or.
>
> "every once a while" being every 0.7 - 1.7 seconds? :)

Yes, in this particular case ...

> And I assume that it's no difference between the power button or the lid
> opening? (Looking for workarounds..)

I'm not sure about the lid to be honest, let me try to dig into that somewhat.

> > I would argue that this is an EC firmware bug on the XPS13 9365.
>
> That it happens too frequently or at all?

It shouldn't wake you up at all in the state we have requested from it, but if it did that every minute, say, it probably wouldn't really matter.

> > > And on resume I get a, most likely completely unrelated and purely
> > cosmetic:
> > >
> > > [49569.968486] intel-vbtn INT33D6:00: unknown event index 0xcd
> >
> > I'm quite confident that this is not the event that woke you up, but can
> you
> > paste more lines from dmesg around this for more context?
>
> Here's a complete suspend/resume:

[cut]

> [ 442.460866] Restarting tasks ... done.
> [ 442.552172] thermal thermal_zone11: failed to read out thermal zone (-5)
> [ 442.553302] [drm] RC6 on
> [ 442.630048] IPv6: ADDRCONF(NETDEV_UP): wlp60s0: link is not ready
> [ 442.690004] intel-vbtn INT33D6:00: unknown event index 0xcd

Well, so this happens when user space runs again, so it's not the same event.

Most likely there is one more event coming from the EC in addition to the first wakeup one and sure enough it is not in the driver's keymap. Again, I need to have a look into the ACPI tables of this machine to see what may be going on here.