Bug 1079662 - [abrt] WARNING: CPU: 0 PID: 187 at lib/dma-debug.c:950 check_for_stack+0xa0/0x100() [NEEDINFO]
Summary: [abrt] WARNING: CPU: 0 PID: 187 at lib/dma-debug.c:950 check_for_stack+0xa0/0...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:786077f5a53e9d406293f564b92...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-22 19:26 UTC by michael.c.thiel
Modified: 2014-06-23 14:48 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-23 14:48:58 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (60.92 KB, text/plain)
2014-03-22 19:26 UTC, michael.c.thiel
no flags Details

Description michael.c.thiel 2014-03-22 19:26:51 UTC
Additional info:
reporter:       libreport-2.2.0
WARNING: CPU: 0 PID: 187 at lib/dma-debug.c:950 check_for_stack+0xa0/0x100()
uhci_hcd 0000:00:1d.3: DMA-API: device driver maps memory fromstack [addr=ffff880113779d68]
Modules linked in: video ata_generic mxm_wmi i2c_algo_bit pata_acpi drm_kms_helper ttm drm i2c_core wmi ums_cypress usb_storage
CPU: 0 PID: 187 Comm: usb-storage Not tainted 3.13.6-200.fc20.x86_64+debug #1
Hardware name: Hewlett-Packard HP xw4300 Workstation/0A00h, BIOS 786D3 v01.08 03/10/2006
 0000000000000009 ffff8801137799a0 ffffffff81769454 ffff8801137799e8
 ffff8801137799d8 ffffffff8107887d ffff880118893470 ffff880118888d70
 ffff880113779d68 ffff880118893470 ffffffff81c29020 ffff880113779a38
Call Trace:
 [<ffffffff81769454>] dump_stack+0x4d/0x66
 [<ffffffff8107887d>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff810788ec>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffff813b4710>] check_for_stack+0xa0/0x100
 [<ffffffff813b4ab0>] debug_dma_map_page+0x100/0x140
 [<ffffffff8152ce80>] usb_hcd_map_urb_for_dma+0x5d0/0x700
 [<ffffffff8152d19d>] usb_hcd_submit_urb+0x1ed/0xaf0
 [<ffffffff810d2ec7>] ? __lock_is_held+0x57/0x80
 [<ffffffff8110aa59>] ? __module_address+0xe9/0x130
 [<ffffffff8110f086>] ? is_module_address+0x16/0x30
 [<ffffffff810d280c>] ? static_obj+0x3c/0x50
 [<ffffffff8152eba9>] usb_submit_urb+0x1f9/0x470
 [<ffffffffa0000f5f>] usb_stor_msg_common+0xaf/0x160 [usb_storage]
 [<ffffffff8176e2eb>] ? wait_for_completion_interruptible_timeout+0xfb/0x130
 [<ffffffffa0001332>] usb_stor_ctrl_transfer+0xa2/0xd0 [usb_storage]
 [<ffffffffa0001b0e>] usb_stor_CB_transport+0x4e/0x250 [usb_storage]
 [<ffffffffa00020b4>] usb_stor_invoke_transport+0x254/0x550 [usb_storage]
 [<ffffffffa0000e45>] usb_stor_ufi_command+0x55/0xa0 [usb_storage]
 [<ffffffffa0002d73>] usb_stor_control_thread+0x173/0x290 [usb_storage]
 [<ffffffffa0002c00>] ? fill_inquiry_response+0x20/0x20 [usb_storage]
 [<ffffffffa0002c00>] ? fill_inquiry_response+0x20/0x20 [usb_storage]
 [<ffffffff810a437f>] kthread+0xff/0x120
 [<ffffffff810a4280>] ? insert_kthread_work+0x80/0x80
 [<ffffffff8177c43c>] ret_from_fork+0x7c/0xb0
 [<ffffffff810a4280>] ? insert_kthread_work+0x80/0x80

Potential duplicate: bug 977558

Comment 1 michael.c.thiel 2014-03-22 19:26:55 UTC
Created attachment 877638 [details]
File: dmesg

Comment 2 Justin M. Forbes 2014-05-21 19:36:55 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2014-06-23 14:48:58 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.