All of lore.kernel.org
 help / color / mirror / Atom feed
From: stsp@list.ru (Stas Sergeev)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] n_tty: use kmalloc() instead of vmalloc() to avoid crash on armada-xp
Date: Thu, 12 Mar 2015 15:44:44 +0300	[thread overview]
Message-ID: <55018A3C.7020409@list.ru> (raw)
In-Reply-To: <20150311193343.0317e3e1@free-electrons.com>

11.03.2015 21:33, Thomas Petazzoni ?????:
> Dear Stas Sergeev,
>
> On Wed, 11 Mar 2015 21:08:03 +0300, Stas Sergeev wrote:
>
>> mem=0xc0000000 seems to work!
>> 0xd0000000 or 0xe0000000 do not.
>> OK, so 3Gb instead of 8... but at least it boots! :)
> What is the value of the register 0xf1020254 ?
Hello Thomas, I haven't got to look into that register:
uboot is updated to v2011.12-2014_T2.0 and everything
is working! So thanks once again.
The only problem I now have is the lack of 256Mb of
ram.

[    0.000000] MEMBLOCK
configuration:                                         
[    0.000000]  memory size = 0x1f0000000 reserved size =
0x70d6e3             
[    0.000000]  memory.cnt  =
0x2                                              
[    0.000000]  memory[0x0]     [0x00000000000000-0x000000efffffff],
0xf0000000
bytes flags:
0x0                                                               
[    0.000000]  memory[0x1]     [0x00000100000000-0x000001ffffffff],
0x100000000
 bytes flags: 0x0 

There is a 8Gb in a single dimm.
Do you have any idea why 0xf0000000-0xffffffff range is missing?
I suspect this is something with uboot too.

WARNING: multiple messages have this Message-ID (diff)
From: Stas Sergeev <stsp@list.ru>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	"Linux kernel" <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	"Gregory Clément" <gregory.clement@free-electrons.com>,
	"Catalin Marinas" <catalin.marinas@arm.com>
Subject: Re: [PATCH] n_tty: use kmalloc() instead of vmalloc() to avoid crash on armada-xp
Date: Thu, 12 Mar 2015 15:44:44 +0300	[thread overview]
Message-ID: <55018A3C.7020409@list.ru> (raw)
In-Reply-To: <20150311193343.0317e3e1@free-electrons.com>

11.03.2015 21:33, Thomas Petazzoni пишет:
> Dear Stas Sergeev,
>
> On Wed, 11 Mar 2015 21:08:03 +0300, Stas Sergeev wrote:
>
>> mem=0xc0000000 seems to work!
>> 0xd0000000 or 0xe0000000 do not.
>> OK, so 3Gb instead of 8... but at least it boots! :)
> What is the value of the register 0xf1020254 ?
Hello Thomas, I haven't got to look into that register:
uboot is updated to v2011.12-2014_T2.0 and everything
is working! So thanks once again.
The only problem I now have is the lack of 256Mb of
ram.

[    0.000000] MEMBLOCK
configuration:                                         
[    0.000000]  memory size = 0x1f0000000 reserved size =
0x70d6e3             
[    0.000000]  memory.cnt  =
0x2                                              
[    0.000000]  memory[0x0]     [0x00000000000000-0x000000efffffff],
0xf0000000
bytes flags:
0x0                                                               
[    0.000000]  memory[0x1]     [0x00000100000000-0x000001ffffffff],
0x100000000
 bytes flags: 0x0 

There is a 8Gb in a single dimm.
Do you have any idea why 0xf0000000-0xffffffff range is missing?
I suspect this is something with uboot too.

  reply	other threads:[~2015-03-12 12:44 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
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 [this message]
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=55018A3C.7020409@list.ru \
    --to=stsp@list.ru \
    --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.