public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: James.Smart@Emulex.Com
Cc: andrew.vasquez@qlogic.com, linux-scsi@vger.kernel.org, akpm@osdl.org
Subject: Re: still BUG's for smp_processor_id() on interrupt
Date: Wed, 9 Feb 2005 10:26:01 -0800	[thread overview]
Message-ID: <20050209182601.GA7023@us.ibm.com> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C12EB58@xbl3.ma.emulex.com>

On Wed, Feb 09, 2005 at 01:13:44PM -0500, James.Smart@Emulex.Com wrote:
> This looks suspiciously like the oops trace that I saw when
> loading/unloading driver a couple of times. Make sure you have the
> following patches.
> 
> http://marc.theaimsgroup.com/?l=linux-scsi&m=110729104720492&w=2
> http://marc.theaimsgroup.com/?l=linux-scsi&m=110737816906830&w=2

Thanks James -

Yes, it was a driver reload (after applying Andrew V's patch, rmmod
qla2300 and then insmod qla2300).

I had found the second patch "fix the fix for multiple HBA problem with
transport" and verified it is in mainline. 

But missed the first one "fix HBA removal problem with transport classes",
plus it is NOT in mainline.

I applied and no more oops (and no BUGs using _smp_processor_id()).

-- Patrick Mansfield

  reply	other threads:[~2005-02-09 18:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 18:13 still BUG's for smp_processor_id() on interrupt James.Smart
2005-02-09 18:26 ` Patrick Mansfield [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-09  1:09 Patrick Mansfield
2005-02-09  6:44 ` Andrew Vasquez
2005-02-09 17:22   ` Patrick Mansfield

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=20050209182601.GA7023@us.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=James.Smart@Emulex.Com \
    --cc=akpm@osdl.org \
    --cc=andrew.vasquez@qlogic.com \
    --cc=linux-scsi@vger.kernel.org \
    /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