Ubuntu
linux package

qla2xxx broken on boot after upgrade to lucid

Bug #654080 reported by James Troup
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After upgrading a server to lucid, it no longer discovers the DAS array attached via a qla2xxx HBA. If I rmmod and modprobe qla2xxx after boot then the DAS array is found just fine. I've attached two dmesgs: one directly after boot, and and one after I ran rmmod+modprobe.

Revision history for this message
James Troup (elmo) wrote :
Revision history for this message
James Troup (elmo) wrote :
Revision history for this message
James Troup (elmo) wrote :
Revision history for this message
James Troup (elmo) wrote :
Revision history for this message
James Troup (elmo) wrote :
tags: added: regression-potential
Revision history for this message
James Troup (elmo) wrote :

Sorry I forgot to add this server was previously running on both dapper and hardy without this issue.

Revision history for this message
James Troup (elmo) wrote :

and apparently I'm just impatient. Given enough time it'll eventually recover and find the array by itself. It takes nearly 5 minutes to do so though. (This was only possible, I think, because I went through and made all the fstab entries relating to this array be 'noauto' - the machine wouldn't boot when they weren't, so this is still a pretty bad regression, IMO)

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Jeremy Foshee (jeremyfoshee)
tags: removed: regression-potential
penalvch (penalvch)
tags: added: lucid needs-upstream-testing regression-release
Revision history for this message
penalvch (penalvch) wrote :

James Troup, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 654080

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: needs-kernel-logs
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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