From: Eugene Surovegin <ebs@ebshome•net>
To: dhlii@comcast•net
Cc: Chris Dumoulin <cdumoulin@ics-ltd•com>, linuxppc-embedded@ozlabs•org
Subject: Re: Calculating virtual address from physical address
Date: Wed, 10 May 2006 09:43:29 -0700 [thread overview]
Message-ID: <20060510164329.GA32200@gate.ebshome.net> (raw)
In-Reply-To: <4461C8BE.4050504@dlasys.net>
On Wed, May 10, 2006 at 07:04:30AM -0400, David H. Lynch Jr. wrote:
[skip]
> Unless I am completely mistaken, machine checks are not cause by
> softwded are or programming errors, they are cause by hardware problems,
You can trivially trigger MachineChecks without any hardware problems
- just map some non-existent physical address and try to access it.
--
Eugene
next prev parent reply other threads:[~2006-05-10 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 18:43 Calculating virtual address from physical address Chris Dumoulin
2006-05-06 19:38 ` Grant Likely
2006-05-10 11:04 ` David H. Lynch Jr.
2006-05-10 16:43 ` Eugene Surovegin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-06 8:43 Alexander Szekely
2006-05-05 15:08 Chris Dumoulin
2006-05-05 19:27 ` Sylvain Munaut
2006-05-05 20:24 ` Matt Porter
2006-05-05 20:58 ` Josh Boyer
2006-05-05 23:35 ` David H. Lynch Jr.
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=20060510164329.GA32200@gate.ebshome.net \
--to=ebs@ebshome$(echo .)net \
--cc=cdumoulin@ics-ltd$(echo .)com \
--cc=dhlii@comcast$(echo .)net \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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