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?
--
Brian 'you Bastard' Reichert <[EMAIL PROTECTED]>
37 Crystal Ave. #303 Daytime number: (603) 434-6842
Derry NH 03038-1713 USA Intel architecture: the left-hand path
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
