From: Micha Nelissen <micha@neli•hopto.org>
To: Bastiaan Nijkamp <bastiaan.nijkamp@gmail•com>
Cc: linuxppc-dev@lists•ozlabs.org
Subject: Re: Serial RapidIO Maintaintance read causes lock up
Date: Thu, 07 Oct 2010 16:21:46 +0200 [thread overview]
Message-ID: <4CADD77A.90503@neli.hopto.org> (raw)
In-Reply-To: <AANLkTimFgrRbRfsQqN9d9GOZhth072F9TKGXunaqJNVB@mail.gmail.com>
Hi Bastian,
Bastiaan Nijkamp wrote:
> It seems i forgot to include the relevant TLB entries in U-Boot and the
> Device Tree in the e-mail, so here they are:
>
> The TLB entries in U-Boot:
The kernel maintains the TLB, you must not set those in U-boot. It might
cause conflicts when the kernel chooses its virtual memory space. You
should only configure LAWs in U-boot as the kernel does not do that.
That's the physical address you pass in the DTB (which seems to work,
reading your kernel log).
Do you access RapidIO space in U-boot also?
Do you have a logic analyser, then you can see whether the read is
actually coming out.
Check whether the time-to-live, packet and link timeouts have been set
to sane values to prevent deadlocks (especially time-to-live). At least
then your kernel will crash instead of lock up.
Micha
next prev parent reply other threads:[~2010-10-07 14:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 22:35 Serial RapidIO Maintaintance read causes lock up Bastiaan Nijkamp
2010-10-02 7:20 ` Bastiaan Nijkamp
2010-10-07 14:21 ` Micha Nelissen [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-04 15:49 Bounine, Alexandre
2010-10-05 8:56 ` Bastiaan Nijkamp
2010-10-05 13:24 ` John Traill
2010-10-05 13:49 ` Bounine, Alexandre
2010-10-05 14:28 ` Bastiaan Nijkamp
2010-10-05 14:45 ` John Traill
2010-10-11 17:27 ` Bastiaan Nijkamp
2010-10-13 8:30 ` Bastiaan Nijkamp
2010-10-13 13:38 ` Bounine, Alexandre
2010-10-13 15:05 ` Bastiaan Nijkamp
2010-10-13 15:34 ` Bounine, Alexandre
2010-10-05 15:11 ` Bounine, Alexandre
2010-10-06 18:08 ` Anderson, Trevor
2010-10-05 13:34 ` Bounine, Alexandre
2010-10-05 14:30 ` Bastiaan Nijkamp
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=4CADD77A.90503@neli.hopto.org \
--to=micha@neli$(echo .)hopto.org \
--cc=bastiaan.nijkamp@gmail$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.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