From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ab6f78c7f070d9898693681e9fe2a693@plan9.bell-labs.com>
Date: Fri, 10 Dec 2004 13:14:19 -0500
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] wierd interrupt 0xc6
In-Reply-To: <6d0cac4bece238981f87835046c70c15@yourdomain.dom>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 143cb514-eace-11e9-9e20-41e7f4b1d025

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