From: Andreas Schwarz <usenet.2117@andreas-s.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Call traces due to lost IRQ
Date: Tue, 30 Sep 2003 16:47:56 +0000 (UTC) [thread overview]
Message-ID: <slrnbnjcu8.43n.usenet.2117@home.andreas-s.net> (raw)
In-Reply-To: 20030930154032.GA795@donald.balu5
Martin Pitt wrote:
> [1.] Kernel boot yields lost IRQ with some call traces
>
> [2.] When booting 2.6.0-test6, the following message appears:
>
> ------------- snip -------------
> irq 12: nobody cared!
> Call Trace:
> [<c010b5ca>] __report_bad_irq+0x2a/0x90
> [<c010b6bc>] note_interrupt+0x6c/0xa0
I've got the same messages (2.6.0-test6-mm1).
--
AVR-Tutorial, über 350 Links
Forum für AVRGCC und MSPGCC
-> http://www.mikrocontroller.net
next prev parent reply other threads:[~2003-09-30 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 15:40 Call traces due to lost IRQ Martin Pitt
2003-09-30 16:47 ` Andreas Schwarz [this message]
2003-09-30 17:28 ` Sergey S. Kostyliov
2003-09-30 18:24 ` Chris Wright
2003-09-30 19:03 ` Andreas Schwarz
2003-09-30 20:59 ` Chris Wright
2003-10-01 9:54 ` Andreas Schwarz
2003-09-30 22:24 ` Martin Pitt
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=slrnbnjcu8.43n.usenet.2117@home.andreas-s.net \
--to=usenet.2117@andreas-s.net \
--cc=linux-kernel@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).