mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "pmenzel+linux-block@molgen.mpg.de" <pmenzel+linux-block@molgen.mpg.de>
Cc: "jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
	"regressions@leemhuis.info" <regressions@leemhuis.info>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: Regression 4.17-rc1: SSD doesn properly resume causing system hang (NULL pointer dereference)
Date: Tue, 24 Apr 2018 21:17:50 +0000	[thread overview]
Message-ID: <19e19bc6b2fef11faf428fe75447b06e56af9ffd.camel@wdc.com> (raw)
In-Reply-To: <6a2162a7-5f48-c107-0b1c-5258089522c5@molgen.mpg.de>

On Tue, 2018-04-24 at 23:04 +0200, Paul Menzel wrote:
> I applied your change, and rebuilt the Linux kernel. Unfortunately, it 
> looks like, it didn’t make a difference.

In that case I don't know what is causing the failure. Can you run a bisect
to determine which commit introduced this regression?

Thanks,

Bart.

  reply	other threads:[~2018-04-24 21:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 16:14 Regression 4.17-rc1: SSD doesn’t " Paul Menzel
2018-04-24 16:26 ` Regression 4.17-rc1: SSD doesnʼt " Bart Van Assche
2018-04-24 17:10   ` Paul Menzel
2018-04-24 17:31     ` Regression 4.17-rc1: SSD doesn " Bart Van Assche
2018-04-24 17:37       ` Paul Menzel
2018-04-24 18:27         ` Bart Van Assche
2018-04-24 21:04           ` Paul Menzel
2018-04-24 21:17             ` Bart Van Assche [this message]
2018-04-25  5:37               ` Paul Menzel
2018-04-25 12:26                 ` Bart Van Assche
2018-04-25 12:34                   ` Regression 4.17-rc1: SSD doesn’t " 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=19e19bc6b2fef11faf428fe75447b06e56af9ffd.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=pmenzel+linux-block@molgen.mpg.de \
    --cc=regressions@leemhuis.info \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®