Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
Cc: linux-mips@linux-mips.org
Subject: Re: unexpected irq 71 on ip32
Date: Mon, 17 Mar 2008 11:08:15 +0100	[thread overview]
Message-ID: <20080317100815.GA10179@alpha.franken.de> (raw)
In-Reply-To: <1205746904.3515.37.camel@localhost>

On Mon, Mar 17, 2008 at 10:41:44AM +0100, Giuseppe Sacco wrote:
> from what I understand, this is an irq related to serial line ttyS1. On

I had a closer look, and it's related to ttyS1. Looks like the DMA
interface for serial (probably RX DMA overrun). I'll have a look
later, why we don't ignore this interrupt.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2008-03-17 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17  9:41 unexpected irq 71 on ip32 Giuseppe Sacco
2008-03-17 10:01 ` Thomas Bogendoerfer
2008-03-17 10:07   ` Giuseppe Sacco
2008-03-17 10:08 ` Thomas Bogendoerfer [this message]

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=20080317100815.GA10179@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=giuseppe@eppesuigoccas.homedns.org \
    --cc=linux-mips@linux-mips.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