Won't boot from FC Qlogic qla2312

Bug #375999 reported by Stephen Pearson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Ubuntu Release: Jaunty 9.04

I installed Jaunty onto a HP bl25p blade, with a 60GB root disk on an EVA8000 connected via two Qlogic qla2312 cards (we have two paths to the disk). The live environment can see the disk, and appeared to install the os fine, however the system will not boot. I've tried upgrading from within the rescue environment, but to no avail. After grub I see:

[ 62.450036] qla2xxx 0000:06:01.0: Firmware image unavailable.
 [ 62.450115] qla2xxx 0000:06:01.0: Firmware images can be retrieved from:
    ftp://ftp.qlogic.com/outgoing/linux/firmware/.

Shortly after this I get dropped into initramfs.

There seem to be a couple of reasons why this might be happening. Firstly the /lib/firmware directory is not included in the initramfs generated by "updaet-initramfs -c -k all". This can be bodged by copying the firmware in /lib/firmware into /lib/firmware/<KERNELVER> and running update-initramfs again.

A second problem seems to be that the hotplug event (generated when the qla2xxx driver is loaded and calls request_firmware) is never handled. Proof of this is that I can simulate the event handler manually in initramfs as follows:

echo 1 > /sys/class/firmware/<DEV>/loading
cat qla2300_fw.bin > /sys/class/firmware/<DEV>/data
echo 0 > /sys/class/firmware/<DEV>/loading

Then the root disk appears as /dev/sda1.

Revision history for this message
Kurt Wall (kwall) wrote :

Thanks for reporting this bug and helping to improve Ubuntu. Please review https://bugs.launchpad.net/ubuntu/+source/udev/+bug/328550 and see if the issue and workaround described there will address the issue you have with firmware not loading at boot.

Regards,

Kurt

affects: ubuntu → udev (Ubuntu)
Changed in udev (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.