public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: John Stoffel <john@stoffel.org>,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6.18-rc1-mm1 - bad serial port count messages
Date: Tue, 11 Jul 2006 16:02:45 -0400	[thread overview]
Message-ID: <17588.997.688135.786150@stoffel.org> (raw)
In-Reply-To: <20060711185630.GA1240@flint.arm.linux.org.uk>


Russell> On Tue, Jul 11, 2006 at 09:20:29AM -0400, John Stoffel wrote:
>> I'm getting the following messages in dmesg:
>> 
>> uart_close: bad serial port count; tty->count is 1, state->count is 0
>> uart_close: bad serial port count for ttyS0: -1
>> uart_close: bad serial port count for ttyS0: -1

Russell> I assume that it's 100% reproducable, and doesn't happen with
Russell> mainline?

Not sure, haven't rebooted yet to make sure it happens again.  The
hardware is a Dell Dimension 630, Dual Xeon PIII 550mhz, 768mb of
RAM.  It's been my main machine for a number of years now.  

Russell> I'm not aware of any serial core patches in -mm which would
Russell> produce this type of breakage - maybe there's something funny
Russell> with the tty layer in that it's trying to close the port more
Russell> times than it's been opened...  Hmm.

I thought I saw something float by where someone had raised some new
locking or count variables?  I dunno... I'll work on it tonight and
see what happens after another reboot.

John

  reply	other threads:[~2006-07-11 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-11 13:20 2.6.18-rc1-mm1 - bad serial port count messages John Stoffel
2006-07-11 18:56 ` Russell King
2006-07-11 20:02   ` John Stoffel [this message]
2006-07-11 20:15     ` 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=17588.997.688135.786150@stoffel.org \
    --to=john@stoffel.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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