Bug 903351 - networking broken after 3.7.2-204.fc18 update
Summary: networking broken after 3.7.2-204.fc18 update
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Neil Horman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-23 19:36 UTC by Zach Carter
Modified: 2013-06-04 14:17 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-06-04 14:17:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Ifconfig -a after booting from 204 kernel (1.52 KB, application/octet-stream)
2013-01-23 19:36 UTC, Zach Carter
no flags Details
ifconfig -a after booting from previous .201 kernel (2.97 KB, application/octet-stream)
2013-01-23 19:37 UTC, Zach Carter
no flags Details

Description Zach Carter 2013-01-23 19:36:39 UTC
Created attachment 686208 [details]
Ifconfig -a after booting from 204 kernel

Description of problem:

Networking is down after applying kernel update and rebooting.


Version-Release number of selected component (if applicable):

kernel-3.7.2-204.fc18 

How reproducible:

100% reproducible on my machine


Steps to Reproduce:
1. Apply update
2. Reboot
3. No interfaces are up
  
Actual results:

No interfaces are up

Expected results:

Network should behave as it did before the update

Additional info:

If I select the previous .201 kernel in the grub menu, networking comes up fine.

Comment 1 Zach Carter 2013-01-23 19:37:25 UTC
Created attachment 686210 [details]
ifconfig -a after booting from previous .201 kernel

Comment 2 Neil Horman 2013-06-03 20:39:16 UTC
Can you attach ifconfig output and /var/log/messages from a boot of the 3.7.2-204.fc18 kernel?

Comment 3 Zach Carter 2013-06-03 20:46:39 UTC
Thanks for responding Neil.

Unfortunately I just upgraded over the weekend and can no longer reproduce the problem.

Here's what I know.

I had two interfaces, one bridge (br0) and one actual (eth1), if I booted into the old kernel they worked, on newer kernels they didn't.

I decided to just blow away both of them and reconfigure networking from scratch, at which point I was able to apply and use kernel updates again, which enabled me to upgrade my system.

So, there was probably some bug/problem/interaction with how the updates were being handled in my particular case.

As far as I'm concerned the bug can be closed WONTFIX or WORKSFORME, unless you have taken a special interest in it.

Comment 4 Neil Horman 2013-06-04 14:17:56 UTC
No, without being able to tinker with it, it will all just be a guessing game.  I'll close this for now, feel free to reopen it if the problem recurs.


Note You need to log in before you can comment on or make changes to this bug.