Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
=Comment: #0=================================================
Breno Henrique Leitao <leitao.ibm.com> -
On a dbench traffic, cxgb4i is crashing, due a iommu_alloc() failure.
It seems that there is a memory leak.
Giving the following error:
iommu_alloc failed, tbl c00000007ec0b700 vaddr c000000042d0c000 npages 2
iommu_alloc failed, tbl c00000007ec0b700 vaddr c000000042d0c000 npages 2
iommu_alloc failed, tbl c00000007ec0b700 vaddr c000000042d0c000 npages 2
iommu_alloc failed, tbl c00000007ec0b700 vaddr c000000042d0c000 npages 2
iommu_alloc failed, tbl c00000007ec0b700 vaddr c000000042d0c000 npages 2
iommu_alloc failed, tbl c00000007ec0b700 vaddr c000000042d0c000 npages 2
Contact Information = brenohl.com
---uname output---
Red hat 6.1 kernel (alpha 1)
Machine Type = pSeries
---Debugger---
A debugger is not configured
---Kernel - IO Component Data---
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
*Additional Instructions for brenohl.com:
-Attach sysctl -a output output to the bug.
=Comment: #2=================================================
Timothy P. Noonan <tpnoonan.com> -
HI Red Hat, Once the RHBZ is opened can you let Chelsio see the RHBZ as well? Thanks
=Comment: #4=================================================
JASON J. SPIETH <spieth.com> -
1.Server architecture(s) (please list all effected) (x86/POWER6/Z/etc.):
Power
2.Server type (9117-MMA/HS20/s390/etc.):
n/a
3.General component (desktop/kernel/base OS/dev tools/etc.):
kernel
4.Other components involved (ixgbe/java/emulex/etc.):
no
5.Does the server have the latest GA firmware?
yes
6.Has the problem been shown to occur on more than one system?
yes
7.Is a tested patch available?
no
If yes to the above, has it been approved upstream?
n/a
8.What is the latest official Red Hat build on which this bug has been
seen?
RHEL 6.1 Alpha
------- Comment From leitao.ibm.com 2011-03-24 11:35 EDT-------
I also tested on upstream kernel and this problem also happens.
Also, I tested using open iscsi (iscsi_tcp), and a similar problem also happen. Thus, it could be a cxgb4 NIC issue (instead of cxgb4i iscsi issue).
This is likely due to missing support for CONFIG_NEED_DMA_MAP_STATE, which chelsio has provided a workaround for. I'll be updating cxgb4 as soon as testing is done. There are test kernel links available in bz 647006 comment 69
FYI, we got the -124 kernel source bits from IBM and tested it on P7 system and am not seeing this issue. So far, transfered ~200G data already.
I did see the error if the cxgb4 patch regarding CONFIG_NEED_DMA_MAP_STATE is not included.
------- Comment From leitao.ibm.com 2011-04-04 08:06 EDT-------
> Hm, this is still occuring upstream as well, I take it? (just saw what you said
> in comment 2). Which upstream kernel version are you using?
Well, I tested it on 2.6.37 and I saw the problem.
------- Comment From tpnoonan.com 2011-04-06 13:31 EDT-------
HiChelsio/Breno, It's unclear from he last few comments if there is a fix, is there? Thanks
------- Comment From leitao.ibm.com 2011-04-06 16:13 EDT-------
> HiChelsio/Breno, It's unclear from he last few comments if there is a fix, is
> there? Thanks
Hi,
Yes, we finally see this problem disappear in the last (-128) kernel.
Thanks
Breno