The Notebooks

In order to test this issue thoroughly, we looked at five notebooks:

ASUS W5A (Sonoma/Pentium M)

ASUS W5F (Napa/Core Duo)

Dell Inspiron E1705 (Napa/Core Duo)

Lenovo Thinkpad T60 (Napa/Core Duo)

Lenovo Thinkpad T43 (Sonoma/Pentium M)



The USB Devices

We tested with three USB devices:

Kingston Data Traveler Elite (USB 2.0)

Vantec NexStar 2 External 3.5" Hard Drive Enclosure (USB 2.0)


Not that this device is entirely externally powered

Microsoft Intellimouse Optical Blue (USB 1.0)



The Test

We standardized on Mobile Mark's Reader 2002SE test simply because that test is hardly CPU intensive, giving it a lot of time to spend in lower power states and potentially giving the asynchronous scheduler bug a good chance to impact battery life. 

 
ASUS W5F
ASUS W5A
Dell Inspiron E1705 Lenovo Thinkpad T60 Lenovo Thinkpad T43
CPU:
Intel Core Duo T2400 (1.86GHz)
Intel Pentium M 750 (1.86GHz)
Intel Core Duo T2600 (2.16GHz)
Intel Core Duo T2600 (2.16GHz)
Intel Pentium M 780 (2.26GHz)
Chipset:
Intel 945G
Intel 915G
Intel 945G
Intel 945G
Intel 915G
Chipset Drivers:
Intel 7.2.2.1006
Intel 7.2.2.1006
Intel 7.2.2.1006
Intel 7.2.2.1006
Intel 7.2.2.1006
Memory:
1 x 512MB (DDR2-533)
1 x 512MB (DDR2-400)
2 x 512MB (DDR2-667)
2 x 512MB (DDR2-533)
2 x 512MB (DDR2-533)
Graphics:
Intel Integrated 945G Graphics
Intel Integrated 915G Graphics
Intel Integrated 945G Graphics
Intel Integrated 945G Graphics
Intel Integrated 915G Graphics
Video Drivers:
Intel 14.18.2
Intel 14.18.2
Intel 14.18.2
Intel 14.18.2
Intel 14.18.2
Desktop Resolution:
1280 x 768
1280 x 768
1920 x 1200
1400 x 1050
1024 x 768
Battery Capacity:
50 WHr
50 WHr
80 WHr
56 WHr
51 WHr
The Fix Problem #1 - Perfmon is Inaccurate
Comments Locked

61 Comments

View All Comments

  • Anand Lal Shimpi - Monday, February 13, 2006 - link

    It's not a refusal to test, we're simply not sent any for review :) My next article will be a look at Core Duo vs. Turion performance on the desktop, but I'm still working on securing notebook review units. I would like to see if this issue does impact AMD systems as well, and to what degree.

    After the Core Duo vs. Turion piece, if we still haven't gotten a Turion notebook in house I'll just buy one for this comparison.

    Take care,
    Anand
  • havokprod - Monday, February 13, 2006 - link

    Does this problem surface with SP1??
  • DigitalFreak - Monday, February 13, 2006 - link

    Microsoft has supposedly known about this since at least July 2005. WTF? Why hasn't this been fixed yet?
  • scavio - Monday, February 13, 2006 - link

    It must have been difficult to mention and actually link to Tom's, I'm glad to see professionalism still lives.

    Very nice job on the article, it looks as though you guys went the extra mile and actually did the work to try figure out what was going on. I read the Tom's article a couple of weeks ago and although they uncovered an important issue they seemed to think they could try to get to the bottom of it with phone calls rather than getting their hands dirty and taking the time to test things themselves.
  • hergieburbur - Tuesday, February 14, 2006 - link

    While the technical aspects of this article are intriging, I think there is too much editorial opinion added on top of that.

    I think the main reason they post the link to Toms is to dispute the claim Tom's supposedly made that this was a Core Duo issue. That is not what the original article stated, though several times in this article there are thinly veiled allusions to that supposed claim.

    I think that tech sites should spend a little more time focusing on themselves and the products they review, and a little less trying to show how they are better than the rest. That goes for all sites. You work speaks for itself.
  • Anand Lal Shimpi - Tuesday, February 14, 2006 - link

    The reason for linking the THG article was to avoid taking credit for a discovery that I did not make. They were the first to stumble upon the issue and it was their article that inspired a deeper investigation, which eventually resulted in this article.

    The point of this article wasn't to show how we were somehow better, but to address the mischaracterization of the problem. The THG results show a tremendous penalty on their Core Duo notebook due to the issue but a relatively small penalty on their Sonoma platform; this article was designed to explain why that was and hopefully clear up the very common misconception that this is predominantly a Core Duo problem.

    The problem is that lots of people linked to that first article, and a very large number of those links incorrectly referred to the problem as a Core Duo issue based on the results that were originally presented. In reality, this problem appears to be nothing more than a Microsoft issue that impacts both Core Duo and Pentium M systems (I'm trying to figure out if it impacts Turion systems as well) but it was grossly mischaracterized in its public acception. I don't really care whose fault that is (personally I believe it's the fault of those who linked to the original article without thoroughly reading it), but I do care that the right information gets out there, which is what this article was designed to do.

    I learned long ago that the best you can do is to put your best foot forward and let the reader decide on their own how they feel about you. I'm not trying to shape anyone's view of another site through my work, I'm just trying to get the most accurate information out there.

    Take care,
    Anand
  • DigitalFreak - Monday, February 13, 2006 - link

    That's why Tomshardware sucks and Anandtech doesn't. That and other things *cough*bias *cough*.

  • Anand Lal Shimpi - Monday, February 13, 2006 - link

    Be nice guys, if it weren't for the original THG article it would've taken much longer for this investigation to even happen. I just wanted to make sure that the bug was properly characertized and even more importantly, I want to actually see a fully functional fix from Microsoft that works even out of standby.

    Take care,
    Anand
  • Zebo - Monday, February 13, 2006 - link

    Careful back in the day TOMs revealed many of intels buggy hardware (i820, MTH, crashing dualcores ...)
  • bupkus - Monday, February 13, 2006 - link

    Look, I just read the intro and the conclusion, and I don't even own a laptop, but...
    [see subject], I do have an external hard drive and plans to get a laptop.

Log in

Don't have an account? Sign up now