| 1 |
On 23/12/12 23:00, felix@×××××××.com wrote: |
| 2 |
> On Sun, Dec 23, 2012 at 10:49:46PM +0200, Nikos Chantziaras wrote: |
| 3 |
>> On 23/12/12 21:23, felix@×××××××.com wrote: |
| 4 |
>>> A few weeks ago I had a scare when a reboot paniced the kernel with a |
| 5 |
>>> complaint that it could not find the root device (/dev/sde), and |
| 6 |
>>> further reboots couldn't even see the USB keyboard. Leavng the |
| 7 |
>>> system powered off overnight "fixed" the problem and the system has |
| 8 |
>>> been working fine ever since. |
| 9 |
>> |
| 10 |
>> Do a memtest first. emerge sys-apps/memtest86+ and then add an entry |
| 11 |
>> for it in Grub: |
| 12 |
>> |
| 13 |
>> title=Memtest86+ |
| 14 |
>> root (hd0,0) # <- adapt this to your partition |
| 15 |
>> kernel /boot/memtest86plus/memtest.bin |
| 16 |
>> |
| 17 |
>> Then boot that entry and see if you get any errors in the first 5 |
| 18 |
>> minutes or so. |
| 19 |
> |
| 20 |
> Starting the emerge etc. But why would this be a memory problem when |
| 21 |
> it is so clearly 3.6 vs 3.7? |
| 22 |
|
| 23 |
It's simply an easy check to do and can rule RAM failure out early on. |
| 24 |
When RAM dies, various seemingly unrelated issues can pop up. |
| 25 |
|
| 26 |
But since your RAM seems clean, it's not the issue. |
Archives