Slashdot Mirror

← Back to Stories (view on slashdot.org)

Core Duo Power Sapping Bug is Microsoft Issue

Posted by ryuzaki0 on from the explore-all-possibilities dept.

illusoryphoenix writes "A few weeks ago, Tom's Hardware noted a significant reduction in battery life of the Core Duo processors it tested when USB devices were inserted. Intel claimed that Microsoft had a bug in their USB drivers, while Tom's Hardware was unable to reproduce the same result for any of the other Pentium M microarchitecures. This issue has finally been publicly confirmed by Microsoft to be a USB driver problem which keeps the processor from entering advanced sleep states."

5 of 109 comments (clear)

  1. This is good news by nurb432 · · Score: 3, Insightful

    That means its fixable with a minor software patch. Much better then having broken hardware.

    At least we know someones QA is still working.. ( and that wouldnt be microsoft in this case )

    --
    ---- Booth was a patriot ----
    1. Re:This is good news by FireFury03 · · Score: 3, Insightful

      A good code review can often (not always) find problems before they show up at runtime.

      In my experience, code reviews only pick up the reasonably obvious problems - your example was an obvious problem that could be spotted a mile off. Code reviews generally don't tend to pick up problems in intricate algorithms.

      Infact, looking at the user agent string _at all_ is a bug, nomatter what string you're looking for. It is the reason that browsers have to fake their UA strings (IE claims to be Mozilla, Opera often claims to be IE, etc) - if you check UA strings then you have to update the site every time a new browser is released. On the other hand, presumably your UA test was to serve up some specific code needed to work around browser bugs - that makes detecting a later version of the browser and serving up the same code to be an invalid thing to do since that later version which hasn't yet been released may not have the same bugs so you're suddenly serving up workarounds that aren't needed and may potentially break.

      That said, as other people pointed out, whilest MS didn't originally spot this bug (whcih may or may not be a problem with their QA procedures), they _did_ spot it over 6 months ago and didn't bother to fix it - that's the bigger problem. I wouldn't complain too much since under existing hardware this didn't affect people much - the real problem is that they also take this attitude with security bugs, and that's more worrying (only fix the bug when it has public attention... usually coz it's being exploited in the wild)

      --
      http://blog.nexusuk.org
  2. BIOS Fix? by slashnik · · Score: 3, Insightful
    From TFA

    Microsoft outlined a fix that involved modifying the registry key for USB 2.0. However, since then the company has realized that this is an impractical fix for most users, and is working on a new fix that could involve a BIOS update patch


    What! Microsift to patch the BIOS
    Not on my notebook
    1. Re:BIOS Fix? by gstoddart · · Score: 4, Insightful
      Microsoft outlined a fix that involved modifying the registry key for USB 2.0. However, since then the company has realized that this is an impractical fix for most users, and is working on a new fix that could involve a BIOS update patch

      What! Microsift to patch the BIOS
      Not on my notebook

      Indeed. Microsoft can easily patch their own friggin' registry monstrosity.

      Patching the BIOS of the machine is an outrageously bad suggestion, and a bad precedent.

      How long before MS patches everyone's BIOS into oblivion or DRM hell?
      --
      Lost at C:>. Found at C.
  3. All a bunch of whiners.... by jnadke · · Score: 3, Insightful

    Jesus... if Microsoft fixed every little bug to come along, then who would upgrade to Vista?!?!?