From: nayobix@nayobix.org (nayobix at nayobix.org)
To: kernelnewbies@lists.kernelnewbies.org
Subject: text segment corruption - probable suspects?
Date: Fri, 24 Jan 2014 09:50:51 +0200 [thread overview]
Message-ID: <52E21B5B.6030407@nayobix.org> (raw)
In-Reply-To: <CAGdaadbGRd5+9DaqgzZpiG58xpijnKHtKDXscO_equVWDvqjzQ@mail.gmail.com>
On 01/23/2014 02:04 PM, Mulyadi Santosa wrote:
> On Tue, Jan 7, 2014 at 10:09 PM, Boyan Vladinov <nayobix@nayobix.org> wrote:
>> Hey guys,
>>
>> recently I experience .text segment corruption in Kernel space. Could
>> someone give some hints which can be the reason
>> for this text segment corruption, because as we know it is read-only?
> Could you share what evidence did you get so you can get conclusion
> there happen such corruption?
>
> IMHO, I suspect it is due RAM error...so it's not corruption coming
> from kernel image itself
>
I compared the addresses/instructions from the crash with these in
vmlinux image and they were different in 1 or 2 bits. Yep, we also
suspect RAM issues, but is it possible to be something other like DMA
transfers?
next prev parent reply other threads:[~2014-01-24 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 15:09 text segment corruption - probable suspects? Boyan Vladinov
2014-01-23 12:04 ` Mulyadi Santosa
2014-01-24 7:50 ` nayobix at nayobix.org [this message]
2014-01-24 14:20 ` Greg Freemyer
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=52E21B5B.6030407@nayobix.org \
--to=nayobix@nayobix.org \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).