Bug 695050

Summary: Unplug and replug of r8169 causes interface failure to come up
Product: [Fedora] Fedora Reporter: Matt Willsher <matt>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-30 17:03:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matt Willsher 2011-04-10 07:41:01 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
kernel-2.6.38.2-9.fc15.x86_64

How reproducible:
Happen both time I've tried it

Steps to Reproduce:
1. NIC is connected
2. Unplug cable. 
3. Plug it back it to the same port
4. Light blip but link isn't established
  
Actual results:
Interface doesn't come up


Expected results:
Link comes up on interface

Additional info:

From dmesg: 

[26650.782048] r8169 0000:02:01.0: eth1: link up
[26650.793025] r8169 0000:02:01.0: BAR 0: set to [io  0xca00-0xcaff] (PCI address [0xca00-0xcaff])
[26650.793034] r8169 0000:02:01.0: BAR 1: set to [mem 0xdfffe000-0xdfffe0ff] (PCI address [0xdfffe000-0xdfffe0ff])
[26650.793077] r8169 0000:02:01.0: PME# disabled
[26650.793535] r8169 0000:02:01.0: eth1: link down
[26650.794762] r8169 0000:02:01.0: eth1: link up
[26650.795172] r8169 0000:02:01.0: eth1: link down
[26650.795953] r8169 0000:02:01.0: eth1: link up
[26650.797178] r8169 0000:02:01.0: eth1: link down
[26650.801030] r8169 0000:02:01.0: eth1: link down
[26650.897049] r8169 0000:02:01.0: PME# enabled

Same link works an e1000 NIC on the same machine
Comment 1 Josh Boyer 2011-09-27 13:55:49 UTC 
Is this still happening on the latest 2.6.40.x F15 kernel?