Bug 766921
Summary: | [abrt] kernel: WARNING: at lib/dma-debug.c:930 check_for_stack+0xb3/0xf0() | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Josef Schafer <josef.schafer> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, rh-bugzilla, sgruszka |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:b19cd4e918559b252bdfebc71de56e40e3e8413b | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-02-26 12:26:42 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
Josef Schafer
2011-12-12 19:41:21 UTC
We indeed map stack memory for DMA in logi_dj_recv_switch_to_dj_mode() and logi_dj_recv_query_paired_devices(). But I do not see why this is a problem, we wait until DMA finish before we exit from both functions ... Just booted my fedora 17 test OS Package: kernel OS Release: Fedora release 17 (Rawhide) Hi, For me, this issue only occurs when I switch from kernel 3.1.x (Fedora 16) to 3.2.x (Fedora 17) c.q. usb-generic driver to hid_logitech_dj driver and had total system freezes after reboot from 3.2.x to 3.1.x. Reboots from 3.2.x to 3.2.x and from 3.1.x to 3.1.x are okay. Martin Kho Hi, With the latest kernel (3.2.0-2.fc17.x86_64) I don't see the DMA message. So, for me at least, it seems to be solved. Thanks, Martin Kho (In reply to comment #4) > Hi, > > With the latest kernel (3.2.0-2.fc17.x86_64) I don't see the DMA message. So, > for me at least, it seems to be solved. No, that kernel just has the debug options disabled so the warning goes away. The underlying problem is still present. Actually I do not think there is any problem here. We use stack memory for DMA, but we wait on function that allocate stack until DMA finish. So this time issue is a DMA API debugger false positive. |