Bug 1087596 - [abrt] WARNING: CPU: 1 PID: 206 at drivers/gpu/drm/drm_mm.c:211 drm_mm_reserve_node+0x132/0x190 [drm]()
Summary: [abrt] WARNING: CPU: 1 PID: 206 at drivers/gpu/drm/drm_mm.c:211 drm_mm_reserv...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:eb5d9a0b433c02184ee3367f662...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-14 18:28 UTC by Filipe Rosset
Modified: 2016-07-19 11:21 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 11:21:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (111.49 KB, text/plain)
2014-04-14 18:28 UTC, Filipe Rosset
no flags Details

Description Filipe Rosset 2014-04-14 18:28:37 UTC
Description of problem:
reboot w/ kernel 3.15.0-0.rc0.git12.2.fc21.x86_64

Additional info:
reporter:       libreport-2.2.1
WARNING: CPU: 1 PID: 206 at drivers/gpu/drm/drm_mm.c:211 drm_mm_reserve_node+0x132/0x190 [drm]()
no hole found for node 0x1000000 + 0x640000
Modules linked in: firewire_ohci firewire_core pata_acpi(+) crc_itu_t sky2 i915(+) i2c_algo_bit drm_kms_helper drm i2c_core video
CPU: 1 PID: 206 Comm: systemd-udevd Not tainted 3.15.0-0.rc0.git12.2.fc21.x86_64 #1
Hardware name: Apple Inc. MacBook4,1/Mac-F22788A9, BIOS     MB41.88Z.00C1.B00.0802091535 02/09/08
 0000000000000000 00000000ee746f3c ffff88003f6e3768 ffffffff81700dce
 ffff88003f6e37b0 ffff88003f6e37a0 ffffffff81089f6d ffff88013836e978
 0000000000000000 0000000001000000 ffff88003fe80b98 ffff88013836e978
Call Trace:
 [<ffffffff81700dce>] dump_stack+0x45/0x56
 [<ffffffff81089f6d>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff81089fec>] warn_slowpath_fmt+0x5c/0x80
 [<ffffffffa00310c2>] drm_mm_reserve_node+0x132/0x190 [drm]
 [<ffffffff811d22fe>] ? kmem_cache_alloc_trace+0x1ee/0x220
 [<ffffffffa00b55a8>] ? i915_gem_object_create_stolen_for_preallocated+0x78/0x2d0 [i915]
 [<ffffffffa00b55ce>] i915_gem_object_create_stolen_for_preallocated+0x9e/0x2d0 [i915]
 [<ffffffffa00e6d06>] intel_modeset_init+0x926/0x12e0 [i915]
 [<ffffffffa011164f>] i915_driver_load+0xd5f/0xf70 [i915]
 [<ffffffff81703484>] ? __schedule+0x2c4/0x770
 [<ffffffff81468c77>] ? get_device+0x17/0x30
 [<ffffffff8146e8c5>] ? klist_class_dev_get+0x15/0x20
 [<ffffffff816f46f2>] ? klist_add_tail+0x32/0x40
 [<ffffffff8146a66b>] ? device_add+0x1db/0x6d0
 [<ffffffffa00305d7>] ? drm_sysfs_device_add+0xd7/0x120 [drm]
 [<ffffffffa002c86d>] drm_dev_register+0xad/0x100 [drm]
 [<ffffffffa002f579>] drm_get_pci_dev+0x89/0x210 [drm]
 [<ffffffffa008e60b>] i915_pci_probe+0x3b/0x60 [i915]
 [<ffffffff8139d125>] local_pci_probe+0x45/0xa0
 [<ffffffff8139e4b9>] pci_device_probe+0xf9/0x150
 [<ffffffff8146db0c>] driver_probe_device+0x9c/0x3d0
 [<ffffffff8146df0b>] __driver_attach+0x8b/0x90
 [<ffffffff8146de80>] ? __device_attach+0x40/0x40
 [<ffffffff8146b833>] bus_for_each_dev+0x73/0xc0
 [<ffffffff8146d55e>] driver_attach+0x1e/0x20
 [<ffffffff8146d100>] bus_add_driver+0x180/0x250
 [<ffffffffa015f000>] ? 0xffffffffa015efff
 [<ffffffff8146e5b4>] driver_register+0x64/0xf0
 [<ffffffffa015f000>] ? 0xffffffffa015efff
 [<ffffffff8139c9dc>] __pci_register_driver+0x4c/0x50
 [<ffffffffa002f80a>] drm_pci_init+0x10a/0x140 [drm]
 [<ffffffffa015f000>] ? 0xffffffffa015efff
 [<ffffffffa015f06a>] i915_init+0x6a/0x6c [i915]
 [<ffffffff81002162>] do_one_initcall+0xf2/0x1b0
 [<ffffffff8105a753>] ? set_memory_nx+0x43/0x50
 [<ffffffff81106f93>] load_module+0x2043/0x25f0
 [<ffffffff81102930>] ? store_uevent+0x70/0x70
 [<ffffffff811f4f07>] ? kernel_read+0x57/0x90
 [<ffffffff81107706>] SyS_finit_module+0xa6/0xe0
 [<ffffffff81710b29>] system_call_fastpath+0x16/0x1b

Comment 1 Filipe Rosset 2014-04-14 18:28:43 UTC
Created attachment 886230 [details]
File: dmesg

Comment 2 Jaroslav Reznik 2015-03-03 15:42:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 3 Fedora End Of Life 2016-07-19 11:21:56 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.