From owner-freebsd-hackers Fri Feb 7 6:27: 5 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CA0237B401 for ; Fri, 7 Feb 2003 06:27:04 -0800 (PST) Received: from mail.eecs.harvard.edu (bowser.eecs.harvard.edu [140.247.60.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBCE443FD7 for ; Fri, 7 Feb 2003 06:26:56 -0800 (PST) (envelope-from ellard@eecs.harvard.edu) Received: by mail.eecs.harvard.edu (Postfix, from userid 465) id 1AC9E54C43C; Fri, 7 Feb 2003 09:26:49 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.eecs.harvard.edu (Postfix) with ESMTP id 1848554C437 for ; Fri, 7 Feb 2003 09:26:49 -0500 (EST) Date: Fri, 7 Feb 2003 09:26:49 -0500 (EST) From: Daniel Ellard To: freebsd-hackers@freebsd.org Subject: finding changes from one release/patch level to another? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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. In 4.6.2p6 almost everything works, but programs that push the device (such as netperf) can hang. The same program running on other ethernet devices (fxp, xl) works fine. This happens on several machines, and they were all running correctly before I updated them, so I doubt that it is a hardware problem. I don't see any changes for the em driver source itself between p4 and p6, and the announced differences between these patch levels don't look related, but something must have changed. Is there a straightforward way to track down all the source code differences between p4 and p6 (or any arbitrary pair of patchlevels)? Thanks, -Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message