Date: Fri, 16 Apr 2010 11:37:59 +0200 From: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-stable@freebsd.org, Jack Vogel <jfvogel@gmail.com> Subject: Re: em regression, UDP LOR followed by ssh stall Message-ID: <4BC82FF7.1030700@omnilan.de> In-Reply-To: <20100416092803.GA17526@icarus.home.lan> References: <4BC82B80.3070108@omnilan.de> <20100416092803.GA17526@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig7D0EC7A77DA5184A88D78BDE
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Jeremy Chadwick schrieb am 16.04.2010 11:28 (localtime):
> On Fri, Apr 16, 2010 at 11:18:56AM +0200, Harald Schmalzbauer wrote:
>> with RELENG_8 from 6 weeks ago I never ran into the problem that my
>> ssh connection stalled.
>> With today's RELENG_8 it reproducably hangs at first login. After
>> some time I can open another ssh session which seems to stay without
>> problems, but the first sessions is always dying a few seconds after
>> login.
>> here's a LOR:
>> {snip}
>=20
> The e1000/em driver was recently modified (heavily). I saw the large
> number of commits come across in a csup a few weeks ago, and there's
> even more coming across in recent days (~38 hours ago):
>=20
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/e1000/
>=20
> This is the 2nd problem report to come in about the recent e1000/em
> changes. Because of this, I've avoided building kernel on all of my
> systems, and would recommend others avoid doing the same until these
> problems can get worked out.
>=20
> Jack, can you shed some light on what's going on here?
Som more info:
it seems only one of my em interfaces is affected. The other interface=20
doesn't show any odd behaviour:
em1: <Intel(R) PRO/1000 Legacy Network Connection 1.0.0> port=20
0x1800-0x183f mem 0xe1920000-0xe193ffff,0xe1900000-0xe191ffff irq 18 at=20
device 2.0 on pci3
em1: [FILTER]
em1: Ethernet address: 00:15:17:8d:aa:d4
I only have one
em1: Watchdog timeout -- resetting
So the one with problems is:
em0@pci0:1:0:0: class=3D0x020000 card=3D0xa01f8086 chip=3D0x10d38086 rev=3D=
0x00=20
hdr=3D0x00
vendor =3D 'Intel Corporation'
class =3D network
subclass =3D ethernet
The one without problems so far:
em1@pci0:3:2:0: class=3D0x020000 card=3D0x34d08086 chip=3D0x10768086 rev=3D=
0x05=20
hdr=3D0x00
vendor =3D 'Intel Corporation'
device =3D 'Gigabit Ethernet Controller (82541EI)'
class =3D network
subclass =3D ethernet
Thanks,
-Harry
--------------enig7D0EC7A77DA5184A88D78BDE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)
iEYEARECAAYFAkvIL/gACgkQLDqVQ9VXb8g6VwCfc0M7ilOc0cv6RQ4TfeaqSUbX
078AoJZDH4NBjO6bgQlELNmLereO6ly/
=is0i
-----END PGP SIGNATURE-----
--------------enig7D0EC7A77DA5184A88D78BDE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BC82FF7.1030700>