From: Dan Malek <dan@embeddededge•com>
To: Jean-Denis Boyer <jdboyer@mediatrix•com>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: 8260 - Spurious interrupt when calling __sti()
Date: Wed, 10 Apr 2002 14:33:38 -0400 [thread overview]
Message-ID: <3CB48582.5030502@embeddededge.com> (raw)
In-Reply-To: F1BED55F35F4D3118C0F00E0295CFF4DFF9F95@mail.mediatrix.com
Jean-Denis Boyer wrote:
> However, this apparent 'out of sync' has nothing to do
> with the fact that the invalid interrupt pops up, right ?
If it happens only once at boot, there must be some device
with a dangling interrupt not properly initialized.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-10 18:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 18:30 8260 - Spurious interrupt when calling __sti() Jean-Denis Boyer
2002-04-10 18:33 ` Dan Malek [this message]
2002-04-10 20:24 ` Ron Bianco
2002-04-10 21:25 ` Dan Malek
2002-04-15 18:33 ` Val Henson
2002-04-16 18:58 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 17:16 Re[2]: " Jean-Denis Boyer
2002-04-10 17:04 ` Dan Malek
2002-04-10 16:31 Jean-Denis Boyer
2002-04-10 15:50 ` Dan Malek
2002-04-09 14:53 Jean-Denis Boyer
2002-04-09 17:09 ` Ricardo Scop
2002-04-09 18:26 ` Dan Malek
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=3CB48582.5030502@embeddededge.com \
--to=dan@embeddededge$(echo .)com \
--cc=jdboyer@mediatrix$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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