All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Patrick Huesmann" <tricknology@gmx.de>
To: "Mark Chambers" <markc@mail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel oops when initializing ethernet driver
Date: Fri, 27 Aug 2004 14:31:34 +0200 (MEST)	[thread overview]
Message-ID: <30642.1093609894@www18.gmx.net> (raw)
In-Reply-To: 002c01c48c30$f663f000$0301a8c0@chuck2


Hi,

> Machine check means you generated an address that the hardware was
> unable to complete - you wrote (or read) a non-existent address.  It's
> mapped in the MMU ok but doesn't exist on the board.

Do you mean something like a "bus error"?

> Memory mapped I/O tends to exist in tight little clusters, and if you get
> your address off by 1 or something you get a machine check.  So you
> gotta find exactly what address it's writing to and why it's off -
> probably
> .h configuration kind of thing somewhere...

Interestingly, the kernel only crashes when accessing that one particular
register (at offset 0x0040). Every other register in that range can be
written to and read from w/o problems.

> Hope that's some kind of help :-)

Thanks a lot,
Patrick


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2004-08-27 12:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <002c01c48c30$f663f000$0301a8c0@chuck2>
2004-08-27 12:31 ` Patrick Huesmann [this message]
     [not found] <17232.1093615319@www63.gmx.net>
2004-08-27 14:04 ` Kernel oops when initializing ethernet driver Patrick Huesmann
     [not found] <003901c48c34$6e73fe20$0301a8c0@chuck2>
2004-08-27 13:06 ` Patrick Huesmann
2004-08-27 13:52   ` Andrei Konovalov
2004-08-27 14:02     ` Patrick Huesmann
2004-08-27 11:59 Patrick Huesmann

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=30642.1093609894@www18.gmx.net \
    --to=tricknology@gmx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=markc@mail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.