| 1 |
Jules Colding wrote: |
| 2 |
> On Wed, 2005-08-03 at 00:57 -0700, Zac Medico wrote: |
| 3 |
> |
| 4 |
>>Jules Colding wrote: |
| 5 |
>> |
| 6 |
>>>On Tue, 2005-08-02 at 18:14 +0200, Richard Fish wrote: |
| 7 |
>>> |
| 8 |
>>> |
| 9 |
>>>>Jules Colding wrote: |
| 10 |
> |
| 11 |
> |
| 12 |
>>>I would expect other things to fail too if it was bad RAM or memory |
| 13 |
>>>timings, right? The only failure scenario is mkdir under high load which |
| 14 |
>>>to me points towards s specific problem area in the code. This is just |
| 15 |
>>>an unqualified guess, naturally... |
| 16 |
>>> |
| 17 |
>> |
| 18 |
>>Can you reproduce the problem if you boot from a livecd? That could |
| 19 |
>>help settle the question of whether your problems are rooted in |
| 20 |
>>hardware or software. |
| 21 |
> |
| 22 |
> |
| 23 |
> Would it? I must access the disk and use the RAM, so wouldn't the |
| 24 |
> results be identical provided that the same kernel is used? |
| 25 |
> |
| 26 |
> If not, do you have any particular livecd in mind? |
| 27 |
> |
| 28 |
|
| 29 |
I was thinking that *all* the software should be different, including the kernel. If you still experience they same segfaults then that would point to a hardware problem. |
| 30 |
|
| 31 |
Use a livecd that may other people have tested on similar hardware. I've heard people recommend Kanotix for x86_64. There is a livecd list that can be filtered by architecture here: http://www.livecdlist.com/. |
| 32 |
|
| 33 |
Zac |
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives