Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261299AbTHXUWP (ORCPT ); Sun, 24 Aug 2003 16:22:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261300AbTHXUWO (ORCPT ); Sun, 24 Aug 2003 16:22:14 -0400 Received: from ms-smtp-01.texas.rr.com ([24.93.36.229]:56459 "EHLO ms-smtp-01.texas.rr.com") by vger.kernel.org with ESMTP id S261299AbTHXUWN (ORCPT ); Sun, 24 Aug 2003 16:22:13 -0400 Message-ID: <3F491E69.5090206@austin.rr.com> Date: Sun, 24 Aug 2003 15:22:01 -0500 From: Steve French User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: via rhine network failure on 2.6.0-test4 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1297 Lines: 24 The via rhine driver fails to get a dhcp address on my test system on 2.6.0-test4. ethereal shows no dhcp request leaving the box but ifconfig does show the device and it is detected in /proc/pci. Switching from the test3 vs. test4 snapshots built with equivalent configure options on the same system (SuSE 8.2) - test3 works but test4 does not. This is using essentially the default config for both the test3 and test4 cases - the only changes are SMP disabled, scsi devices disabled, Athlon, via-rhine enabled in network devices and a handful of additional filesystems enabled, debug memory allocations enabled. This is the first time in many months that I have seen problems with the via-rhine driver on 2.6 Analyzing the code differences between 2.6.0-test3 and test4 (in via-rhine.c) is not very promising since the only line that has changed (kfree to free_netdev) is in the routine via_rhine_remove_one that seems unlikely to cause problems sending data on the network. Ideas as to what could have caused the regression? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/