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