Bug 1884 - drm problem at boot
Summary: drm problem at boot
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
: 3326 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-06-21 22:35 CEST by C Verschuuren
Modified: 2012-12-02 14:31 CET (History)
8 users (show)

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments
Dmesg right after startup (123.22 KB, text/x-log)
2011-07-13 17:55 CEST, Thomas Courbon
Details

Description C Verschuuren 2011-06-21 22:35:48 CEST
Whenever i boot up, the boot process complains about a drm problem in relation to the ATI 4850 video card. I have the fglrx driver installed. There seems to be a conflict with a vesa driver. 
During boot there is a problem allocating memory, which repeates itself during about 1-2 minutes. Then i get to the login screen.

The following error message which i found in dmesg might be connected with this problem.

WARNING: at drivers/gpu/drm/radeon/radeon_gart.c:176 radeon_gart_bind+0x1ab/0x1c0 [radeon]()$
Hardware name: System Product Name$
trying to bind memory to unitialized GART !$
Modules linked in: binfmt_misc fuse cpufreq_ondemand cpufreq_conservative cpufreq_powersave powernow_k8 freq_table mperf ppdev dm_mod parport_pc parport asus_atk0110 joydev k8temp thermal edac_core floppy processor fan button evdev pata_atiixp ata_piix ahci libahci libata sd_mod scsi_mod crc_t10dif ext3 jbd uhci_hcd ohci_hcd ehci_hcd usbhid hid usbcore radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core$
Pid: 63, comm: plymouthd Tainted: G        W   2.6.38.7-desktop-1.mga #1$
Call Trace:$
 [<ffffffff81057aff>] ? warn_slowpath_common+0x7f/0xc0$
 [<ffffffff81057bf6>] ? warn_slowpath_fmt+0x46/0x50$
 [<ffffffffa0057ce5>] ? ttm_mem_global_alloc_page+0x55/0x60 [ttm]$
 [<ffffffffa00b6a6b>] ? radeon_gart_bind+0x1ab/0x1c0 [radeon]$
 [<ffffffffa00b4372>] ? radeon_ttm_backend_bind+0x32/0x90 [radeon]$
 [<ffffffffa00587c8>] ? ttm_tt_bind+0x58/0x80 [ttm]$
 [<ffffffffa005a504>] ? ttm_bo_handle_move_mem+0x194/0x3c0 [ttm]$
 [<ffffffff81040600>] ? check_preempt_curr+0x0/0xa0$
 [<ffffffffa005b68e>] ? ttm_bo_move_buffer+0x12e/0x140 [ttm]$
 [<ffffffffa005b736>] ? ttm_bo_validate+0x96/0x120 [ttm]$
 [<ffffffffa005bac6>] ? ttm_bo_init+0x306/0x380 [ttm]$
 [<ffffffffa00b5707>] ? radeon_bo_create+0x147/0x2a0 [radeon]$
 [<ffffffffa00b5460>] ? radeon_ttm_bo_destroy+0x0/0xc0 [radeon]$
 [<ffffffffa00cc76c>] ? radeon_gem_object_create+0x8c/0x120 [radeon]$
 [<ffffffffa00ccbb8>] ? radeon_gem_create_ioctl+0x58/0xd0 [radeon]$
 [<ffffffff8107cfb0>] ? lock_hrtimer_base.clone.25+0x30/0x60$
 [<ffffffffa00212b4>] ? drm_ioctl+0x3e4/0x4c0 [drm]$
 [<ffffffffa00ccb60>] ? radeon_gem_create_ioctl+0x0/0xd0 [radeon]$
 [<ffffffff8107d864>] ? hrtimer_start_range_ns+0x14/0x20$
 [<ffffffff811ea6ba>] ? tomoyo_init_request_info+0x3a/0x70$
 [<ffffffff8115ab89>] ? do_vfs_ioctl+0x99/0x570$
 [<ffffffff8115b0f1>] ? sys_ioctl+0x91/0xa0$
 [<ffffffff81077671>] ? posix_ktime_get_ts+0x11/0x20$
 [<ffffffff81002e92>] ? system_call_fastpath+0x16/0x1b$
