From owner-freebsd-hackers@FreeBSD.ORG Sat Jul 22 08:20:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4841316A4E1 for ; Sat, 22 Jul 2006 08:20:30 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91A3443D45 for ; Sat, 22 Jul 2006 08:20:29 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail07.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k6M8KR8Z008936 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 22 Jul 2006 18:20:27 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k6M8KQtQ011344; Sat, 22 Jul 2006 18:20:26 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k6M8KQAT011343; Sat, 22 Jul 2006 18:20:26 +1000 (EST) (envelope-from peter) Date: Sat, 22 Jul 2006 18:20:26 +1000 From: Peter Jeremy To: george+freebsd@m5p.com Message-ID: <20060722082026.GG728@turion.vk2pj.dyndns.org> References: <200607220546.k6M5kq59001314@m5p.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SUk9VBj82R8Xhb8H" Content-Disposition: inline In-Reply-To: <200607220546.k6M5kq59001314@m5p.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 6.0/6.1: open ("/dev/lpt0" ...) hangs up X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jul 2006 08:20:30 -0000 --SUk9VBj82R8Xhb8H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 2006-Jul-21 22:46:52 -0700, george+freebsd@m5p.com wrote: >sprinkled in). I'm guessing that if_plip.c has requested it and not >released it, which apparently happens when there's been an ioctl on >the plip. There's no plausible reason why anythhing should be >happeneing on plip, as far as I can tell. There are several points in the startup code where it iterates through all the available network interfaces. Possibly one of those is the culprit. > What can I call in lpioctl >(if_plip.c line 302) to print out some identifying information >about the process doing the ioctl?=20 All I can suggest is looking in curproc (struct proc). There doesn't seem to be anything passed to lpioctl() that would allow you to locate the calling process. >This problem is also present in 6.0. Why haven't a whole bunch of >people already run into it? Am I the only person still using a >parallel port printer and (at first) a generic kernel? I suspect plip has outlived its usefulness. --=20 Peter Jeremy --SUk9VBj82R8Xhb8H Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEwd/J/opHv/APuIcRAnZTAJ4trxhJIwXX7EM8xdGm+lHaaRFqnwCfcAMJ VQxgLjJ+U/tMf4UBHgH8z+c= =RsGD -----END PGP SIGNATURE----- --SUk9VBj82R8Xhb8H--