From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open
Date: Tue, 11 Mar 2003 15:49:54 -0800 [thread overview]
Message-ID: <45750000.1047426594@flay> (raw)
I'm getting lots of these messages whilst running big SDET runs on
an 16-way machine ... anyone recognize them?
(64-bk3 + a few patches).
dev (pts(136,0)) tty->count(4) != #fd's(3) in release_dev
Warning: dev (pts(136,0)) tty->count(4) != #fd's(3) in tty_open
Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open
Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in release_dev
Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open
Warning: dev (pts(136,0)) tty->count(6) != #fd's(5) in tty_open
Warning: dev (pts(136,0)) tty->count(7) != #fd's(6) in tty_open
Warning: dev (pts(136,0)) tty->count(8) != #fd's(7) in tty_open
Warning: dev (pts(136,0)) tty->count(9) != #fd's(8) in tty_open
Warning: dev (pts(136,0)) tty->count(10) != #fd's(9) in tty_open
Warning: dev (pts(136,0)) tty->count(11) != #fd's(10) in tty_open
Warning: dev (pts(136,0)) tty->count(12) != #fd's(11) in tty_open
Warning: dev (pts(136,0)) tty->count(13) != #fd's(12) in tty_open
Warning: dev (pts(136,0)) tty->count(14) != #fd's(13) in tty_open
Warning: dev (pts(136,0)) tty->count(15) != #fd's(14) in tty_open
Warning: dev (pts(136,0)) tty->count(16) != #fd's(15) in tty_open
Warning: dev (pts(136,0)) tty->count(17) != #fd's(16) in tty_open
Warning: dev (pts(136,0)) tty->count(18) != #fd's(17) in tty_open
Warning: dev (pts(136,0)) tty->count(18) != #fd's(17) in release_dev
Warning: dev (pts(136,0)) tty->count(18) != #fd's(17) in tty_open
Warning: dev (pts(136,0)) tty->count(19) != #fd's(18) in tty_open
Warning: dev (pts(136,0)) tty->count(20) != #fd's(19) in tty_open
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in tty_open
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in tty_open
Warning: dev (pts(136,0)) tty->count(23) != #fd's(22) in tty_open
Warning: dev (pts(136,0)) tty->count(23) != #fd's(22) in release_dev
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in release_dev
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in release_dev
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in tty_open
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in tty_open
Warning: dev (pts(136,0)) tty->count(23) != #fd's(22) in tty_open
Warning: dev (pts(136,0)) tty->count(23) != #fd's(22) in release_dev
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in release_dev
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in tty_open
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in release_dev
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in release_dev
Warning: dev (pts(136,0)) tty->count(20) != #fd's(19) in release_dev
Warning: dev (pts(136,0)) tty->count(20) != #fd's(19) in tty_open
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in tty_open
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in tty_open
Warning: dev (pts(136,0)) tty->count(22) != #fd's(21) in release_dev
Warning: dev (pts(136,0)) tty->count(21) != #fd's(20) in release_dev
Warning: dev (pts(136,0)) tty->count(20) != #fd's(19) in release_dev
Warning: dev (pts(136,0)) tty->count(19) != #fd's(18) in release_dev
Warning: dev (pts(136,0)) tty->count(18) != #fd's(17) in release_dev
Warning: dev (pts(136,0)) tty->count(17) != #fd's(16) in release_dev
Warning: dev (pts(136,0)) tty->count(16) != #fd's(15) in release_dev
Warning: dev (pts(136,0)) tty->count(15) != #fd's(14) in release_dev
Warning: dev (pts(136,0)) tty->count(14) != #fd's(13) in release_dev
Warning: dev (pts(136,0)) tty->count(13) != #fd's(12) in release_dev
Warning: dev (pts(136,0)) tty->count(12) != #fd's(11) in release_dev
Warning: dev (pts(136,0)) tty->count(12) != #fd's(11) in tty_open
Warning: dev (pts(136,0)) tty->count(12) != #fd's(11) in release_dev
Warning: dev (pts(136,0)) tty->count(11) != #fd's(3) in release_dev
Warning: dev (pts(136,0)) tty->count(10) != #fd's(3) in release_dev
Warning: dev (pts(136,0)) tty->count(9) != #fd's(3) in release_dev
Warning: dev (pts(136,0)) tty->count(9) != #fd's(4) in tty_open
Warning: dev (pts(136,0)) tty->count(9) != #fd's(4) in release_dev
Warning: dev (pts(136,0)) tty->count(9) != #fd's(5) in tty_open
Warning: dev (pts(136,0)) tty->count(10) != #fd's(6) in tty_open
Warning: dev (pts(136,0)) tty->count(11) != #fd's(7) in tty_open
next reply other threads:[~2003-03-11 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 23:49 Martin J. Bligh [this message]
2003-03-12 0:21 ` Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open Andrew Morton
2003-03-12 0:29 ` Martin J. Bligh
2003-03-12 1:30 ` Alan Cox
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=45750000.1047426594@flay \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.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