All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Mario Limonciello <mario.limonciello@dell.com>,
	Borislav Petkov <bp@alien8.de>
Cc: Ashok Raj <ashok.raj@intel.com>,
	linux-kernel@vger.kernel.org,
	Thorsten Leemhuis <linux@leemhuis.info>,
	Len Brown <len.brown@intel.com>, Tony Luck <tony.luck@intel.com>
Subject: Re: Dell XPS13: MCE (Hardware Error) reported
Date: Tue, 31 Jan 2017 16:29:51 +0100	[thread overview]
Message-ID: <c326e985-d362-fb2c-2516-1ac8c6c2e9e1@molgen.mpg.de> (raw)
In-Reply-To: <b85ce65020bd479697149a6a2405756e@ausx13mpc120.AMER.DELL.COM>

Dear Borislav, dear Mario,


On 01/27/17 18:16, Mario.Limonciello@dell.com wrote:
>> -----Original Message-----
>> From: Borislav Petkov [mailto:bp@alien8.de]
>> Sent: Friday, January 27, 2017 11:11 AM
>> To: Paul Menzel <pmenzel@molgen.mpg.de>
>> Cc: Ashok Raj <ashok.raj@intel.com>; Linux Kernel Mailing List <linux-
>> kernel@vger.kernel.org>; Thorsten Leemhuis <linux@leemhuis.info>; Len
>> Brown <len.brown@intel.com>; Tony Luck <tony.luck@intel.com>;
>> Limonciello, Mario <Mario_Limonciello@Dell.com>
>> Subject: Re: Dell XPS13: MCE (Hardware Error) reported
>>
>> On Fri, Jan 27, 2017 at 02:35:16PM +0100, Paul Menzel wrote:
>>> Thank you very much for your help. After wasting my time with the Dell
>>> support over Twitter [1], where they basically also make you jump
>>> through hoops,
>>
>> Fun read that twitter page. Especially the bit about not supporting Linux but
>> but you did ship this laptop with ubuntu. LOOL.
>>
>> FWIW, this is not the first time I've heard vendors trying to get away from
>> dealing with bugs by playing the "we-dont-support-Linux" card.

I think, in this case it was an honest mistake from the support person, 
which they corrected in a follow-up post.

But the next conversion was a little disappointing as the problem was 
already diagnosed out on the LKML.

As Mario replied, the Twitter people do not seem to know the free 
software world that well, that “normal” people actually are in contact 
with the developers.

What surprises me though is, that the change-log for the firmware seems 
to be incomplete even for the Dell staff.

>> Good to know when I go looking for a new laptop in the future.

Unfortunately, there are not a lot of options. If you know a good 
vendor, please share.

Dell is one of the view “big” vendors selling laptops with a GNU/Linux 
operating system installed.

There are Google Chromebooks, which even have coreboot. Google’s 
Chromium team does a great job and have a great quality assurance. On 
par, or even better than Apple, I’d say.

Some people need more powerful devices though.

In Germany, I know of TUXEDO [1]. Also, Purism devices have GNU/Linux 
installed [2].

TUXEDO does not build the devices themselves, and gets template 
models(?) from Chinese manufactures. They only seem to start hiring the 
expertise to do Linux kernel and OS work themselves [3]. Currently, it’s 
mostly the stock Ubuntu for desktop with their artwork and some small 
optimizations.

> Sorry you had that experience.  I'll pass that on to get that messaging
> corrected.  The team that does Linux support doesn't use twitter, they
> do phone and email support only.

Thank you that’s good to know.

> I'm glad you got things sorted moving to the next FW version.

Me too.

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?


Kind regards,

Paul


[1] https://www.tuxedocomputers.com/
[2] https://puri.sm/
[3] 
https://www.tuxedocomputers.com/Jobs-Karriere-Stellenausschreibungen.geek?x6a1ec=o8323ih26224vook9uu997r1a5
[4] https://github.molgen.mpg.de/mariux64/dell_xps13/
[5] https://bugzilla.kernel.org/show_bug.cgi?id=185611
[6] https://bugzilla.kernel.org/show_bug.cgi?id=185621

  reply	other threads:[~2017-01-31 15:29 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 [this message]
2017-01-31 17:20                 ` Borislav Petkov
2017-01-31 18:50                 ` Austin S. Hemmelgarn
2017-02-01 20:52                 ` Mario.Limonciello
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=c326e985-d362-fb2c-2516-1ac8c6c2e9e1@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --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=mario.limonciello@dell.com \
    --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.