From: Steve French <smfrench@austin.rr.com>
To: linux-kernel@vger.kernel.org
Subject: via rhine network failure on 2.6.0-test4
Date: Sun, 24 Aug 2003 15:22:01 -0500 [thread overview]
Message-ID: <3F491E69.5090206@austin.rr.com> (raw)
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?
next reply other threads:[~2003-08-24 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-24 20:22 Steve French [this message]
2003-08-25 2:36 ` via rhine network failure on 2.6.0-test4 Jeff Garzik
2003-08-25 3:59 ` Steve French
2003-08-25 4:32 ` Steve French
-- strict thread matches above, loose matches on Subject: below --
2003-08-25 6:30 Nakajima, Jun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F491E69.5090206@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.