Created attachment 683424 [details] File from /var/log/messages Description of problem: The following error messages apparently coming from mgag200 fills up dmesg: [drm:mgag200_bo_reserve] *ERROR* reserve failed ffff8804231e8c00 [drm:mga_dirty_update] *ERROR* failed to reserve fb bo Then, after countless times, the following message appears in dmesg: [ 3.968011] ------------[ cut here ]------------ [ 3.968015] WARNING: at kernel/smp.c:461 smp_call_function_many+0xbd/0x260() [ 3.968015] Hardware name: S1200BTL [ 3.968019] Modules linked in: mgag200 i2c_algo_bit drm_kms_helper ttm drm crc32c_intel ghash_clmulni_intel i2c_core video [ 3.968020] Pid: 57, comm: kworker/2:1 Not tainted 3.6.10-4.fc18.x86_64 #1 [ 3.968020] Call Trace: [ 3.968023] [<ffffffff8105c8df>] warn_slowpath_common+0x7f/0xc0 [ 3.968024] [<ffffffff8105c93a>] warn_slowpath_null+0x1a/0x20 [ 3.968025] [<ffffffff810b9a0d>] smp_call_function_many+0xbd/0x260 [ 3.968026] [<ffffffff8104b2f0>] ? leave_mm+0x60/0x60 [ 3.968027] [<ffffffff8104b2f0>] ? leave_mm+0x60/0x60 [ 3.968028] [<ffffffff810b9c42>] smp_call_function+0x22/0x30 [ 3.968029] [<ffffffff810b9db8>] on_each_cpu+0x28/0x70 [ 3.968030] [<ffffffff8104b81a>] flush_tlb_kernel_range+0x4a/0x70 [ 3.968032] [<ffffffff811624d4>] __purge_vmap_area_lazy+0x164/0x1c0 [ 3.968034] [<ffffffff8116308e>] free_vmap_area_noflush+0x5e/0x60 [ 3.968035] [<ffffffff8116425f>] remove_vm_area+0x3f/0xb0 [ 3.968036] [<ffffffff811643ae>] __vunmap+0x2e/0x110 [ 3.968037] [<ffffffff811644c5>] vunmap+0x35/0x40 [ 3.968041] [<ffffffffa00a6165>] ttm_bo_kunmap+0xb5/0xd0 [ttm] [ 3.968043] [<ffffffffa00beff0>] mga_dirty_update+0xf0/0x170 [mgag200] [ 3.968044] [<ffffffffa00bf0a8>] mga_imageblit+0x38/0x50 [mgag200] [ 3.968046] [<ffffffff813325b5>] bit_putcs+0x315/0x580 [ 3.968047] [<ffffffffa00befcf>] ? mga_dirty_update+0xcf/0x170 [mgag200] [ 3.968049] [<ffffffffa00bf0a8>] ? mga_imageblit+0x38/0x50 [mgag200] [ 3.968050] [<ffffffff81333227>] ? soft_cursor+0x1d7/0x280 [ 3.968051] [<ffffffff8132c9d0>] ? get_color.isra.14+0x40/0x150 [ 3.968052] [<ffffffff8132e5b3>] fbcon_putcs+0x133/0x170 [ 3.968052] [<ffffffff813322a0>] ? bit_clear_margins+0x180/0x180 [ 3.968053] [<ffffffff8132e8df>] fbcon_redraw.isra.21+0x18f/0x200 [ 3.968054] [<ffffffff813304db>] fbcon_scroll+0x1db/0xd10 [ 3.968057] [<ffffffff8139ccc3>] scrup+0x113/0x120 [ 3.968058] [<ffffffff8139cd70>] lf+0x70/0x80 [ 3.968059] [<ffffffff8139dadc>] vt_console_print+0x27c/0x3a0 [ 3.968061] [<ffffffff8105d5a9>] call_console_drivers.constprop.15+0x99/0x100 [ 3.968062] [<ffffffff8105e613>] console_unlock+0x403/0x440 [ 3.968062] [<ffffffff81332920>] ? bit_clear+0x100/0x100 [ 3.968063] [<ffffffff8132cb48>] fb_flashcursor+0x68/0x160 [ 3.968065] [<ffffffff81078ca7>] process_one_work+0x147/0x4a0 [ 3.968066] [<ffffffff8132cae0>] ? get_color.isra.14+0x150/0x150 [ 3.968067] [<ffffffff8107aa1e>] worker_thread+0x15e/0x480 [ 3.968068] [<ffffffff8107a8c0>] ? manage_workers+0x2f0/0x2f0 [ 3.968070] [<ffffffff8107fde3>] kthread+0x93/0xa0 [ 3.968072] [<ffffffff8162cb84>] kernel_thread_helper+0x4/0x10 [ 3.968073] [<ffffffff8107fd50>] ? kthread_freezable_should_stop+0x70/0x70 [ 3.968074] [<ffffffff8162cb80>] ? gs_change+0x13/0x13 [ 3.968074] ---[ end trace 065318f24c4db0b3 ]--- [ 4.029383] [drm] mga base 0 How reproducible: Always. Booting the system is enough to show the message. Steps to Reproduce: 1. Boot the computer 2. In a terminal, type "dmesg" 3. Done. Actual results: Expected results: Additional info: My hardware: Intel Server Board S1200BTLR Intel Xeon E3-1270v2 16GB DDR ECC Video: Server Engines BMC Note: I am able to use console and graphical modes normally.
Created attachment 683425 [details] Xorg.0.log
Created attachment 683436 [details] output from 'lspci -vv'
UPDATE: Defining detault target to console mode instead of graphical does not changes nothing. The message appear before Xorg startup.
Additional Note: Removing the "rhgb" kernel boot option prevents error messages apeear in dmesg.
The latest kernel and this update fixes the issue for me. https://admin.fedoraproject.org/updates/FEDORA-2013-4960/xorg-x11-drv-mga-1.6.2-6.fc18 Can you try this update, fernando?
The problem is occurring before X starts so how does the updated driver help?
I have not tested yet but I will report back ASAP.
I am still getting the error messages in dmesg, despite using this driver. They seem to be coming before X starts (as noted above).
(In reply to comment #8) > I am still getting the error messages in dmesg, despite using this driver. > They seem to be coming before X starts (as noted above). I noted that I also updated my kernel. What kernel are you using?
okay I'll try and reproduce this here, its a kernel bug, but leave it under -mga as its easier to track for now.
I'm using kernel 3.8.9-200.fc18.x86_64
OK the issue went away in the 3.8 kernels for me. My particular chip is no longer affected. 05:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)
okay I've tracked this down a posted a patch upstream http://lists.freedesktop.org/archives/dri-devel/2013-May/038159.html I'll try and get it into a Fedora kernel soon. it might have gone away if you stopped passing rhgb to the kernel.
(In reply to comment #13) > it might have gone away if you stopped passing rhgb to the kernel. No, it is still there. [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.8.9-200.fc18.x86_64 root=/dev/mapper/luks-foo ro rd.md.uuid=foo rd.lvm=0 rd.dm=0 vconsole.keymap=us quiet rhgb rd.luks.uuid=luks-foo intel_iommu=on nmi_watchdog=0 LANG=en_US.UTF-8
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.