Bug 478567
Summary: | DMA: Out of SW-IOMMU space for 32768 bytes at device 0000:05:03.0 (firewire) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tobias Mueller <fedora-bugs> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 9 | CC: | jarod, kernel-maint, quintela, stefan-r-rhbz |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.6.27.12-78.2.8.fc9 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-06-10 19:19:26 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: |
Description
Tobias Mueller
2009-01-01 03:55:26 UTC
Strange. There was an IOMMU resource leak in the firewire drivers which is supposed to be fixed in your kernel already: https://bugzilla.redhat.com/show_bug.cgi?id=475156 Hi :) Well, I am willing to track this issue down. I just need some advice or instructions. I boot with swiotlb=512M and I didn't have to reboot due to *this* error since. OK, then it is likely not a leak but just a too small default (64 MB). I'll ask on LKML. Thread on LKML, cc'd LSML: http://lkml.org/lkml/2009/1/20/279 There was indeed still a DMA resource leak in firewire-sbp2. http://lkml.org/lkml/2009/1/27/216 updated patch: http://lkml.org/lkml/2009/1/27/402 patch was merged into Linus' linux-2.6.git a week ago, mailed to kernel.org's stable list just now Jarod, is there a Fedora kernel with patch "firewire: sbp2: fix DMA mapping leak on the failure path" included? Tobias, does such a kernel work OK with default swiotlb size? Hey Stefan :) Thank you very much for your engagement! I'd love to test this, but I have no idea how to install that patched kernel. FWIW: I've updated to F10 recently. The bug assignees will hopefully point you to a respective kernel rpm. Fixed upstream in 2.6.27.10. Sorry, fixed in 2.6.27.16. kernel-2.6.27.19-78.2.30.fc9 is in the updates-testing repostory now. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This ought to be all good in the latest updates kernel for all supported distros now. |