From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] n_tty: use kmalloc() instead of vmalloc() to avoid crash on armada-xp
Date: Wed, 11 Mar 2015 16:13:05 +0100 [thread overview]
Message-ID: <55005B81.9020103@free-electrons.com> (raw)
In-Reply-To: <550058BE.3060406@list.ru>
On 11/03/2015 16:01, Stas Sergeev wrote:
> 11.03.2015 16:14, Russell King - ARM Linux ?????:
>> On Wed, Mar 11, 2015 at 01:44:57PM +0100, Gregory CLEMENT wrote:
>>> Hi Stas,
>>>
>>> On 10/03/2015 17:54, Stas Sergeev wrote:
>>>> Hello, the patch below is needed for a successful boot on armada-xp.
>>>>
>>> I am really surprised by this patch because I used the Armada XP based
>>> board in a daily base and I never saw this issue.
>> Can you provide some details about your board - does it have 8GB of
>> memory, ranging from 0-0xf0000000, and 4G-8G ?
> I wonder about this 256Mb memory hole.
This is where the SoC registers are.
> There is only one dimm for whole 8Gb.
> It seems 0xf000000-0xffffffff is used for PCI though:
> ---
>
> 0xf3000000-0xf303ffff 64bit]
> [ 119.290027] pci 0000:00:00.0: BAR 2: set to [mem
> 0xf3000000-0xf303ffff 64bit] (PCI address [0xf3000000-0xf303ffff])
> [ 119.300509] pci 0000:00:00.0: BAR 0: assigned [mem
> 0xf3040000-0xf305ffff 64bit]
> [ 119.307883] pci 0000:00:00.0: BAR 0: set to [mem
> 0xf3040000-0xf305ffff 64bit] (PCI address [0xf3040000-0xf305ffff])
> [ 119.318367] pci 0000:00:00.0: BAR 6: assigned [mem
> 0xf3060000-0xf306ffff pref]
>
> ---
>
> Does this mean that the 256Mb of physical memory is
> completely unaccessable on this board?
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Stas Sergeev <stsp@list.ru>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] n_tty: use kmalloc() instead of vmalloc() to avoid crash on armada-xp
Date: Wed, 11 Mar 2015 16:13:05 +0100 [thread overview]
Message-ID: <55005B81.9020103@free-electrons.com> (raw)
In-Reply-To: <550058BE.3060406@list.ru>
On 11/03/2015 16:01, Stas Sergeev wrote:
> 11.03.2015 16:14, Russell King - ARM Linux пишет:
>> On Wed, Mar 11, 2015 at 01:44:57PM +0100, Gregory CLEMENT wrote:
>>> Hi Stas,
>>>
>>> On 10/03/2015 17:54, Stas Sergeev wrote:
>>>> Hello, the patch below is needed for a successful boot on armada-xp.
>>>>
>>> I am really surprised by this patch because I used the Armada XP based
>>> board in a daily base and I never saw this issue.
>> Can you provide some details about your board - does it have 8GB of
>> memory, ranging from 0-0xf0000000, and 4G-8G ?
> I wonder about this 256Mb memory hole.
This is where the SoC registers are.
> There is only one dimm for whole 8Gb.
> It seems 0xf000000-0xffffffff is used for PCI though:
> ---
>
> 0xf3000000-0xf303ffff 64bit]
> [ 119.290027] pci 0000:00:00.0: BAR 2: set to [mem
> 0xf3000000-0xf303ffff 64bit] (PCI address [0xf3000000-0xf303ffff])
> [ 119.300509] pci 0000:00:00.0: BAR 0: assigned [mem
> 0xf3040000-0xf305ffff 64bit]
> [ 119.307883] pci 0000:00:00.0: BAR 0: set to [mem
> 0xf3040000-0xf305ffff 64bit] (PCI address [0xf3040000-0xf305ffff])
> [ 119.318367] pci 0000:00:00.0: BAR 6: assigned [mem
> 0xf3060000-0xf306ffff pref]
>
> ---
>
> Does this mean that the 256Mb of physical memory is
> completely unaccessable on this board?
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2015-03-11 15:13 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 16:54 [PATCH] n_tty: use kmalloc() instead of vmalloc() to avoid crash on armada-xp Stas Sergeev
2015-03-10 16:54 ` Stas Sergeev
2015-03-10 17:17 ` Catalin Marinas
2015-03-10 17:17 ` Catalin Marinas
2015-03-10 17:27 ` Stas Sergeev
2015-03-10 17:27 ` Stas Sergeev
2015-03-10 17:38 ` Russell King - ARM Linux
2015-03-10 17:38 ` Russell King - ARM Linux
2015-03-10 18:31 ` Stas Sergeev
2015-03-10 18:31 ` Stas Sergeev
2015-03-10 18:54 ` Russell King - ARM Linux
2015-03-10 18:54 ` Russell King - ARM Linux
2015-03-11 12:30 ` Stas Sergeev
2015-03-11 12:30 ` Stas Sergeev
2015-03-11 12:47 ` Russell King - ARM Linux
2015-03-11 12:47 ` Russell King - ARM Linux
2015-03-11 14:24 ` Stas Sergeev
2015-03-11 14:24 ` Stas Sergeev
2015-03-11 16:30 ` Peter Hurley
2015-03-11 16:30 ` Peter Hurley
2015-03-11 16:39 ` Stas Sergeev
2015-03-11 16:39 ` Stas Sergeev
2015-03-12 12:33 ` Peter Hurley
2015-03-12 12:33 ` Peter Hurley
2015-03-12 12:47 ` Stas Sergeev
2015-03-12 12:47 ` Stas Sergeev
2015-03-12 13:04 ` Russell King - ARM Linux
2015-03-12 13:04 ` Russell King - ARM Linux
2015-03-12 13:11 ` Stas Sergeev
2015-03-12 13:11 ` Stas Sergeev
2015-03-12 15:34 ` Vladimir Murzin
2015-03-12 15:34 ` Vladimir Murzin
2015-03-12 12:59 ` Russell King - ARM Linux
2015-03-12 12:59 ` Russell King - ARM Linux
2015-03-10 17:29 ` Russell King - ARM Linux
2015-03-10 17:29 ` Russell King - ARM Linux
2015-03-10 17:35 ` Peter Hurley
2015-03-10 17:35 ` Peter Hurley
2015-03-10 17:51 ` Stas Sergeev
2015-03-10 17:51 ` Stas Sergeev
2015-03-10 18:45 ` Peter Hurley
2015-03-10 18:45 ` Peter Hurley
2015-03-11 12:44 ` Gregory CLEMENT
2015-03-11 12:44 ` Gregory CLEMENT
2015-03-11 12:57 ` Stas Sergeev
2015-03-11 12:57 ` Stas Sergeev
2015-03-11 13:14 ` Russell King - ARM Linux
2015-03-11 13:14 ` Russell King - ARM Linux
2015-03-11 14:33 ` Stas Sergeev
2015-03-11 14:33 ` Stas Sergeev
2015-03-11 15:01 ` Stas Sergeev
2015-03-11 15:01 ` Stas Sergeev
2015-03-11 15:13 ` Gregory CLEMENT [this message]
2015-03-11 15:13 ` Gregory CLEMENT
2015-03-11 15:22 ` Stas Sergeev
2015-03-11 15:22 ` Stas Sergeev
2015-03-12 13:06 ` Russell King - ARM Linux
2015-03-12 13:06 ` Russell King - ARM Linux
2015-03-11 16:52 ` Thomas Petazzoni
2015-03-11 16:52 ` Thomas Petazzoni
2015-03-11 17:26 ` Stas Sergeev
2015-03-11 17:26 ` Stas Sergeev
2015-03-11 17:46 ` Russell King - ARM Linux
2015-03-11 17:46 ` Russell King - ARM Linux
2015-03-11 17:56 ` Stas Sergeev
2015-03-11 17:56 ` Stas Sergeev
2015-03-11 18:11 ` Thomas Petazzoni
2015-03-11 18:11 ` Thomas Petazzoni
2015-03-11 18:38 ` Stas Sergeev
2015-03-11 18:38 ` Stas Sergeev
2015-03-11 18:41 ` Russell King - ARM Linux
2015-03-11 18:41 ` Russell King - ARM Linux
2015-03-11 18:08 ` Stas Sergeev
2015-03-11 18:08 ` Stas Sergeev
2015-03-11 18:33 ` Thomas Petazzoni
2015-03-11 18:33 ` Thomas Petazzoni
2015-03-12 12:44 ` Stas Sergeev
2015-03-12 12:44 ` Stas Sergeev
2015-03-12 12:47 ` Thomas Petazzoni
2015-03-12 12:47 ` Thomas Petazzoni
2015-03-12 13:03 ` Stas Sergeev
2015-03-12 13:03 ` Stas Sergeev
2015-03-12 13:12 ` Russell King - ARM Linux
2015-03-12 13:12 ` Russell King - ARM Linux
2015-03-12 13:16 ` Stas Sergeev
2015-03-12 13:16 ` Stas Sergeev
2015-03-12 13:55 ` Thomas Petazzoni
2015-03-12 13:55 ` Thomas Petazzoni
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=55005B81.9020103@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 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.