All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dany Madden <drt@linux.ibm.com>
To: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Cc: netdev@vger.kernel.org, Brian King <brking@linux.ibm.com>,
	abdhalee@in.ibm.com, vaish123@in.ibm.com
Subject: Re: [PATCH net 2/3] ibmvnic: Process crqs after enabling interrupts
Date: Fri, 29 Oct 2021 15:23:52 -0700	[thread overview]
Message-ID: <e4d7bd9bdeab64959c25635e16d0bc09@imap.linux.ibm.com> (raw)
In-Reply-To: <20211029220316.2003519-2-sukadev@linux.ibm.com>

On 2021-10-29 15:03, Sukadev Bhattiprolu wrote:
> Soon after registering a CRQ it is possible that we get a fail over or
> maybe a CRQ_INIT from the VIOS while interrupts were disabled.
> 
> Look for any such CRQs after enabling interrupts.
> 
> Otherwise we can intermittently fail to bring up ibmvnic adapters 
> during
> boot, specially in kexec/kdump kernels.
> 
> Fixes: 032c5e82847a ("Driver for IBM System i/p VNIC protocol")
> Reported-by: Vaishnavi Bhat <vaish123@in.ibm.com>
> Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>

Reviewed-by: Dany Madden <drt@linux.ibm.com>

  reply	other threads:[~2021-10-29 22:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 22:03 [PATCH net 1/3] ibmvnic: don't stop queue in xmit Sukadev Bhattiprolu
2021-10-29 22:03 ` [PATCH net 2/3] ibmvnic: Process crqs after enabling interrupts Sukadev Bhattiprolu
2021-10-29 22:23   ` Dany Madden [this message]
2021-10-29 22:03 ` [PATCH net 3/3] ibmvnic: delay complete() Sukadev Bhattiprolu
2021-10-29 22:25   ` Dany Madden
2021-10-29 22:18 ` [PATCH net 1/3] ibmvnic: don't stop queue in xmit Dany Madden
2021-11-01 13:20 ` patchwork-bot+netdevbpf

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=e4d7bd9bdeab64959c25635e16d0bc09@imap.linux.ibm.com \
    --to=drt@linux.ibm.com \
    --cc=abdhalee@in.ibm.com \
    --cc=brking@linux.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=sukadev@linux.ibm.com \
    --cc=vaish123@in.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.