linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lili Deng (Wicresoft North America Ltd)" <v-lide@microsoft.com>
To: Sachin Sant <sachinp@linux.vnet.ibm.com>,
	Dexuan-Linux Cui <dexuan.linux@gmail.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Dexuan Cui <decui@microsoft.com>
Subject: RE: [next-20190530] Boot failure on PowerPC
Date: Mon, 3 Jun 2019 03:23:34 +0000	[thread overview]
Message-ID: <KL1P15301MB02948DA3C780A2DC4A145E0F9E140@KL1P15301MB0294.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <D8C9598F-4A51-4402-9344-894EC6B6CE47@linux.vnet.ibm.com>

Hi Sachin,

I verified below patch against Ubuntu 18.04, didn't hit the kernel panic any more, could you please let know how did you verify?

Thanks,
Lili
-----Original Message-----
From: Sachin Sant <sachinp@linux.vnet.ibm.com> 
Sent: Monday, June 3, 2019 11:12 AM
To: Dexuan-Linux Cui <dexuan.linux@gmail.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>; linuxppc-dev@lists.ozlabs.org; linux-next@vger.kernel.org; Dexuan Cui <decui@microsoft.com>; Lili Deng (Wicresoft North America Ltd) <v-lide@microsoft.com>
Subject: Re: [next-20190530] Boot failure on PowerPC



> On 31-May-2019, at 11:43 PM, Dexuan-Linux Cui <dexuan.linux@gmail.com> wrote:
> 
> On Fri, May 31, 2019 at 6:52 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>>> 
>>> Machine boots till login prompt and then panics few seconds later.
>>> 
>>> Last known next build was May 24th. Will attempt few builds till May 
>>> 30 to narrow down this problem.
>> 
>> My CI was fine with next-20190529 (9a15d2e3fd03e3).
>> 
>> cheers
> 
> Hi Sachin,
> It looks this patch may fix the issue:
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flkml.org%2Flkml%2F2019%2F5%2F30%2F1630&amp;data=02%7C01%7Cv-lide%40microsoft.com%7C66e1ef6017aa461703f808d6e7d148cd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636951283393233385&amp;sdata=IJFhtvL2Bd87HCoMZ7oWL%2Bar6NY%2FfPbmdCZMT%2BJz5t4%3D&amp;reserved=0 , but I'm not sure.

It does not help fix the kernel panic issue, but it fixes the get_swap_device warning messages during the boot.

Thanks
-Sachin

  reply	other threads:[~2019-06-03  3:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31 13:00 [next-20190530] Boot failure on PowerPC Sachin Sant
2019-05-31 13:52 ` Michael Ellerman
2019-05-31 18:13   ` Dexuan-Linux Cui
2019-06-03  3:11     ` Sachin Sant
2019-06-03  3:23       ` Lili Deng (Wicresoft North America Ltd) [this message]
2019-06-03  7:15         ` Lili Deng (Wicresoft North America Ltd)

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=KL1P15301MB02948DA3C780A2DC4A145E0F9E140@KL1P15301MB0294.APCP153.PROD.OUTLOOK.COM \
    --to=v-lide@microsoft.com \
    --cc=decui@microsoft.com \
    --cc=dexuan.linux@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sachinp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).