Prev: sysfs: cannot create duplicate filename ... XVR-600 related?
Next: block: Implement a blk_yield function to voluntarily give up the I/O scheduler.
From: Mikael Pettersson on 1 Jun 2010 16:10 Booting 2.6.35-rc1 on a Sun Blade 2500 Red with builtin tg3 I get: tg3.c:v3.110 (April 9, 2010) PCI: Enabling device: (0000:00:03.0), cmd 2 .... tg3 0000:00:03.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. tg3 0000:00:03.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. tg3 0000:00:03.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. tg3 0000:00:03.0: eth0: Tigon3 [partno(none) rev 1002] (PCI:66MHz:64-bit) MAC address ... tg3 0000:00:03.0: eth0: attached PHY is 5703 (10/100/1000Base-T Ethernet) (WireSpeed[1]) tg3 0000:00:03.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] tg3 0000:00:03.0: eth0: dma_rwctrl[763f0000] dma_mask[32-bit] .... tg3 0000:00:03.0: eth0: No firmware running tg3 0000:00:03.0: eth0: Link is up at 100 Mbps, full duplex tg3 0000:00:03.0: eth0: Flow control is on for TX and on for RX The three 'vpd r/w failed' messages are new and did not occur with 2.6.34 or earlier kernels. /Mikael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |