src/sys/dev, branch release/10.1.0

Update the Intel ixl/ixlv drivers to fix a panic in the boot/install

2014-11-11T05:00:51Z

kernel if the system has a fiber-based Intel XL710 adapter installed. In addition ixl version 1.2.8 and ixlv version 1.1.18 give: - Improved VF stability (thanks to Ryan Stone for this) - RSS fixes - link detection in the ixlv driver - new sysctl's added - corrected media reporting Submitted by: jfv Approved by: re

MFS r273580: MFC r273577:

2014-10-24T07:50:34Z

Return BUS_PROBE_DEFAULT instead of BUS_PROBE_VENDOR or 0 for in-tree driver. This change was verified by Microsoft. Approved by: re (kib)

MFstable10 r273429:

2014-10-21T23:07:30Z

MFC r273402: Fix an issue where a FreeBSD virtual machine provisioned in the Microsoft Azure service does not recognize the second attached disk on the system. PR: 194376 Approved by: re (delphij) Sponsored by: The FreeBSD Foundation

MFS10 r273296 (r273219 in HEAD):

2014-10-20T03:17:48Z

Do nothing in vt_upgrade if there is no vt driver Previously, if no drivers attached at boot we would panic with "vtbuf_fill_locked begin.tp_row 0 must be < screen height 0". PR: 192248 Approved by: re

vt(4): Don't recalculate buffer size if we don't know screen size

2014-10-14T19:10:00Z

MF10: r273037 MFC: r272537 When the screen size is unknown, it's set to 0x0. We can't use that as the buffer size, otherwise, functions such as vtbuf_fill() will fail. This fixes a panic on RaspberryPi, where there's no vt(4) backend configured early in boot. PR: 193981 Tested by: danilo@ Approved by: re (marius)

vt(4): Save/restore keyboard mode & LED states when switching window

2014-10-14T19:01:11Z

MF10: r273036 MFC: r272416 Add new functions to manipulate these mode & state, instead of calling kbdd_ioctl() everyhere. This fixes at least two bugs: 1. The state of the Scroll Lock LED and the state of scroll mode could be out-of-sync. For instance, if one enables scroll mode on window #1 and switches to window #2, the LED would remain on, but the window wouldn't be in scroll mode. Similarily, when switching between a console and an X.Org session, the LED states could be inconsistent with the real state. 2. When exiting from an X.Org session, the user could be unable to type anything. The workaround was to switch to another console window and come back. Differential Revision: https://reviews.freebsd.org/D821 Reviewed by: ray@ Approved by: re (marius), ray@ Tested by: kwm@

MFS r272892 (r272713 in head):

2014-10-12T10:39:59Z

Since introducing the extra mapping in r250103 (head) for architectural performance events we have actually counted 'Branch Instruction Retired' when people asked for 'Unhalted core cycles' using the 'unhalted-core-cycles' event mask mnemonic. Reviewed by: jimharris Discussed with: gnn, rwatson Sponsored by: DARPA/AFRL Approved by: re (gjb)

MFC r272308: Fix old iSCSI initiator to work with new CAM locking.

2014-10-06T20:38:55Z

This switches code to using xpt_rescan() routine, irrelevant to locking. Using xpt_action() directly requires knowledge about higher level locks, that SIM does not need to have. This code is obsolete, but that is not a reason to crash. Approved by: re (marius)

MFC r272480:

2014-10-06T12:08:47Z

When we fail to get a USB reference we should just return, because there are no more references held. Approved by: re, marius

MFC r272349, r272422 and r272479:

2014-10-06T11:05:56Z

- Fix XHCI driver for devices which have more than 15 physical root HUB ports. The current bitmap array was too small to hold more than 16 bits and would at some point toggle the context size, which then would trigger an enumeration fault and cause a fallback to the EHCI companion controller, if any. - Make sure we always set the maximum number of valid contexts. - Set default cycle state in case of early interrupts. Approved by: re, marius