From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Luciano Coelho <coelho@ti.com>
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 3.1-rc3 fails to boot on my pandaboard
Date: Thu, 25 Aug 2011 13:04:23 +0200 [thread overview]
Message-ID: <20110825110423.GA12911@linutronix.de> (raw)
In-Reply-To: <1314268769.2296.283.camel@cumari>
* Luciano Coelho | 2011-08-25 13:39:29 [+0300]:
>Hi,
Hi,
>Any ideas what may be going wrong?
I think my commit was identified as bogus and tglx is going to revert
it. The problem is that I force ONESHOT mode for all threaded IRQs but
there are also others without the flag which is not allowed.
I was trying to check something but I don't get my board to boot. Could
you please try to boot with the patch reverted and paste me the
the output of
cat /proc/interrupts | grep 74 ?
I *think* that the flow handler is level (I can't find evidence of it
beeing edge, and omap_alloc_gc() is the place installing it).
So could you please gather additional debug info with this patch?
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index 2e94258..eda25a0 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -1327,6 +1327,9 @@ int request_threaded_irq(unsigned int irq, irq_handler_t handler,
if (!irq_settings_can_request(desc))
return -EINVAL;
+ if (irq == 74)
+ printk(KERN_ERR "%s() h %pS th %pS f %lx dev %s flow %pS\n", __func__,
+ handler, thread_fn, irqflags, devname, desc->handle_irq);
if (!handler) {
if (!thread_fn)
return -EINVAL;
%pS should resolve the function names.
Sebastian
next prev parent reply other threads:[~2011-08-25 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 10:39 Luciano Coelho
2011-08-25 11:04 ` Sebastian Andrzej Siewior [this message]
2011-08-25 11:24 ` Luciano Coelho
2011-08-25 11:41 ` Sebastian Andrzej Siewior
2011-08-25 11:35 ` Govindraj
2011-08-25 11:39 ` Luciano Coelho
2011-08-25 11:45 ` Govindraj
2011-08-26 19:05 ` Maupin, Chase
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=20110825110423.GA12911@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=coelho@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®