Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 233928 - Picky RFE: 3c59x driver should print MAC address of the card at boot time
Summary: Picky RFE: 3c59x driver should print MAC address of the card at boot time
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Neil Horman
QA Contact: Martin Jenner
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-25 22:37 UTC by David Tonhofer
Modified: 2007-11-30 22:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-04-16 14:24:00 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description David Tonhofer 2007-03-25 22:37:03 UTC
Description of problem:

  In the boot log, we find the following lines:

  ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 12 (level, low) -> IRQ 12
  3c59x: Donald Becker and others.
  0000:00:0a.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xdc00. Vers LK1.1.19
  divert: allocating divert_blk for eth0
  ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 10 (level, low) -> IRQ 10
  0000:00:0b.0: 3Com PCI 3c905C Tornado at 0xe000. Vers LK1.1.19
  divert: allocating divert_blk for eth1

  sis900.c: v1.08.07 11/02/2003
  ACPI: PCI interrupt 0000:00:04.0[A] -> GSI 10 (level, low) -> IRQ 10
  divert: allocating divert_blk for eth2
  eth2: Realtek RTL8201 PHY transceiver found at address 1.
  eth2: Using transceiver found at address 1 as default
  eth2: SiS 900 PCI Fast Ethernet at 0xbc00, IRQ 10, 00:0d:61:5d:47:f9.

  As one can see, the ouput of the sis900 driver is marginally more useful,
  as it prints the device name and MAC address. Shouldn't the "3c59x" do so,

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


Comment 3 Neil Horman 2007-04-16 14:24:00 UTC
This isn't a bug, and not something we should spend our time on.

The initalization strings printed when a driver is inserted into the kernel
provide whatever information the author deems relevant during the initzliation
process.  While printing the set of mac addresses that a card may contain may be
usefull, this strings are generated within individual drivers, so this is not a
scalable to large numbers of drivers, and as such is not usefull for much beyond
sysadmin interest.

There are several standard methods for retrieving MAC addresses from interfaces
in existance already.  ifconfig provides MAC address information, as does the
use of lspci in conjunction with the sysfs interface.  udev rules can be added
to automatically trigger the printing of this information to the syslog in a
consistent manner if you need the information during boot.

If you really feel strongly about the addition of this feature to the 3c59x
driver, you can propose it upstream (for which there will likely not be much
resistance) and then we will incorporate it in a future RHEL release, but shy of
that, you already have better, more consistent and standard methods for
obtaining this information.

Comment 4 John W. Linville 2007-04-16 15:00:12 UTC
Don't forget ethtool...

Comment 5 David Tonhofer 2007-04-19 21:57:54 UTC
> If you really feel strongly (...)

No, no, as I said it's "picky". I agree that consistency on driver
initialization output is not exactly top priority.

Thanks for the extensive clarifications.

Best regards,

-- David

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