Bug 23205

Summary: lptcontrol -e causes panic
Product: Base System Reporter: jmcl <jmcl>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description jmcl 2000-12-01 11:30:01 UTC
On my system (Dell PowerEdge 1300 dual PIII), switching lpt0 to extended
mode using lptcontrol -e and attempting to print anything causes an 
immediate panic and reboot. The printer is a HP 2100M.

I tried using extended mode to fix another problem where the printer 
occasionally hangs necessitating a reboot after a suggestion in PR 14787
(no PR submitted for the original problem as I want to investigate a bit
further)

dmesh output:
ppc0: <Parallel port> at port 0x378-0x37f irq 7 flags 0x40 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppbus0: IEEE1284 device found /NIBBLE/ECP
Probing for PnP devices on ppbus0:
ppbus0: <Hewlett-Packard HP LaserJet 2100 Series> PJL,MLC,PCL,PCLXL,POSTSCRIPT
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port

Fix: 

None known
How-To-Repeat: # lptcontrol -e
# lpr -Plp somefile.ps
Comment 1 iedowse freebsd_committer freebsd_triage 2001-11-18 12:26:34 UTC
State Changed
From-To: open->feedback


Does this problem still occur in more recent releases? If so, could 
you try to get a crashdump and a gdb backtrace as per the instructions 
in the FreeBSD developers handbook?
Comment 2 iedowse freebsd_committer freebsd_triage 2001-11-18 17:12:58 UTC
State Changed
From-To: feedback->closed


Mail to submitter bounces.