Date: Fri, 2 Oct 1998 20:46:17 +0200 (CEST) From: Søren Schmidt <sos@FreeBSD.ORG> To: sprice@hiwaay.net (Steve Price) Cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: bizarre behavior with vx0 driver? Message-ID: <199810021846.UAA00964@sos.freebsd.dk> In-Reply-To: <Pine.OSF.4.02.9810021223510.6844-100000@fly.HiWAAY.net> from Steve Price at "Oct 2, 98 12:38:08 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Steve Price who wrote:
> On Fri, 2 Oct 1998, Mike Smith wrote:
>
> # >
> # > Anyone using the vx0 driver and seeing behavior like this?
> # > This is on a -current box CVSup'd and rebuilt yesterday.
> #
> # This is classic "interrupts not happening, running on watchdog"
> # behaviour. If you're -current, it means you can't use the xl driver I
> # guess. Dump the card; it sucks and so does our driver for it.
>
> The card is trash I admit, but this is on a work machine...
> I did figure out exactly what was causing it however. I had
> an unconfigured (no pnp0 in kernel) PNP modem in the box and
> removing it seems to have made the problem go away. Don't
> know why it fixed it but things are better now.
I have one of those cards too in my main box here (sos.freebsd.org),
and it works pretty well, except when it shares a PCI interrupt
with another card, that makes it fail like you described...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
Even more code to hack -- will it ever end?
..
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810021846.UAA00964>