From owner-freebsd-stable Sat Feb 13 09:11:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22903 for freebsd-stable-outgoing; Sat, 13 Feb 1999 09:11:29 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22894 for ; Sat, 13 Feb 1999 09:11:27 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id MAA09313 for ; Sat, 13 Feb 1999 12:11:22 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19990213121635.0537e120@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 13 Feb 1999 12:18:44 -0500 To: stable@FreeBSD.ORG From: Mike Tancsa Subject: bad fxp card or driver issue ? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed that on a RELENG_3 box, that I am getting the odd fxp0: device timeout The card was working fine under 2.2 and I am wondering if its just coincidence, or a problem with the driver ? ns3% dmesg | grep irq fxp0: rev 0x05 int a irq 19 on pci0.9.0 ahc0: rev 0x00 int a irq 18 on pci0.10.0 fxp1: rev 0x05 int a irq 17 on pci0.11.0 vga0: rev 0x5c int a irq 16 on pci1.0.0 atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa wdc0 at 0x1f0-0x1f7 irq 14 on isa FreeBSD 3.0-STABLE #0: Fri Jan 22 08:28:49 EST 1999 ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message