Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 08 May 2001 21:09:47 -0700
From:      Dave Tweten <tweten@nas.nasa.gov>
To:        Kevin Oberman <oberman@es.net>, Darryl Okahata <darrylo@soco.agilent.com>, Jamie Bowden <ragnar@sysabend.org>
Cc:        mobile@FreeBSD.ORG
Subject:   Re: Xircom Watchdog Time-out Bug 
Message-ID:  <200105090409.f4949m096261@gilmore.nas.nasa.gov>
In-Reply-To: Message from "Kevin Oberman" <oberman@es.net>  of "Tue, 08 May 2001 13:25:16 PDT." <200105082025.f48KPHc00963@ptavv.es.net>

next in thread | previous in thread | raw e-mail | index | archive | help
oberman@es.net said:
>I do strongly recommend the pccardd_flags="-z". This pauses the daemon
>until the card in up, but I don't think it will impact your problem. 

Done, and it didn't.  Unfortunately, the watchdog timer's tendency to bark 
went away right after I changed /etc/rc.conf to include

	pccardd_flags="-z"

and before I rebooted the machine.  I doubt any cause and effect relationship.

>Of most import is that you are not running pccard_ether. I don't
>understand why you have deleted this, but I can see how it might cause
>problems.

I deleted it because it does a lot of things I don't want to do and doesn't do 
what I want.  I want the DHCP client automatically to handle subnets that have 
a server and also to handle my laptop's home subnet, on which there is no DHCP 
server and for which the machine has a static IP address.  The DHCP client can 
do that with some manipulation of its hooks files, and pccard_ether doesn't 
contribute to the effort.

darrylo@soco.agilent.com said:
>One really ugly, nasty kludge to try, is to add something like "sleep
>10" to /etc/dhclient-enter-hooks, with the idea being that the
>watchdog timeout will occur during the sleep.

I'm not morally opposed to kludges, even nasty ones, but this one can't work.  
When the watchdog timer was barking, it did so after dhclient's first attempt 
to write a packet to the Xircom.  Making dhclient wait will only delay the 
first write, and delay the ultimate time-out of the first write.  Dhclient 
doesn't seem to like having its writes time out.

Originally quoting someone quoting me, ragnar@sysabend.org said:
>>	pccard_ifconfig="inet 129.99.32.24 netmask 255.255.255.0"

>If you are trying to use dhcp, then why set the network up in the
>first place? 

That was cruft left over from before I began trying to use DHCP.  Since I 
don't use pccard_ether, it has no effect.  It's gone now anyway.

Sorry to have wasted people's time.  I'll pipe up again if this heisenbug 
returns.
-- 
M/S 258-5                     | 1024-bit PGP fingerprint: | tweten@nas.nasa.gov
NASA Ames Research Center     |  41 B0 89 0A  8F 94 6C 59 |      (650) 604-4416
Moffett Field, CA  94035-1000 |  7C 80 10 20  25 C7 2F E6 | FAX: (650) 604-4377
We each earn what freedom of speech we defend for those who most offend us.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message




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