From: Peter Hurley <peter@hurleysoftware.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>, Mikael Pettersson <mikpe@it.uu.se>,
David Howells <dhowells@redhat.com>,
Orion Poplawski <orion@cora.nwra.com>
Subject: Re: [PATCH] tty: Debug EIO from write()
Date: Thu, 13 Jun 2013 12:29:31 -0400 [thread overview]
Message-ID: <51B9F36B.6020802@hurleysoftware.com> (raw)
In-Reply-To: <20130613161606.GA516@x4>
On 06/13/2013 12:16 PM, Markus Trippelsdorf wrote:
> I've reproduced the Mozilla build failure, but there's nothing exiting
> in the logs. The only strange thing is the single tty_write at
> 1507.456817 (roughly at this point the Mozilla build failed):
>
> ...
> [ 1507.453547] tty_release: pts11 (tty count=4)...
> [ 1507.455695] tty_open: opening pts11...
> [ 1507.455699] tty_release: pts11 (tty count=4)...
> [ 1507.455854] tty_open: opening pts11...
> [ 1507.455858] tty_release: pts11 (tty count=4)...
> [ 1507.456815] tty_open: opening pts11...
> [ 1507.456817] tty_write: pts11: 0xa03
Totally obvious now, thanks!
Patch coming.
> [ 1507.456819] tty_release: pts11 (tty count=4)...
> [ 1507.457313] tty_open: opening pts11...
> [ 1507.457317] tty_release: pts11 (tty count=4)...
> [ 1507.458711] tty_open: opening pts11...
> [ 1507.458715] tty_release: pts11 (tty count=4)...
> [ 1507.458918] tty_open: opening pts11...
> [ 1507.458922] tty_release: pts11 (tty count=4)...
> [ 1507.459062] tty_open: opening pts11...
> [ 1507.459066] tty_release: pts11 (tty count=4)...
> ...
>
> Looking through my logs I see a few ldisc errors, but please note that they are
> all unrelated to the actual Mozilla failure.
>
> Jun 13 17:31:07 x4 kernel: tty_open: opening pts11...
> Jun 13 17:31:07 x4 kernel: tty_release: pts11 (tty count=4)...
> Jun 13 17:31:08 x4 kernel: tty_release: ptm1 (tty count=1)...
> Jun 13 17:31:08 x4 kernel: tty_read: pts1: ldisc error (0xa05)
These "ldisc error"s are expected. In this case, the master end has closed while
the slave end is reading....
> Jun 13 17:31:08 x4 kernel: pts1 vhangup...
> Jun 13 17:31:08 x4 kernel: hung_up_tty_write: pts1: 0x200a05
and writing.
The others in this snippet are similar.
> Jun 13 17:31:08 x4 kernel: tty_release: pts1 (tty count=2)...
> Jun 13 17:31:08 x4 kernel: tty_release: ptm1: final close
> Jun 13 17:31:08 x4 kernel: tty_release: ptm1: freeing structure...
> Jun 13 17:31:08 x4 kernel: tty_release: ptm0 (tty count=1)...
> Jun 13 17:31:08 x4 kernel: pts0 vhangup...
> Jun 13 17:31:08 x4 kernel: tty_release: pts0 (tty count=1)...
> Jun 13 17:31:08 x4 kernel: tty_release: pts0: final close
> Jun 13 17:31:08 x4 kernel: tty_release: pts0: freeing structure...
> Jun 13 17:31:08 x4 kernel: tty_release: tty1 (tty count=8)...
> Jun 13 17:31:08 x4 kernel: tty_release: tty3 (tty count=1)...
> Jun 13 17:31:08 x4 kernel: tty_release: tty3: final close
> Jun 13 17:31:08 x4 kernel: tty_release: tty3: freeing structure...
> Jun 13 17:31:11 x4 kernel: tty_open: opening tty1...
> Jun 13 17:31:11 x4 kernel: tty_open: opening tty1...
> Jun 13 17:31:11 x4 kernel: tty_release: tty1 (tty count=9)...
> Jun 13 17:31:13 x4 kernel: tty_release: tty1 (tty count=8)...
> Jun 13 17:31:13 x4 kernel: tty_release: tty2 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: tty_release: tty2: final close
> Jun 13 17:31:13 x4 kernel: tty_release: tty2: freeing structure...
> Jun 13 17:31:13 x4 kernel: tty_release: pts6 (tty count=2)...
> Jun 13 17:31:13 x4 kernel: tty1 vhangup session...
> Jun 13 17:31:13 x4 kernel: tty_open: opening pts2...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm5 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: pts5 vhangup...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm6 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: pts6 vhangup...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm6: final close
> Jun 13 17:31:13 x4 kernel: tty_release: ptm6: freeing structure...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm7 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: pts7 vhangup...
> Jun 13 17:31:13 x4 kernel: tty_release: pts5 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: tty_release: pts5: final close
> Jun 13 17:31:13 x4 kernel: tty_release: pts5: freeing structure...
> Jun 13 17:31:13 x4 kernel: tty_read: pts7: ldisc error (0x200805)
> Jun 13 17:31:13 x4 kernel: tty_release: ptm8 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: pts8 vhangup...
> Jun 13 17:31:13 x4 kernel: tty_read: pts8: ldisc error (0x200805)
> Jun 13 17:31:13 x4 kernel: tty_release: tty1 (tty count=7)...
> Jun 13 17:31:13 x4 kernel: tty_release: tty1 (tty count=6)...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm9 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: pts9 vhangup...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm10 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: pts10 vhangup...
> Jun 13 17:31:13 x4 kernel: hung_up_tty_write: pts10: 0x40a04
> Jun 13 17:31:13 x4 kernel: hung_up_tty_write: pts10: 0x40a04
> Jun 13 17:31:13 x4 kernel: tty_open: opening tty1...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm3 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: pts3 vhangup...
> Jun 13 17:31:13 x4 kernel: tty_read: pts3: ldisc error (0x200805)
> Jun 13 17:31:13 x4 kernel: tty_release: pts7 (tty count=2)...
> Jun 13 17:31:13 x4 kernel: tty_release: pts7 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: tty_release: pts7: final close
> Jun 13 17:31:13 x4 kernel: tty_release: pts7: freeing structure...
> Jun 13 17:31:13 x4 kernel: tty_release: pts4 (tty count=2)...
> Jun 13 17:31:13 x4 kernel: tty_open: opening tty2...
> Jun 13 17:31:13 x4 kernel: tty_release: tty2 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: tty_release: tty2: final close
> Jun 13 17:31:13 x4 kernel: tty_release: tty2: freeing structure...
> Jun 13 17:31:13 x4 kernel: tty_open: opening tty2...
> Jun 13 17:31:13 x4 kernel: tty_release: tty1 (tty count=6)...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm4 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: pts4 vhangup...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm4: final close
> Jun 13 17:31:13 x4 kernel: tty_release: ptm4: freeing structure...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm11 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: pts11 vhangup...
> Jun 13 17:31:13 x4 kernel: tty_read: pts11: ldisc error (0x200a05)
> Jun 13 17:31:13 x4 kernel: tty_release: pts11 (tty count=3)...
> Jun 13 17:31:13 x4 kernel: tty_release: pts11 (tty count=2)...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm11: final close
> Jun 13 17:31:13 x4 kernel: tty_release: ptm11: freeing structure...
> Jun 13 17:31:13 x4 kernel: tty_release: ptm2 (tty count=1)...
> Jun 13 17:31:13 x4 kernel: pts2 vhangup...
> Jun 13 17:31:13 x4 kernel: tty_read: pts2: ldisc error (0x200a05)
> Jun 13 17:31:13 x4 kernel: tty_release: pts2 (tty count=3)...
> Jun 13 17:31:13 x4 kernel: tty_release: pts3 (tty count=2)...
> Jun 13 17:31:13 x4 kernel: hung_up_tty_write: pts3: 0x40a06
> Jun 13 17:31:13 x4 kernel: hung_up_tty_write: pts3: 0x40a06
>
>
next prev parent reply other threads:[~2013-06-13 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 11:54 Strange intermittent EIO error when writing to stdout since v3.8.0 Markus Trippelsdorf
2013-06-06 14:18 ` Peter Hurley
2013-06-06 14:37 ` Markus Trippelsdorf
2013-06-07 15:39 ` Peter Hurley
2013-06-07 16:07 ` Markus Trippelsdorf
2013-06-07 18:22 ` Mikael Pettersson
2013-06-13 10:39 ` Markus Trippelsdorf
2013-06-13 14:16 ` Peter Hurley
2013-06-13 14:51 ` Markus Trippelsdorf
2013-06-13 15:25 ` [PATCH] tty: Debug EIO from write() Peter Hurley
2013-06-13 16:16 ` Markus Trippelsdorf
2013-06-13 16:29 ` Peter Hurley [this message]
2013-06-13 19:56 ` [PATCH] tty: Fix transient pty write() EIO Peter Hurley
2013-06-16 17:31 ` Mikael Pettersson
2013-06-07 19:56 ` Strange intermittent EIO error when writing to stdout since v3.8.0 David Howells
2013-06-11 22:14 ` Orion Poplawski
2013-06-13 10:38 ` Markus Trippelsdorf
2013-06-06 14:41 ` Mikael Pettersson
2013-06-06 17:31 ` David Howells
2013-06-06 18:41 ` Markus Trippelsdorf
2013-06-08 18:56 ` Rob Landley
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=51B9F36B.6020802@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mikpe@it.uu.se \
--cc=orion@cora.nwra.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.