From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: ARC AXS101 problems with linux next-20151221
Date: Wed, 23 Dec 2015 16:44:46 +0530 [thread overview]
Message-ID: <567A8226.80308@synopsys.com> (raw)
In-Reply-To: <56784531.1000007@synopsys.com>
Hi Christoph, Andrew
> On Tuesday 22 December 2015 12:00 AM, Carlos Palminha wrote:
> Hi guys,
>
> I just compiled the kernel for axs101_defconfig based on linux next tag 'next-20151221'.
> I can't boot it due to the following errors causing strange stack traces after freeing unused kernel memory (check log below).
>
> Any clue?
> Do you more info to understand the issue?
....[snip]
> dw_mmc e0015000.mmc: IDMAC supports 32-bit address mode.
> dw_mmc e0015000.mmc: Using internal DMA controller.
> dw_mmc e0015000.mmc: Version ID is 270a
> dw_mmc e0015000.mmc: DW MMC controller at irq 34,32 bit host data width,16 deep fifo
> dw_mmc e0015000.mmc: 1 slots initialized
> sdhci-pltfm: SDHCI platform and OF driver helper
> usbcore: registered new interface driver usbhid
> usbhid: USB HID core driver
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> ttyS3 - failed to request DMA
> Freeing unused kernel memory: 928K (80002000 - 800ea000)
> INFO: rcu_preempt self-detected stall on CPU
> 0-...: (2100 ticks this GP) idle=011/140000000000001/0 softirq=92/92 fqs=0
> (t=2100 jiffies g=-261 c=-262 q=60)
> rcu_preempt kthread starved for 2100 jiffies! g4294967035 c4294967034 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x1
> rcu_preempt S 8053879e 0 7 2 0x00000000
>
> Stack Trace:
> __switch_to+0x0/0x94
> __schedule+0x1c2/0x724
> schedule+0x2a/0x74
> schedule_timeout+0x126/0x198
> rcu_gp_kthread+0x5fa/0xee8
> kthread+0xe2/0xf4
> ret_from_fork+0x18/0x1c
> Task dump for CPU 0:
> kworker/0:1 R running 0 19 2 0x00000008
> Workqueue: events_freezable mmc_rescan
[snip]
It seems the dma ops rework for ARC makes kernel belly up.
Patch below fixes it.
------------->
parent reply other threads:[~2015-12-23 11:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <56784531.1000007@synopsys.com>]
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=567A8226.80308@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).