Date: Tue, 15 Mar 2016 12:28:02 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 208022] ixgbe - unexpected "ix0: Invalid advertised speed; valid modes are 0x1 through 0x7" at boot time Message-ID: <bug-208022-6@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208022 Bug ID: 208022 Summary: ixgbe - unexpected "ix0: Invalid advertised speed; valid modes are 0x1 through 0x7" at boot time Product: Base System Version: 10.3-BETA2 Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: terry-freebsd@glaver.org CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Created attachment 168236 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D168236&action= =3Dedit Example console messages and sysctl values Somewhere along the line, the ixgbe driver started printing an unexpected "= ix0: Invalid advertised speed; valid modes are 0x1 through 0x7" at boot time as shown in the attachment. The hardware is a retail Intel X540-T1 card at the latest firmware revision. The two (why two?) sysctls in the attachment are = at their default value. The 2.8.3 driver in earlier 10.3 builds didn't do this= , so it is probably due to something in the 3.1.13-k import. The message seems harmless, but should probably be fixed. Note that simply changing the default value of one / both sysctls may not have the desired effect - a quick look in the driver source shows a bunch of potential error messages when trying to select the advertised speed on (for example) fiber ports. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-208022-6>