Messages in this thread | | | Date | Wed, 10 Mar 2010 16:33:28 +0100 | From | Mikael Pettersson <> | Subject | [BUG 2.6.34-rc1] bogus "(null)" in tulip init messages |
| |
Booting 2.6.34-rc1 on a machine with a tulip nic I see a number of kernel messages that include "(null)" where previous kernels included the string "tulip0":
--- dmesg-2.6.33 2010-02-26 12:58:32.000000000 +0100 +++ dmesg-2.6.34-rc1 2010-03-10 16:17:06.000000000 +0100 ... Linux Tulip driver version 1.1.15 (Feb 27, 2007) tulip 0000:00:0f.0: enabling device (0014 -> 0017) -tulip0: EEPROM default media type Autosense. -tulip0: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block. -tulip0: Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2) block. -tulip0: Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block. -tulip0: Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) block. -tulip0: Index #4 - Media 100baseTx (#3) described by a 21143 reset method (5) block. -eth0: Digital DS21142/43 Tulip rev 48 at Port 0x800, 00:00:c5:50:f9:51, IRQ 25. + (null): EEPROM default media type Autosense + (null): Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block + (null): Index #1 - Media 10baseT-FDX (#4) described by a 21142 Serial PHY (2) block + (null): Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block + (null): Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM PHY (4) block + (null): Index #4 - Media 100baseTx (#3) described by a 21143 reset method (5) block +net eth0: Digital DS21142/43 Tulip rev 48 at Port 0x800, 00:00:c5:50:f9:51, IRQ 25
Apart from this the tulip driver seems to work in 2.6.34-rc1.
/Mikael
| |