Bug 716368 - [abrt] kernel: BUG: sleeping function called from invalid context at mm/dmapool.c:314
Summary: [abrt] kernel: BUG: sleeping function called from invalid context at mm/dmapo...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d2f57ba5f9d01ca9c0763fc872d...
: 710800 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-24 08:09 UTC by John
Modified: 2013-01-10 08:20 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 05:58:26 UTC
Type: ---


Attachments (Terms of Use)

Description John 2011-06-24 08:09:04 UTC
abrt version: 2.0.1
architecture:   x86_64
cmdline:        ro root=/dev/mapper/vg_250Gb-lv_250Gb_root rd_LUKS_UUID=luks-b57aec87-f7df-4bf8-9f40-21243858a37b rd_LUKS_UUID=luks-8ba99765-5a64-40f2-9f08-7dd4ce010147 rd_MD_UUID=eb349241:80fc37aa:c0d852fb:9ea58c87 rd_MD_UUID=c4406a90:398f4ee1:e2955ad1:28b9e187 rd_LVM_LV=vg_250Gb/lv_250Gb_root rd_LVM_LV=vg_250Gb/lv_250Gb_swap rd_LVM_LV=vg_750Gb/lv_750Gb rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
comment:        switching on wifi
component:      kernel
kernel:         2.6.38.8-32.fc15.x86_64
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         BUG: sleeping function called from invalid context at mm/dmapool.c:314
reported_to:    kerneloops: URL=http://submit.kerneloops.org/submitoops.php
time:           Fri Jun 17 11:11:15 2011

backtrace:
:BUG: sleeping function called from invalid context at mm/dmapool.c:314
:in_atomic(): 0, irqs_disabled(): 1, pid: 10966, name: modprobe
:Pid: 10966, comm: modprobe Not tainted 2.6.38.8-32.fc15.x86_64 #1
:Call Trace:
: [<ffffffff81047d33>] __might_sleep+0xeb/0xf0
: [<ffffffff81104ac0>] dma_pool_alloc+0x38/0x25c
: [<ffffffff813502df>] ehci_qtd_alloc+0x1d/0x5e
: [<ffffffff813507b9>] qh_urb_transaction+0x2a/0x2f1
: [<ffffffff8123d0bf>] ? swiotlb_tbl_map_single+0x1d4/0x1e6
: [<ffffffff81355d7b>] ehci_urb_enqueue+0x7c/0xced
: [<ffffffff8123d10b>] ? map_single+0x3a/0x45
: [<ffffffff8123ccd5>] ? swiotlb_dma_mapping_error+0x15/0x23
: [<ffffffff8133f7ea>] usb_hcd_submit_urb+0x8f0/0x91b
: [<ffffffffa04539b6>] ? AddToURBList+0xa3/0xe5 [QCUSBNet2kSony]
: [<ffffffff81111621>] ? kmem_cache_alloc_trace+0xc6/0xd8
: [<ffffffff81340556>] usb_submit_urb+0x301/0x313
: [<ffffffffa0453ca7>] WriteSync+0x1fc/0x3e2 [QCUSBNet2kSony]
: [<ffffffffa0454115>] GetClientID+0xde/0x272 [QCUSBNet2kSony]
: [<ffffffff810615dd>] ? msleep+0x1b/0x22
: [<ffffffffa0454e68>] SetupQMIWDSCallback+0x54/0x202 [QCUSBNet2kSony]
: [<ffffffffa0455224>] RegisterQMIDevice+0x9b/0x20b [QCUSBNet2kSony]
: [<ffffffffa0451fd6>] QCUSBNetProbe+0x263/0x27c [QCUSBNet2kSony]
: [<ffffffff813441d6>] usb_probe_interface+0x14a/0x1b7
: [<ffffffff812e69e5>] driver_probe_device+0x124/0x1ff
: [<ffffffff812e6b1a>] __driver_attach+0x5a/0x7e
: [<ffffffff812e6ac0>] ? __driver_attach+0x0/0x7e
: [<ffffffff812e5a86>] bus_for_each_dev+0x53/0x89
: [<ffffffff812e65f2>] driver_attach+0x1e/0x20
: [<ffffffff812e6204>] bus_add_driver+0xe2/0x235
: [<ffffffff812e6d03>] driver_register+0x98/0x105
: [<ffffffff813432da>] usb_register_driver+0x94/0x158
: [<ffffffffa045c000>] ? QCUSBNetModInit+0x0/0x95 [QCUSBNet2kSony]
: [<ffffffffa045c08d>] QCUSBNetModInit+0x8d/0x95 [QCUSBNet2kSony]
: [<ffffffff810020a4>] do_one_initcall+0x7f/0x137
: [<ffffffff81085329>] sys_init_module+0xa6/0x1e4
: [<ffffffff81009bc2>] system_call_fastpath+0x16/0x1b

event_log:
:2011-06-24-12:09:32> Submitting oops report to http://submit.kerneloops.org/submitoops.php
:2011-06-24-12:09:38  Kernel oops report was uploaded

Comment 1 Chuck Ebbert 2011-06-27 05:46:22 UTC
*** Bug 710800 has been marked as a duplicate of this bug. ***

Comment 2 Chuck Ebbert 2011-06-27 05:49:48 UTC
Where did this driver "QCUSBNet2kSony" come from? It looks like it is the cause of this problem, and we don't provide it.

Comment 3 Matthew Garrett 2011-06-27 05:58:26 UTC
It's a driver for the native network interface mode on Gobi 2000 devices. I don't think we can do anything about this one.


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