Date: Tue, 21 Nov 2000 07:53:01 -0600 From: "Matt Bettinger" <mattb@finsyn.com> To: <stable@FreeBSD.ORG> Subject: RE: Panic during disconnect of USB LPT device Message-ID: <71F816A89AA9D3119F4C00D0B7094EFC2062FB@FIN_SYN> In-Reply-To: <71F816A89AA9D3119F4C00D0B7094EFC2397B3@FIN_SYN>
next in thread | previous in thread | raw e-mail | index | archive | help
I too have had strange things happen when a USB plug was unplugged.
Whenever i coldsync a handspring on 4.1.1 STABLE and unplug the cradle my
system gives me a message and then reboots. I can't seee what the message
says in time b/c the cpu reboots. This only occurs AFTER a cold sync
operation.
Matt
-----Original Message-----
From: owner-freebsd-stable@FreeBSD.ORG
[mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of
joe@OpenSoftwareServices.com
Sent: Monday, November 20, 2000 4:24 PM
To: stable@FreeBSD.ORG
Subject: Panic during disconnect of USB LPT device
I've experienced a repeatable panic apparently related to the USB code.
I'm running 4.2-BETA from sources cvsup'ed late the afternoon of Nov 15th.
FreeBSD 4.2-BETA #0: Wed Nov 15 20:46:36 CST 2000
root@benevolence.rootnode.com:/x1/obj/usr/src/sys/ABUNDANCE
uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 6 at device 4.2
on pci0
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ulpt0: Xerox Xerox DocuPrint N2125 USB, rev 1.00/1.00, addr 2, iclass 7/1
I am using lpd and a standard printcap entry specifying /dev/ulpt0 as the
printer device. No filter specified.
It seems that if lpd(8) has the ulpt0 device open and is writing to it
while the usb cable is unplugged from the printer, it panics. I cannot
provide the output of the panic dump at the moment but will attempt to
tonight.
I discovered this while rebooting while a large job was in the lpd spool.
LPD started printing again upon boot, and I didn't want the job, so I
yanked the cable. Panic, immediately after the "ulpt0: disconnected"
message on the console. Since the machine was down, I tried it a couple of
times with the same result.
Other than that, printing via USB works great.
Note the strange IRQ (6) that the BIOS chose for the USB controller. I
don't know why it did that (stupid intel architecture). The FDC is
enabled, but there's no floppy drive connected. Perhaps the BIOS disables
it if there isn't a drive.
ata0 irq14 242068 3
ata1 irq15 110948 1
mux irq6 4434445 57
fxp0 irq5 4843 0
dpt0 irq10 103616 1
atkbd0 irq1 39 0
ppc0 irq7 1 0
clk irq0 7743843 99
rtc irq8 9912513 128
uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f irq 6 at device 4.2
on pci0
xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xd000-0xd03f irq 6 at device
9.0 on pci0
dc0: <82c169 PNIC 10/100BaseTX> port 0xb000-0xb0ff mem
0xe1000000-0xe10000ff irq 6 at device 13.0 on pci0
This IRQ sharing doesn't seem to adversely affect any of these devices,
although xl0 isn't in active use.
I'll attempt to provide a more detailed dump later tonight.
Thanks for your time,
Joe
-------+--+---++-+---+-+-++--+++ ++++ ++ + + + ++ + +
Joe Koberg PO BOX 24306
Open Software Services, LLC Little Rock AR 72221-4603
joe@OpenSoftwareServices.com (501) 258-3673
http://OpenSoftwareServices.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?71F816A89AA9D3119F4C00D0B7094EFC2062FB>