Bug 759912 - [abrt] kernel: BUG: scheduling while atomic: modprobe/150/0x10000200
Summary: [abrt] kernel: BUG: scheduling while atomic: modprobe/150/0x10000200
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0320b9b2a2baa0febec6b622ac2...
: 771763 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-04 20:46 UTC by Adrian Saftoiu
Modified: 2013-02-13 12:45 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 12:45:11 UTC
Type: ---


Attachments (Terms of Use)
File: smolt_data (5.36 KB, text/plain)
2011-12-04 20:46 UTC, Adrian Saftoiu
no flags Details
File: backtrace (2.29 KB, text/plain)
2011-12-04 20:46 UTC, Adrian Saftoiu
no flags Details

Description Adrian Saftoiu 2011-12-04 20:46:48 UTC
libreport version: 2.0.7
abrt_version:   2.0.4.981
cmdline:        BOOT_IMAGE=/vmlinuz-3.1.0-7.fc16.x86_64 root=/dev/mapper/vg_adriandelllaptop-lv_root ro rd.md=0 rd.dm=0 rd.lvm.lv=vg_adriandelllaptop/lv_root KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.lvm.lv=vg_adriandelllaptop/lv_swap rd.luks=0 LANG=en_US.UTF-8
event_log:      2011-12-04-21:44:43> Smolt profile successfully saved
kernel:         undefined
reason:         BUG: scheduling while atomic: modprobe/150/0x10000200
time:           Sun 04 Dec 2011 07:22:35 PM CET

backtrace:      Text file, 2341 bytes
smolt_data:     Text file, 5485 bytes

Comment 1 Adrian Saftoiu 2011-12-04 20:46:52 UTC
Created attachment 540432 [details]
File: smolt_data

Comment 2 Adrian Saftoiu 2011-12-04 20:46:54 UTC
Created attachment 540433 [details]
File: backtrace

Comment 3 Josh Boyer 2011-12-05 14:45:48 UTC
BUG: scheduling while atomic: modprobe/150/0x10000200
Modules linked in: nouveau(+) ttm drm_kms_helper drm i2c_algo_bit i2c_core mxm_wmi wmi video
Pid: 150, comm: modprobe Not tainted 3.1.0-7.fc16.x86_64 #1
Call Trace:
 [<ffffffff814ac9fd>] __schedule_bug+0x5d/0x62
 [<ffffffff814b4053>] __schedule+0x88/0x669
 [<ffffffff81226c80>] ? number+0x13a/0x256
 [<ffffffffa00a1f2b>] ? nouveau_i2c_init+0x99/0x32b [nouveau]
 [<ffffffff810525d3>] __cond_resched+0x28/0x34
 [<ffffffff814b4690>] _cond_resched+0x19/0x22
 [<ffffffff811195c6>] kmem_cache_alloc_trace+0x35/0xc5
 [<ffffffffa00a1f2b>] nouveau_i2c_init+0x99/0x32b [nouveau]
 [<ffffffffa00a22b6>] nouveau_i2c_find+0xc8/0xe2 [nouveau]
 [<ffffffffa0099502>] init_i2c_device_find+0xeb/0xf3 [nouveau]
 [<ffffffffa009b4ca>] init_zm_i2c_byte+0xbb/0x202 [nouveau]
 [<ffffffffa00988f9>] ? bios_wr32+0x31/0xa6 [nouveau]
 [<ffffffffa009be90>] parse_init_table+0xfe/0x1f1 [nouveau]
 [<ffffffffa009f2fb>] nouveau_bios_run_init_table+0x5f/0x81 [nouveau]
 [<ffffffffa009f83e>] nouveau_bios_run_display_table+0x521/0x532 [nouveau]
 [<ffffffffa009fb80>] nouveau_run_vbios_init+0x300/0x31a [nouveau]
 [<ffffffffa00a15ad>] nouveau_bios_init+0x1a13/0x1da6 [nouveau]
 [<ffffffff8122046c>] ? ioremap_page_range+0x238/0x298
 [<ffffffffa0089907>] nouveau_card_init+0xfe4/0x14e9 [nouveau]
 [<ffffffffa008a511>] nouveau_load+0x610/0x657 [nouveau]
 [<ffffffffa002f5b0>] drm_get_pci_dev+0x16e/0x26a [drm]
 [<ffffffff81085db7>] ? arch_local_irq_save+0x15/0x1b
 [<ffffffffa00ec78c>] nouveau_pci_probe+0x10/0x12 [nouveau]
 [<ffffffff8123f9b7>] local_pci_probe+0x44/0x75
 [<ffffffff8124051a>] pci_device_probe+0xd0/0xff
 [<ffffffff812de4b7>] driver_probe_device+0x131/0x213
 [<ffffffff812de5f3>] __driver_attach+0x5a/0x7e
 [<ffffffff812de599>] ? driver_probe_device+0x213/0x213
 [<ffffffff812dd53f>] bus_for_each_dev+0x53/0x89
 [<ffffffff812de096>] driver_attach+0x1e/0x20
 [<ffffffff812ddcba>] bus_add_driver+0xd1/0x224
 [<ffffffff812dea97>] driver_register+0x98/0x105
 [<ffffffff81240ddd>] __pci_register_driver+0x56/0xc1
 [<ffffffffa002f736>] drm_pci_init+0x8a/0xef [drm]
 [<ffffffffa0117000>] ? 0xffffffffa0116fff
 [<ffffffffa011704f>] nouveau_init+0x4f/0x51 [nouveau]
 [<ffffffff81002099>] do_one_initcall+0x7f/0x136
 [<ffffffff8108a5dd>] sys_init_module+0x88/0x1d0
 [<ffffffff814bc482>] system_call_fastpath+0x16/0x1b

Comment 4 Ben Skeggs 2012-01-10 04:17:11 UTC
*** Bug 771763 has been marked as a duplicate of this bug. ***

Comment 5 Fedora End Of Life 2013-01-16 12:28:36 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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

Comment 6 Fedora End Of Life 2013-02-13 12:45:14 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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