Bug 213376
| Summary: | ethernet driver module problem w/8139 chip set | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sam Azer <sam> | ||||||
| Component: | kernel-xen | Assignee: | Xen Maintainance List <xen-maint> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 6 | CC: | bstein, katzj, notting, xen-maint | ||||||
| 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-05-06 16:30:16 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
Sam Azer
2006-11-01 07:16:18 UTC
Could you please give "dmesg" output for both the xen and non-xen kernels? Thanks. Created attachment 139993 [details]
kernel messages from .fc6 boot
lines containing named grepped out for privacy
Created attachment 139994 [details]
kernel messages from .xenfc6 boot
lines containing named grepped out for privacy
- additional IPs (10.177.1.7 and 1.8) don't show in the xen boot because I removed them after reviewing old bugzilla entries. - samba is configured to listen to some VPN subnets that don't exist at boot time. Thanks again. This problem appeared recently when booting into the non-xen OS. This leads me to think that perhaps this is related to the code that determines which network driver to use at boot time. Something about the XEN boot process causes the bug to appear consistently. Thanks, Sam. I'm not seeing this in your posted messages - in both of them, the proper thing happens - 8139cp loads, ignores the device. 8139too loads, initializes as eth0. e100 loads, initializes as eth1. Do you have the proper HWADDR in /etc/sysconfig/network-scripts/ifcfg-ethX? Do you have a log from when it fails for you? (kudzu has nothing to do with module loading, FWIW - pushing back to kernel.) This problem no longer appears - I'm not sure why. I note that you mention eth0 and eth1 backwards in your last comment - so perhaps the HWADDR had something to do with it. I did find it missing and added it at some point but never got around to doing any more tests. Sorry for that and thanks again for your effort. |