Announcement

Collapse
No announcement yet.

Mobility HD2600 PowerPlay problem

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

  • #11
    glxgears is CPU bound
    is your CPU changing speed?

    Comment


    • #12
      I have CPU set to performance and was on cable when trying it. So it was on full (1,6GHz) speed..

      Comment


      • #13
        Another possibility is a background task, usually started by cron or anacron. Since glxgears is CPU bound, rather than GPU bound, CPU intensive background tasks can do this. Unfortunately, cron/anacron don't run nice'd by default.

        Comment


        • #14
          i am sure, that it isnt caused by CPU usage. Its GPU related, because i have bad FPS in games as well. I think it is powerplay related, but i cant be sure.. Maybe is there another bug in drivers? Or maybe it can be kernel related? I really dont know...

          Comment


          • #15
            Originally posted by Schmaker View Post
            i am sure, that it isnt caused by CPU usage. Its GPU related, because i have bad FPS in games as well. I think it is powerplay related, but i cant be sure.. Maybe is there another bug in drivers? Or maybe it can be kernel related? I really dont know...
            8-10 maybe 8-9 as well has a bug that causes a fps drop in quake3 demo timedemos after the first run.

            It's not 100% reproduceable and with what little testing I did (using OSS drivers currently) it seemed like it could be fixed by running other 3D apps IIRC the unigine benchmark after which it was fine. That observation could be a red herring.

            It happened on both my AGP X1600 and AGP HD3850 cards.

            Comment


            • #16
              glxgears doesn't do enough to max out a modern GPU, so 50% GPU load is actually doing not too bad.

              Check activity and CPU load while playing your game for better info.

              Erasing /etc/ati/amdpcsdb doesn't work if X is running. It is recreated when X exits.

              Comment


              • #17
                Originally posted by spikethehobbitmage View Post
                glxgears doesn't do enough to max out a modern GPU, so 50% GPU load is actually doing not too bad.

                Check activity and CPU load while playing your game for better info.

                Erasing /etc/ati/amdpcsdb doesn't work if X is running. It is recreated when X exits.
                I think you have not read the begining of thread. I said, i had full FPS (>4k FPS) sometimes, but it falls down after some time of returning from suspend and when i start i have low FPS as well. I cant return my GPU to full speed again
                I gonna try erasing of amdpcsdb again without X running...
                It's not 100% reproduceable and with what little testing I did (using OSS drivers currently) it seemed like it could be fixed by running other 3D apps IIRC the unigine benchmark after which it was fine. That observation could be a red herring.
                The problem is, that i have low FPS everytime. I can try it about infinite times and FPS will still be same...

                Comment


                • #18
                  My point was that glxgears slowdown may not be GPU. Your GPU would have to slow down by 50% before glxgears would even notice. Any change in CPU load on the other hand would affect glxgears immediately. Overloaded CPU will slow down games too.

                  Your game will be more GPU intensive than glxgears, so it would provide better information. What I was suggesting is to get GPU and CPU speed and load readings while your game is running.

                  The likely possibilities I see are memory leak in the driver (filling video memory) which should show as GPU load increase, or a background program slowing down your whole system, which should show as a CPU load increase with a GPU load decrease.

                  Comment


                  • #19
                    Originally posted by spikethehobbitmage View Post
                    My point was that glxgears slowdown may not be GPU. Your GPU would have to slow down by 50% before glxgears would even notice. Any change in CPU load on the other hand would affect glxgears immediately. Overloaded CPU will slow down games too.

                    Your game will be more GPU intensive than glxgears, so it would provide better information. What I was suggesting is to get GPU and CPU speed and load readings while your game is running.

                    The likely possibilities I see are memory leak in the driver (filling video memory) which should show as GPU load increase, or a background program slowing down your whole system, which should show as a CPU load increase with a GPU load decrease.
                    I've tried it in Urban Terror - CPU usage wasnt bigger than 75% for every core and GPU activity was 8%.. I got only <30FPS...

                    Comment


                    • #20
                      That definitely sounds like it isn't a GPU problem. Was that 75% user with 25% idle, 25% system, or 25% wait?
                      idle - CPU isn't loaded either, could be IRQ or DMA problem
                      system - likely driver, possibly incorrectly setup kernel (preempt can cause this)
                      wait - IO problem. either hard drive problem (is DMA turned on? 32 bit transfer? read ahead?), something wrong in IRQ or DMA settings for card, or driver problem.

                      Comment

                      Working...
                      X