Bug 434308

Summary: TOSHIBA TX/3516: e100 won't link up on 2.6.24.2-10.fc8
Product: [Fedora] Fedora Reporter: Mamoru TASAKA <mtasaka>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: medium    
Version: 8   
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: 2008-03-01 13:50:01 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:
Attachments:
Description Flags
dmesg on 2.6.24.2-10.fc8
none
dmesg on 2.6.23.14-107.fc8 none

Description Mamoru TASAKA 2008-02-22 15:57:48 UTC 
Description of problem:
With my laptop (Toshiba TX/3516) my network eth0 (acutally e100)
won't link up on 2.6.24.2-10.fc8

With 2.6.23.14-107.fc8 network links up normally

Version-Release number of selected component (if applicable):
kernel-2.6.24.2-10.fc8.i686

How reproducible:
100%

Steps to Reproduce:
1. boot with 2.6.24.2-10.fc8
2.
3.
  
Actual results:
dmesg attached

Expected results:
link up as 2.6.23.14-107.fc8 (dmesg attached)

Additional info:
Comment 1 Mamoru TASAKA 2008-02-22 15:57:48 UTC 
Created attachment 295642 [details]
dmesg on 2.6.24.2-10.fc8
Comment 2 Mamoru TASAKA 2008-02-22 15:58:44 UTC 
Created attachment 295643 [details]
dmesg on 2.6.23.14-107.fc8
Comment 3 Mamoru TASAKA 2008-03-01 13:50:01 UTC 
It seems that it is okay after I set up network configuration
after booting with 2.6.24 kernel again.