From: Alemao <xcarandiru@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Fwd: serial8250: too much work
Date: Thu, 28 May 2009 23:57:55 -0300 [thread overview]
Message-ID: <d970ff420905281957p69fba993ue7426f8413ec958f@mail.gmail.com> (raw)
In-Reply-To: <d970ff420905281057kefbf339y29257154c142186a@mail.gmail.com>
Im facing some problems with serial, getting flooded with this
message:
---
serial8250: too much work for irq16
---
Something I notice, in my .dts I have the following lines:
serial0: serial@4500, interrupts =3D <9 =A00x8>
serial1: serial@4600, interrupts =3D <10 0x8>
spi: =A0 =A0 spi@7000, =A0 =A0 interrupts =3D <16 0x8>
But when kernel starts:
---
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0xe0004500 (irq =3D 16) is a 16550A
---
Why IRQ 16? Shouldn't it be IRQ 9?
I traced functions calls in 8250.c driver:
---
serial8250_interrup() -> serial8250_handle_port() -> transmit_chars()
---
"too much work" is for transmiting, but there's nothing to transmit.
In my MPC8343 board I have only serial0 connected to a MAX3232, serial1
is floating. Maybe some electromagnetic interference in the bus?
I found this comments in linux/drivers/serial/8250.h, and tried to use
same defines that they used, but no success:
/*
=A0* Digital did something really horribly wrong with the OUT1 and OUT2
=A0* lines on at least some ALPHA's. =A0The failure mode is that if either
=A0* is cleared, the machine locks up with endless interrupts.
=A0*/
/*
=A0* WindRiver did something similarly broken on their SBC8560 board. The
=A0* UART tristates its IRQ output while OUT2 is clear, but they pulled
=A0* the interrupt line _up_ instead of down, so if we register the IRQ
=A0* while the UART is in that state, we die in an IRQ storm.
=A0*/
I also tried removing serial1 and spi from .dts, but didn't work.
Any sugestions?
Cheers,
--
Alemao
parent reply other threads:[~2009-05-29 2:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <d970ff420905281057kefbf339y29257154c142186a@mail.gmail.com>]
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=d970ff420905281957p69fba993ue7426f8413ec958f@mail.gmail.com \
--to=xcarandiru@gmail.com \
--cc=linuxppc-dev@ozlabs.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).