Date: Sat, 17 Feb 2007 20:12:11 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Daniel Rudy <dr2867@pacbell.net> Cc: freebsd-hackers@freebsd.org Subject: Re: PING: Someone on the core team. (Modem Problem) Message-ID: <20070217091211.GP859@turion.vk2pj.dyndns.org> In-Reply-To: <45D57B29.2050408@pacbell.net> References: <45CC2DDF.6040600@pacbell.net> <20070212.234959.-432837120.imp@bsdimp.com> <45D2A48F.1010104@pacbell.net> <20070213.232425.-1929114897.imp@bsdimp.com> <45D2C7F8.9050302@pacbell.net> <20070215081426.GH862@turion.vk2pj.dyndns.org> <45D57B29.2050408@pacbell.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--9Ek0hoCL9XbhcSqy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Feb-16 01:36:41 -0800, Daniel Rudy <dr2867@pacbell.net> wrote: >No, it does not report as fast. That means it's getting a "slow" interrupt handler (or maybe none at all =66rom what you wrote below). >Here is the verbose dmesg from a reboot that I did just now: > >sio0: Reserved 0x100 bytes for rid 0x14 type 4 at 0xd400 >sio0: configured irq 17 not in bitmap of probed irqs 0 >sio0: port may not be enabled >sio0: irq maps: 0xcb9 0xcb9 0xcb9 0xcb9 >sio0: <Lucent kermit based PCI Modem> port >0xd400-0xd4ff,0xd800-0xd8ff,0xdc00-0xdc07 mem 0xeb105000-0xeb1050ff > irq 17 at device 9.0 on pci0 >sio0: type 16550A > >What I don't understand is why it keeps saying that "configured irq 17 >not in bitmap of probed irqs 0"... What exactly does that mean? Basically, the probe routine forces the device to raise an IRQ and reads the list of pending IRQs (the first irq map above). It then clears the interrupt (by reading the relevant status registers) and again checks the list of pending IRQs (the second irq map above). In your case both are the same (0xcb9) so the driver reports that it is unable to detect an interrupt generated by the device. The only fly in the ointment is that the probe code only checks for pending ISA interrupts and so misses irq 17. Looking at the code, the only impact should be those warning messages. As I mentioned before, you might like to try uart(4) instead of sio(4). It looks like it also supports that card and may behave slightly better for you. On 2007-Feb-16 12:51:37 -0800, Daniel Rudy <dr2867@pacbell.net> wrote: >overflows. Is there a way for force the driver to attach as fast since >it's not doing it? sio tries to attach as fast and falls back to the default if that fails. It should only fail if something else is already registered on that IRQ. --=20 Peter Jeremy --9Ek0hoCL9XbhcSqy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF1sbr/opHv/APuIcRAs4/AKDAwcIu1FfL0wDVmp1gP/RA8MJXHgCePAGM wjK0yONAc7hj/Fcgr9xROVo= =zAcp -----END PGP SIGNATURE----- --9Ek0hoCL9XbhcSqy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070217091211.GP859>