From: Vineet.Gupta1@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: AXS101: Problems with next-20160104
Date: Wed, 6 Jan 2016 11:51:39 +0530 [thread overview]
Message-ID: <568CB273.7040900@synopsys.com> (raw)
In-Reply-To: <568ABBAB.6090706@synopsys.com>
On Tuesday 05 January 2016 12:06 AM, Carlos Palminha wrote:
> Hi guys,
>
> I just tried to boot next-20160104 with ARC AXS101 and it goes on a loop when freeing boot mem... (check log below).
>
....
> Starting kernel ...
>
> Linux version 4.4.0-rc7-next-20160104 (palminha at palminha-vm) (gcc version 4.8.4 (Buildroot 2015.08.1) ) #2 PREEMPT Mon Jan 4 17:41:19 WET 2016
> Memory @ 80000000 [512M]
> Machine model: snps,axs101
> earlycon: Early serial console at MMIO32 0xe0022000 (options '115200n8')
> bootconsole [uart0] enabled
> AXS: MainBoard v3 FPGA Date: 25-6-2015
>
> IDENTITY : ARCVER [0x34] ARCNUM [0x4] CHIPID [ 0x0]
> processor [0] : ARC 700 R4.10 (ARCompact ISA)
> CPU speed : 750.00 Mhz
> Timers : Timer0 Timer1
...
> Stack Trace:
> arc_unwind_core.constprop.1+0xa4/0x110
> bad_page+0xda/0x120
> free_pages_prepare+0x218/0x244
> __free_pages_ok+0x1c/0x300
> free_all_bootmem+0x13c/0x1b8
> BUG: Bad page state in process swapper pfn:403bb
> page:9fdc864c count:0 mapcount:1 mapping: (null) index:0x0
> flags: 0x0()
> page dumped because: nonzero mapcount
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper Tainted: G B 4.4.0-rc7-next-20160104 #2
>
Hi Carlos,
Thx for the report. This is an upstream bug which is being discussed on mailing
list since yesterday !
-Vineet
next prev parent reply other threads:[~2016-01-06 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 18:36 AXS101: Problems with next-20160104 Carlos Palminha
2016-01-06 6:21 ` Vineet Gupta [this message]
2016-01-06 17:03 ` Carlos Palminha
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=568CB273.7040900@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=linux-snps-arc@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.