From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
sim <sim@linux.vnet.ibm.com>, Oliver <oohall@gmail.com>,
manvanth <manvanth@linux.vnet.ibm.com>,
maurosr <maurosr@linux.vnet.ibm.com>
Subject: Re: [mainline][ppc][bnx2x] watchdog: CPU 80 self-detected hard LOCKUP @ opal_interrupt+0x28/0x70 when module load/unload
Date: Fri, 16 Nov 2018 10:31:51 +0530 [thread overview]
Message-ID: <1542344511.15177.12.camel@abdul> (raw)
In-Reply-To: <87lg5ttyvv.fsf@concordia.ellerman.id.au>
On Fri, 2018-11-16 at 15:44 +1100, Michael Ellerman wrote:
> Abdul Haleem <abdhalee@linux.vnet.ibm.com> writes:
> > On Thu, 2018-11-15 at 16:40 +0530, Abdul Haleem wrote:
> >> On Mon, 2018-09-24 at 15:49 +0530, Abdul Haleem wrote:
> >> > On Mon, 2018-09-24 at 19:35 +1000, Oliver wrote:
> >> > > On Mon, Sep 24, 2018 at 6:56 PM, Abdul Haleem
> >> > > <abdhalee@linux.vnet.ibm.com> wrote:
> >> > > > Greeting's
> >> > > >
> >> > > > bnx2x module load/unload test results in continuous hard LOCKUP trace on
> >> > > > my powerpc bare-metal running mainline 4.19.0-rc4 kernel
> ^^^^^^^^^^
> >>
> >> Warnings also show up on 4.20.0-rc2-next-20181114
> >
> > We have a patch fix available https://patchwork.ozlabs.org/patch/998054/
> >
> > It fixed the problem.
>
> But the bug it fixes wasn't present in 4.19.0-rc4, which is the version
> you originally reported against. Or is that version string not accurate?
Yes, version string wrong. the bug was first seen on linux-next
4.19.0-rc3-next-20180913 and on mainline version 4.19.0-rc8
--
Regard's
Abdul Haleem
IBM Linux Technology Centre
next prev parent reply other threads:[~2018-11-16 5:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 8:56 [mainline][ppc][bnx2x] watchdog: CPU 80 self-detected hard LOCKUP @ opal_interrupt+0x28/0x70 when module load/unload Abdul Haleem
2018-09-24 9:35 ` Oliver
2018-09-24 10:19 ` Abdul Haleem
2018-11-15 11:10 ` Abdul Haleem
2018-11-15 14:16 ` Abdul Haleem
2018-11-16 4:44 ` Michael Ellerman
2018-11-16 5:01 ` Abdul Haleem [this message]
2018-11-16 10:02 ` Michael Ellerman
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=1542344511.15177.12.camel@abdul \
--to=abdhalee@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manvanth@linux.vnet.ibm.com \
--cc=maurosr@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=oohall@gmail.com \
--cc=sim@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.