Bug 177032
Summary: | Kernel panic when connecting USB device | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Göran Uddeborg <goeran> | ||||
Component: | kernel | Assignee: | Dave Jones <davej> | ||||
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4 | CC: | pfrields, wtogami | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | 2.6.15-1.1830_FC4 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-02-06 17:09:25 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: | |||||||
Attachments: |
|
Description
Göran Uddeborg
2006-01-05 16:01:49 UTC
Please attach a full dmesg (do not drop into the comments box). I suspect that swiotlb saw 4GB and decided not to initialize, but some memory hole or other made a part of memory to move above 4GB. Created attachment 122863 [details]
Output from dmesg
There are two settings in the BIOS concerning DRAM remappings: "S/W DRAM Over
4G Remapping" and a line which is identical except that it starts with "H/W".
They are not mentioned in the printed manual. Both were enabled. I tried to
disable both. That gave me only 3 GB when running, but USB units started to
work.
I see this in dmesg: BIOS-e820: 0000000100000000 - 0000000140000000 (usable) ... Checking aperture... CPU 0: aperture @ 8000000 size 32 MB Aperture from northbridge cpu 0 too small (32 MB) No AGP bridge found Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup This costs you 64 MB of RAM Mapping aperture over 65536 KB of RAM @ 8000000 So, this is an AMD CPU, so swiotlb is not applicable (and it has normal iommu mode). The iommu is enabled, with difficulties, but for some reason it did not work... We need someone who is an Opteron specialist here. Strictly speaking it's not an Opteron but an Athlon 64 X2. (Maybe that is the same thing as far as these things are concerned. I don't know. With this comment I just want to prevent any possible mistakes.) Another aspect of what I guess is the same underlying bug: When I tried to activate the separate network card (05:08.0 in the lcpci listing in comment 0), I again get a crash with the message Kernel panic - not syncing: PCI-DMA: high address but no IOMMU No stack trace this time. I have had the card in the machine for some time without problems. But when I tried to activate it (ONBOOT=yes), then the kernel crashes during startup. As before, if I disable the two BIOS settings things work, but I only get 3 GB of available memory. This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you. The problem seems to be fixed in this release. I could use both the USB camera and the network card, without crashing the machine. |