Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!sdd.hp.com!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!math.fu-berlin.de!news.th-darmstadt.de!news.uni-mainz.de!wilbur!grefen From: grefen@wilbur.uni-mainz.de (Stefan Grefen) Subject: Re: Problems with 386bsd and 3COM 503 ethernet interface Message-ID: <RUY7DL@minnie.zdv.uni-mainz.de> Keywords: 386bsd 3COM ethernet Sender: grefen@wilbur (Stefan Grefen) Nntp-Posting-Host: wilbur Organization: Johannes Gutenberg Universitaet Mainz References: <1bfunsINN3ek@iskut.ucs.ubc.ca> Date: Thu, 15 Oct 1992 15:26:11 GMT Lines: 20 In article <1bfunsINN3ek@iskut.ucs.ubc.ca>, felawka@sitka.triumf.ca (Larry Felawka) writes: |> Help! Is there anyone out there who has got the 3COM 503 ethernet interface |> running with 386bsd? I have had success with 386bsd and the Western Digital |> that the driver is suspect, although possibly it works for the on-board thinnet |> ethernet interface (it works great). When I rebuild the kernel with only the |> transceiver. The system crashes with the messages |> |> vm_fault(fe103000,fe623000,3,0) -> 1 |> type c, code fe070002 |> trap type 12 code = fe070002 eip = fe0007f7 cs = 8 eflags = 10696 cr2 |> |> panic: trap fe6230ed cpl 525a Also with thinnet (under some circumstances, normaly it runs just ok) With wd-cards I get some remque panics:-/ But I can't find any obvious errors in if_ec.[ch]. Stefan -- Stefan Grefen --- Johannes Gutenberg University Mainz --- Germany Email: grefen@goofy.zdv.uni-mainz.de --- Phone: 06131/392415