RE: [dm-devel] RE: qla2xxx 0000:03:0c.0: Firmware image unavailable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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. 

One workaround that I could think of, as I mentioned above this is an
issue with nash which is active only when you load qlogic through initrd
mechanism. Check if you really need to compile your qlogic driver as
part of initrd image and recreate initrd image without qlogic module.
Later you could load the qlogic module(again using hotplug mechanism)
when kernel comes alive.

Regards
Sudhakar

> -----Original Message-----
> From: linux-scsi-owner@xxxxxxxxxxxxxxx 
> [mailto:linux-scsi-owner@xxxxxxxxxxxxxxx] On Behalf Of Moger, Babu
> Sent: Friday, January 23, 2009 5:46 AM
> To: device-mapper development
> Cc: linux-scsi@xxxxxxxxxxxxxxx
> Subject: RE: [dm-devel] RE: qla2xxx 0000:03:0c.0: Firmware 
> image unavailable
> 
> 
> Yes, firmware images are in the initrd. I have verified that. 
> 
> Thanks
> Babu Moger 
> 
> -----Original Message-----
> From: dm-devel-bounces@xxxxxxxxxx 
> [mailto:dm-devel-bounces@xxxxxxxxxx] On Behalf Of Dave Holland
> Sent: Thursday, January 22, 2009 10:46 AM
> To: device-mapper development
> Cc: linux-scsi@xxxxxxxxxxxxxxx
> Subject: Re: [dm-devel] RE: qla2xxx 0000:03:0c.0: Firmware 
> image unavailable
> 
> On Thu, Jan 22, 2009 at 08:20:48AM -0700, Moger, Babu wrote:
> > You are right. Looks like qlogic driver loads even before 
> udev hotplug 
> > is functional.  Driver loads successfully when I re-load the driver 
> > after the system in up.  Is there any solution or 
> work-around for this 
> > problem?
> 
> So the problem only happens at boot time? Are you using an 
> initrd, and if so, have you got the firmware images in the 
> initrd image?
> (mkinitramfs, update-initramfs, etc)
> 
> Dave
> --
> ** Dave Holland ** Systems Support -- Infrastructure Management **
> ** 01223 496923 ** The Sanger Institute, Hinxton, Cambridge, 
> UK ** "Your bumper is my crumple zone."
> 
> 
> -- 
>  The Wellcome Trust Sanger Institute is operated by Genome Research 
>  Limited, a charity registered in England with number 1021457 and a 
>  company registered in England with number 2742969, whose registered 
>  office is 215 Euston Road, London, NW1 2BE. 
> 
> --
> dm-devel mailing list
> dm-devel@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/dm-devel
> --
> To unsubscribe from this list: send the line "unsubscribe 
> linux-scsi" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux