Re: ep0 etherlink III breakage
>> Mark Hittinger wrote: >> Hey per request I'm reporting some ep0 breakage in today's -current. I have >> an etherlink III 3c509B and the probing appears correct. >> Sequence of events boot -s >> # ifconfig ep0 inet 192.168.18.200 >> (PC hangs) >> More later... > From: Russell Cattelan <[EMAIL PROTECTED]> > Was there ever a conclusion as to how to get around this problem? One suggestion was to comment out the pnp0 isa line in your config file, i.e. controller isa0 #controller pnp0# PnP support for ISA controller eisa0 ** It would really be nice if you could disable pnp0 in the boot -c dialog ** (At least I can't see how to do that :-) ). Then config, make depend, and build the kernel. This does work but it doesn't help debug our PnP code, and I have seen several other messages relating to problems in our PnP code over the past couple of days. When I have time I've been looking in the PnP code trying to find the bug - it doesn't look like an easy find to me. Later Mark Hittinger Mindspring/Netcom/Dallas [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 etherlink III breakage
Mark Hittinger wrote: > Hey per request I'm reporting some ep0 breakage in today's -current. I have > an etherlink III 3c509B and the probing appears correct. > > Sequence of events boot -s > # ifconfig ep0 inet 192.168.18.200 > (PC hangs) > > More later... Was there ever a conclusion as to how to get around this problem? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 etherlink III breakage
> Actually I don't really care what you do with this. I did say "more later" > but you chopped that part out. I was only trying to give a heads up. Then way waste people's time with content-free messages? Just to lower the signal-to-noise ratio? We all could have waited for this email. > Guess I made the mistake of misreading a request that came through > freebsd-current a few days ago asking for any problem reports with ep0. Yes report problems. That means giving enough details that someone can figure out what is going on. I guess I'm the only one that has ever been in a position where I had to fix others' problems from their description of the problem. > Mindspring/Netcom/Dallas > [EMAIL PROTECTED] I guess what really thru me off was this email address -- I assumed you were a system administrator. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 etherlink III breakage
> I think David was joking with you, hence the \begin{wpaul} statement. Bill
> Paul is of course our resident Ethernet driver guy, and he is not known
> for his patience with people who do not supply enough information. :)
Only 1/2 joking. This seems to be my month for content free bug reports.
I would also expect a computer professional (especially one running
-CURRENT) to understand what a bug report is and what should be contained
in one. Gezz, am I the only one that has had to do system administration
before?
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ep0 etherlink III breakage
On Wed, Sep 22, 1999 at 10:40:22AM +0800, Peter Wemm wrote: > No, it's better to remove "device ep0 at isa ? port foo irq blah ..." etc > and just have "device ep0" *only*. If the pnp code finds it, let it use > pnp to configure it. Does it do that by now? About two or three months ago it didn't and I started writing the necessary code. Now I'm just learning how to remotely debug the kernel... Cheers, Timo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 etherlink III breakage
Jason Young wrote: > > > ie0: unknown board_id: f000 > > 1 3C5x9 board(s) on ISA found at 0x300 > > ep0 at port 0x300-0x30f irq 10 on isa0 > > ep0: utp[*UTP*] address 00:a0:24:a1:9a:1e > > isa_compat: didn't get ports for le > > isa_compat: didn't get ports for cs > > unknown0: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 > > ep0 XXX: driver didn't set ifq_maxlen > > changing root device to wd0s1a > > > > Since we have an ep0 and an unknown0 the ifconfig ep0 causes a hang. Doing > > this in stand alone eliminates other issues. When debugging it pays to do > > that. > > I think that the PNP code is finding your 3C509 and doing things with it, > like, moving its resources around. That's your unknown0 device. Try > disabling PNP in your kernel or PNP on your card with the DOS utility. No, it's better to remove "device ep0 at isa ? port foo irq blah ..." etc and just have "device ep0" *only*. If the pnp code finds it, let it use pnp to configure it. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 etherlink III breakage
> ie0: unknown board_id: f000
> 1 3C5x9 board(s) on ISA found at 0x300
> ep0 at port 0x300-0x30f irq 10 on isa0
> ep0: utp[*UTP*] address 00:a0:24:a1:9a:1e
> isa_compat: didn't get ports for le
> isa_compat: didn't get ports for cs
> unknown0: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0
> ep0 XXX: driver didn't set ifq_maxlen
> changing root device to wd0s1a
>
> Since we have an ep0 and an unknown0 the ifconfig ep0 causes a hang. Doing
> this in stand alone eliminates other issues. When debugging it pays to do
> that.
I think that the PNP code is finding your 3C509 and doing things with it,
like, moving its resources around. That's your unknown0 device. Try
disabling PNP in your kernel or PNP on your card with the DOS utility.
> Guess I made the mistake of misreading a request that came through
> freebsd-current a few days ago asking for any problem reports with ep0.
> My mistake - sorry - I shall return to lurking.
I think David was joking with you, hence the \begin{wpaul} statement. Bill
Paul is of course our resident Ethernet driver guy, and he is not known
for his patience with people who do not supply enough information. :)
Jason Young
accessUS Chief Network Engineer
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ep0 etherlink III breakage
> WHAT am I supose to do with this? I don't even understand what you > are trying to tell me. You booted single user and got a hang. What > is the #'ed line supose to be? Last time *_I_* booted single user I > didn't see such output. Actually I don't really care what you do with this. I did say "more later" but you chopped that part out. I was only trying to give a heads up. I've been playing with it for a few minutes and here is some more info: ie0: unknown board_id: f000 1 3C5x9 board(s) on ISA found at 0x300 ep0 at port 0x300-0x30f irq 10 on isa0 ep0: utp[*UTP*] address 00:a0:24:a1:9a:1e isa_compat: didn't get ports for le isa_compat: didn't get ports for cs unknown0: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 ep0 XXX: driver didn't set ifq_maxlen changing root device to wd0s1a Since we have an ep0 and an unknown0 the ifconfig ep0 causes a hang. Doing this in stand alone eliminates other issues. When debugging it pays to do that. I assume that the unknown0 probe success is where we are going astray - this may be a similar buglet to the ed_probe_HP_pclanp() routine I submitted a patch for last week ( lots of return 0 instead of return ENXIO ). I'll be doing some additional debugging this evening when I have more time. Guess I made the mistake of misreading a request that came through freebsd-current a few days ago asking for any problem reports with ep0. My mistake - sorry - I shall return to lurking. Regards, Mark Hittinger Mindspring/Netcom/Dallas [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ep0 etherlink III breakage
I'm not certain what the problem is, but the ep0 changes that generated
the HEADS UP messages affect _only_ PC Cards. The other sections of code
are untouched. Further, I'm 99% sure the only card that could possibly
have been broken by the probe change is the 3C574 PC Card (not 3C574B).
Jason Young
accessUS Chief Network Engineer
On Mon, 20 Sep 1999, Matthew Hunt wrote:
> On Mon, Sep 20, 1999 at 11:58:28AM -0700, David O'Brien wrote:
>
> > > Sequence of events boot -s
> > ># ifconfig ep0 inet 192.168.18.200
> > > (PC hangs)
>
> > \begin{wpaul}
>
> Dunno, you seem too mellow.
>
> > WHAT am I supose to do with this? I don't even understand what you
> > are trying to tell me. You booted single user and got a hang. What
> > is the #'ed line supose to be? Last time *_I_* booted single user I
> > didn't see such output.
>
> At a guess, the "#" is the root prompt that shows up after boot -s,
> and he typed the ifconfig command.
>
> --
> Matthew Hunt <[EMAIL PROTECTED]> * Stay close to the Vorlon.
> http://www.pobox.com/~mph/ *
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ep0 etherlink III breakage
On Mon, Sep 20, 1999 at 11:58:28AM -0700, David O'Brien wrote:
> > Sequence of events boot -s
> > # ifconfig ep0 inet 192.168.18.200
> > (PC hangs)
> \begin{wpaul}
Dunno, you seem too mellow.
> WHAT am I supose to do with this? I don't even understand what you
> are trying to tell me. You booted single user and got a hang. What
> is the #'ed line supose to be? Last time *_I_* booted single user I
> didn't see such output.
At a guess, the "#" is the root prompt that shows up after boot -s,
and he typed the ifconfig command.
--
Matthew Hunt <[EMAIL PROTECTED]> * Stay close to the Vorlon.
http://www.pobox.com/~mph/ *
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ep0 etherlink III breakage
On Mon, Sep 20, 1999 at 12:28:27PM -0500, Mark Hittinger wrote:
> Hey per request I'm reporting some ep0 breakage in today's -current. I have
> an etherlink III 3c509B and the probing appears correct.
>
> Sequence of events boot -s
># ifconfig ep0 inet 192.168.18.200
> (PC hangs)
\begin{wpaul}
WHAT am I supose to do with this? I don't even understand what you
are trying to tell me. You booted single user and got a hang. What
is the #'ed line supose to be? Last time *_I_* booted single user I
didn't see such output.
Can you ``boot -sv''. How far does it get? (give the last two-three
lines). What is printed out about your 3c509B? (give this verbatum)
\end{wpaul}
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ep0 etherlink III breakage
Hey per request I'm reporting some ep0 breakage in today's -current. I have an etherlink III 3c509B and the probing appears correct. Sequence of events boot -s # ifconfig ep0 inet 192.168.18.200 (PC hangs) More later... Mark Hittinger Mindspring/Netcom/Dallas [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
