All of lore.kernel.org
 help / color / mirror / Atom feed
From: a.bockholdt@precitec-optronik.de (Bockholdt Arne)
Subject: [REGRESSION] DELL XPS 9550 with SM951 NVME SSD quits the bus in battery mode (new in 4.18/4.19)
Date: Mon, 1 Oct 2018 09:03:21 +0000	[thread overview]
Message-ID: <56b14c92bba20fd8a63cfb6986356ed604e41d2c.camel@precitec-optronik.de> (raw)
In-Reply-To: <20180925140438.GA11633@localhost.localdomain>


On Tue, 2018-09-25@08:04 -0600, Keith Busch wrote:
> On Tue, Sep 25, 2018@07:31:40AM +0000, Bockholdt Arne wrote:
> 
> Hi all,
> 
> I've noticed a regression in the 4.18/4.19 kernel lines with my Dell
> XPS 9550 laptop and the SM951 NVME SSD. Only in battery mode the SSD
> seems to quit from the PCIe bus and I need to reboot the device. The
> laptop is updated to the latest BIOS 1.80. When the device is
> connected
> to AC power the error seems to vanish. It seems to be easily
> reproducible by starting a VM via Qemu/KVM, after some seconds the
> device and the file system vanishes.
> I've tried to disable APST completely by kernel command line
> parameter
> "nvme_core.default_ps_max_latency_us=0" but it doesn't seem to help. 
> 
> 4.17 doesn't seem to be affected, tested with 4.18.6 and 4.19-rc5.
> 
> Is this a known regression? If you need more information, please let
> me
> know.
> 
> This regression sounds external to the nvme driver. Would it be
> possible
> to bisect between 4.17 and 4.18?


This regression happens on my day to day working laptop only and it
would be to time intensive and dangerous to bisect it, sorry. Maybe I
could provide log files if you point me to the right one and tell me if
I should enable some kind of debug flags.

Thanks,

   Arne

      reply	other threads:[~2018-10-01  9:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  7:31 [REGRESSION] DELL XPS 9550 with SM951 NVME SSD quits the bus in battery mode (new in 4.18/4.19) Bockholdt Arne
2018-09-25 14:04 ` Keith Busch
2018-10-01  9:03   ` Bockholdt Arne [this message]

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=56b14c92bba20fd8a63cfb6986356ed604e41d2c.camel@precitec-optronik.de \
    --to=a.bockholdt@precitec-optronik.de \
    /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.