| 1 |
On Monday 25 October 2004 00:56, A. Gabriel W. Daleson wrote: |
| 2 |
> Hm. I've emerged openoffice already, and also given it long lists of |
| 3 |
> other packages to merge, both while X doesn't run. It doesn't seem to |
| 4 |
> be related to the machine load in the that sense. |
| 5 |
> |
| 6 |
> Also on this note, I'm dual booting the system - Windows seems to |
| 7 |
> have no trouble with it at all, and every hardware check I've run comes |
| 8 |
> out fine. If it's a hardware problem, it's a real subtle one. |
| 9 |
|
| 10 |
Windows behaviour is normally not very good in detecting broken hardware. |
| 11 |
Windows is rather conservative in it's use of instructions (it must run |
| 12 |
on the whole range, while a gentoo system doesn't need to). Further there |
| 13 |
are normally enough other sources of crashes to make it hard to see that |
| 14 |
a crash is hardware related. |
| 15 |
|
| 16 |
Paul |
| 17 |
|
| 18 |
ps. Do note that the X drivers are not entirely bugfree either, and can |
| 19 |
and will lock up your screen, keyboard and mouse. Remote access is |
| 20 |
normally still possible. |
| 21 |
|
| 22 |
pps. There is another good source of seemingly random crashes, and that |
| 23 |
has to do with race conditions and other thread related issues. |
| 24 |
Programming safely for multiple threads is difficult. Especially if those |
| 25 |
threads are executed on more than one processor. |
| 26 |
|
| 27 |
The causes of such behaviour could be anywhere. Given that kde is normally |
| 28 |
stable on multiprocessor systems I would certainly not exclude the |
| 29 |
mainboard or graphics card bioses. (Yes, graphic cards have a bios too, |
| 30 |
and it can normally be updated) |
| 31 |
|
| 32 |
-- |
| 33 |
Paul de Vrieze |
| 34 |
Gentoo Developer |
| 35 |
Mail: pauldv@g.o |
| 36 |
Homepage: http://www.devrieze.net |
Archives