Hi, I am trying to bring up gigabit interface in couple of Nexcom blade servers running FreeBSD/amd64. The interfaces (two Marvell Yukon 88E8062 controllers) are recognized properly, but no media is ever detected:> ifconfigmsk0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=11a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4> ether 00:10:f3:0d:d6:45 media: Ethernet autoselect (none) status: no carrier msk1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=11a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4> ether 00:10:f3:0d:d6:46 media: Ethernet autoselect (none) status: no carrier I tried manual setting of media - but the driver won't allow me to set 1000baseSX link (this is what other blades in the same chasis with working em driver are reporting). # ifconfig msk0 media 1000baseSX ifconfig: SIOCSIFMEDIA (media): Device not configured I'm puzzled here: are there known limitations in the driver wrt support of certain media types? Here is pciconf -lv information if it helps... mskc0@pci0:3:0:0: class=0x020000 card=0x628211ab chip=0x434711ab rev=0x14 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = 'Yukon 88E8062 PCI-E IPMI Gigabit Ethernet Controller' class = network subclass = ethernet This is on 7.0-RELEASE on amd64. I also tried kernel from 7-STABLE from few days ago, but the problem was still present. -- Best regards, Krzysztof Jedruczyk
On Mon, Jun 30, 2008 at 01:54:23PM +0200, Krzysztof Jedruczyk wrote: > Hi, > > I am trying to bring up gigabit interface in couple of Nexcom blade servers running FreeBSD/amd64. The interfaces (two Marvell Yukon 88E8062 controllers) are recognized properly, but no media is ever detected: > > > ifconfig > msk0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=11a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4> > ether 00:10:f3:0d:d6:45 > media: Ethernet autoselect (none) > status: no carrier > msk1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=11a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4> > ether 00:10:f3:0d:d6:46 > media: Ethernet autoselect (none) > status: no carrier > > I tried manual setting of media - but the driver won't allow me to set 1000baseSX link (this is what other blades in the same chasis with working em driver are reporting). > > # ifconfig msk0 media 1000baseSX > ifconfig: SIOCSIFMEDIA (media): Device not configured > > I'm puzzled here: are there known limitations in the driver wrt support of certain media types? > > Here is pciconf -lv information if it helps... > > mskc0@pci0:3:0:0: class=0x020000 card=0x628211ab chip=0x434711ab rev=0x14 hdr=0x00 > vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' > device = 'Yukon 88E8062 PCI-E IPMI Gigabit Ethernet Controller' > class = network > subclass = ethernet > > This is on 7.0-RELEASE on amd64. I also tried kernel from 7-STABLE from few days ago, but the problem was still present. > The 88E8062 support wasn't tested due to lack of hardware and I just copied the device id from myk driver. Would you show me the output of "devinfo -rv| grep oui" ? Also it would be better if I can see verbosed boot message. -- Regards, Pyun YongHyeon
आशीष शुक्ल Ashish Shukla
2008-Jul-01 16:39 UTC
Marvell Yukon 88E8062 - media selection problem
,--[ On Mon, Jun 30, 2008 at 01:54:23PM +0200, Krzysztof Jedruczyk wrote: | Hi, | | I am trying to bring up gigabit interface in couple of Nexcom blade servers running FreeBSD/amd64. The interfaces (two Marvell Yukon 88E8062 controllers) are recognized properly, but no media is ever detected: | | > ifconfig | msk0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 | options=11a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4> | ether 00:10:f3:0d:d6:45 | media: Ethernet autoselect (none) | status: no carrier | msk1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 | options=11a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4> | ether 00:10:f3:0d:d6:46 | media: Ethernet autoselect (none) | status: no carrier | | I tried manual setting of media - but the driver won't allow me to set 1000baseSX link (this is what other blades in the same chasis with working em driver are reporting). | | # ifconfig msk0 media 1000baseSX | ifconfig: SIOCSIFMEDIA (media): Device not configured How about doing 'ifconfig msk0 up' prior to setting media ? Not sure, if that'll work. HTH Ashish -- ?-- ?- ???? ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? --- -- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080701/ba15d131/attachment.pgp
Pyun YongHyeon pisze:> > Would you try the patch at the following URL? > http://people.freebsd.org/~yongari/msk/msk.88E8040.patch5 > > The diff generated against HEAD and it could be cleanly applied to > 7-stable. 7-stable also has a couple of important bug fixes. > So it would be better to use 7-stable.After applying both patches (the one from previous email and the one from http link) both interfaces work. I'm impressed :) I understand the media selection fix I am using at the moment is just a hack - but will the other patch get in the -stable anytime soon? -- Best regards, Krzysztof J?druczyk -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3221 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080706/9a8d8c2a/smime.bin