I'm not on the core team but I'm not sure why you believe that this has anything to do with core.
On 2007-Feb-09 00:16:31 -0800, Daniel Rudy <[EMAIL PROTECTED]> wrote: >sio0: configured irq 19 not in bitmap of probed irqs 0 >sio0: port may not be enabled >sio0: <Lucent kermit based PCI Modem> port >0xdc00-0xdcff,0xe000-0xe0ff,0xe400-0xe407 mem 0xeb107000-0xeb1070ff > irq 19 at device 11.0 on pci0 >sio0: type 16550A Is this device visible in the BIOS and if so, what does the BIOS say its configuration is. The dmesg from a verbose boot may be useful. The "port may not be enabled" line looks to be the most relevant one. >I have no idea WHY it's saying IRQ 19 as IRQ 19 is used by sis0. Interrupts on the PCI bus can be shared and quite often are. >Now I know that device says WinModem, but this is most definitely *NOT* >a WinModem. It appears that there is an error in /usr/share/misc/pci_vendors. Feel free to write a bug report. The kernel is correctly recognizing it. >Here's the problem. Anything that this modem outputs, requires multiple >inputs for it to read out on the screen. Here's an example: > >gateway# cu -l /dev/cuad0 -s 57600 >Connected >at&v > > Option Selection AT Cmd > --------------- ------------ -------- ... So it _does_ work. >In order to get that output, I have to hit either enter or space 61 >times (yes sixty-one is not a typo) to get it. When it prints, it only >prints out about 16 characters at a time (which happens to be the size >of the FIFO buffer in a generic 16550A UART). Probably because the interrupts are not working. >As to why FreeBSD is assigning two devices to the same IRQ I have no >idea, especially since there are plenty of IRQs available that can be >used (serial, parallel are turned off in the BIOS). Probably because your motherboard vendor decided to save a few deci- cents by not bothering to connect up all the available interrupt inputs and just share one. This isn't FreeBSD - it's the copper tracks on your motherboard. -- Peter Jeremy
pgpc7wd5PSWnP.pgp
Description: PGP signature
