Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 7 Feb 2003 11:13:36 -0500 (EST)
From:      Daniel Ellard <ellard@eecs.harvard.edu>
To:        "Jacques A. Vidrine" <nectar@FreeBSD.org>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: finding changes from one release/patch level to another?
Message-ID:  <Pine.BSF.4.51.0302071049100.23416@bowser.eecs.harvard.edu>
In-Reply-To: <20030207153658.GB90222@opus.celabo.org>
References:  <Pine.BSF.4.51.0302070917530.19912@bowser.eecs.harvard.edu> <20030207153658.GB90222@opus.celabo.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 7 Feb 2003, Jacques A. Vidrine wrote:

> > Something slightly broke the em (gigabit ethernet) driver between
> > 4.6.2p4 and 4.6.2p6, and I'm trying to figure what the change was so I
> > can back it out on my machine.  ...
>
> It seems awfully unlikely that the changes between 4.6.2p4 and 4.6.2p6
> have anything to do with your problem.  I think you are probably barking
> up the wrong tree.

I agree that it seems unlikely, based on the apparent differences, but
I don't have a better theory right now.

Everything worked under 4.6.2 base install (from the ISO on the
freebsd site), and everything continued to work under 4.6.2p2 and
4.6.2p4 (upgraded by doing a cvsup, make world, make buildkernel,
etc).  I updated two machines to 4.6.2p6 a few weeks ago, and things
started to break.  (I updated almost all my machines, but only the
machines with the intel em cards have the problems, and only on the
network connections that use the em cards.) I rebuilt netperf and
netserver after each update.

Since the em cards are all attached to the same network switch, my
first suspicion was the switch.  I tried a different switch, and even
(just to be complete) tried a 100Mb switch and even a 10Mb hub, but
this did not solve the problem.

Yesterday I backed out two of the em machines, bringing their kernels
back to 4.6.2p0 (and doing a buildkernel for my local config), and the
problem went away again.

So whether the problem is related to the kernel code, or some part of
the update process, it looks to me like it's something that happens
along the way from 4.6.2p4 and 4.6.2p6.

> > Is there a straightforward way to track down all the source code
> > differences between p4 and p6 (or any arbitrary pair of
> > patchlevels)?
>
> Check out the RELENG_4_6 branch.  Then run e.g.
>
> cvs -q diff -j 'RELENG_4_6:2002/10/28' -j 'RELENG_4_6:2003/01/08'
>
> Output attached to save you the trouble.

I'll take a look at it.

Thanks,
	-Dan


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




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