All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Keith Busch <keith.busch@linux.intel.com>
Cc: Yi Zhang <yi.zhang@redhat.com>,
	Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@kernel.dk>,
	linux-nvme@lists.infradead.org, Ming Lei <ming.lei@redhat.com>,
	linux-block@vger.kernel.org,
	Johannes Thumshirn <jthumshirn@suse.de>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH blktests] Fix block/011 to not use sysfs for device disabling
Date: Tue, 29 May 2018 12:54:28 -0700	[thread overview]
Message-ID: <20180529195428.GE23487@vader> (raw)
In-Reply-To: <20180521140821.GB5528@localhost.localdomain>

On Mon, May 21, 2018 at 08:08:21AM -0600, Keith Busch wrote:
> On Mon, May 21, 2018 at 02:37:56AM -0400, Yi Zhang wrote:
> > Hi Keith
> > I tried this patch on my R730 Server, but it lead to system hang after setpci, could you help check it, thanks.
> > 
> > Console log:
> > storageqe-62 login: 
> > Kernel 4.17.0-rc5 on an x86_64
> > 
> > storageqe-62 login: [ 1058.118258] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 3
> > [ 1058.118261] {1}[Hardware Error]: event severity: fatal
> > [ 1058.118262] {1}[Hardware Error]:  Error 0, type: fatal
> > [ 1058.118265] {1}[Hardware Error]:   section_type: PCIe error
> > [ 1058.118266] {1}[Hardware Error]:   port_type: 0, PCIe end point
> > [ 1058.118267] {1}[Hardware Error]:   version: 1.16
> > [ 1058.118269] {1}[Hardware Error]:   command: 0x0400, status: 0x0010
> > [ 1058.118270] {1}[Hardware Error]:   device_id: 0000:85:00.0
> > [ 1058.118271] {1}[Hardware Error]:   slot: 0
> > [ 1058.118271] {1}[Hardware Error]:   secondary_bus: 0x00
> > [ 1058.118273] {1}[Hardware Error]:   vendor_id: 0x144d, device_id: 0xa821
> > [ 1058.118274] {1}[Hardware Error]:   class_code: 020801
> > [ 1058.118275] Kernel panic - not syncing: Fatal hardware error!
> > [ 1058.118301] Kernel Offset: 0x14800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
> 
> Thanks for the notice. The test may be going to far with the config
> registers it's touching. Let me see if we just do the BME bit as Ming
> suggested fixes this.

What's the plan for this test? Do you have a v2 coming?

WARNING: multiple messages have this Message-ID (diff)
From: osandov@osandov.com (Omar Sandoval)
Subject: [PATCH blktests] Fix block/011 to not use sysfs for device disabling
Date: Tue, 29 May 2018 12:54:28 -0700	[thread overview]
Message-ID: <20180529195428.GE23487@vader> (raw)
In-Reply-To: <20180521140821.GB5528@localhost.localdomain>

On Mon, May 21, 2018@08:08:21AM -0600, Keith Busch wrote:
> On Mon, May 21, 2018@02:37:56AM -0400, Yi Zhang wrote:
> > Hi Keith
> > I tried this patch on my R730 Server, but it lead to system hang after setpci, could you help check it, thanks.
> > 
> > Console log:
> > storageqe-62 login: 
> > Kernel 4.17.0-rc5 on an x86_64
> > 
> > storageqe-62 login: [ 1058.118258] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 3
> > [ 1058.118261] {1}[Hardware Error]: event severity: fatal
> > [ 1058.118262] {1}[Hardware Error]:  Error 0, type: fatal
> > [ 1058.118265] {1}[Hardware Error]:   section_type: PCIe error
> > [ 1058.118266] {1}[Hardware Error]:   port_type: 0, PCIe end point
> > [ 1058.118267] {1}[Hardware Error]:   version: 1.16
> > [ 1058.118269] {1}[Hardware Error]:   command: 0x0400, status: 0x0010
> > [ 1058.118270] {1}[Hardware Error]:   device_id: 0000:85:00.0
> > [ 1058.118271] {1}[Hardware Error]:   slot: 0
> > [ 1058.118271] {1}[Hardware Error]:   secondary_bus: 0x00
> > [ 1058.118273] {1}[Hardware Error]:   vendor_id: 0x144d, device_id: 0xa821
> > [ 1058.118274] {1}[Hardware Error]:   class_code: 020801
> > [ 1058.118275] Kernel panic - not syncing: Fatal hardware error!
> > [ 1058.118301] Kernel Offset: 0x14800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
> 
> Thanks for the notice. The test may be going to far with the config
> registers it's touching. Let me see if we just do the BME bit as Ming
> suggested fixes this.

What's the plan for this test? Do you have a v2 coming?

  reply	other threads:[~2018-05-29 19:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 17:42 [PATCH blktests] Fix block/011 to not use sysfs for device disabling Keith Busch
2018-05-18 17:42 ` Keith Busch
2018-05-19 11:58 ` Ming Lei
2018-05-19 11:58   ` Ming Lei
2018-05-21  6:37 ` Yi Zhang
2018-05-21  6:37   ` Yi Zhang
2018-05-21 14:08   ` Keith Busch
2018-05-21 14:08     ` Keith Busch
2018-05-29 19:54     ` Omar Sandoval [this message]
2018-05-29 19:54       ` Omar Sandoval
2018-06-04 19:38       ` Keith Busch
2018-06-04 19:38         ` Keith Busch

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=20180529195428.GE23487@vader \
    --to=osandov@osandov.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=jthumshirn@suse.de \
    --cc=keith.busch@intel.com \
    --cc=keith.busch@linux.intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=ming.lei@redhat.com \
    --cc=yi.zhang@redhat.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.