Bug 220246
| Summary: | [RHEL 5.0] qla3xxx panics when eth1 (qla3xxx) is sending pings | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Konrad Rzeszutek <konradr> | ||||
| Component: | kernel | Assignee: | Konrad Rzeszutek <konradr> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.0 | CC: | andriusb, coughlan, david.somayajulu, dwm, jturner, lcm, mchristi, qlogic-redhat-ext, redhat, rkenna, ron.mercer, sameer.shurpalekar | ||||
| Target Milestone: | --- | Keywords: | EasyFix | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 5.0.0 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-01-15 14:22:27 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 216985, 222067 | ||||||
| Attachments: |
|
||||||
|
Description
Konrad Rzeszutek
2006-12-19 21:24:36 UTC
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: http://www.spinics.net/lists/netdev/msg21646.html 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. Jay,
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:
#!/bin/bash
COUNT=1
while (true)
do
expr $COUNT \> 65500 1>/dev/null
if [ "$?" == 0 ]; then
exit 0;
fi
COUNT=`expr $COUNT + 1` 1>/dev/null
ping ibm-x232.lab.boston.redhat.com -c 5 -s$COUNT 1>/dev/null 2>/dev/null &
done
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. Andrius, 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 issue. 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? No. 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 inclusion. in 2.6.18-1.3002.el5 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! |