1 |
No errors were found after 12 hours of memtest. |
2 |
|
3 |
However some serious crashes still occur. |
4 |
|
5 |
I attach snippets of kern.log. |
6 |
|
7 |
Is it still suggests a hardware error? |
8 |
|
9 |
I have to try out another laptop. That is not convenient... |
10 |
|
11 |
Dw. |
12 |
-- |
13 |
dr Tóth Attila, Radiológus, 06-20-825-8057 |
14 |
Attila Toth MD, Radiologist, +36-20-825-8057 |
15 |
|
16 |
2010.December 30.(Cs) 21:35 időpontban pageexec@××××××××.hu ezt írta: |
17 |
> On 30 Dec 2010 at 20:29, "Tóth Attila" wrote: |
18 |
> |
19 |
>> There were two screen shots attached. The older one was outdated related |
20 |
>> to 2.6.32 kernel. |
21 |
>> |
22 |
>> But the other was a recent panic. |
23 |
> |
24 |
> unfortunately this one had the first oops scroll away already, so i can't |
25 |
> tell |
26 |
> much about it... |
27 |
> |
28 |
>> So here is another one. This time I could paste it from the log: |
29 |
> |
30 |
> this is gain some fs/journaling code trying to increment some seemingly |
31 |
> invalid |
32 |
> pointer (in eax), there's probably some memory corruption going on here |
33 |
> and it'd |
34 |
> be important to try both vanilla and -r7. |
35 |
> |
36 |
>> It happens during IO activity. I wouldn't say heavy IO. The memory is |
37 |
>> OK, |
38 |
>> the harddrive is perfect. |
39 |
>> I can dd the whole hdd to my backup booting on a gentoo CD. |
40 |
> |
41 |
> is the filesystem ok as well (fsck)? |
42 |
> |
43 |
> |
44 |
> |