public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: James Smart <jsmart2021@gmail•com>
To: Abdul Haleem <abdhalee@linux•vnet.ibm.com>,
	linuxppc-dev <linuxppc-dev@lists•ozlabs.org>
Cc: linux-next <linux-next@vger•kernel.org>,
	linux-kernel <linux-kernel@vger•kernel.org>,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	sachinp <sachinp@linux•vnet.ibm.com>,
	manvanth <manvanth@linux•vnet.ibm.com>,
	linux-scsi <linux-scsi@vger•kernel.org>,
	dick.kennedy@broadcom•com,
	"Martin K. Petersen" <martin.petersen@oracle•com>,
	dougmill <dougmill@linux•vnet.ibm.com>,
	Brian King <brking@linux•vnet.ibm.com>
Subject: Re: [linux-next][BUG][driver/scsi/lpfc][10541f] Kernel panics when booting next kernel on my Power 9 box
Date: Wed, 28 Aug 2019 08:22:17 -0700	[thread overview]
Message-ID: <601365f6-c753-96f6-5d61-481f54d95440@gmail.com> (raw)
In-Reply-To: <1566968536.23670.9.camel@abdul>

On 8/27/2019 10:02 PM, Abdul Haleem wrote:
> Greetings,
> 
> linux-next kernel 5.3.0-rc1 failed to boot with kernel Oops on Power 9
> box
> 
> I see a recent changes to lpfc code was from commit
> 10541f03 scsi: lpfc: Update lpfc version to 12.4.0.0
> 
> Recent boot logs:
> 
> [..snip..]

see  https://www.spinics.net/lists/linux-scsi/msg133343.html

It hasn't been tested yet, but appears to be the issue.

-- james

  reply	other threads:[~2019-08-28 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28  5:02 [linux-next][BUG][driver/scsi/lpfc][10541f] Kernel panics when booting next kernel on my Power 9 box Abdul Haleem
2019-08-28 15:22 ` James Smart [this message]
2019-08-28 17:42   ` [linux-next][BUG][driver/scsi/lpfc][c00f62e6] " Abdul Haleem

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=601365f6-c753-96f6-5d61-481f54d95440@gmail.com \
    --to=jsmart2021@gmail$(echo .)com \
    --cc=abdhalee@linux$(echo .)vnet.ibm.com \
    --cc=brking@linux$(echo .)vnet.ibm.com \
    --cc=dick.kennedy@broadcom$(echo .)com \
    --cc=dougmill@linux$(echo .)vnet.ibm.com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-scsi@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=manvanth@linux$(echo .)vnet.ibm.com \
    --cc=martin.petersen@oracle$(echo .)com \
    --cc=sachinp@linux$(echo .)vnet.ibm.com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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