Bug 249950
Summary: | After updating and booting to kernel version 2.6.22.1-33.fc7 Network adapters failed to aquire an IP Address, wired and wireless | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rico R. <richempire> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | jan.public, neugens, sb |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-01 11:03:56 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rico R.
2007-07-28 12:23:23 UTC
I can confirm this, same thing happens to me on a Dell XPS M1210, both wireless (Intel 3945) and wired (Broadcom). Booting back to 2.6.22.1-27 makes the problem go away. Using tshark I can see the DHCPOFFER messages coming back into my interface, but somehow they get dropped/ignored. Also, when I manually assign an IP and set the default route, data transfers happen much slower than normally (around 65Kbit/s vs. the normal 10Mbit/s). "Something rotten in the state of Kernel" methinks. Cheers, Steven I can confirm this too, I solved setting "allow users to enable this device" in system-config-network. Mmmh, system-config-network offers me "allow ALL users to ...". I'm not sure I want to do that. Even so, it's a regression with respect to 2.6.22.1-27 and it does look like a bug to me. Also, when using this new kernel, my X session keeps giving me a warning that I was logged in for 0 seconds whenever I logout. Could well be a permission problem as well, but where is the difference with the previous kernel...? Yeah, right, I've noticed that too... There are at least 3 regressions that could be somewhat related and were introduced by this kernel, the X bug (not sure someone has already filed that), the clock bug (250049) and this one. As for the network issue, maybe keeping -27 for now is the safest thing (I agree on multi-user machine is not really nice to allow everybody to control the devices), but for users that use NetworkManager (usually single user/family machines) this can be a good workaround if -33 is needed for some other reason. There's a kernel mentioned in comment 13 of bug #249857 (250049 is a duplicate of that one) that fixes both that bug and this one for me. As for -33? Those bits have been de-gaused on my disk :-) The latest kernel-2.6.22.1-41.fc7 solves the problem. Please reopen or create new bugreport if your problem persist. See bug #250003 for more info. *** This bug has been marked as a duplicate of 250003 *** |