Announcement

Collapse
No announcement yet.

The Linux Kernel Power Problems On Older Desktop Hardware

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

  • #31
    Originally posted by deanjo View Post
    I never said you might not be right, but you have not proved that it doesn't exist. You say "This power bug doesn't exist" which is an absolute answer with no possibility of any chance that you might be missing something or unable to replicate. The only one displaying arrogance is you with your self confidence that what ever results you come up with has to be the only and absolute right answer.
    Unable to replicate across many systems and many use cases, remember I have 0 bug reports and a few thousand users. This in itself is evidence against this "bug".

    What you fail to realize though is that the burdon of proof is not on me. It is not my responsibility to disprove that the bug exists, it is on Phoronix who initiated and continued these same baseless claims for months. I don't think that it is too much to ask for Phoronix to actually prove their theory after all this time by showing us the commit since the claim was made in the first article that it would be found "quickly".

    Instead all we have seen is more sensationalist journalism proclaiming that the sky is falling.

    Give us the commit.

    Comment


    • #32
      Originally posted by Artemis3 View Post
      Hey fewt, where are your tests that demonstrate the power usage across kernels has not changed? Until then, you have no right to discredit others.

      I hope to see more tests, with actual facts and science done, not petty bickering in a forum based on beliefs.
      We test every kernel release at Fuduntu with powertop, and have not seen a change that wasn't expected. We began testing starting with kernel 2.6.35, and the only "problem" we have found is that nmi watchdog needed to be turned off in 2.6.38 (it defaulted on) when on battery.

      We added this to Jupiter, and it's since been forgotten about.

      Comment


      • #33
        fewt, I gather you ran all your tests with your Mono app on? Have you considered that maybe the regressed component is something your app disables or otherwise affects?

        Comment


        • #34
          Originally posted by curaga View Post
          fewt, I gather you ran all your tests with your Mono app on? Have you considered that maybe the regressed component is something your app disables or otherwise affects?
          I'm not sure why you have chosen to call it out as a Mono app, unless you are trolling (which I hope is not the case).

          To answer your question though, yes I have run all tests with Jupiter. If you think about it though, that's how it's supposed to work.

          You wouldn't benchmark Windows battery life with the Windows power manager disabled, or set on high, that would be silly. The same applies here.

          The kernel doesn't dynamically tune itself, which is why it is necessary for tools like Jupiter and tuned to exist. This is "business as usual".

          As the kernel grows in size (new functionality, and even bug fixes) it should be expected that it would use more power over time, because the kernel does more work over time.

          It is not up to the kernel team to change the running configuration (dynamic tuning), as that would negatively impact a great many things. This function belongs in userland.

          Comment


          • #35
            Originally posted by fewt View Post
            What you fail to realize though is that the burdon of proof is not on me. It is not my responsibility to disprove that the bug exists,
            When you give an absolute answer saying something "doesn't exist" the burden of proof does become yours as well. If you were to say something like "I doubt that it exists", "I haven't seen any iron clad proof it exists", etc then you have no burden of proof as you are just giving an opinion which does still allow for the possibility to be there even though you have not seen any satisfactory evidence to prove otherwise.

            Comment


            • #36
              Originally posted by deanjo View Post
              When you give an absolute answer saying something "doesn't exist" the burden of proof does become yours as well. If you were to say something like "I doubt that it exists", "I haven't seen any iron clad proof it exists", etc then you have no burden of proof as you are just giving an opinion which does still allow for the possibility to be there even though you have not seen any satisfactory evidence to prove otherwise.
              Stop attempting to deflect, and just show us the commit.

              Comment


              • #37
                Is michael seeing things in all those graphs that I cannot?
                I too think that this 'bug' is a load of nonsense, and this article deffinately is.
                Phoronix on top form as usual.

                Deanjo you need to actually read what fewt has said in this thread and the bug report.
                There is little to no evidence of a possible bug and it also doesn't seem to affect the vast majority of users. My laptop actually seems to last a bit longer on the latest kernel!

                Comment


                • #38
                  DPMS off, display?

                  Michael,

                  Since this is a desktop you are testing, is the display hooked up on the power meter as well when testing the effect of DPMS off? The first graph doesn't show any measurable difference (I can't see where the DPMS off/on events are).

                  Also as mentioned several times, make sure you 'align' the tests, so you end up with the same amount of idle and non-idle periods for each system.

                  Comment


                  • #39
                    Originally posted by fewt View Post
                    Stop attempting to deflect, and just show us the commit.
                    I think you just did that in a previous comment, at least for one of them:

                    Originally posted by fewt View Post
                    We began testing starting with kernel 2.6.35, and the only "problem" we have found is that nmi watchdog needed to be turned off in 2.6.38 (it defaulted on) when on battery.
                    Since Michael and all others that are complaining about the performance regressions are not using your application they are affected by this change of default setting. Now, if you can dig in the history of your application to find out what else it started disabling after kernel 2.6.35 you will also solve the mistery of the "first major regression".

                    Comment


                    • #40
                      Originally posted by Ansla View Post
                      I think you just did that in a previous comment, at least for one of them:



                      Since Michael and all others that are complaining about the performance regressions are not using your application they are affected by this change of default setting. Now, if you can dig in the history of your application to find out what else it started disabling after kernel 2.6.35 you will also solve the mistery of the "first major regression".
                      My source is on SourceForge, if you think the "regression" is a "regression" you are free to analyze it.

                      Comment

                      Working...
                      X