Date: 10 Mar 1999 17:31:22 +0100 From: Graeme Brown <graeme.brown@bt-sys.bt.co.uk> To: "FreeBSD-Net (FreeBSD.Org) List" <freebsd-net@freebsd.org> Subject: ALTQ-1.1.3 and ENI-155 ATM Nics Message-ID: <n1291035616.42327@maczebedee>
next in thread | raw e-mail | index | archive | help
Has anyone one on the list seen anything like this with ALTQ-1.1.3 ? hi kenjiro kjc>SUNI is the phys device (UTP for your case) and the driver doesn't kjc>touch the phys device settings. So, it seems to be a problem of the kjc>phys device or the cable. I have four PC routers running FBSD-2.2.6 each with with two ENI 155 ATM cards (UTP media) running ALTQ-1.1.3. I ran ENI DOS diagnostics on two cards in one paticular PC router and they appear OK. kjc>If I remember correctly, an ENI card comes with a DOS based diag kjc>program that initializes the phys device (and possibly tests it). I have four PC routers running FBSD-2.2.6 each with with two ENI 155 ATM cards (UTP media) running ALTQ-1.1.3. I ran ENI DOS diagnostics on two cards in one paticular PC router and they appear OK. On this PC router I have kernel debug options compilede in options DDB options DDB_UNATTENDED I find this PC is continuously generating a kernel trap to the debugger. On the console I see db> continue NMI ... going to debugger kernel: type 19 trap, code=0 Stopped at _en_service+0x215: mov1 %eax,%ebx db> continue NMI ... going to debugger kernel: type 19 trap, code=0 Stopped at _en_service+0x215: mov1 %eax,%ebx and so on. I'm starting to believe that this is more driver related. Is there any further info I can get for you ? regards graeme brown bt laboratories, uk email: graeme.brown@bt-sys.bt.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?n1291035616.42327>