Date: Sat, 22 Jul 2006 18:20:26 +1000
From: Peter Jeremy <peterjeremy@optushome.com.au>
To: george+freebsd@m5p.com
Cc: freebsd-hackers@freebsd.org
Subject: Re: FreeBSD 6.0/6.1: open ("/dev/lpt0" ...) hangs up
Message-ID: <20060722082026.GG728@turion.vk2pj.dyndns.org>
In-Reply-To: <200607220546.k6M5kq59001314@m5p.com>
References: <200607220546.k6M5kq59001314@m5p.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060722082026.GG728>