Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Jan 1998 14:04:14 +1030
From:      Mike Smith <mike@smith.net.au>
To:        Bill Trost <trost@cloud.rain.com>
Cc:        mobile@FreeBSD.ORG
Subject:   Re: SVEC NE2000 "clone" doom and gloom 
Message-ID:  <199801240334.OAA00957@word.smith.net.au>
In-Reply-To: Your message of "Fri, 23 Jan 1998 13:26:52 -0800." <m0xvqdr-0002TEC@jli.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
> Mike Smith writes:
>     > Since the block is less than the memory quanta of MEMUNIT, bit_fns ends
>     > up getting asked to allocate a memory region of size zero (ROUNDOFF
>     > BUG!), which it can't do.
> 
>     Damn, I've seen this one before too.  Want to submit a patch? 8)
> 
> It should be trivial -- but for some reason, "make" in usr.sbin/pccard/pccardd
> fails, so I am not going to bother unless I get the rest of this sorted out.

Bleagh.  Try going up a directory.

>     If you throw a few printf()'s in sys/pccard.c:allocate_driver() you should
>     be able to work out what's going wrong pretty quickly.
> 
> OK, allocate_driver hangs in drv->enable (the whole system hangs inside the
> splhigh(), surprise).  That is bound to edinit, which hangs in ed_probe_pccard,
> which hangs in ed_probe_WD80x3, which hangs computing the ether address PROM
> checksum(???).  It doesn't even manage to read the first byte.

When you say "doesn't even manage to read the first byte", what 
happens?  Is this a software bug (spinning forever), or a hardware bug 
(read from card locks machine?).

> What's the TOSH_ETHER in if_ed.c for?  If I define that, then I don't get the
> hang -- instead, the checksum checks fail, and pccardd says that the driver
> allocation fails (and I got an "unfiended interrupt (0)" once, too).  The probe
> does not believe the card is an NE2000.

The TOSH_ETHER define is for some Toshiba cards.  Unfiended interrupt 0 
is doubly odd.  8)

I take it that you tried removing the call to ed_probe_WD80x3() in 
order to determine that the NE2000 probe fails?

>     > AARGH!  Yeah, sure, NE2000-compatible my foot!
> 
>     Could be.  Nobody said the code was perfect either.
> 
> You mean there might be a *bug*?  In the *kernel*?  Naaah.... (-:
> 
> However, the way things are going, I am becoming more and more convinced that
> the vendor botched it (at best).

I'd have to confess that I'm inclined to wonder if the card really is
an NE2000 PCCARD.  One question; the Danpex card I use at the moment is 
actually quite easy to open up.  If yours is the same, it'd be 
very interesting to know what was actually inside it.  In some cases 
the vendors of these cards actually provide quite detailed data on 
their parts, and that may well lead to understanding or even a Real Fix.

-- 
\\  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.  \\ 





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801240334.OAA00957>