Red Hat Bugzilla – Bug 220246
[RHEL 5.0] qla3xxx panics when eth1 (qla3xxx) is sending pings
Last modified: 2010-03-14 17:27:49 EDT
+++ This bug was initially created as a clone of Bug #217546 +++
QLA3XXX dies when a ping test is performed.
-- Additional comment from email@example.com on 2006-12-19 13:53 EST --
Have you pushed the fixes for this bug into RHEL5, or should we do it?
-- Additional comment from firstname.lastname@example.org on 2006-12-19 16:19 EST --
I have not pushed the updates to RHEL5. Let me clone this BZ for RHEL5 and ask
RH management to make an exception to get this in.
Have the fixes that are in this BZ been pushed upstream? If so, do you have the
I've pushed the changes upstream, but they haven't been committed yet. Having
some trouble getting attention probably because of the release cycle for
2.6.20. I resent them this morning. Take a look at:
Patch 4/5 is the ping test patch. Patch 3/5 adds delay to NVRAM access and is
in the code you have also. The other 3 patches are for 4032 chip support
which we can tackle later.
What are your thoughts to have this as a blocker for RHEL5? The patches are for
the driver only and they are being pushed upstream. The test-case that
reproduces this panic is quite simple:
expr $COUNT \> 65500 1>/dev/null
if [ "$?" == 0 ]; then
COUNT=`expr $COUNT + 1` 1>/dev/null
ping ibm-x232.lab.boston.redhat.com -c 5 -s$COUNT 1>/dev/null 2>/dev/null &
or should this wait until RHEL5 U1?
Konrad, will dependent bug 217546 fix this issue?
Created attachment 144831 [details]
Patch back-ported from BZ 217546.
The BZ 217546 is a RHEL4 U5 bug. This BZ is for RHEL5. To answer your question,
fixing 217546 will NOT fix this issue. But the patch in comment #4 will fix this
Raising the flags to make the management aware of this BZ.
devel_ack. This fixes an easy-to-reproduce panic. The one-line fix is entirely
confined to this (new) driver in RHEL 5.
Patch has been posted on RHKL.
QE ack for RHEL5.
Konrad, does this solve recently created bug 221328?
(In reply to comment #11)
> Konrad, does this solve recently created bug 221328?
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
QE ack for RHEL5. Fix confirmed with 2.6.18-1.3002.el5:
$ grep -r "CONFIG_QLA3XXX" 2.6.18-1.3002.el5-*
2.6.18-1.3002.el5-i686/.config:# CONFIG_QLA3XXX is not set
2.6.18-1.3002.el5-ia64/.config:# CONFIG_QLA3XXX is not set
2.6.18-1.3002.el5-kdump-ppc64/.config:# CONFIG_QLA3XXX is not set
2.6.18-1.3002.el5-PAE-i686/.config:# CONFIG_QLA3XXX is not set
2.6.18-1.3002.el5-ppc64/.config:# CONFIG_QLA3XXX is not set
2.6.18-1.3002.el5-x86_64/.config:# CONFIG_QLA3XXX is not set
2.6.18-1.3002.el5-xen-i686/.config:# CONFIG_QLA3XXX is not set
2.6.18-1.3002.el5-xen-ia64/.config:# CONFIG_QLA3XXX is not set
2.6.18-1.3002.el5-xen-x86_64/.config:# CONFIG_QLA3XXX is not set
kernel-2.6.18-1.3002.el5 included in 20070111.1 and 20070112.3.
Does this issue require documentation in the RHEL5.3 release notes?
If so, please provide a release notes draft in the "Release Notes" field of
this bug. thanks!