--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Martin Husemann <martin@duskware.de> wrote:
> On Tue, Feb 07, 2006 at 03:24:21PM -0500, Jan Schaumann wrote:
> > nfs_boot: trying DHCP/BOOTP
> > nfs_boot: timeout...
> > nfs_boot: timeout...
> > nfs_boot: timeout...
>=20
> This is the first time that the kernel itself talks to the network.
>=20
> Check with tcpdump that the request packets make it out.

Here's a tcpdump: http://www.cs.stevens.edu/~jschauma/netbsd/dump

13:35:51.793581 172.16.4.30.1847 > 172.16.4.1.2049: 104 read [|nfs]=20
13:35:51.793619 172.16.4.1.2049 > 172.16.4.30.1847: reply ok 1124 read
13:35:51.793812 172.16.4.30.1848 > 172.16.4.1.2049: 104 read [|nfs]=20
13:35:51.793848 172.16.4.1.2049 > 172.16.4.30.1848: reply ok 1124 read
13:35:51.794043 172.16.4.30.1849 > 172.16.4.1.2049: 104 re=20

And that's where it stops.

> Maybe for some reason the kernel can not properly use the network interfa=
ce?
> Maybe it has interrupt problems and does not notice the answers?

Hmm, what can I do to check if that's the case, and what if it is?

Thanks,
-Jan

--=20
Information wants to be free.
Information wants to be useful.

--M9NhX3UHpAaciwkO
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFD649DfFtkr68iakwRAtFvAJ97+88hhaWuHs3GR21bPBknlek42QCg1QEx
3ejhyq9uUxVb6FDinLM/2H0=
=zaFQ
-----END PGP SIGNATURE-----

--M9NhX3UHpAaciwkO--