Page 10 of 10 FirstFirst ... 8910
Results 91 to 99 of 99

Thread: Linux 2.6.32 To Get R600 KMS Along With 3D

  1. #91
    Join Date
    Aug 2009
    Posts
    4

    Default

    I have an issue with firmware loading when drm/radeon compiled as module (latest drm-next kernel, RS780). 1 of 10 `modprobe radeon modeset=1` works fine. According to `strace -o log modprobe radeon modeset=1` it looks like some timeout issues:
    Code:
    open("/lib/modules/2.6.31-rc9-ojab-kms/kernel/drivers/gpu/drm/radeon/radeon.ko", O_RDONLY) = 3
    stat("/sys/module", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
    stat("/sys/module/radeon", 0x7fff49165050) = -1 ENOENT (No such file or directory)
    fcntl(3, F_GETFL)                       = 0x8000 (flags O_RDONLY|O_LARGEFILE)
    fstat(3, {st_mode=S_IFREG|0644, st_size=829530, ...}) = 0
    mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f2ef433c000
    lseek(3, 0, SEEK_CUR)                   = 0
    After modprobe /sys/module/radeon dir always exists.

    Also I've had a backtrace several times
    Code:
    Sep 13 13:21:21 ojab kernel: [  165.507267] [drm] radeon kernel modesetting enabled.
    Sep 13 13:21:21 ojab kernel: [  165.507397] radeon 0000:01:05.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    Sep 13 13:21:21 ojab kernel: [  165.507449] radeon 0000:01:05.0: setting latency timer to 64
    Sep 13 13:21:21 ojab kernel: [  165.508933] [drm] radeon: Initializing kernel modesetting.
    Sep 13 13:21:21 ojab kernel: [  165.509010] [drm] register mmio base: 0xFE9F0000
    Sep 13 13:21:21 ojab kernel: [  165.509047] [drm] register mmio size: 65536
    Sep 13 13:21:21 ojab kernel: [  165.509568] ATOM BIOS: B27722
    Sep 13 13:21:21 ojab kernel: [  165.509607] [drm] Clocks initialized !
    Sep 13 13:21:21 ojab kernel: [  165.509654] [drm] radeon: 384M of VRAM memory ready
    Sep 13 13:21:21 ojab kernel: [  165.509691] [drm] radeon: 512M of GTT memory ready.
    Sep 13 13:21:21 ojab kernel: [  165.509771] [drm] Loading RS780 CP Microcode
    Sep 13 13:21:21 ojab kernel: [  165.509817] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin
    Sep 13 13:21:21 ojab kernel: [  165.513727] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin
    Sep 13 13:21:21 ojab kernel: [  165.517498] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
    Sep 13 13:21:21 ojab kernel: [  165.517602] IP: [<ffffffff8123af3b>] firmware_loading_store+0x5b/0x210
    Sep 13 13:21:21 ojab kernel: [  165.517669] PGD 64587067 PUD 66062067 PMD 0 
    Sep 13 13:21:21 ojab kernel: [  165.517779] Oops: 0000 [#1] PREEMPT SMP 
    Sep 13 13:21:21 ojab kernel: [  165.517888] last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading
    Sep 13 13:21:21 ojab kernel: [  165.517940] CPU 1 
    Sep 13 13:21:21 ojab kernel: [  165.517999] Modules linked in: radeon(+) usbhid hid amd64_edac_mod edac_core evdev ehci_hcd i2c_piix4 r8169 sg ohci_hcd rtc_cmos rtc_core mii processor rtc_lib thermal button af_packet kvm_amd kvm usbcore 
    snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore snd_page_alloc ttm drm_kms_helper drm fb cfbcopyarea cfbimgblt cfbfillrect unix [last unloaded: radeon]
    Sep 13 13:21:21 ojab kernel: [  165.518254] Pid: 1233, comm: firmware.sh Not tainted 2.6.31-rc9-ojab-kms #5 MS-7576
    Sep 13 13:21:21 ojab kernel: [  165.518254] RIP: 0010:[<ffffffff8123af3b>]  [<ffffffff8123af3b>] firmware_loading_store+0x5b/0x210
    Sep 13 13:21:21 ojab kernel: [  165.518254] RSP: 0018:ffff880063947e58  EFLAGS: 00010202
    Sep 13 13:21:21 ojab kernel: [  165.518254] RAX: 0000000000000000 RBX: ffff88006fbaf800 RCX: 000000000000000a
    Sep 13 13:21:21 ojab kernel: [  165.518254] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88006511e001
    Sep 13 13:21:21 ojab kernel: [  165.518254] RBP: 0000000000000002 R08: 0000000000000028 R09: 000000000000000a
    Sep 13 13:21:21 ojab kernel: [  165.518254] R10: 0000000000000001 R11: 0000000000000246 R12: ffff88006d77a400
    Sep 13 13:21:21 ojab kernel: [  165.518254] R13: ffffffff81421230 R14: 0000000000000000 R15: ffff88006c945e40
    Sep 13 13:21:21 ojab kernel: [  165.518254] FS:  00007f969c2e86f0(0000) GS:ffff88000154f000(0000) knlGS:0000000000000000
    Sep 13 13:21:21 ojab kernel: [  165.518254] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Sep 13 13:21:21 ojab kernel: [  165.518254] CR2: 0000000000000008 CR3: 0000000063504000 CR4: 00000000000006e0
    Sep 13 13:21:21 ojab kernel: [  165.518254] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Sep 13 13:21:21 ojab kernel: [  165.518254] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Sep 13 13:21:21 ojab kernel: [  165.518254] Process firmware.sh (pid: 1233, threadinfo ffff880063946000, task ffff88006d1c96c0)
    Sep 13 13:21:21 ojab kernel: [  165.518254] Stack:
    Sep 13 13:21:21 ojab kernel: [  165.518254]  0000000000000002 000000008d98c31a ffff88006c945e60 ffff880063947f50
    Sep 13 13:21:21 ojab kernel: [  165.518254] <0> ffff8800634c2fa0 ffffffff81421230 ffff88006d77a410 ffffffff81136c85
    Sep 13 13:21:21 ojab kernel: [  165.518254] <0> ffff88006d1c96c0 0000000000000002 ffff88006ea829c0 000000008d98c31a
    Sep 13 13:21:21 ojab kernel: [  165.518254] Call Trace:
    Sep 13 13:21:21 ojab kernel: [  165.518254]  [<ffffffff81136c85>] ? sysfs_write_file+0xe5/0x190
    Sep 13 13:21:21 ojab kernel: [  165.518254]  [<ffffffff810d9734>] ? vfs_write+0xe4/0x1b0
    Sep 13 13:21:21 ojab kernel: [  165.518254]  [<ffffffff810d991e>] ? sys_write+0x5e/0xb0
    Sep 13 13:21:21 ojab kernel: [  165.518254]  [<ffffffff8100c182>] ? system_call_fastpath+0x16/0x1b
    Sep 13 13:21:21 ojab kernel: [  165.518254] Code: 48 89 5c 24 10 4c 89 6c 24 28 48 89 cd 49 8b 9c 24 88 00 00 00 e8 86 20 f7 ff 85 c0 41 89 c6 75 6f f6 43 70 01 74 73 48 8b 43 68 <48> 8b 78 08 e8 0c 13 e8 ff 4c 8b 6b 68 8b b3 80 00 00 00
     31 d2 
    Sep 13 13:21:21 ojab kernel: [  165.518254] RIP  [<ffffffff8123af3b>] firmware_loading_store+0x5b/0x210
    Sep 13 13:21:21 ojab kernel: [  165.518254]  RSP <ffff880063947e58>
    Sep 13 13:21:21 ojab kernel: [  165.518254] CR2: 0000000000000008
    Sep 13 13:21:21 ojab kernel: [  165.522528] ---[ end trace 8ccc6e8414991f02 ]---

  2. #92
    Join Date
    Jan 2009
    Posts
    117

    Default

    Quote Originally Posted by ojab View Post
    I have an issue with firmware loading when drm/radeon compiled as module (latest drm-next kernel, RS780). 1 of 10 `modprobe radeon modeset=1` works fine. According to `strace -o log modprobe radeon modeset=1` it looks like some timeout issues:
    Code:
    open("/lib/modules/2.6.31-rc9-ojab-kms/kernel/drivers/gpu/drm/radeon/radeon.ko", O_RDONLY) = 3
    stat("/sys/module", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
    stat("/sys/module/radeon", 0x7fff49165050) = -1 ENOENT (No such file or directory)
    fcntl(3, F_GETFL)                       = 0x8000 (flags O_RDONLY|O_LARGEFILE)
    fstat(3, {st_mode=S_IFREG|0644, st_size=829530, ...}) = 0
    mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f2ef433c000
    lseek(3, 0, SEEK_CUR)                   = 0
    After modprobe /sys/module/radeon dir always exists.

    Also I've had a backtrace several times
    Code:
    Sep 13 13:21:21 ojab kernel: [  165.507267] [drm] radeon kernel modesetting enabled.
    Sep 13 13:21:21 ojab kernel: [  165.507397] radeon 0000:01:05.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    Sep 13 13:21:21 ojab kernel: [  165.507449] radeon 0000:01:05.0: setting latency timer to 64
    Sep 13 13:21:21 ojab kernel: [  165.508933] [drm] radeon: Initializing kernel modesetting.
    Sep 13 13:21:21 ojab kernel: [  165.509010] [drm] register mmio base: 0xFE9F0000
    Sep 13 13:21:21 ojab kernel: [  165.509047] [drm] register mmio size: 65536
    Sep 13 13:21:21 ojab kernel: [  165.509568] ATOM BIOS: B27722
    Sep 13 13:21:21 ojab kernel: [  165.509607] [drm] Clocks initialized !
    Sep 13 13:21:21 ojab kernel: [  165.509654] [drm] radeon: 384M of VRAM memory ready
    Sep 13 13:21:21 ojab kernel: [  165.509691] [drm] radeon: 512M of GTT memory ready.
    Sep 13 13:21:21 ojab kernel: [  165.509771] [drm] Loading RS780 CP Microcode
    Sep 13 13:21:21 ojab kernel: [  165.509817] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin
    Sep 13 13:21:21 ojab kernel: [  165.513727] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin
    Sep 13 13:21:21 ojab kernel: [  165.517498] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
    Sep 13 13:21:21 ojab kernel: [  165.517602] IP: [<ffffffff8123af3b>] firmware_loading_store+0x5b/0x210
    Sep 13 13:21:21 ojab kernel: [  165.517669] PGD 64587067 PUD 66062067 PMD 0 
    Sep 13 13:21:21 ojab kernel: [  165.517779] Oops: 0000 [#1] PREEMPT SMP 
    Sep 13 13:21:21 ojab kernel: [  165.517888] last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading
    Sep 13 13:21:21 ojab kernel: [  165.517940] CPU 1 
    Sep 13 13:21:21 ojab kernel: [  165.517999] Modules linked in: radeon(+) usbhid hid amd64_edac_mod edac_core evdev ehci_hcd i2c_piix4 r8169 sg ohci_hcd rtc_cmos rtc_core mii processor rtc_lib thermal button af_packet kvm_amd kvm usbcore 
    snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore snd_page_alloc ttm drm_kms_helper drm fb cfbcopyarea cfbimgblt cfbfillrect unix [last unloaded: radeon]
    Sep 13 13:21:21 ojab kernel: [  165.518254] Pid: 1233, comm: firmware.sh Not tainted 2.6.31-rc9-ojab-kms #5 MS-7576
    Sep 13 13:21:21 ojab kernel: [  165.518254] RIP: 0010:[<ffffffff8123af3b>]  [<ffffffff8123af3b>] firmware_loading_store+0x5b/0x210
    Sep 13 13:21:21 ojab kernel: [  165.518254] RSP: 0018:ffff880063947e58  EFLAGS: 00010202
    Sep 13 13:21:21 ojab kernel: [  165.518254] RAX: 0000000000000000 RBX: ffff88006fbaf800 RCX: 000000000000000a
    Sep 13 13:21:21 ojab kernel: [  165.518254] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88006511e001
    Sep 13 13:21:21 ojab kernel: [  165.518254] RBP: 0000000000000002 R08: 0000000000000028 R09: 000000000000000a
    Sep 13 13:21:21 ojab kernel: [  165.518254] R10: 0000000000000001 R11: 0000000000000246 R12: ffff88006d77a400
    Sep 13 13:21:21 ojab kernel: [  165.518254] R13: ffffffff81421230 R14: 0000000000000000 R15: ffff88006c945e40
    Sep 13 13:21:21 ojab kernel: [  165.518254] FS:  00007f969c2e86f0(0000) GS:ffff88000154f000(0000) knlGS:0000000000000000
    Sep 13 13:21:21 ojab kernel: [  165.518254] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Sep 13 13:21:21 ojab kernel: [  165.518254] CR2: 0000000000000008 CR3: 0000000063504000 CR4: 00000000000006e0
    Sep 13 13:21:21 ojab kernel: [  165.518254] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Sep 13 13:21:21 ojab kernel: [  165.518254] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Sep 13 13:21:21 ojab kernel: [  165.518254] Process firmware.sh (pid: 1233, threadinfo ffff880063946000, task ffff88006d1c96c0)
    Sep 13 13:21:21 ojab kernel: [  165.518254] Stack:
    Sep 13 13:21:21 ojab kernel: [  165.518254]  0000000000000002 000000008d98c31a ffff88006c945e60 ffff880063947f50
    Sep 13 13:21:21 ojab kernel: [  165.518254] <0> ffff8800634c2fa0 ffffffff81421230 ffff88006d77a410 ffffffff81136c85
    Sep 13 13:21:21 ojab kernel: [  165.518254] <0> ffff88006d1c96c0 0000000000000002 ffff88006ea829c0 000000008d98c31a
    Sep 13 13:21:21 ojab kernel: [  165.518254] Call Trace:
    Sep 13 13:21:21 ojab kernel: [  165.518254]  [<ffffffff81136c85>] ? sysfs_write_file+0xe5/0x190
    Sep 13 13:21:21 ojab kernel: [  165.518254]  [<ffffffff810d9734>] ? vfs_write+0xe4/0x1b0
    Sep 13 13:21:21 ojab kernel: [  165.518254]  [<ffffffff810d991e>] ? sys_write+0x5e/0xb0
    Sep 13 13:21:21 ojab kernel: [  165.518254]  [<ffffffff8100c182>] ? system_call_fastpath+0x16/0x1b
    Sep 13 13:21:21 ojab kernel: [  165.518254] Code: 48 89 5c 24 10 4c 89 6c 24 28 48 89 cd 49 8b 9c 24 88 00 00 00 e8 86 20 f7 ff 85 c0 41 89 c6 75 6f f6 43 70 01 74 73 48 8b 43 68 <48> 8b 78 08 e8 0c 13 e8 ff 4c 8b 6b 68 8b b3 80 00 00 00
     31 d2 
    Sep 13 13:21:21 ojab kernel: [  165.518254] RIP  [<ffffffff8123af3b>] firmware_loading_store+0x5b/0x210
    Sep 13 13:21:21 ojab kernel: [  165.518254]  RSP <ffff880063947e58>
    Sep 13 13:21:21 ojab kernel: [  165.518254] CR2: 0000000000000008
    Sep 13 13:21:21 ojab kernel: [  165.522528] ---[ end trace 8ccc6e8414991f02 ]---
    You need the firmware for r600 cards. It is separate file that should be put to initrd if you load radeon early. maybe that loading could be improved so it is delayed if not finding immediately. And try again after root fs has been mounted.

  3. #93
    Join Date
    Aug 2009
    Posts
    4

    Default

    Quote Originally Posted by suokko View Post
    You need the firmware for r600 cards. It is separate file that should be put to initrd if you load radeon early. maybe that loading could be improved so it is delayed if not finding immediately. And try again after root fs has been mounted.
    It happens also if I'm loading radeon modules manually, after system is completely booted. So I think itintrd is irrelevant here (and also 1 of 10 radeon module loading attempts works ok, so it can find and load firmware).
    Last edited by ojab; 09-13-2009 at 09:57 AM.

  4. #94
    Join Date
    Jan 2009
    Posts
    117

    Default

    Quote Originally Posted by ojab View Post
    It happens also if I'm loading radeon modules manually, after system is completely booted. So I think itintrd is irrelevant here.
    Then you just have to install the firmwares.

  5. #95
    Join Date
    Aug 2008
    Location
    Finland
    Posts
    1,805

    Default

    Quote Originally Posted by suokko View Post
    Then you just have to install the firmwares.
    Sep 13 13:21:21 ojab kernel: [ 165.517498] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
    This should obviously never happen even if the microcode can't be found though...

  6. #96
    Join Date
    Dec 2008
    Posts
    17

    Default

    Update: I have installed 5 mins ago the latest version of libdrm,xf86-video-ati (master),mesa(master) and drm-next kernel. I did a couple tries, and in all of them the framebuffer started nicely, startx(xfce, no compiz/3d effects/...) worked fine with no warnings/errors, switching back/forth to console worked (!!), BUT starting new apps would just immediately hard-lock the whole thing (crashed when launching ossxmix the first time, audacious the second time, firefox the 3rd time, with a black screen). I couldn't reboot via sysrq, and the ssh session would also lock pretty badly, had to turn it off by pressing the power button for 5 secs. Strangely enough, mplayer (-vo xv /and/ -vo gl seems to be working, even though I still get the syslog spammed with those
    Code:
    [drm:radeon_ring_write] *ERROR* radeon: writting more dword to ring than expected !
    lines.

    Is there any way I could help troubleshooting this kind of problem? I can get no error messages if the whole thing locks up so badly!

    A funny (probably unrelated thing): if I use X with a vanilla .31 kernel without KMS, launching a mplayer -vo gl also locks the system, although in a slightly different way (mouse starts choking and after a while the whole thing becomes totally unresponsive).

    erm.. any ideas ? please


    Quote Originally Posted by moomoo View Post
    Doesn't work too well here. hd 3470 mobility on toshiba laptop (RV620).
    gentoo, xorg-server 1.6.4-rc1, latest drm-next kernel, xf86-video-ati, mesa and libdrm from git (all compiled 10 mins ago). It loads the firmware only when radeon is compiled as module, then gives a very nice high-res console; starting X works /but/
    1) sometimes X crashes when launching even 'simple' apps, and the whole laptop hangs
    2) if it manages to survive for a while, on dmesg I get a bunch of
    Code:
    [drm:radeon_ring_write] *ERROR* radeon: writting more dword to ring than expected !

  7. #97
    Join Date
    Dec 2007
    Posts
    2,404

    Default

    there seems to be a problem with the dword accounting for the blit bo move code. You can revert a381287759b2b65e7de9fb35801c781cab016f10 as a workaround for now.

  8. #98
    Join Date
    Dec 2008
    Posts
    17

    Default

    yay! seems to be working ! thanks !!!

  9. #99
    Join Date
    Dec 2008
    Posts
    17

    Default

    okay I tried updating to today's drm-next,mesa,xf86-video-ati etc. Now the behaviour is different: fb console works fine, and X always loads fine, but always somehow locks up after a few seconds. By somehow I mean that I can still move the mouse, but nothing else can be done, everything else is locked. I can login via ssh and kill the X server, that gives me a black screen, and I can also launch it again from ssh! And that gives me a garbled screen. And the nasty stuff is that I get no error whatsoever on dmesg/messages/Xorg.0.log! When booting, my dmesg says
    Code:
    [    6.588571] radeon 0000:01:00.0: power state changed by ACPI to D0
    [    6.588590] radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [    6.588601] radeon 0000:01:00.0: setting latency timer to 64
    [    6.592466] [drm] radeon: Initializing kernel modesetting.
    [    6.592519] [drm] register mmio base: 0xF0200000
    [    6.592523] [drm] register mmio size: 65536
    [    6.592803] ATOM BIOS: M82XT
    [    6.592813] [drm] Clocks initialized !
    [    6.595368] [drm] Detected VRAM RAM=256M, BAR=256M
    [    6.595374] [drm] RAM width 64bits DDR
    [    6.595514] [TTM] Zone  kernel: Available graphics memory: 1544718 kiB.
    [    6.595541] [drm] radeon: 256M of VRAM memory ready
    [    6.595545] [drm] radeon: 512M of GTT memory ready.
    [    6.595845] [drm] Loading RV620 CP Microcode
    [    6.595848] platform radeon_cp.0: firmware: requesting radeon/RV620_pfp.bin
    [    6.765417] platform radeon_cp.0: firmware: requesting radeon/RV620_me.bin
    [    6.777862] [drm] GART: num cpu pages 131072, num gpu pages 131072
    [    6.813593] [drm] ring test succeeded in 0 usecs
    [    6.813676] [drm] radeon: ib pool ready.
    [    6.813694] [drm] ib test succeeded in 0 usecs
    [    6.813696] [drm] radeon: kernel modesetting successfully initialized.
    [    6.813931] [drm] Radeon Display Connectors
    [    6.813933] [drm] Connector 0:
    [    6.813934] [drm]   LVDS
    [    6.813936] [drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
    [    6.813938] [drm]   Encoders:
    [    6.813939] [drm]     LCD1: INTERNAL_KLDSCP_LVTMA
    [    6.813941] [drm] Connector 1:
    [    6.813942] [drm]   VGA
    [    6.813944] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
    [    6.813946] [drm]   Encoders:
    [    6.813947] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
    [    6.813949] [drm] Connector 2:
    [    6.813950] [drm]   HDMI-A
    [    6.813952] [drm]   DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c
    [    6.813953] [drm]   Encoders:
    [    6.813954] [drm]     DFP1: INTERNAL_UNIPHY
    [    6.980058] [drm] fb mappable at 0xD0141000
    [    6.980060] [drm] vram apper at 0xD0000000
    [    6.980061] [drm] size 4096000
    [    6.980063] [drm] fb depth is 24
    [    6.980064] [drm]    pitch is 5120
    [    7.022498] firewire_core: created device fw0: GUID 001b240000d4b7de, S400
    [    7.501934] executing set pll
    [    7.506363] executing set crtc timing
    [    7.506430] [drm] LVDS-5: set mode 1280x800 15
    [    7.900588] Console: switching to colour frame buffer device 160x50
    [    7.906080] fb0: radeondrmfb frame buffer device
    [    7.906082] registered panic notifier
    [    7.906086] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0
    Now, is there some way to fix it, or at least to pull out some useful debugging info? Which options should I include when compiling the kernel / which commands should I run to get some information ??

    EDIT: I have done a 'modprobe drm debug=1 ; modprobe radeon modeset=1' , the dmesg log is flooded with messages like
    Code:
    [d219, 237.567840] [drm:drm_ioctl], ret = fffffff0
    , and in particular when X is stuck they become
    Code:
    [drm:drm_ioctl], pid=8219, cmd=0xc0086464, nr=0x64, dev 0xe200, auth=1
    [drm:drm_ioctl], ret = fffffff0
    Last edited by moomoo; 09-17-2009 at 10:31 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •