From: linas@austin•ibm.com (Linas Vepstas)
To: "Peter N. Andreasen" <peterarbejde@gmail•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: Linux on custom Xilinx board with PPC405 hangs on boot
Date: Wed, 20 Sep 2006 18:57:16 -0500 [thread overview]
Message-ID: <20060920235716.GV29167@austin.ibm.com> (raw)
In-Reply-To: <36468a5c0609200216n753d69b0hdf8ff2cb53714f90@mail.gmail.com>
On Wed, Sep 20, 2006 at 11:16:53AM +0200, Peter N. Andreasen wrote:
> I have a custom Xilinx FPGA board which is similar to ML300 but uses
> Uartllite and does not have disk or display.
> When I start the Linux kernel I end up with an exception during the probe
> for Flash - I think.
Well, its not just "an exception" its a machine check.
> (after get_mtd_chip_driver) drivers/mtd/chips/chipreg.c: do_map_probe
> (start) drivers/mtd/chips/gen_probe.c: mtd_do_chip_probe
> (start) drivers/mtd/chips/gen_probe.c: genprobe_ident_chips
> Instruction machine check in kernel mode.
> Oops: machine check, sig: 7
> NIP: C00A2960 XER: 40000000 LR: C009CBD8 SP: C04D9D90 REGS: c04d9ce0 TRAP:
> 0200 Not tainted
> MSR: 00009030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
Machine checks happen when some hunk of hardware is wired to the
machine-check pin of the cpu chip, and that bit of hardware decides to
raise the wire. I'd say the first step is to figure ou what hardware
is wired up this way, and what would make it unhappy enough to assert a
machine check.
SRR1 has bits that state what caused he machine check. -- e.g partity
error on data or address bus, "transfer error", or MC signal.
--linas
next prev parent reply other threads:[~2006-09-20 23:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 14:06 Linux on custom Xilinx board with PPC405 hangs on boot Peter N. Andreasen
2006-09-12 15:53 ` Andrei Konovalov
2006-09-14 14:13 ` Peter N. Andreasen
2006-09-20 9:16 ` Peter N. Andreasen
2006-09-20 23:57 ` Linas Vepstas [this message]
2006-09-21 3:50 ` Liu Dave-r63238
2006-09-21 7:40 ` Peter N. Andreasen
2006-10-17 9:06 ` Peter N. Andreasen
2006-09-21 3:42 ` Liu Dave-r63238
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=20060920235716.GV29167@austin.ibm.com \
--to=linas@austin$(echo .)ibm.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=peterarbejde@gmail$(echo .)com \
/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