From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: TI-Davinci 6446 oops on interrupts
Date: Mon, 6 Jun 2011 19:50:29 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1106061948140.13964@ionos> (raw)
In-Reply-To: <4DED124C.50205@selfish.org>
On Mon, 6 Jun 2011, Holger Freyther wrote:
> On 06/06/2011 06:32 PM, Russell King - ARM Linux wrote:
> Hi Russell,
>
> thanks for your time and sorry for sending a truncated kernel oops. In the
> other part of the thread we found that the davinci GPIO code overrides the IRQ
> chip data.
>
>
> > Unless we have the Code: line we don't know what the code being executed
> > was. It's important that folk always report the entire oops dump, not
> > extracts from it that they _think_ may be relevant.
>
> is it still useful to send a complete oops, or do you think the issue is fully
> understood?
It is. Letting chip data point to something which is not expected by
the generic chip is definitly causing that issue.
Thanks,
tglx
next prev parent reply other threads:[~2011-06-06 17:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 12:41 TI-Davinci 6446 oops on interrupts Holger Freyther
2011-06-06 13:40 ` Holger Hans Peter Freyther
2011-06-06 14:54 ` Thomas Gleixner
2011-06-06 15:10 ` Holger Freyther
2011-06-06 15:25 ` Thomas Gleixner
2011-06-06 15:32 ` Holger Freyther
2011-06-06 21:31 ` Thomas Gleixner
2011-06-06 22:50 ` Kevin Hilman
2011-06-07 18:13 ` Nori, Sekhar
2011-06-07 22:59 ` Thomas Gleixner
2011-06-10 18:47 ` Holger Freyther
2011-06-06 14:49 ` Thomas Gleixner
2011-06-06 16:32 ` Russell King - ARM Linux
2011-06-06 17:45 ` Holger Freyther
2011-06-06 17:50 ` Thomas Gleixner [this message]
2011-06-06 21:30 ` Thomas Gleixner
2011-06-06 16:30 ` Russell King - ARM Linux
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=alpine.LFD.2.02.1106061948140.13964@ionos \
--to=tglx@linutronix.de \
--cc=linux-arm-kernel@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