Stories
Slash Boxes
Comments
Search

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Core Duo Power Sapping Bug is Microsoft Issue

Posted by Zonk on Fri Feb 17, 2006 10:40 AM
from the explore-all-possibilities dept.
Intel Microsoft Hardware
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."
+ -
story

Related Stories

[+] IT: Faulty Microsoft Driver Saps Intel Core Duo power 268 comments
Critical_ writes "Tom's Hardware recently discovered a bug in Microsoft's ACPI driver implementation under Windows XP SP2 that causes a loss of more than one hour of battery time when connecting any USB 2.0 device to an Intel Core Duo based system. Apparently Microsoft, Intel and ODMs have known of this problem under a confidentiality agreement since July 12, 2005 via (a still private) Knowledge Base article KB899179. The bug lies in the asynchronous scheduler component inadvertently being left running causing Windows' internal task scheduler (ITS) to treat it as a running process involving the attached device. This in turn prevents the ITS from powering down the processor into one of the ACPI sleep states causing the system to use more battery power. At this time there seems to be no fix. Strangely, single-core systems and AMD systems are not affected. This leads one to wonder if it is truely a software problem or if there a much larger hardware problem that may affect Core Duo equipped Apple systems."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Core Duo Power Sapping Bug is Microsoft Issue 25 Comments More /

 Full
 Abbreviated
 Hidden
