From owner-freebsd-current Fri Oct 2 10:39:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07074 for freebsd-current-outgoing; Fri, 2 Oct 1998 10:39:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07067 for ; Fri, 2 Oct 1998 10:38:59 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.0/8.9.0) with SMTP id MAA16940; Fri, 2 Oct 1998 12:38:08 -0500 (CDT) Date: Fri, 2 Oct 1998 12:38:08 -0500 (CDT) From: Steve Price To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: bizarre behavior with vx0 driver? In-Reply-To: <199810021657.JAA00442@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Thanks, Steve # -- # \\ Sometimes you're ahead, \\ Mike Smith # \\ sometimes you're behind. \\ mike@smith.net.au # \\ The race is long, and in the \\ msmith@freebsd.org # \\ end it's only with yourself. \\ msmith@cdrom.com # # # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message