From: Helge Deller <deller@gmx.de>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-parisc@vger.kernel.org
Subject: Re: parisc boot crash on 3.10-rc1+git
Date: Tue, 14 May 2013 22:29:31 +0200 [thread overview]
Message-ID: <51929EAB.3020503@gmx.de> (raw)
In-Reply-To: <alpine.SOC.1.00.1305141432120.9094@math.ut.ee>
Hi Meelis,
(I dropped linux-kernel mailing list from CC!)
On 05/14/2013 01:48 PM, Meelis Roos wrote:
> I saw parsic fixes in todays git and gave my RP3440 a test.
Great :-)
> It did not
> work - first a __schedule_bug,
I assume you have CONFIG_PREEMPT enabled?
We know it's currently broken.
> then a lot of warnings from
> drivers/pci/search.c (2 different places) and finally a kernel panic.
See below.
> BUG: scheduling while atomic: swapper/0/0x0000000d
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper Not tainted 3.10.0-rc1-00087-g674825d #28
> Backtrace:
> [<0000000040114c90>] show_stack+0x20/0x38
> [<000000004030066c>] dump_stack+0x3c/0x50
> [<000000004016b6a8>] __schedule_bug+0x70/0x98
> [<000000004010fde0>] __schedule+0x368/0x398
> [<000000004010ff40>] schedule+0x38/0x90
> [<0000000040110184>] schedule_preempt_disabled+0x2c/0x50
^ yep.... CONFIG_PREEMPT I assume.
> WARNING: at drivers/pci/search.c:110
this line has: WARN_ON(in_interrupt());
I assume this is triggered by CONFIG_PREEMPT as well.
> ------------[ cut here ]------------
> kernel BUG at mm/vmalloc.c:1339!
-> again: BUG_ON(in_interrupt());
Please try again with CONFIG_PREEMPT disabled.
Helge
next prev parent reply other threads:[~2013-05-14 20:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 11:48 parisc boot crash on 3.10-rc1+git Meelis Roos
2013-05-14 20:29 ` Helge Deller [this message]
2013-05-15 6:59 ` Meelis Roos
2013-05-15 18:16 ` Helge Deller
2013-05-15 19:34 ` Rolf Eike Beer
2013-05-15 22:32 ` John David Anglin
2013-05-16 8:38 ` Rolf Eike Beer
2013-05-16 6:35 ` Meelis Roos
2013-05-16 12:15 ` John David Anglin
2013-05-16 12:23 ` Meelis Roos
2013-05-17 20:15 ` Helge Deller
2013-05-27 7:15 ` Meelis Roos
2013-05-27 19:20 ` Helge Deller
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=51929EAB.3020503@gmx.de \
--to=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=mroos@linux.ee \
/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.