More
Loading... please wait.

  • Oh My God! (Score:4, Funny)

    by NutscrapeSucks (446616) on Friday February 17 2006, @10:43AM (#14741936)
    There's a driver glitch with brand new hardware!!! It's already been two weeks and they haven't fixed it yet!! What does this mean for the computing landscape? Is this Wintel's downfall? Will Apple return to their days of prominence? The implications could be enormous!
    • There's a driver glitch with brand new hardware!!! It's already been two weeks and they haven't fixed it yet!! What does this mean for the computing landscape? Is this Wintel's downfall? Will Apple return to their days of prominence? The implications could be enormous!

      Didn't you hear??? Apple is switching to MS Windows, I heard it from a reliable source! And Linux costs just too much to run, we're all out of alternatives!

    • Re:Oh My God! (Score:5, Informative)

      by evilgrug (915703) on Friday February 17 2006, @11:08AM (#14742121)
      "There's a driver glitch with brand new hardware!!! "

      Actually it affects Pentium Ms as well, according to Anandtech.

      "It's already been two weeks and they haven't fixed it yet!!"

      Microsoft first identified the issue and published a Knowledgebase article July 12, 2005. That's a little more than 2 weeks.

      In fact, the regedit quickfix they're recommending was also published on that date ... meaning they still haven't resolved it 7 months later.

    • Re:Oh My God! (Score:5, Informative)

      by tpgp (48001) on Friday February 17 2006, @11:09AM (#14742130) Homepage
      I know that you're joking, but I have to reply to the serious parts of your post.

      There's a driver glitch with brand new hardware!!!

      From the TFA
      When a peripheral device was connected to a USB (universal serial bus) 2.0 port, the notebook's battery life plunged at a greater rate than would normally be expected from the use of a peripheral such as a mouse or storage key.
      Nope, not new hardware. USB is not new. The core duos just made the problem more obvious.

      It's already been two weeks and they haven't fixed it yet!!
      From the TFA
      Microsoft published a Knowledge Base article on the subject in July 2005, but made that information available only to PC vendors and partners, a company representative said in a statement.
      So, its actually been over six months and they haven't fixed it yet.

      As usual, Microsoft waits for an issue to become public before bothering to fix it.

      • Re:Oh My God! (Score:5, Funny)

        by cloudmaster (10662) on Friday February 17 2006, @11:45AM (#14742411) Homepage Journal
        From the TFA

        Don't you mean "From the TFA article", or maybe "from the friggin' TFA article"? :)

        FYI information, this post is courtesy of Windows XP, based on NT technology, and transimtted using NIC card features to get the message posted as ASAP as possible.

        just becuase I've nothing more to contribute (except that Tom's Hardware sucks)
      • One could argue that keeping USB2 devices plugged for long in a laptop running on battery is a kind of new scenario. The issue is also aggrevated on a dual core machine, as the need for "deep sleep" on one of the cores is actually a quite common scenario there, whereas the effects on a single-core older Pentium M is less pronounced (especially if you're using the system for anything, like playing a MP3, which will prevent your system from going to that level of power saving most of the time anyway).

    • Re:Oh My God! (Score:5, Funny)

      by MysteriousPreacher (702266) on Friday February 17 2006, @12:14PM (#14742683) Homepage Journal
      There's a driver glitch with brand new hardware!!! It's already been two weeks and they haven't fixed it yet!! What does this mean for the computing landscape? Is this Wintel's downfall? Will Apple return to their days of prominence? The implications could be enormous!


      John Dvorak, is that you?

  • anandtech test (Score:4, Informative)

    by Dionysus (12737) on Friday February 17 2006, @10:45AM (#14741964) Homepage
    According to some testing over at anandtech [anandtech.com], problem was in the way Windows XP polls USB2 devices.

  • This is good news (Score:4, Insightful)

    by nurb432 (527695) on Friday February 17 2006, @10:46AM (#14741972) Homepage Journal
    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 )
    • The fact that it didn't break until a brand new processor hit the scenes tells me their QA was fine. How do you QA for non-existant products?

        • Re:This is good news (Score:4, Insightful)

          by FireFury03 (653718) <slashdot@ne x u s uk.org> on Friday February 17 2006, @12:36PM (#14742923) Homepage
          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)
    • This is good news....That means its fixable with a minor software patch. Much better then having broken hardware.

      Good news for whom?

      I agree that it's certainly good for people unfortunate enough to use Microsoft's operating systems - they'll be able to fix a problem with a software patch rather then a hardware patch.

      However, it's certainly not good news for microsoft - the small amount of trust that people have left in MS's QA processes will be lost in the news that they found this bug over six months ago,

  • Tom's was wrong (Score:5, Informative)

    by jamesl (106902) on Friday February 17 2006, @10:52AM (#14742011)
    AnandTech has an in depth analysis. Like most things, the answer can't be found in a headline.
    http://www.anandtech.com/mobile/showdoc.aspx?i=269 3/ [anandtech.com]

    We've spent almost the past two weeks performing non-stop battery life testing on five notebooks with up to 4 different USB devices, testing theories, trying to pinpoint exactly what causes this problem and testing Microsoft's fix. What follows is the process that we went through in our labs when faced with this strange bug.

  • Where's the new logo ? (Score:5, Funny)

    by Potatomasher (798018) on Friday February 17 2006, @10:58AM (#14742039)
    Intel with a dropped e ? That's so like 1970 to end of 2005.
    Get with the times Slashdot.

  • BIOS Fix? (Score:4, Insightful)

    by slashnik (181800) on Friday February 17 2006, @10:59AM (#14742055)
    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
    • Because a BIOS patch is much more pratical for most users? I get annoyed just by having to use a floppy drive to update my BIOS.

    • Re:BIOS Fix? (Score:5, Insightful)

      by gstoddart (321705) on Friday February 17 2006, @11:12AM (#14742147) Homepage
      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?

  • So predictable. (Score:4, Interesting)

    by twitter (104583) on Friday February 17 2006, @11:04AM (#14742093) Homepage Journal
    Good thing no one made the Critical error of speciously faulting Apple or Linux without testing [slashdot.org], that would look like FUD when faced with a typical Microsoft problem.

  • power sapping bug (Score:5, Funny)

    by revery (456516) * <`charles' `at' `cac2.net'> on Friday February 17 2006, @11:06AM (#14742107) Homepage
    Core Duo Power Sapping Bug

    [Starscream holds a press conference]
    Ummmm, yes... we were hoping no one would notice, but it's the fricking Insecticons gathering Energon for Megatron... Again. Microsoft only got involved because they own the North American rights to all acts of evil.

  • It's not just Microsoft... (Score:5, Funny)

    by Junior J. Junior III (192702) on Friday February 17 2006, @11:11AM (#14742139) Homepage
    I can't get into a deep sleep when someone jabs a USB plug into one of my ports, either. Apparently I'm hot, I'm pluggable, but I'm not hot-pluggable.

    • Re:It's not just Microsoft... (Score:5, Funny)

      by Odin's Raven (145278) on Friday February 17 2006, @02:01PM (#14743703)
      Inexperienced hot-pluggers often feel this way. First, and most importantly - there's absolutely nothing wrong with you - you are hot-pluggable. Don't let a bad initial experience convince you otherwise.

      The realy problem here is with technique - jabbing is never recommended. You want to firmly grasp the peripheral near its end, then gently slide it into the port. Okay, try that a few times - firm grasp - good! - and gennnntly slide it in. Now withdraw the device, and gennnntly reinsert. In and out, in and out, over and over and over again. Excellent, now you're getting the hang of it.

      Although it's sometimes normal to encounter resistance inserting a peripheral into a brand-new port, this friction should disappear with use. Be extra-gentle in these circumstances, and resist the urge to just jab a device into the slot. Again, slow and easy, gently sliding in and out. Yes...yessssss! Getting frustrated and randomly jabbing with your peripheral is unlikely to result in a successful connection, and can damage your peripheral unit or the slot. Overly forceful insertions have even caused the tip of a device to snap clean off - don't let this happen to you!

      Deep sleep is a separate issue. It's normal not to sleep immediately after a peripheral is inserted - the unit is in active use, and sleeping would be undesirable. Wait until interactions with the device have ceased before entering sleep.

      Hopefully this has cleared up some of your concerns. Remember that hot-plugging is a perfectly normal activity, one which anyone can learn to enjoy with a little practice.

  • All a bunch of whiners.... (Score:3, Insightful)

    by jnadke (907188) on Friday February 17 2006, @11:32AM (#14742312)
    Jesus... if Microsoft fixed every little bug to come along, then who would upgrade to Vista?!?!?

All trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the Poster. The Rest © 1997-2009 Geeknet, Inc.