All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff DeFouw <jeffd@i2k.com>
To: "Kohne, Mike" <mike.kohne@gilbarco.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: 8250 misses interrupt, stalls
Date: Wed, 20 Aug 2008 11:29:38 -0400	[thread overview]
Message-ID: <20080820152938.GA10530@blorp.plorb.com> (raw)
In-Reply-To: <BD6105C44DDDF84AB07C23F6A35AE54E01E99F6D@dhrseasvxb03.messaging.danaherad.com>

On Fri, Aug 08, 2008 at 05:36:58AM -0700, Kohne, Mike wrote:
> I have a system (single core CPU, Winbond 83627HF, but with extra serial
> ports provided by a SCH3116 - another superio chip). In my box, the
> extra serial ports refuse to work (I never see interrupts) when I use
> SMP kernels. If I rebuild the kernel without SMP, my serial ports work
> fine. I've never gotten a sufficient explaination as to why turning on
> an SMP kernel would screw up these serial ports. We don't have the heavy
> (continuous) use that you do, so we would never have noticed the kind of
> errors you see.
> 
> Now obviously there's a wide difference between my behavior (they never
> work) and yours (they work for a while), but you might want to try
> building a non-SMP kernel (I took the distributed kernel config as my
> starting point, and just turned off SMP using make menuconfig). 
> 
> I'd be interested to know if this had any effect on your problem. 

I tried a stripped down UP kernel, but it didn't fix the problem.  It 
took about an hour to fail, compared to the usual under 10 minutes.  I 
also tried adding counters all over the interrupt paths and couldn't 
find any interrupts getting lost in the kernel.  It's looking like 
hardware for me.  I'll have to do some sort of workaround with timers.

-- 
Jeff DeFouw <jeffd@i2k.com>

      parent reply	other threads:[~2008-08-20 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08  5:27 8250 misses interrupt, stalls Jeff DeFouw
2008-08-08 12:36 ` Kohne, Mike
2008-08-13 14:56   ` [PATCH/RFC] " Robert Evans
2008-08-20 15:29   ` Jeff DeFouw [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=20080820152938.GA10530@blorp.plorb.com \
    --to=jeffd@i2k.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=mike.kohne@gilbarco.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.