Bug 235502 - SMC nic mac lost after booting kernel-xen / xend
SMC nic mac lost after booting kernel-xen / xend
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Xen Maintainance List
Martin Jenner
Depends On:
Blocks: 514491
  Show dependency treegraph
Reported: 2007-04-06 08:27 EDT by Joshua M. Hoffman
Modified: 2010-06-22 14:53 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-22 14:53:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joshua M. Hoffman 2007-04-06 08:27:26 EDT
Description of problem:

After booting kernel-xen and starting xend with a default config, my nic's mac
becomes locked to FF:FE:FF:FF:FF:FF.  Booting back to non-xen kernel does not
help.  The "broken" mac is still there, even when I PXE boot from bios.

The only way I have found to fix the problem is to remove and re-seat the nic.

I have a lab of 15 of the same machines all having this problem.

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

RHEL5 (2.6.18-8.el5xen)
SMC pci card model: SMC1255TX
SMC optional boot rom installed: SMC1255B-ROM V1.23

How reproducible:

Almost every time.  Fails to occur only rarely.

Steps to Reproduce:

1. Install said nic w/ optional boot rom (as eth0)
2. Boot kernel-xen
3. Reboot to non-xen kernel

Actual results:


Expected results:


Additional info:

Computers are all Dell Optiplex GX280 "n" series
Bios revision A08

Note: On these machines the SMC pci is eth0 (built-in is eth1). The problem does
not occur with built-in nic (if pci is removed and built-in is used as eth0).

I'll be happy to ship one of these nics to someone, if desired.
Comment 1 Red Hat Bugzilla 2007-07-24 20:44:52 EDT
change QA contact
Comment 5 Andrew Jones 2010-06-22 13:06:00 EDT
I have a feeling this isn't a problem any more, since it's been quite for 3 years. Joshua, can you confirm that this is no longer an issue?
Comment 6 Joshua M. Hoffman 2010-06-22 14:46:50 EDT
It is no longer a problem for me as I do not have any SMC1255TXs in service and have not for some time.
Comment 7 Andrew Jones 2010-06-22 14:53:09 EDT
The only reporter of this bug is no longer affected by it. I'll close it out, if somebody comes across it and has the same issue, then they can feel free to reopen.


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