Date: Fri, 20 Dec 2002 10:20:40 -0800 (PST) From: jimmie james <h2g2_jimmiejaz@yahoo.com> To: hackers@freebsd.org Subject: RE: 3COM PCI FaxModem with shared IRQ causes FBSD to freeze Message-ID: <20021220182040.66644.qmail@web13402.mail.yahoo.com>
next in thread | raw e-mail | index | archive | help
The subject line is the same subject line as kern/28856 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/28856 The above PR refers to an issue, with a workaround, for 5.0-CURRENT circa July 2001. I have nearly the identical issue under 4.7-RELEASE. I see an additional symptom, however, under my setup. With a kernel config that looks like this: #device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio0 at isa? port IO_COM1 flags 0x10 irq 11 #device sio2 at isa? disable port IO_COM3 irq 5 #device sio3 at isa? disable port IO_COM4 irq 9 A dmesg looks like this: sio0: <3COM PCI FaxModem> port 0xec00-0xec07 irq 5 at device 10.0 on pci0 sio0: moving to sio2 sio2: type 16550A ... sio0: configured irq 11 not in bitmap of probed irqs 0x10 sio0 at port 0x3f8-0x3ff irq 11 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A Note the 'sio0: moving to sio2' line. That's the new symptom. If I try to access sio0, I don't probe a modem. If I try to access sio2, my machine wedges up tight. I tried this with a stock kernel as well: device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 yeilds: sio0: <3COM PCI FaxModem> port 0xec00-0xec07 irq 5 at device 10.0 on pci0 sio0: moving to sio4 sio4: type 16550A I've tried varying combos of the 'PnP BIOS' settings, to no avail. Of course, Win98 has no problem with the hardware, as-is. The idea of putting the modem on it's own IRQ (the workaround in the original PR) seems sound, but I'm being thwarted by this 'sio0: moving to sioN' behavior; I don't know why it's saying that, and I don't know which device I'm supposed to use for access afterward... 'sioN' seems to always resolve to a higher number than the number of sio devices I configured in my kernel. I'm seeing this problem described in a few other places: 4.6.2-RELEASE-p2 http://www.atm.tut.fi/list-archive/freebsd-stable/msg05830.html 4.7-stable circa Oct 2002 http://www.geocrawler.com/mail/msg.php3?msg_id=10027753&list=152 but no one seems to be resolve it. Does anyone have any new advice on this matter? May not be new or a fix, but I had the same issues with a Dell Dimension L566cx and sioN moving around, and locking up the box (sharing IRQ) uname -v FreeBSD 4.7-STABLE #0: Sat Dec 7 21:58:02 EST 2002 jimmie@fortytwo.free-bsd.org:/usr/obj/usr/src/sys/FORTYTWO dmesg <snip> puc0: <US Robotics (3Com) 3CP5609 PCI 16550 Modem> port 0xdff0-0xdff7 irq 10 at device 11.0 on pci1 sio0: type 16550A uhci0: <Intel 82801AA (ICH) USB controller> port 0xef80-0xef9f irq 10 at d evice 31.2 on pci0 sio1: configured irq 3 not in bitmap of probed irqs 0x10 sio1 at port 0x3f8-0x3ff irq 3 on isa0 sio1: type 16550A and my kernel config looks like: device sio1 at isa? port IO_COM1 irq 3 options CONSPEED=115200 device puc options PUC_FASTINTR I'm using the modem on: set device /dev/cuaa0 I have PnP off in the BIOS, and the options pnpbios out of the kernel. All *seems* to be working fine now, (execpt for multiple sound sources and the sysctl vchans kill all sound *shrugs*) so I hope this may shed some light, or offer some ideas. (please c.c me, as I'm not on the list, thank you) Jimmie James ===== -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GMU dpu s+:+ a? C++++ UB++++ P+++ L++++ E--- W+++ N+++ o++++ K+++++ w--- O+++ M- V-- PS+++ PE+++ Y++ PGP+++ 5-- X+ R* !tv b++++ DI++++ D---- G++ e* h* r+ z** ------END GEEK CODE BLOCK------ __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021220182040.66644.qmail>