---[ end trace 0683a34a160aaed9 ]---$
[drm:radeon_ttm_backend_bind] *ERROR* failed to bind 1772 pages at 0x00000000$
radeon 0000:01:00.0: object_init failed for (7258112, 0x00000002)$
[drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (7258112, 2, 4096, -22)$
Comment 1 mnaud mnaud 2011-06-28 21:56:22 CEST
same behaviour with asus EAH4650 video card on mageia 1 

lspci | grep Radeon
01:00.0 VGA compatible controller: ATI Technologies Inc RV730 PRO [Radeon HD 4650]

lspci -s 01:00.0 -vv
01:00.0 VGA compatible controller: ATI Technologies Inc RV730 PRO [Radeon HD 4650] (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Device 026e
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 18
        Region 0: Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Region 2: Memory at fdae0000 (64-bit, non-prefetchable) [size=64K]
        Region 4: I/O ports at ce00 [size=256]
        [virtual] Expansion ROM at fda00000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: radeon
        Kernel modules: radeon

extract of dmesg :
------------[ cut here ]------------
WARNING: at drivers/gpu/drm/radeon/radeon_gart.c:176 radeon_gart_bind+0x196/0x1a0 [radeon]()
Hardware name: GA-MA790FXT-UD5P
trying to bind memory to unitialized GART !
Modules linked in: rfcomm sco bnep l2cap crc16 vboxnetadp vboxnetflt vboxdrv binfmt_misc loop cpufreq_ond
emand cpufreq_conservative cpufreq_powersave powernow_k8 freq_table mperf kvm_amd kvm ipv6 saa7134_alsa s
nd_hda_codec_hdmi ir_lirc_codec lirc_dev snd_hda_codec_realtek ir_sony_decoder ir_jvc_decoder ir_rc6_deco
der ir_rc5_decoder ir_nec_decoder saa7134 rc_core v4l2_common uvcvideo snd_usb_audio snd_hda_intel btusb 
snd_hda_codec snd_seq_dummy videodev snd_usbmidi_lib snd_rawmidi snd_seq_oss snd_seq_midi_event videobuf_
dma_sg i2c_piix4 bluetooth snd_seq snd_seq_device 8139cp ppdev snd_pcm_oss rfkill sp5100_tco r8169 snd_mi
xer_oss videobuf_core tveeprom 8139too firewire_ohci firewire_core k10temp snd_hwdep parport_pc mii wmi s
nd_pcm snd_timer parport snd soundcore snd_page_alloc floppy sg processor sr_mod button evdev crc_itu_t p
ata_atiixp pata_jmicron dm_snapshot dm_zero dm_mirror dm_region_hash dm_log dm_mod ata_piix ahci libahci 
libata sd_mod scsi_mod crc_t10dif raid1 ext3 jbd uhci_hcd ohci_hcd ehci_hcd usbhid hid usbcore radeon ttm
 drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
Pid: 45, comm: plymouthd Tainted: G        W   2.6.38.7-server-1.mga #1
Call Trace:
 [<c0153cb2>] ? warn_slowpath_common+0x72/0xa0
 [<f3ddb616>] ? radeon_gart_bind+0x196/0x1a0 [radeon]
 [<f3ddb616>] ? radeon_gart_bind+0x196/0x1a0 [radeon]
 [<c0153d83>] ? warn_slowpath_fmt+0x33/0x40
 [<f3ddb616>] ? radeon_gart_bind+0x196/0x1a0 [radeon]
 [<f3c89f66>] ? __ttm_tt_get_page+0x76/0x110 [ttm]
 [<f3dd9151>] ? radeon_ttm_backend_bind+0x31/0xa0 [radeon]
 [<f3c8a61f>] ? ttm_tt_populate+0x6f/0x90 [ttm]
 [<f3c8a68c>] ? ttm_tt_bind+0x4c/0x70 [ttm]
 [<f3c8bf7e>] ? ttm_bo_handle_move_mem+0x17e/0x380 [ttm]
 [<f3c8cebf>] ? ttm_bo_move_buffer+0x12f/0x150 [ttm]
 [<f3c8cf88>] ? ttm_bo_validate+0xa8/0x120 [ttm]
 [<f3c8d259>] ? ttm_bo_init+0x259/0x310 [ttm]
 [<f3dda2e0>] ? radeon_bo_create+0xb0/0x290 [radeon]
 [<f3dda35f>] ? radeon_bo_create+0x12f/0x290 [radeon]
 [<f3dda100>] ? radeon_ttm_bo_destroy+0x0/0xa0 [radeon]
 [<f3df0ea9>] ? radeon_gem_object_create+0x79/0x100 [radeon]
 [<f3df12e7>] ? radeon_gem_create_ioctl+0x67/0xe0 [radeon]
 [<c01c645d>] ? ftrace_syscall_exit+0x3d/0xc0
 [<f3a4bd31>] ? drm_ioctl+0x1e1/0x450 [drm]
 [<c01c645d>] ? ftrace_syscall_exit+0x3d/0xc0
 [<f3df1280>] ? radeon_gem_create_ioctl+0x0/0xe0 [radeon]
 [<c0485468>] ? schedule_hrtimeout_range_clock+0x108/0x1a0
 [<c0174f50>] ? hrtimer_wakeup+0x0/0x30
 [<c0175a66>] ? hrtimer_start_range_ns+0x26/0x30
 [<f3a4bb50>] ? drm_ioctl+0x0/0x450 [drm]
 [<c02301dd>] ? do_vfs_ioctl+0x7d/0x590
 [<c02a72d6>] ? tomoyo_init_request_info+0x46/0x50
 [<c02a3c5e>] ? tomoyo_path_number_perm+0x2e/0xf0
 [<c0257105>] ? sys_epoll_wait+0x75/0x350
 [<c01c645d>] ? ftrace_syscall_exit+0x3d/0xc0
 [<c017b768>] ? ktime_get_ts+0xf8/0x120
 [<c02a6027>] ? tomoyo_file_ioctl+0x17/0x20
 [<c0230777>] ? sys_ioctl+0x87/0x90
 [<c01709b1>] ? sys_clock_gettime+0x71/0xb0
 [<c0486734>] ? syscall_call+0x7/0xb
 [<c01c645d>] ? ftrace_syscall_exit+0x3d/0xc0
 [<c01c645d>] ? ftrace_syscall_exit+0x3d/0xc0
---[ end trace b679c95df257bc3a ]---

CC: (none) => mnaud.free

Comment 2 Thomas Courbon 2011-07-13 17:53:20 CEST
I can also confirm this behavior, at first boot with everything set as default during the setup.

lspci:
[thomas@localhost ~]$ lspci | grep -i radeon
02:00.0 VGA compatible controller: ATI Technologies Inc Juniper [Radeon HD 5700 Series]
02:00.1 Audio device: ATI Technologies Inc Juniper HDMI Audio [Radeon HD 5700 Series]

Graphic driver:
[thomas@localhost ~]$ glxinfo | grep -i opengl
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.10.2

dmesg is attached.

CC: (none) => thcourbon

Comment 3 Thomas Courbon 2011-07-13 17:55:33 CEST
Created attachment 650 [details]
Dmesg right after startup
Comment 4 Thomas Courbon 2011-07-13 22:22:02 CEST
I just upgraded my desktop box to cauldron (following: http://www.mageia.org/wiki/doku.php?id=cauldron) and the problem still occurs.

[thomas@localhost ~]$ glxinfo | grep -i opengl
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.11-rc1
OpenGL shading language version string: 1.20
Comment 5 Thomas Courbon 2011-07-14 19:28:57 CEST
I was able to solve this issue (and a couple of others) by (re ?)installing the radeon-firmware package and rebuilding the initrd. Much thank to someone (sory, I can't remember your nickname) on irc who pointed me to the following bug report: 
https://bugs.mageia.org/show_bug.cgi?id=1951

On cauldron/x86_64 this is the command I issued to rebuild the initrd image:
mkinitrd -v -f /boot/initrd-2.6.38.8-desktop-5.mga2.img  2.6.38.8-desktop-5.mga2

That should fix the issue also on Mageia 1. I understand that license/patent issues encumber the firmware but I wonder why it's not installed (and embedded in initrd) by default since without it the graphic card is unusable.

Also now glxinfo report the correct renderer and I can activate the desktop effect.

[root@localhost ~]# glxinfo | grep -i opengl
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD JUNIPER
OpenGL version string: 2.1 Mesa 7.11-rc1
OpenGL shading language version string: 1.20
Comment 6 C Verschuuren 2011-07-14 21:50:13 CEST
The solution Thomas Courbon pointed me to (bug 1951) solved the problem.
Thank you Thomas and Shlomi Fish.
Comment 7 Thierry Vignaud 2011-08-28 22:43:51 CEST
Requires/suggest should be stricter maybe

CC: (none) => thierry.vignaud
Assignee: bugsquad => tmb
Source RPM: (none) => kernel

Comment 8 Frank Griffin 2011-09-26 19:49:42 CEST
This is still occurring in cauldron.  Worse, you are no longer prompted as to whether you want the proprietary driver or not, you just get it.

That means the first reboot finds an unusable system.  The kernel/driver error loop now appears infinite.

CC: (none) => ftg

Comment 9 Frank Griffin 2011-09-27 13:18:29 CEST
My error.  The loop is not infinite, just a lot longer.
Comment 10 Frank Griffin 2011-09-27 18:40:55 CEST
Note that bootloader-config --action=rebuild-initrds does *not* add the firmware.
Comment 11 Thomas Backlund 2011-09-27 19:34:16 CEST
Do you have radeon-firmware installed ?
Comment 12 Frank Griffin 2011-09-27 19:42:00 CEST
Yes, but it doesn't appear to get pulled in by bootloader-config.  It does get included by the full mkinitrd command noted in bug 1951.

This bug is probably an offshoot of the free-only policy during install.  If a driver requires firmware in non-free, then a free-only install shouldn't be using that driver at all.  But if install *is* going to use such a driver, then it will just have to hold its nose and enable non-free if that repository is available.
Comment 13 Kamil Rytarowski 2011-10-07 02:25:59 CEST
I can't boot Mageia on the default detected settings. Mageia selects radeon/fglrx driver for my video card. And this "radeon" is completly broken and it blocks system from booting.

Everything works fine with the drivers vesa/fglrx.

# lspci | grep -i radeon
01:00.0 VGA compatible controller: ATI Technologies Inc M92 [Mobility Radeon HD 4500 Series]

CC: (none) => krytarowski

Manuel Hiebel 2011-11-08 19:27:28 CET

Component: Release (media or process) => RPM Packages
Assignee: tmb => bugsquad

Manuel Hiebel 2011-11-08 19:33:41 CET

Assignee: bugsquad => tmb

Comment 14 Kamil Rytarowski 2011-11-12 05:58:03 CET
*** Bug 3326 has been marked as a duplicate of this bug. ***

CC: (none) => davidwhodgins

Comment 15 Dave Hodgins 2011-12-10 05:02:31 CET
I've now found, that on my system, I don't have to disable kmsboot.

Adding vmalloc=192M allows a kmsboot.  I guess with kms, the default
of 128M (on i586 kernels) isn't enough.

Perhaps it's time to change the default in the i586 kernels.
Comment 16 Thomas Backlund 2011-12-10 14:12:34 CET
Hmm, wonder why your system does not work...

We already raised vmalloc to 192 for Mageia 1 final.
https://bugs.mageia.org/show_bug.cgi?id=904
Comment 17 Dave Hodgins 2011-12-11 08:45:34 CET
(In reply to comment #16)
> Hmm, wonder why your system does not work...
> 
> We already raised vmalloc to 192 for Mageia 1 final.
> https://bugs.mageia.org/show_bug.cgi?id=904

During the reboot, I actually used vmalloc=256M, rather then 192M.

After searching on the web, I was under the impression 192 would be
enough.

I first ran into this problem a month or so ago, on a Mandriva 2010.2
system, where roughly 1 in 10 boots would fail with the default vmalloc
being too low.  I don't understand why it would work most of the time,
but not all of the time.  These are cold boots, so I expect anything
that fails to consistently fail.

How can I find out how much vmalloc is actually needed for a given
system?
Comment 18 Dave Hodgins 2012-02-20 03:40:19 CET
This bug applies to a pre beta 1 install too.
Comment 19 Herbert Poetzl 2012-03-16 06:36:28 CET
just ran into this issue with a Mageia 2 Beta 1 updated to the latest Cauldron.


[   26.804165] WARNING: at drivers/gpu/drm/radeon/radeon_gart.c:184 radeon_gart_bind+0xd8/0xe0 [radeon]()
[   26.804169] Hardware name: DX79TO
[   26.804171] trying to bind memory to uninitialized GART !
[   26.804174] Modules linked in: xt_dccp xt_conntrack xt_connmark xt_CLASSIFY xt_AUDIT ipt_LOG xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_mangle nfnetlink iptable_filter ip_tables x_tables af_packet snd_hda_codec_hdmi snd_hda_codec_realtek sb_edac edac_core i2c_i801 mei(C) xhci_hcd iTCO_wdt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm e1000e iTCO_vendor_support snd_timer snd serio_raw mxm_wmi soundcore snd_page_alloc wmi tpm_tis joydev tpm tpm_bios button cpufreq_ondemand cpufreq_conservative cpufreq_powersave acpi_cpufreq freq_table processor mperf evdev nvram ipv6 autofs4 usbhid hid ext4 jbd2 crc16 sd_mod crc_t10dif ahci libahci ehci_hcd libata usbcore scsi_mod firewire_ohci firewire_core crc_itu_t usb_common radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
[   26.804247] Pid: 153, comm: plymouthd Tainted: G        WC   3.3.0-desktop-0.rc7.1.mga2 #1
[   26.804251] Call Trace:
[   26.804263]  [<ffffffff8104e05f>] warn_slowpath_common+0x7f/0xc0
[   26.804269]  [<ffffffff8104e156>] warn_slowpath_fmt+0x46/0x50
[   26.804294]  [<ffffffffa00bed38>] radeon_gart_bind+0xd8/0xe0 [radeon]
[   26.804318]  [<ffffffffa00bc137>] radeon_ttm_backend_bind+0x37/0xa0 [radeon]
[   26.804330]  [<ffffffffa0079e1f>] ttm_tt_bind+0x4f/0x70 [ttm]
[   26.804342]  [<ffffffffa007c1bf>] ttm_bo_handle_move_mem+0x5bf/0x670 [ttm]
[   26.804349]  [<ffffffff8111d1ca>] ? shmem_alloc_inode+0x1a/0x30
[   26.804360]  [<ffffffffa007d272>] ttm_bo_move_buffer+0x132/0x140 [ttm]
[   26.804371]  [<ffffffffa007d314>] ttm_bo_validate+0x94/0x110 [ttm]
[   26.804382]  [<ffffffffa007d6a0>] ttm_bo_init+0x310/0x3b0 [ttm]
[   26.804405]  [<ffffffffa00bd9d4>] radeon_bo_create+0x194/0x2c0 [radeon]
[   26.804427]  [<ffffffffa00bd6d0>] ? radeon_bo_clear_va+0xd0/0xd0 [radeon]
[   26.804453]  [<ffffffffa00ceffa>] radeon_gem_object_create+0x5a/0x100 [radeon]
[   26.804478]  [<ffffffffa00cf4a4>] radeon_gem_create_ioctl+0x54/0xf0 [radeon]
[   26.804485]  [<ffffffff8120c2a8>] ? tomoyo_init_request_info+0x88/0x100
[   26.804501]  [<ffffffffa001d4f4>] drm_ioctl+0x444/0x510 [drm]
[   26.804525]  [<ffffffffa00cf450>] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
[   26.804532]  [<ffffffff811772e8>] do_vfs_ioctl+0x98/0x550
[   26.804538]  [<ffffffff811a8873>] ? sys_epoll_wait+0x93/0x440
[   26.804544]  [<ffffffff81177831>] sys_ioctl+0x91/0xa0
[   26.804551]  [<ffffffff814616f9>] system_call_fastpath+0x16/0x1b
[   26.804555] ---[ end trace bda9765ea8d3300b ]---
[   26.804560] [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 1056 pages at 0x00000000
[   26.805003] radeon 0000:04:00.0: object_init failed for (4325376, 0x00000002)
[   26.805052] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (4325376, 2, 4096, -22)

CC: (none) => herbert

Comment 20 Kamil Rytarowski 2012-03-16 12:48:27 CET
I have encountered that after a default boot.iso installation there was missing radeon firmware and I can't boot normally.
Comment 21 Thierry Vignaud 2012-03-16 13:27:36 CET
boot-nonfree.iso would have worked for you
Comment 22 Fabrice Boyrie 2012-05-02 19:59:06 CEST
I have the same bugs on a 
Card:ATI Radeon HD 2000 to HD 6300 (radeon/fglrx): ATI Technologies Inc|RV730 PRO [Radeon HD 4650] [DISPLAY_VGA]
May  1 06:54:36 localhost kernel: d: 153, comm: plymouthd Tainted: G        W    3.3.4-desktop-1.mga2 #1
May  1 06:54:36 localhost kernel: [    7.708458] Call Trace:
May  1 06:54:36 localhost kernel: [    7.708465]  [<ffffffff8104dedf>] warn_slowpath_common+0x7f/0xc0
May  1 06:54:36 localhost kernel: [    7.708468]  [<ffffffff8104dfd6>] warn_slowpath_fmt+0x46/0x50
May  1 06:54:36 localhost kernel: [    7.708480]  [<ffffffffa0140418>] radeon_gart_bind+0xd8/0xe0 [radeon]
May  1 06:54:36 localhost kernel: [    7.708491]  [<ffffffffa013d657>] radeon_ttm_backend_bind+0x37/0xa0 [radeon]
May  1 06:54:36 localhost kernel: [    7.708500]  [<ffffffffa00fae1f>] ttm_tt_bind+0x4f/0x70 [ttm]
May  1 06:54:36 localhost kernel: [    7.708504]  [<ffffffffa00fd1bf>] ttm_bo_handle_move_mem+0x5bf/0x670 [ttm]
May  1 06:54:36 localhost kernel: [    7.708508]  [<ffffffff8111d09a>] ? shmem_alloc_inode+0x1a/0x30
May  1 06:54:36 localhost kernel: [    7.708513]  [<ffffffffa00fe272>] ttm_bo_move_buffer+0x132/0x140 [ttm]
May  1 06:54:36 localhost kernel: [    7.708518]  [<ffffffffa00fe314>] ttm_bo_validate+0x94/0x110 [ttm]
May  1 06:54:36 localhost kernel: [    7.708522]  [<ffffffffa00fe6a0>] ttm_bo_init+0x310/0x3b0 [ttm]
May  1 06:54:36 localhost kernel: [    7.708533]  [<ffffffffa013ef34>] radeon_bo_create+0x194/0x2c0 [radeon]
May  1 06:54:36 localhost kernel: [    7.708545]  [<ffffffffa013ec30>] ? radeon_bo_clear_va+0xd0/0xd0 [radeon]
May  1 06:54:36 localhost kernel: [    7.708558]  [<ffffffffa01507ea>] radeon_gem_object_create+0x5a/0x100 [radeon]
May  1 06:54:36 localhost kernel: [    7.708571]  [<ffffffffa0150bf4>] radeon_gem_create_ioctl+0x54/0xf0 [radeon]
May  1 06:54:36 localhost kernel: [    7.708576]  [<ffffffff8120c448>] ? tomoyo_init_request_info+0x88/0x100
May  1 06:54:36 localhost kernel: [    7.708592]  [<ffffffffa00aa4f4>] drm_ioctl+0x444/0x510 [drm]
May  1 06:54:36 localhost kernel: [    7.708605]  [<ffffffffa0150ba0>] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
May  1 06:54:36 localhost kernel: [    7.708610]  [<ffffffff81177298>] do_vfs_ioctl+0x98/0x550
May  1 06:54:36 localhost kernel: [    7.708613]  [<ffffffff811a8893>] ? sys_epoll_wait+0x93/0x440
May  1 06:54:36 localhost kernel: [    7.708616]  [<ffffffff811777e1>] sys_ioctl+0x91/0xa0
May  1 06:54:36 localhost kernel: [    7.708620]  [<ffffffff81461079>] system_call_fastpath+0x16/0x1b
May  1 06:54:36 localhost kernel: [    7.708622] ---[ end trace 1e9616398fd90e43 ]---
May  1 06:54:36 localhost kernel: [    7.708625] [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 1875 pages at 0x00000000
May  1 06:54:36 localhost kernel: [    7.709238] radeon 0000:01:00.0: object_init failed for (7680000, 0x00000002)
May  1 06:54:36 localhost kernel: [    7.709241] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (7680000, 2, 4096, -22)
May  1 06:54:36 localhost kernel: [    7.728347] ------------[ cut here ]------------

It seems radeon firmware is in the initrd.
I've tried to increase vmalloc, without results.
The only way to boot is to press Escape during the boot
xvinfo 

X-Video Extension version 2.2
screen #0
 no adaptors present

Is it a consequence of the first bug, or should I report another bug report ?

CC: (none) => fboyrie

Comment 23 Marja Van Waes 2012-07-06 15:04:13 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 24 Manuel Hiebel 2012-11-05 16:51:55 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

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 
Mageia version prior to Mageia 1'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 Mageia 1 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 Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

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 Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 25 Manuel Hiebel 2012-12-02 14:31:44 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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 Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

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

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX


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