Hi Ted! On Thu, 31 Jul 2008 15:15:12 +0200, Theodore Tso wrote: > On Thu, Jul 31, 2008 at 03:04:03PM +0200, Luca Capello wrote: >> I read the list, thanks. I was so surprised that no one reported this >> issue before and I've already planned to deal with it during >> DebCamp8/DebConf8 (starting on Sunday, Aug 3rd [2]). > > One possibility is that it's a hardware problem; for example, it could > be that your heat sink on the CPU or GPU didn't have enough thermal > compound installed, or some such. In that case I'd try to have it repaired ;-) > I have an X61s, which has a different BIOS series and a low-voltage > CPU chip, so it's not directly comparable, but I can say that I've not > had any problems even when I've loaded the CPU significantly. OK, if you want to give a try to my test case: $ [install darcs] $ darcs get http://alioth.debian.org/~gismo/darcs-pull-bug/parenscript.upstream/ $ darcs get http://alioth.debian.org/~gismo/darcs-pull-bug/parenscript/ $ cd parenscript $ darcs pull ../parenscript.upstream/ [choose to apply only the first patch] At that point, darcs takes 100% of the CPU and temperature starts to rise :-( FWIW, the same process on a PIII-500 is running for more than 5819 *hours* and it haven't finished nor spotted an error, yet. > Of course, I also use mainline kernels and not Debian kernels. One > thing that you might try to do while you are at DebConf is to see if > you can find other people with the same laptop model and see if they > can duplicate the problem on their machine, so you can try varying > both the Debian/non-debian kernel, as well as trying to see if you can > reproduce the problem on multiple laptops. This was exactly my idea: I already know that at least another X60 Debian Developer will be at DebConf8, this is another reason I waited. Thx, bye, Gismo / Luca
Attachment:
pgpgj51NigxKn.pgp
Description: PGP signature
