From: Claudius Heine <ch@denx.de>
To: linux-rt-users@vger.kernel.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Got stacktrace "irq 17: nobody cared" on Intel GalileoGen2 with 4.6.7-rt13
Date: Thu, 22 Sep 2016 10:19:31 +0200 [thread overview]
Message-ID: <1474532371.10922.50.camel@denx.de> (raw)
Hi everyone,
I am currently trying to get the current Linux 4.6.7-rt13 running on an
Intel QUARK/GalileoGen2 Board and got the same repeating stacktrace
when booting. This does not happen in the vanilla kernel.
For 4.6.7-rt13 I used this Kernel commit:
f1cf4c43c5ff76957459ea90dc39dcd93a5d0ebd
Also tried the 4.4.19-rt27 and 4.4.20-rt19 with the same result.
Does anyone know what could cause this and how to fix it?
Thanks and have a nice day,
Claudius
Full bootlog: http://pastebin.com/qhSQdHYY
Kernel config: http://pastebin.com/XFKihFr4
Stacktrace:
[ 7.165722] irq 17: nobody cared (try booting with the "irqpoll"
option)
[ 7.165752] CPU: 0 PID: 82 Comm: irq/17-pxa2xx-s Not tainted 4.6.7-
rt13-yocto-preempt-rt #1
[ 7.165762] Hardware name: Intel Corp. QUARK/GalileoGen2, BIOS
0x01000400 01/01/2014
[ 7.165804] cd65db78 cd65db78 cd433f4c c13a0c54 cd433f68 c10888cd
c18829d8 00000011
[ 7.165839] cd65db40 cd65db40 00000011 cd433f8c c1088c4f cd65db40
00000020 cd798a40
[ 7.165872] cd433f84 cd65db40 00000020 00000000 cd433fd8 c10866c3
00000000 00000007
[ 7.165877] Call Trace:
[ 7.165921] [<c13a0c54>] dump_stack+0x16/0x22
[ 7.165967] [<c10888cd>] __report_bad_irq.isra.0+0x2d/0x110
[ 7.166008] [<c1088c4f>] note_interrupt+0x22f/0x270
[ 7.166051] [<c10866c3>] handle_irq_event_percpu+0xd3/0x240
[ 7.166091] [<c10878b4>] ? irq_thread+0xc4/0x1b0
[ 7.166137] [<c10894e0>] ? handle_edge_irq+0x170/0x170
[ 7.166173] [<c1086870>] handle_irq_event+0x40/0x90
[ 7.166212] [<c1089570>] handle_fasteoi_irq+0x90/0x190
[ 7.166251] [<c101a6ae>] handle_irq+0x5e/0x70
[ 7.166299] <IRQ> [<c1755822>] do_IRQ+0x42/0xd0
[ 7.166334] [<c1754f8c>] common_interrupt+0x2c/0x40
[ 7.166370] [<c105043d>] ? __local_bh_enable+0xd/0x70
[ 7.166405] [<c1080000>] ? wakeup_count_show+0x40/0x50
[ 7.166443] [<c10878b4>] ? irq_thread+0xc4/0x1b0
[ 7.166485] [<c1087680>] ? irq_finalize_oneshot.part.1+0x160/0x160
[ 7.166521] [<c1087720>] ? irq_thread_fn+0x40/0x40
[ 7.166559] [<c10877f0>] ? irq_thread_dtor+0xd0/0xd0
[ 7.166596] [<c1066cba>] kthread+0x9a/0xb0
[ 7.166636] [<c1754730>] ret_from_kernel_thread+0x20/0x40
[ 7.166666] [<c1066c20>] ? kthread_worker_fn+0x130/0x130
[ 7.166689] handlers:
[ 7.166740] [<c10868c0>] irq_default_primary_handler threaded
[<c14d0360>] ssp_int
[ 7.166749] Disabling IRQ #17
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next reply other threads:[~2016-09-22 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 8:19 Claudius Heine [this message]
2016-09-22 8:24 ` Got stacktrace "irq 17: nobody cared" on Intel GalileoGen2 with 4.6.7-rt13 Jan Kiszka
2016-09-22 13:49 ` Sebastian Andrzej Siewior
2016-09-22 14:16 ` Claudius Heine
2016-09-22 14:41 ` Sebastian Andrzej Siewior
2016-09-23 15:39 ` Jan Kiszka
2016-09-23 16:00 ` Sebastian Andrzej Siewior
2016-09-23 16:12 ` Jan Kiszka
2016-09-23 16:17 ` Sebastian Andrzej Siewior
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=1474532371.10922.50.camel@denx.de \
--to=ch@denx.de \
--cc=jan.kiszka@siemens.com \
--cc=linux-rt-users@vger.kernel.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.