All of lore.kernel.org
 help / color / mirror / Atom feed
From: muhlemmer@gmail.com (Tim Mohlmann)
Subject: nvme device timeout
Date: Tue, 29 Mar 2016 19:52:30 +0300	[thread overview]
Message-ID: <56FAB2CE.6060405@gmail.com> (raw)
In-Reply-To: <20160329144241.GA2396@linux.intel.com>



On 03/29/2016 05:42 PM, Matthew Wilcox wrote:

> 
> I doubt it's the controller.  Usually it's ACPI or how the PCI bridge
> got wired up.
> 

This can be an issue, yes. This is a new laptop, based on the intel
skylake platform. Since I got it a month ago I was walking trough kernel
version to get everything (display, network, sound etc) working.

At kernel version 4.4 nvme stopped to work in UEFI mode and in kernel
4.5 it stopped to work completely. You will probably not be suprised if
I told you that I have ACPI problems too, but they where of a less
priority on my list. Eg: battery information missing and poweroff not
working.

In my original mail I attached a dmesg output. There are also some ACPI
table errors in that. Maybe you want to look at it? I'm willing run a
bug report at kernel.org for ACPI, but I wouldn't know where to start.
It would be fuzzy to open a report saying: some things are not working

  reply	other threads:[~2016-03-29 16:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 16:44 nvme device timeout Tim Mohlmann
2016-03-28 17:24 ` Keith Busch
2016-03-28 22:30   ` Judy Brock-SSI
2016-03-28 22:54     ` Keith Busch
2016-03-29  7:03       ` Christoph Hellwig
2016-03-29 11:04         ` Judy Brock-SSI
2016-03-29 11:06           ` Christoph Hellwig
2016-03-29 14:42             ` Matthew Wilcox
2016-03-29 16:52               ` Tim Mohlmann [this message]
     [not found] <1604554248.106551459228253752.JavaMail.weblogic@epmlwas03c>
2016-03-29 14:38 ` Keith Busch
2016-03-29 17:17   ` Tim Mohlmann
2016-04-01 16:02   ` Derrick, Jonathan
2016-04-01 16:25     ` Derrick, Jonathan

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=56FAB2CE.6060405@gmail.com \
    --to=muhlemmer@gmail.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.