linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Claudius Heine <ch@denx.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Jan Kiszka <jan.kiszka@siemens.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Got stacktrace "irq 17: nobody cared" on Intel GalileoGen2 with 4.6.7-rt13
Date: Thu, 22 Sep 2016 16:16:19 +0200	[thread overview]
Message-ID: <1474553779.10922.87.camel@denx.de> (raw)
In-Reply-To: <20160922134912.6ttkfpphn2ga4z22@linutronix.de>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

On Thu, 2016-09-22 at 15:49 +0200, Sebastian Andrzej Siewior wrote:
> On 2016-09-22 10:24:26 [+0200], Jan Kiszka wrote:
> > 
> > One theory I was thinking about: Could - for whatever reason -
> > disabling
> > of the interrupt line from the primary handler be broken / work
> > unreliably and cause this storm?
> 
> It seems so. If you look at the complete boot log then the core code
> attempts multiple times to disable IRQ #17 with zero success.
> I would assume that booting an unpatched kernel with the threadirqs
> option would give the same result.

Thanks for your help, but I am sorry to disappoint:

Full bootlog: http://pastebin.com/8dHz0LLq
Kernel config: http://pastebin.com/itPLjpjS
ps: http://pastebin.com/D4N0DXae

Claudius

-- 
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

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2016-09-22 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22  8:19 Got stacktrace "irq 17: nobody cared" on Intel GalileoGen2 with 4.6.7-rt13 Claudius Heine
2016-09-22  8:24 ` Jan Kiszka
2016-09-22 13:49   ` Sebastian Andrzej Siewior
2016-09-22 14:16     ` Claudius Heine [this message]
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=1474553779.10922.87.camel@denx.de \
    --to=ch@denx.de \
    --cc=bigeasy@linutronix.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 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).