mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Meelis Roos <mroos@linux.ee>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: Serial: bug in 8250.c when handling PCI or other level triggers
Date: Fri, 23 Dec 2005 10:41:46 +0000	[thread overview]
Message-ID: <20051223104146.GB22506@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.SOC.4.61.0512231204290.8311@math.ut.ee>

On Fri, Dec 23, 2005 at 12:05:35PM +0200, Meelis Roos wrote:
> >Ok, please apply this patch on top of the previous and re-send the
> >kernel messages.  This will let us see what's going on with 'l' and
> >'end'.
> 
> >+		printk("serial8250: port %p(%d) head=%p end=%p\n", up, 
> >up->port.line, i->head, end);
> 
> replaced i->heqad with l because i is shadowed by a local variable here, 
> now it compiles.

Argh, fek fek fek.  The original debug patch contained some extra code
to try to combat a problem I've been seeing here, which is causing more
complaints from your machine.

Right, discard all the patches I sent previously and use this one.

Thanks.

diff --git a/drivers/serial/8250.c b/drivers/serial/8250.c
--- a/drivers/serial/8250.c
+++ b/drivers/serial/8250.c
@@ -69,7 +69,8 @@ static unsigned int share_irqs = SERIAL8
 #define DEBUG_INTR(fmt...)	do { } while (0)
 #endif
 
-#define PASS_LIMIT	256
+//#define PASS_LIMIT	256
+#define PASS_LIMIT	32
 
 /*
  * We default to IRQ0 for the "no irq" hack.   Some
@@ -135,6 +136,18 @@ struct uart_8250_port {
 	 */
 	void			(*pm)(struct uart_port *port,
 				      unsigned int state, unsigned int old);
+
+	struct log {
+		unsigned long	jiffies;
+		unsigned char	type;
+		unsigned char	num;
+		unsigned char	unused[2];
+		unsigned char	lsr_b;
+		unsigned char	iir_b;
+		unsigned char	lsr_e;
+		unsigned char	iir_e;
+	} log[64];
+	unsigned char		log_idx;
 };
 
 struct irq_info {
@@ -1284,6 +1297,8 @@ serial8250_handle_port(struct uart_8250_
 {
 	unsigned int status = serial_inp(up, UART_LSR);
 
+	up->log[up->log_idx].lsr_b = status;
+
 	DEBUG_INTR("status = %x...", status);
 
 	if (status & UART_LSR_DR)
@@ -1291,6 +1306,8 @@ serial8250_handle_port(struct uart_8250_
 	check_modem_status(up);
 	if (status & UART_LSR_THRE)
 		transmit_chars(up);
+
+	up->log[up->log_idx].lsr_e = status;
 }
 
 /*
@@ -1325,6 +1342,12 @@ static irqreturn_t serial8250_interrupt(
 		up = list_entry(l, struct uart_8250_port, list);
 
 		iir = serial_in(up, UART_IIR);
+
+		up->log[up->log_idx].jiffies = jiffies;
+		up->log[up->log_idx].type = 0;
+		up->log[up->log_idx].num = pass_counter;
+		up->log[up->log_idx].iir_b = iir;
+
 		if (!(iir & UART_IIR_NO_INT)) {
 			spin_lock(&up->port.lock);
 			serial8250_handle_port(up, regs);
@@ -1336,21 +1359,45 @@ static irqreturn_t serial8250_interrupt(
 		} else if (end == NULL)
 			end = l;
 
+		up->log[up->log_idx].iir_e = serial_in(up, UART_IIR);
+		up->log_idx = (up->log_idx + 1) & 63;
+
 		l = l->next;
 
 		if (l == i->head && pass_counter++ > PASS_LIMIT) {
 			/* If we hit this, we're dead. */
 			printk(KERN_ERR "serial8250: too much work for "
 				"irq%d\n", irq);
-			break;
+			goto debug;
 		}
 	} while (l != end);
 
+ out:
 	spin_unlock(&i->lock);
 
 	DEBUG_INTR("end.\n");
 
 	return IRQ_RETVAL(handled);
+
+ debug:
+	l = i->head;
+	do {
+		struct uart_8250_port *up = list_entry(l, struct uart_8250_port, list);
+		int j;
+
+		printk("serial8250: port %p(%d)\n", up, up->port.line);
+		for (j = 0; j < 64; j++)
+			printk("%d: jif=%08lx type=%02x num=%02x iir=%02x lsr=%02x => iir=%02x lsr=%02x\n", j,
+				up->log[(up->log_idx + j) & 63].jiffies,
+				up->log[(up->log_idx + j) & 63].type,
+				up->log[(up->log_idx + j) & 63].num,
+				up->log[(up->log_idx + j) & 63].iir_b,
+				up->log[(up->log_idx + j) & 63].lsr_b,
+				up->log[(up->log_idx + j) & 63].iir_e,
+				up->log[(up->log_idx + j) & 63].lsr_e);
+		l = l->next;
+	} while (l != i->head);
+	goto out;
 }
 
 /*


-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-12-23 10:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 15:23 Alan Cox
2005-12-14 16:07 ` Meelis Roos
2005-12-14 17:24   ` Russell King
2005-12-14 18:43     ` Meelis Roos
2005-12-21 15:24       ` Russell King
2005-12-21 20:33     ` Meelis Roos
2005-12-21 22:15       ` Russell King
2005-12-22 10:35         ` Meelis Roos
2005-12-22 13:07           ` Russell King
2005-12-22 13:19             ` Meelis Roos
2005-12-23  9:20             ` Meelis Roos
2005-12-23  9:33               ` Russell King
2005-12-23 10:05                 ` Meelis Roos
2005-12-23 10:41                   ` Russell King [this message]
2005-12-27 13:54                     ` Meelis Roos
2005-12-28 19:55                       ` Russell King
2005-12-29  8:11                         ` Meelis Roos
2006-01-08 23:24                           ` Antonio Vargas
2006-01-09  8:54                             ` Russell King
2005-12-14 22:29   ` Alan Cox
2005-12-15 19:00     ` Stuart MacDonald
2005-12-14 16:55 ` Russell King
2005-12-14 19:08   ` Alan Cox
2005-12-14 19:55     ` Russell King

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=20051223104146.GB22506@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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

all inboxes | Powered by JetHome®