From: "\"Tóth Attila\"" <atoth@atoth.sote.hu>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Disappearing root on 2.6.36-hardened-r6 upgrade
Date: Tue, 4 Jan 2011 19:38:22 +0100 [thread overview]
Message-ID: <cea8e0ac853a56109e1fccf4286d1030.squirrel@atoth.sote.hu> (raw)
In-Reply-To: <4D235D07.24046.6055002F@pageexec.freemail.hu>
I see. Now I fired up my spare notebook and transferred the system in the
mean time. :P
I'm currently suffering of crashes occuring while I'm transcoding a
scientific event's DVD content. It became very frustrating.
Would it be possible that the CPU itself is actually failing (opcode 0000)?
The temperature is absolutely within normal limits even during heavy
usage, so I'm sure it's not because of overheating. It's a Pentium M
1.8Ghz, and the notebook's fan is OK.
I'll give vanilla a spin, nevertheless. How I could get closer to the
failing code in case of a kernel problem? Are there any useful suggestions
- besides changing architecture (which is not possible at the moment)?
Thanks:
Dw.
--
dr Tóth Attila, Radiológus, 06-20-825-8057
Attila Toth MD, Radiologist, +36-20-825-8057
2011.Január 4.(K) 17:46 időpontban pageexec@freemail.hu ezt írta:
> On 4 Jan 2011 at 14:52, "Tóth Attila" wrote:
>
>> No errors were found after 12 hours of memtest.
>>
>> However some serious crashes still occur.
>>
>> I attach snippets of kern.log.
>>
>> Is it still suggests a hardware error?
>
> when i said memory corruption, i didn't mean a hw error but a sw one
> that causes it ;). and i wonder whether the buggy code is in vanilla
> already or not since we don't really touch the failing code directly.
>
>
>
next prev parent reply other threads:[~2011-01-04 18:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-26 6:59 [gentoo-hardened] Disappearing root on 2.6.36-hardened-r6 upgrade Michael Orlitzky
2010-12-26 8:46 ` pageexec
2010-12-26 17:06 ` Michael Orlitzky
2010-12-26 17:57 ` pageexec
2010-12-26 19:09 ` Michael Orlitzky
2010-12-26 20:00 ` pageexec
2010-12-26 23:03 ` klondike
2010-12-27 0:05 ` klondike
2010-12-29 11:36 ` pageexec
2010-12-27 19:49 ` Michael Orlitzky
2010-12-26 19:31 ` Michael Orlitzky
2010-12-26 17:31 ` Anthony G. Basile
2010-12-26 18:01 ` Anthony G. Basile
2010-12-26 18:59 ` "Tóth Attila"
2010-12-26 20:06 ` pageexec
2010-12-26 23:01 ` klondike
2010-12-30 19:29 ` "Tóth Attila"
2010-12-30 20:35 ` pageexec
2010-12-30 23:16 ` "Tóth Attila"
2011-01-04 13:52 ` "Tóth Attila"
2011-01-04 16:46 ` pageexec
2011-01-04 18:38 ` "Tóth Attila" [this message]
2011-01-04 18:18 ` pageexec
2011-01-09 14:55 ` "Tóth Attila"
2011-01-09 22:20 ` Alex Efros
2011-01-10 0:39 ` "Tóth Attila"
2011-01-04 13:52 ` "Tóth Attila"
2011-01-04 13:16 ` pageexec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cea8e0ac853a56109e1fccf4286d1030.squirrel@atoth.sote.hu \
--to=atoth@atoth.sote.hu \
--cc=gentoo-hardened@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox