3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.

Bug #356148 reported by marcobra (Marco Braida)
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
Nominated for Jaunty by Mathieu Marquer

Bug Description

On

Description: Ubuntu jaunty (development branch)
Release: 9.04

with

00:06.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 30)

After today modules and kernel updates i get *** EEPROM MAC address is invalid as you can see in dmesg, i can't connect to the net nomore.

--------------------------------------------------------------

dmesg

[ 2.935772] 3c59x 0000:00:06.0: enabling device (0000 -> 0001)
[ 2.935794] 3c59x 0000:00:06.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 2.935801] 3c59x: Donald Becker and others.
[ 2.935814] 0000:00:06.0: 3Com PCI 3c905C Tornado at 00011000.
[ 2.935824] 3c59x 0000:00:06.0: setting latency timer to 64
[ 3.029781] *** EEPROM MAC address is invalid.
[ 3.029789] 3c59x: vortex_probe1 fails. Returns -22
[ 3.029796] 3c59x 0000:00:06.0: PCI INT A disabled
[ 3.072747] 3c59x: probe of 0000:00:06.0 failed with error -22

-------------------------------------------------------

00:06.0 Ethernet controller [0200]: 3Com Corporation 3c905C-TX/TX-M [Tornado] [10b7:9200] (rev 30)
    Subsystem: 3Com Corporation Device [10b7:1000]
    Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+ INTx-
    Interrupt: pin A routed to IRQ 17
    Region 0: I/O ports at 1000 [size=128]
    Region 1: Memory at <ignored> (32-bit, non-prefetchable) [disabled]
    Expansion ROM at 30000000 [disabled] [size=128K]
    Capabilities: [dc] Power Management version 2
        Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
        Status: D0 PME-Enable- DSel=0 DScale=2 PME-
    Kernel modules: 3c59x

----------------------

Linux ubuntu 2.6.28-11-generic #40-Ubuntu SMP Fri Apr 3 17:39:51 UTC 2009 i686 GNU/Linux

linux-image-2.6.28-11-generic:
  Installato: 2.6.28-11.40
  Candidato: 2.6.28-11.40
  Tabella versione:
 *** 2.6.28-11.40 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

---------------------------------------------------------------

no eth0 recognized on ifconfig only the "lo"

---------
my ubuntu pc internal reference (pc_com_sx)

Thank you

description: updated
tags: added: image jaunty kernel linux
affects: ubuntu → linux (Ubuntu)
summary: - Ethernet controller: 3Com Corporation 3c905C-TX/TX-M *** EEPROM MAC
- address is invalid.
+ 3Com Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid.
Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :

Same issue with today upgrade of kernel (i'm using an alternate nic card to download updates)

Linux ubuntu-desktop 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:38:53 UTC 2009 i686 GNU/Linux

Thank you

Revision history for this message
Mathieu Marquer (slasher-fun) wrote :

Confirming as a user on ubuntu-fr.org forum encounters the same problem.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Martyn Young (martyn-young) wrote :

I'm having the same issue.

dmesg:

[ 9542.571630] 0000:04:00.0: 3Com PCI 3CCFE575CT Tornado CardBus at ffffc2000007a000.
[ 9542.571646] 3c59x 0000:04:00.0: setting latency timer to 64
[ 9542.686126] *** EEPROM MAC address is invalid.
[ 9542.686139] 3c59x: vortex_probe1 fails. Returns -22
[ 9542.686160] 3c59x 0000:04:00.0: PCI INT A disabled
[ 9542.686230] 3c59x: probe of 0000:04:00.0 failed with error -22

Linux ubuntu64 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

I did a quick test on another laptop and it was working fine.

Cheers

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi marcobra,

Can you comment which version of the kernel you had updated from where this wasn't an issue? It will help narrow down the scope of patches to examine which may have introduced this regression. I do see some much older bugs reported against other distros and upstream having a similar issue (but against slightly different hardware). However, patches were commited quite some time ago.

https://bugzilla.redhat.com/show_bug.cgi?id=158725
http://bugzilla.kernel.org/show_bug.cgi?id=1188

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :

I always upgrade my kernel from the standard Ubuntu repository kernel but now i'm on Karmik and i can only test the 3com nic on it
 BTW now i'm not using the

00:06.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 30)

with karmik i still use:

00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

if you want i can put the old nic and i can test it om kermik with differnt kernel

hope this helps

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks for the feedback marcobra. Let's see if Martyn will be able to test since it seems he had the same issue and hardware.

@Martyn, can you comment if this issue remains with the latest Karmic 9.10 Alpha development release? Images are available at http://cdimage.ubuntu.com/releases/karmic/ . Please let us know your results. Thanks.

Changed in linux (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Martyn Young (martyn-young) wrote : AUTO: Martyn Young is out of the office. (returning 13/08/2009)

I am out of the office until 13/08/2009.

I will respond to your message when I return.

If you have an urgent enquiry, please call 0800 SOLNET or contact Stewart
Gebbie <email address hidden>.

Regards
Martyn Young

Note: This is an automated response to your message "[Bug 356148] Re: 3Com
Corporation 3c905C-TX/TX-M fail *** EEPROM MAC address is invalid." sent
on 8/12/09 12:19:50 PM.

This is the only notification you will receive while this person is away.

Attention:
This email may contain information intended for the sole use of
the original recipient. Please respect this when sharing or
disclosing this email's contents with any third party. If you
believe you have received this email in error, please delete it
and notify the sender or <email address hidden> as
soon as possible. The content of this email does not necessarily
reflect the views of Solnet Solutions Ltd.

Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :

Description: Ubuntu karmic (development branch)
Release: 9.10

The 00:06.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 30) is working now with kernel:

Linux ubuntu 2.6.31-7-generic #27-Ubuntu SMP Mon Aug 24 17:33:49 UTC 2009 i686 GNU/Linux

Thank you

Changed in linux (Ubuntu):
status: Incomplete → Fix Committed
status: Fix Committed → Fix Released
status: Fix Released → Incomplete
Revision history for this message
Brad Figg (brad-figg) wrote :

I have this problem after installing Karmic Alpha 5.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :

@Brad Figg can you copy and paste here the result of the lspci (lower of LSPCI) terminal command here...

I use this network interface with karmic the updated alpha5 without any issue (not installed from alpha5 cd)
Linux ubuntu 2.6.31-10-generic 32 bits

Thank you

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.