From owner-freebsd-bugs  Fri Aug 30  8:20:12 2002
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3E7D437B401
	for <freebsd-bugs@hub.freebsd.org>; Fri, 30 Aug 2002 08:20:06 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EF24043E3B
	for <freebsd-bugs@hub.freebsd.org>; Fri, 30 Aug 2002 08:20:05 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g7UFK5JU071134
	for <freebsd-bugs@freefall.freebsd.org>; Fri, 30 Aug 2002 08:20:05 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g7UFK5sf071133;
	Fri, 30 Aug 2002 08:20:05 -0700 (PDT)
Date: Fri, 30 Aug 2002 08:20:05 -0700 (PDT)
Message-Id: <200208301520.g7UFK5sf071133@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Dan Nelson <dnelson@allantgroup.com>
Subject: Re: misc/22190: A threaded read(2) from a socketpair(2) fd can sometimes
 fail with errno 19 (ENODEV)
Reply-To: Dan Nelson <dnelson@allantgroup.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR misc/22190; it has been noted by GNATS.

From: Dan Nelson <dnelson@allantgroup.com>
To: freebsd-gnats-submit@FreeBSD.org, grubba@roxen.com
Cc:  
Subject: Re: misc/22190: A threaded read(2) from a socketpair(2) fd can sometimes
 fail with errno 19 (ENODEV)
Date: Fri, 30 Aug 2002 10:13:48 -0500

 Yes, it does.  The pike developers have a build farm, similar to 
 tinderbox, and my -current machine just failed the testsuite with the 
 error "read(2) failed with ENODEV!".  It seems to be very infrequent; 
 it's probably run a couple dozen builds with no problem.
 
 I'm going to add a PTHREAD_ASSERT in uthread_read.c to see if I other 
 programs are also getting ENODEV but ignoring it.  I haven't been able 
 to get crashdumps working on my -current box, so I can't put a panic in 
 the kernel's read().
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message