Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!ogicse!decwrl!atha!aupair.cs.athabascau.ca!rwa From: rwa@aupair.cs.athabascau.ca (Ross Alexander) Newsgroups: comp.unix.bsd Subject: Re: /386bsd: reject 65340 Message-ID: <rwa.716836288@aupair.cs.athabascau.ca> Date: 18 Sep 92 17:11:28 GMT Article-I.D.: aupair.rwa.716836288 References: <3594@ra.nrl.navy.mil> <1992Sep18.085534@IASTATE.EDU> Sender: news@cs.athabascau.ca Lines: 25 jzelle@IASTATE.EDU (James A Zelle) writes: >In article <3594@ra.nrl.navy.mil>, deal@hightop.nrl.navy.mil (Richard >Deal) writes: >>/386bsd: reject65340 messages. The number is mostly 65340 but is >>some times 65342, 65344, 65366. if I type >I'm having a similar problem with a Western Digital Ethernet card, >except I think the error says "reject655341" in my case. The error >goes away when the Ethernet cable is disconnected, so it appears that >386BSD doesn't like what it sees on the network. Any ideas? This problem arises from having shadow memory enabled in the range of addresses (0xD0000 - 0xD03FFF as I remember) that the dual-port ram in the WD8013 card corresponds to. Turn off any shadowing or caching in this region via your BIOS EAPROM setup firmware and the problem will go away (your mileage may vary :). The errors go away when the cable is disconnected because the WD8013 stops generating interrupts, and so the kernel stops finding bogus stuff in what it thinks is the WD8013 memory (but isn't, because the hardware is lying). regards, Ross -- Ross Alexander rwa@cs.athabascau.ca (403) 675 6311 ve6pdq@ve6mgs.ampr.org