public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] arm: mvebu: limit OpenBlocks AX3-4 to 1 GB of RAM
Date: Sun, 06 Jan 2013 22:36:58 +0100	[thread overview]
Message-ID: <50E9EE7A.1080301@free-electrons.com> (raw)
In-Reply-To: <20130104190345.460151d1@skate>

On 01/04/2013 07:03 PM, Thomas Petazzoni wrote:
> Dear Andrew Lunn,
> 
> On Fri, 04 Jan 2013 18:37:26 +0100, Andrew Lunn wrote:
> 
>> It would be nice to have a sample size bigger than two.
> 
> Indeed.
> 
>> Anybody else have a OpenBlocks AX3-4 and can report if it works or not?
> 
> At least Gr?gory has one.

Until now I didn't notice any problem on this board with the 3GB enable.

I made more tests since I received this email, I booted (cold and hot boot)
the board dozens of times, and indeed every 5 or 10 reboot the kernel hanged
during boot at line:
"UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)"

After applying your patch, I didn't notice any hang after 20 boots. Do you
have a test pattern which make the kernel to hang each time to be sure that
it is the root of the problem?

> 
>> Thomas, could you swap out the RAM module you have for a known good one?
>> Can you test the RAM module in some other board you know works?
> 
> Unfortunately, I don't see off-hand which other board I have in which I
> could test this RAM module, nor if I have a compatible RAM module to
> test things with.
> 
> Thomas
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-01-06 21:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 16:04 arm: mvebu: DT fixes for 3.8 Thomas Petazzoni
2013-01-04 16:04 ` [PATCH 1/4] arm: mvebu: limit OpenBlocks AX3-4 to 1 GB of RAM Thomas Petazzoni
2013-01-04 17:26   ` Andrew Lunn
2013-01-04 17:31     ` Thomas Petazzoni
2013-01-04 17:37       ` Andrew Lunn
2013-01-04 18:03         ` Thomas Petazzoni
2013-01-06 21:36           ` Gregory CLEMENT [this message]
2013-01-06 22:53             ` Thomas Petazzoni
2013-01-07  9:47               ` Andrew Lunn
2013-01-07 11:07                 ` Andrew Lunn
2013-01-07 11:26                   ` Thomas Petazzoni
2013-01-07 11:34                     ` Andrew Lunn
2013-01-07 12:27                       ` Gregory CLEMENT
2013-01-07 13:22                         ` Andrew Lunn
2013-02-26 15:20                       ` Thomas Petazzoni
2013-02-27  7:03                         ` Andrew Lunn
2013-02-27  8:33                           ` Thomas Petazzoni
2013-01-04 16:04 ` [PATCH 2/4] arm: mvebu: Armada XP MV78230 has two cores, not one Thomas Petazzoni
2013-01-04 16:04 ` [PATCH 3/4] arm: mvebu: Armada XP MV78230 has only three Ethernet interfaces Thomas Petazzoni
2013-01-04 16:04 ` [PATCH 4/4] arm: mvebu: indentation fixes for Armada 370/XP .dtsi files Thomas Petazzoni
2013-01-06  9:03   ` Andrew Lunn
2013-01-07 16:53     ` Thomas Petazzoni
2013-01-07 16:55       ` Jason Cooper
2013-01-07 17:04         ` Thomas Petazzoni
2013-01-07 17:08           ` Jason Cooper

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=50E9EE7A.1080301@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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