From owner-freebsd-questions@FreeBSD.ORG Thu Jul 20 18:31:02 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 3912516A4DD for ; Thu, 20 Jul 2006 18:31:02 +0000 (UTC) (envelope-from george@m5p.com) Received: from mailhost.m5p.com (209-162-215-52.dq1sn.easystreet.com [209.162.215.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C10243D49 for ; Thu, 20 Jul 2006 18:31:01 +0000 (GMT) (envelope-from george@m5p.com) Received: from m5p.com (ssh.m5p.com [IPv6:2001:418:3fd::fb]) by mailhost.m5p.com (8.13.7/8.13.7) with ESMTP id k6KIUxdJ023177 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=OK) for ; Thu, 20 Jul 2006 11:30:59 -0700 (PDT) Received: (from george@localhost) by m5p.com (8.13.7/8.13.7/Submit) id k6KIUxbw000837; Thu, 20 Jul 2006 11:30:59 -0700 (PDT) Date: Thu, 20 Jul 2006 11:30:59 -0700 (PDT) Message-Id: <200607201830.k6KIUxbw000837@m5p.com> From: george+freebsd@m5p.com To: freebsd-questions@freebsd.org X-Spam-Score: -2.12 () AWL,BAYES_00,NO_RELAYS X-Scanned-By: MIMEDefang 2.56 on IPv6:2001:418:3fd::f7 Subject: FreeBSD 6: open(/dev/lpt0, O_WRONLY) hangup "fixed" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jul 2006 18:31:02 -0000 I've "solved" my /dev/lpt0 problem. Here is what happened: 1. I observed that the problem is also happening on FreeBSD 6.0. 2. It isn't happening on 5.3. 3. I sprinkled some printf's into lptopen in sys/dev/ppbus/lpt.c. 4. I compiled a new kernel, stripping a whole bunch of stuff out of the generic kernel. The problem went away. 5. I went back to the original lpt.c. Still working. 6. I compiled another kernel, adding "device plip" back in. The problem came back. So the problem, whatever it is, seems to involve an interaction between printing and plip. Since I have printing working again, debugging the problem is no longer a high priority for me. But if anyone has some suggestions for debugging, I would be happy to try them this weekend. Am I the only dinosaur still using a parallel port printer? It seems incredible to me that no one else using 6.0/6.1 could have encountered this problem. Even though I have "fixed" the problem, it should probably be debugged properly, unless there's sentiment for removing "device plip" from the generic kernel. -- George Mitchell