From owner-freebsd-questions@FreeBSD.ORG Fri Jul 2 11:31:47 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F57516A4CE for ; Fri, 2 Jul 2004 11:31:47 +0000 (GMT) Received: from maze.meitech.com (maze.meitech.com [69.33.133.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21FC443D4C for ; Fri, 2 Jul 2004 11:31:47 +0000 (GMT) (envelope-from tjg@meitech.com) Received: from ripley.meitech.com (ripley.meitech.com [192.168.100.12]) by maze.meitech.com (8.12.11/8.12.9) with ESMTP id i62BUAF3058628; Fri, 2 Jul 2004 11:30:11 GMT (envelope-from tjg@meitech.com) Received: by RIPLEY with Internet Mail Service (5.5.2653.19) id ; Fri, 2 Jul 2004 07:34:55 -0400 Message-ID: <86ECB35C998DCC49AD435A099AFACCD1E8DB50@RIPLEY> From: "Gustafson, Tim" To: "'Sergey Zaharchenko'" , "'freebsd-questions@freebsd.org'" Date: Fri, 2 Jul 2004 07:34:54 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on maze.meitech.com Subject: RE: vi / EAGAIN Problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2004 11:31:47 -0000 Sergey, I have submitted the problem to FreeBSD using the send-pr program, as Jonathan Chen asked me to. I will follow up here with some details for you though. Once the problem starts happening, it seems that I have to log off the system and log back in again to fix it. This usually (95% of the time) fixes the problem. It also only happens when I press a key - if I let vi sit there with a file loaded into it, it will not get the error no matter how long I wait. The problem only happens when I press a key, and not always the first one. I can usually work in vi for 10-15 seconds before the error comes up. Anyhow, I have submitted the bug report and the link to my ktrace is still up, so if anyone has any ideas about what could be causing this, I would love to hear from you. For now, my work-around is to just log off and back in again when it happens, but as you can imagine, that gets annoying in a big hurry. Tim Tim Gustafson MEI Technology Consulting, Inc tjg@meitech.com (516) 379-0001 Office (516) 480-1870 Mobile/Emergencies http://www.meitech.com/