Announcement

Collapse
No announcement yet.

"Ask ATI" dev thread

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Guys,

    I installed Catalist 9.6 on Ubuntu 9.04. When trying to run OpenGL apps on my ASUS P5E WS PRo with HD3650 I got an error below. My screen stopped responding. Actually I already tired a bit of my card. On Windows XP I had almost a daily SILENT restart because of "GXO failed to execute AtomBios".
    Looks like this is HW problem. If so - how to claim justify this to my supplier to exchange the card?


    -----------------------------------------------------------------
    Jun 16 03:18:18 hmsk kernel: [ 850.520512] [fglrx] ASIC hang happened
    Jun 16 03:18:18 hmsk kernel: [ 850.520518] Pid: 4606, comm: vmware-vmx-debu Tainted: P 2.6.28-11-generic #42-Ubuntu
    Jun 16 03:18:18 hmsk kernel: [ 850.520520] Call Trace:
    Jun 16 03:18:18 hmsk kernel: [ 850.520569] [<ffffffffa010b019>] KCL_DEBUG_OsDump+0x9/0x10 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.520609] [<ffffffffa011840c>] firegl_hardwareHangRecovery+0x1c/0x50 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.520670] [<ffffffffa019a259>] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.520730] [<ffffffffa019a20c>] ? _ZN4Asic9WaitUntil15WaitForCompleteEv+0x6c/0xb0 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.520790] [<ffffffffa019928d>] ? _ZN4Asic19PM4ElapsedTimeStampERK23PM4_TS_INTERRUPT _PARAMSj14_LARGE_INTEGER+0x18d/0x1c0 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.520833] [<ffffffffa0132cc2>] ? firegl_trace+0x72/0x1e0 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.520894] [<ffffffffa0192062>] ? _ZN15QS_PRIVATE_CORE27multiVpuPM4ElapsedTimeStampE RK23PM4_TS_INTERRUPT_PARAMSj14_LARGE_INTEGER+0x32/0x50 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.520951] [<ffffffffa018c193>] ? _Z19uQSTimeStampRetiredmjj14_LARGE_INTEGER+0xa3/0xb0 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.521008] [<ffffffffa0187f79>] ? _Z8uCWDDEQCmjjPvjS_+0x379/0x1080 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.521052] [<ffffffffa01350c8>] ? firegl_cmmqs_CWDDE_32+0x348/0x410 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.521095] [<ffffffffa0133b60>] ? firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.521101] [<ffffffff803f549c>] ? apparmor_capable+0x1c/0x70
    Jun 16 03:18:18 hmsk kernel: [ 850.521143] [<ffffffffa0133af0>] ? firegl_cmmqs_CWDDE32+0x0/0x100 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.521182] [<ffffffffa0113fba>] ? firegl_ioctl+0x1ea/0x250 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.521219] [<ffffffffa0109311>] ? ip_firegl_ioctl+0x11/0x20 [fglrx]
    Jun 16 03:18:18 hmsk kernel: [ 850.521223] [<ffffffff802f631d>] ? vfs_ioctl+0x7d/0xa0
    Jun 16 03:18:18 hmsk kernel: [ 850.521226] [<ffffffff802f6685>] ? do_vfs_ioctl+0x75/0x230
    Jun 16 03:18:18 hmsk kernel: [ 850.521229] [<ffffffff802f68d9>] ? sys_ioctl+0x99/0xa0
    Jun 16 03:18:18 hmsk kernel: [ 850.521232] [<ffffffff802e82d8>] ? sys_read+0x88/0x90
    Jun 16 03:18:18 hmsk kernel: [ 850.521236] [<ffffffff8021253a>] ? system_call_fastpath+0x16/0x1b
    Jun 16 03:18:18 hmsk kernel: [ 850.521239] pubdev:0xffffffffa0350a40, num of device:1 , name:fglrx, major 8, minor 62.
    Jun 16 03:18:18 hmsk kernel: [ 850.521241] device 0 : 0xffff88012c0a8000 .
    Jun 16 03:18:18 hmsk kernel: [ 850.521243] Asic ID:0x9598, revision:0x51, MMIOReg:0xffffc20010100000.
    Jun 16 03:18:18 hmsk kernel: [ 850.521246] FB phys addr: 0xd0000000, MC :0xc0000000, Total FB size :0x20000000.
    Jun 16 03:18:18 hmsk kernel: [ 850.521248] gart table MC:0xcfc2f000, Physical:0xdfc2f000, size:0x3d0000.
    Jun 16 03:18:18 hmsk kernel: [ 850.521250] mc_node :FB, total 1 zones
    Jun 16 03:18:18 hmsk kernel: [ 850.521252] MC start:0xc0000000, Physical:0xd0000000, size:0x10000000.
    Jun 16 03:18:18 hmsk kernel: [ 850.521255] Mapped heap -- Offset:0x0, size:0xfc2f000, reference count:7, mapping count:0,
    Jun 16 03:18:18 hmsk kernel: [ 850.521258] Mapped heap -- Offset:0x0, size:0x1000000, reference count:1, mapping count:0,
    Jun 16 03:18:18 hmsk kernel: [ 850.521260] Mapped heap -- Offset:0xfc2f000, size:0x3d1000, reference count:1, mapping count:0,
    Jun 16 03:18:18 hmsk kernel: [ 850.521262] mc_node :INV_FB, total 1 zones
    Jun 16 03:18:18 hmsk kernel: [ 850.521264] MC start:0xd0000000, Physical:0xe0000000, size:0x10000000.
    Jun 16 03:18:18 hmsk kernel: [ 850.521267] Mapped heap -- Offset:0xfffc000, size:0x4000, reference count:1, mapping count:0,
    Jun 16 03:18:18 hmsk kernel: [ 850.521269] mc_node :GART_USWC, total 2 zones
    Jun 16 03:18:18 hmsk kernel: [ 850.521270] MC start:0x3dc10000, Physical:0x0, size:0x4c170000.
    Jun 16 03:18:18 hmsk kernel: [ 850.521273] Mapped heap -- Offset:0x3830000, size:0x800000, reference count:1, mapping count:0,
    Jun 16 03:18:18 hmsk kernel: [ 850.521275] Mapped heap -- Offset:0x3030000, size:0x800000, reference count:1, mapping count:0,
    Jun 16 03:18:18 hmsk kernel: [ 850.521278] Mapped heap -- Offset:0x2830000, size:0x800000, reference count:1, mapping count:0,
    Jun 16 03:18:18 hmsk kernel: [ 850.521281] Mapped heap -- Offset:0x2030000, size:0x800000, reference count:2, mapping count:0,
    Jun 16 03:18:18 hmsk kernel: [ 850.521283] Mapped heap -- Offset:0x30000, size:0x2000000, reference count:10, mapping count:0,
    Jun 16 03:18:18 hmsk kernel: [ 850.521285] mc_node :GART_CACHEABLE, total 3 zones
    Jun 16 03:18:18 hmsk kernel: [ 850.521287] MC start:0x10400000, Physical:0x0, size:0x2d810000.
    Jun 16 03:18:18 hmsk kernel: [ 850.521289] Mapped heap -- Offset:0x0, size:0x200000, reference count:6, mapping count:0,
    Jun 16 03:18:18 hmsk kernel: [ 850.521292] Mapped heap -- Offset:0xef000, size:0x11000, reference count:1, mapping count:0,
    Jun 16 03:18:18 hmsk kernel: [ 850.521294] Dump the trace queue.
    Jun 16 03:18:18 hmsk kernel: [ 850.521295] End of dump
    -----------------------------------------------------------------

    Comment


    • And why do you post this here, in this thread?

      Comment


      • Because

        1. My card is fglrx device.
        2. Problem is widely announced and affects not only HD3650, but other HDXXXX cards. There is no clear answer yet how to deal with it. All recommendations to update drivers etc don't help.

        Comment


        • The whole forum section is for fglrx. If everyone was posting technical problems in this thread, we would have thousands of pages right now and there would be no need for an fglrx forum *section*.

          Make a new thread with your question.

          Comment


          • Thanks. Done http://phoronix.com/forums/showthread.php?t=17737

            Comment


            • #bridgman
              Can i ask you if ATI is going to ever support 2.6.29/2.6.30/2.6.31 kernel? Are you going to improve this driver or you are creating secret services on there? Size of this driver is increasing and increasing with every update, what is that? Ansii based Porn? I am asking because I cannot switch to nvidia and I see that you are the only one working there.

              Comment


              • linux-2.6.30 - 56.7Mb
                catalyst 9.6 - 90.0Mb

                Comment


                • 1. When will low end and onboard chips will get rid of vertical flickering problem ?
                  2. When will ATI Overdrive get a GUI ?
                  3. When we will have as good support as nvidia , as we still have no support for Mandriva | Arch Linux officially ? Also when they will deliver faster kernel support , the last I check was Catalyst 9.5 lacking kernel 2.6.29 support No idea abt 9.6

                  4. Lower end card just can't work with kwin composite it keeps on getting back and then all bad ;9

                  Comment


                  • I don't recognize the problem you're describing in #1, can you provide some more information ?

                    Not sure about ATI overdrive plans; would a GUI actually get used much, ie how often do you actually interact with it ?

                    For the last year we have been allocating resources based on user feedback that said adding features (although you call them bug fixes ) is higher priority than early support for new kernels and xorg releases. I assume that once we have added enough new features the feedback from users will change and timely support for new kernels and xorg's will become a higher priority -- and then we'll spend less time on new features and more time on new kernel/xorg support.

                    Don't really understand 4 either... are there bugzilla tickets open for 1 and 4 (at ati.cchtml.com), and if so can you point me to the tickets ?
                    Last edited by bridgman; 06-22-2009, 10:52 PM.

                    Comment


                    • I have posted a thread http://phoronix.com/forums/showthread.php?t=17106

                      my onboard ATI HD3300 works flawlessly in WIndows which I don't like to use and I don't have it installed atm ...But some HD1080p movies don't scale well and I get vertical distortion with any vide of any reso.

                      Well overclockers will be benefited with it.. and a easy gui with temps monitoring and all takes the burden of typing and grasping commands..

                      Not for 4 but yes I opened a bug at ati bugzilla which was never answered..

                      I will list to bug I posted about #4 as well https://qa.mandriva.com/show_bug.cgi?id=49733

                      Comment


                      • Originally posted by Dark_Star View Post
                        2. When will ATI Overdrive get a GUI ?


                        http://www.phoronix.com/forums/showthread.php?t=17331

                        Comment


                        • OK, I read the thread for #1 and I'm still not seeing any mention of vertical flickering - you have those words, but I didn't see anything related to them -- the rest of the thread is about (a) lack of sync-to-vblank with Xv (using GL output should work) and (b) video decoding not being fast enough for 1080P with a single thread decoder. Is the "vertical flickering" something that happens only during video playback ? Does the whole screen flicker, or just the video window ?

                          If you have an X3 processor then it would be good to try mplayer-mt (which I assume is mplayer using ffmpeg-mt), since that will make use of more than one core for decoding and should let you decode HD at full speed and res. I have seen it packaged for Arch and Gentoo but not yet for Mandriva, but I imagine you can build from svn.

                          The mandriva thread for #4 talks about a lot of different things but AFAIK most of them seem to relate to issues maximizing a video playback window while the output is being redirected. I think that was fixed (or at least something related was fixed) in 9.6, might be worth trying to see if that helps.

                          Are there any bug reports filed where our developers would see them, ie ati.cchtml.com ? You mentioned you filed a bug there before but I don't know if that was for #1, #4 or something different. What was the bug ticket you filed ?
                          Last edited by bridgman; 06-23-2009, 12:00 AM.

                          Comment


                          • video playback on hd2400 and hd3200

                            I just bought a HP 6735b laptop with a hd3200 card. I was positively surprised about AMDs decision to support Linux more and after reading about the actual state of the drivers I had the feeling that the proprietary fglrx driver is in a pretty good shape, while the os driver is improoving fast and going to be able to use it within one year maybe. However, at the moment I am quite satisfied with the state of the fglrx driver but I had to play quite a lot to use x11 instead of xv since xv is not working for my card with composite.

                            So to my question:

                            Are the developers aware of the problems with XV on the hd2400 and hd3200 cards? It's really slow and you see only about 1/4 of the actual image. People also suggest to use GL since this way one gets allso vsync. In my case gl is not an option eather since is flickering and when I try to move the window, the image of the video stays in place for a while and moves to the new place after a few secconds. Also skype doesn't support gl eather.

                            https://bugs.launchpad.net/ubuntu/+bug/369375

                            This is the bugreport for Ubuntu. However, it seems I am the only one with the wrong scale problem .. hmm. Maybe I am doing something wrong?

                            Comment


                            • I haven't heard or seen the "only see about 1/4 of the image" problem, other than on early versions of the WIP open source drivers with KMS.

                              The rest of the symptoms you describe sound like you have a fairly old driver; can you check the driver version from the log or pastebin the log -- or just uninstall the driver and install the newest version from amd.com ?

                              Comment


                              • Why is it that the x86_64 version of fglrx requires the ia32 libs?

                                Shouldn't the whole thing be 64-bit?

                                I suspect amdcccle is the reason why ia32 libs are needed, but why is this needed?

                                Also, does multiple monitors with compiz work on Radeon HD 4890 with fglrx and/or radeon/radeonhd drivers?

                                Comment

                                Working...
                                X