All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Mario.Limonciello@dell.com>
To: <pmenzel@molgen.mpg.de>, <bp@alien8.de>
Cc: <ashok.raj@intel.com>, <linux-kernel@vger.kernel.org>,
	<linux@leemhuis.info>, <len.brown@intel.com>,
	<tony.luck@intel.com>
Subject: RE: Dell XPS13: MCE (Hardware Error) reported
Date: Wed, 1 Feb 2017 20:52:35 +0000	[thread overview]
Message-ID: <bda005da4a7540cb956d5071fbe99c4c@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <c326e985-d362-fb2c-2516-1ac8c6c2e9e1@molgen.mpg.de>

Hi Paul,

> Mario, there are at least two more firmware bugs [4][5][6]. Having fast
> suspend and resume says something about the quality of a device. If the Dell
> XPS13 9360 is supposed to compete with Apple devices, and Google
> Chromebooks, then this should be improved in my opinion. Do you have a
> suggestion on how to best get this solved? Do you want me to contact the
> support, or are there Dell employees with access to the Linux kernel Bugzilla
> bug tracker?
> 
> 

Thanks for sharing these to my attention.  I wasn't aware, and neither was the rest
of the team handling these machines.  I've started some internal discussion around
the slow ASL resume one.

The WoWLAN one, I'm not sure there will be much for us to do on the BIOS FW end.
As Kalle was mentioning, this comes down to the device FW needing to spin up.  The
easiest way to keep it quick is to leave the radio active, which is what WoWLAN will
accomplish.

The other option is going to be to move over to suspend to idle.  This will leave most
devices operational (in RTD3), freeze kernel threads and let the CPU go into a low
enough state.  Some of the plumbing that will allow supporting this has recently gone
in, but there are some problems to work through that will prevent letting machines
that support it make it the default until at least the next kernel version.

  parent reply	other threads:[~2017-02-01 20:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 15:42 Dell XPS13: MCE (Hardware Error) reported Paul Menzel
2017-01-04 22:55 ` Borislav Petkov
2017-01-05  1:12   ` Raj, Ashok
2017-01-09 11:53     ` Paul Menzel
2017-01-09 19:23       ` Raj, Ashok
2017-01-27 13:35         ` Paul Menzel
2017-01-27 17:10           ` Borislav Petkov
2017-01-27 17:16             ` Mario.Limonciello
2017-01-31 15:29               ` Paul Menzel
2017-01-31 17:20                 ` Borislav Petkov
2017-01-31 18:50                 ` Austin S. Hemmelgarn
2017-02-01 20:52                 ` Mario.Limonciello [this message]
2017-01-05  5:00 Daniel J Blueman
2017-01-05 14:05 ` Daniel J Blueman
2017-01-05 20:10   ` Alexander Alemayhu
2017-01-05 20:31     ` Borislav Petkov
2017-01-05 20:43       ` Raj, Ashok
2017-01-05 21:03         ` Pandruvada, Srinivas
2017-01-05 23:23           ` Alexander Alemayhu
2017-01-05 21:38       ` Alexander Alemayhu
2017-01-05 23:28       ` Raj, Ashok
2017-01-05 23:56         ` Borislav Petkov
2017-01-06  1:26           ` Raj, Ashok
2017-01-06 11:16             ` Borislav Petkov
2017-01-06 15:58               ` Raj, Ashok
2017-01-06 16:54                 ` Borislav Petkov
2017-01-06 17:04                   ` Raj, Ashok
2017-01-09 10:55                   ` Paul Menzel
2017-01-09 11:05                     ` Borislav Petkov
2017-01-09 11:11                       ` Paul Menzel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bda005da4a7540cb956d5071fbe99c4c@ausx13mpc120.AMER.DELL.COM \
    --to=mario.limonciello@dell.com \
    --cc=ashok.raj@intel.com \
    --cc=bp@alien8.de \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=pmenzel@molgen.mpg.de \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.