From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] wierd interrupt 0xc6
Date: Fri, 10 Dec 2004 13:14:19 -0500 [thread overview]
Message-ID: <ab6f78c7f070d9898693681e9fe2a693@plan9.bell-labs.com> (raw)
In-Reply-To: <6d0cac4bece238981f87835046c70c15@yourdomain.dom>
It looks like the handling of
Irls = 0x06, /* Receiver Line Status */
got lost in the rewrite a little while ago. You could try adding a case for it
in i8250interrupt, lumping it with Irda and Ictoi, i.e.
case Irda: /* Received Data Available */
case Irls: /* Receiver Line Status */
case Ictoi: /* Character Time-out Indication */
That may do, or we might have to split handling the data and error
conditions if it causes problems.
It means you are getting overrun, parity, framing or break interrupts.
--jim
On Fri Dec 10 12:39:05 EST 2004, west9@worldnet.att.net wrote:
> I've been getting this exception for a while now on modem
> downloads longer than about 3min: "wierd interrupt 0xc6" . It appears to be generated by the uart driver:
>
> grep weird ./*
> ./uarti8250.c: iprint("weird uart interrupt 0x%2.2uX\n", iir)
>
> I tried reseating the modem board.
>
> Does this mean I should start looking for a new mother board?
>
> Suggestions, please.
>
> Thanks
> -Tom
prev parent reply other threads:[~2004-12-10 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 17:43 west9
2004-12-10 18:14 ` jmk [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=ab6f78c7f070d9898693681e9fe2a693@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).