All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gunther Mayer <gunther.mayer@gmx.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -rt] Buggy uart (for 2.6.16)
Date: Mon, 10 Apr 2006 18:53:04 +0200	[thread overview]
Message-ID: <443A8D70.3040906@gmx.net> (raw)
In-Reply-To: <1144676225.12145.30.camel@localhost.localdomain>

Steven Rostedt wrote:

>Ingo,
>
>I've noticed that you dropped my "buggy uart" patch.  Probably because
>the 2.6.14 version would cause a deadlock on 2.6.16.  I've sent you a
>new update, but it must have been lost in all the noise.  Here's the
>patch again.  If you don't think this is a bug, try running the attached
>program on the machine that deadlocked (it is the one with the buggy
>uart). Without the patch, the serial_test will miss a wake up, and then
>be stuck in the sleeping TASK_INTERRUPTIBLE state (at least you can
>still kill it).  With the patch, it runs fine.
>
>I ran the program with the following parameters:
>
># ./serial_test /dev/ttyS0 115200 8 0 0 4
>
>(Disclaimer: I did not write this serial_test.  It was hacked up by my
>customer to show me that this bug exists).
>
>This may also be a bug with the vanilla kernel, since I don't see why it
>is not. I'll run more tests on the vanilla kernel, and if it too misses
>a wake up, I'll submit this to vanilla as well.
>
>
>Some 8250 uarts don't zero out the NO_INTERRUPT bit of the IIR register
>  
>
Can you name the exact 8250 model which is buggy ?


  reply	other threads:[~2006-04-10 17:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 13:37 [PATCH -rt] Buggy uart (for 2.6.16) Steven Rostedt
2006-04-10 16:53 ` Gunther Mayer [this message]
2006-04-10 17:51   ` Steven Rostedt
2006-04-10 20:22   ` Steven Rostedt
2006-04-11 20:57   ` Steven Rostedt
2006-04-12  6:27 ` Ingo Molnar
2006-05-07  8:30 ` Russell King
     [not found] <604MF-5Tc-7@gated-at.bofh.it>
     [not found] ` <6083V-2pi-9@gated-at.bofh.it>
     [not found]   ` <60bbB-6XU-17@gated-at.bofh.it>
2006-04-10 23:25     ` Robert Hancock

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=443A8D70.3040906@gmx.net \
    --to=gunther.mayer@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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 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.