All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"vrbagal1@linux.vnet.ibm.com" <vrbagal1@linux.vnet.ibm.com>
Cc: "sachinp@linux.vnet.ibm.com" <sachinp@linux.vnet.ibm.com>
Subject: Re: Fwd: [powerpc/Baremetal]Kernel OOPS while executing memory hotplug on Power8 baremetal
Date: Thu, 7 Jun 2018 07:16:50 +0000	[thread overview]
Message-ID: <d5b62afc48ece5aca8d08a80871c8613dd555d17.camel@wdc.com> (raw)
In-Reply-To: <ee45ead1d96ad05f77aec1d8d3e39c85@linux.vnet.ibm.com>

On Thu, 2018-06-07 at 12:38 +0530, vrbagal1 wrote:
> Observing Kernel oops and machine reboots while executing memory hotplug 
> test case, on Power8 Baremetal machine.
> 
> I see this is introduced some where between rc6 and 4.17.

Please provide the exact versions (git commit IDs) of the kernel versions
you have tested.

Thanks,

Bart.





WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"vrbagal1@linux.vnet.ibm.com" <vrbagal1@linux.vnet.ibm.com>
Cc: "sachinp@linux.vnet.ibm.com" <sachinp@linux.vnet.ibm.com>,
	"mpe@ellerman.id.au" <mpe@ellerman.id.au>
Subject: Re: Fwd: [powerpc/Baremetal]Kernel OOPS while executing memory hotplug on Power8 baremetal
Date: Thu, 7 Jun 2018 07:16:50 +0000	[thread overview]
Message-ID: <d5b62afc48ece5aca8d08a80871c8613dd555d17.camel@wdc.com> (raw)
In-Reply-To: <ee45ead1d96ad05f77aec1d8d3e39c85@linux.vnet.ibm.com>

T24gVGh1LCAyMDE4LTA2LTA3IGF0IDEyOjM4ICswNTMwLCB2cmJhZ2FsMSB3cm90ZToNCj4gT2Jz
ZXJ2aW5nIEtlcm5lbCBvb3BzIGFuZCBtYWNoaW5lIHJlYm9vdHMgd2hpbGUgZXhlY3V0aW5nIG1l
bW9yeSBob3RwbHVnIA0KPiB0ZXN0IGNhc2UsIG9uIFBvd2VyOCBCYXJlbWV0YWwgbWFjaGluZS4N
Cj4gDQo+IEkgc2VlIHRoaXMgaXMgaW50cm9kdWNlZCBzb21lIHdoZXJlIGJldHdlZW4gcmM2IGFu
ZCA0LjE3Lg0KDQpQbGVhc2UgcHJvdmlkZSB0aGUgZXhhY3QgdmVyc2lvbnMgKGdpdCBjb21taXQg
SURzKSBvZiB0aGUga2VybmVsIHZlcnNpb25zDQp5b3UgaGF2ZSB0ZXN0ZWQuDQoNClRoYW5rcywN
Cg0KQmFydC4NCg0KDQoNCg0K

  reply	other threads:[~2018-06-07  7:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07  7:08 Fwd: [powerpc/Baremetal]Kernel OOPS while executing memory hotplug on Power8 baremetal vrbagal1
2018-06-07  7:08 ` vrbagal1
2018-06-07  7:16 ` Bart Van Assche [this message]
2018-06-07  7:16   ` Bart Van Assche
2018-06-07  7:26   ` Venkat Rao B
2018-06-07  7:26     ` Venkat Rao B
2018-06-07  7:42     ` Bart Van Assche
2018-06-07  7:42       ` Bart Van Assche
2018-06-07 10:37       ` vrbagal1
2018-06-07 10:37         ` vrbagal1
2018-06-07 12:51         ` Michael Ellerman
2018-06-07 12:51           ` Michael Ellerman
2018-06-07 14:45         ` Jens Axboe
2018-06-07 14:45           ` Jens Axboe
2018-06-07 15:40           ` Jens Axboe
2018-06-07 15:40             ` Jens Axboe

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=d5b62afc48ece5aca8d08a80871c8613dd555d17.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sachinp@linux.vnet.ibm.com \
    --cc=vrbagal1@linux.vnet.ibm.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.