public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Sudhakar Pannerselvam <sudhakarp@inmage.net>
Cc: "Moger, Babu" <Babu.Moger@lsi.com>,
	device-mapper development <dm-devel@redhat.com>,
	linux-scsi@vger.kernel.org
Subject: RE: [dm-devel] RE: qla2xxx 0000:03:0c.0: Firmware image unavailable
Date: Fri, 23 Jan 2009 09:04:17 -0600	[thread overview]
Message-ID: <1232723057.3250.21.camel@localhost.localdomain> (raw)
In-Reply-To: <D4B83214B57CAC4499F1114D069E451A01A7D765@bunker.inside.abhaisystems.com>

On Thu, 2009-01-22 at 22:22 -0800, Sudhakar Pannerselvam wrote:
> As James mentioned earlier, this is a distribution issue. I had seen
> this issue with redhat. If you observe redhat distro qlogic drivers,
> they compile firmware files along with the driver and hence they
> wouldn't observe this issue when they load through initrd as there is no
> firmware loading procedure through hotplug interface, whereas if you
> compile qlogic driver by hand without inbuilt firmware files and using
> distro's like redhat, you would encounter this issue. This has to be
> addressed in nash hotplug code. 

OK, there is one little wrinkle with Red Hat:  nash is a sort of all in
one process and it keeps going wrong.  I've opened a few bugs with red
hat about nash over the years with hotplug issues, which this is, but
they always ignore them and then close them when the distro goes end of
life.

The way I fixed my RH nash problems was to boot the RH distro with a
debian created initrd ... which is a bit of a time consuming hack, but
it worked.

These problems should be going away when Dave Jones finally kills off
nash in his initrd/boot system rewrite.

James



  reply	other threads:[~2009-01-23 15:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06  4:05 [PATCH] Make sure the state of a path is set properly when controller is swapped from passive to active Chandra Seetharaman
2008-11-10 23:17 ` [PATCH] scsi_dh: Adding LSI vendor and product ids in rdac device list Moger, Babu
2008-11-24  0:04   ` James Bottomley
2008-11-24 15:06     ` Moger, Babu
2008-11-11  0:45 ` DM does not activate the paths if there are more than one path in path group during failover Moger, Babu
2008-11-11  0:59   ` Alasdair G Kergon
2008-11-11 17:13     ` Moger, Babu
2008-11-11 21:00       ` Chandra Seetharaman
2008-11-13 23:48       ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] DM does not activate the paths if there are more than one path in path group during failover") Chandra Seetharaman
2008-11-14  0:12         ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: " Alasdair G Kergon
2008-11-14 19:08           ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] " Chandra Seetharaman
2008-11-14 19:34             ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: " Alasdair G Kergon
2008-11-14 20:24               ` [RFC][PATCH] Handle multipath paths in a path group properly during pg_init (was "RE: [dm-devel] " Chandra Seetharaman
2008-11-11  2:06   ` DM does not activate the paths if there are more than one path in path group during failover Chandra Seetharaman
2008-11-11 17:07     ` Moger, Babu
2008-11-11 17:10       ` Chandra Seetharaman
2008-11-11 17:28         ` Moger, Babu
2009-01-22  0:00 ` qla2xxx 0000:03:0c.0: Firmware image unavailable Moger, Babu
2009-01-22  0:26   ` Seokmann Ju
2009-01-22 14:14     ` Moger, Babu
2009-01-22 14:39       ` Sudhakar Pannerselvam
2009-01-22 15:20         ` Moger, Babu
2009-01-22 16:46           ` Dave Holland
2009-01-23  0:15             ` [dm-devel] " Moger, Babu
2009-01-23  6:22               ` Sudhakar Pannerselvam
2009-01-23 15:04                 ` James Bottomley [this message]
2009-01-25  4:22                   ` Mike Snitzer
2009-01-22 14:56       ` James Bottomley

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=1232723057.3250.21.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Babu.Moger@lsi.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sudhakarp@inmage.net \
    /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