increase debug noise when isc_in has a problem
races with the socket upcall
MFC after: 3 days
redundancy) for the following RAID levels: RAID4/5E/5EE/6/MDF.
This seems to break at least my test board here (AR71xx + AR8316 switch PHY). Since I do have a whole sleuth of "normal" PHY boards (with an AR71xx on a normal PHY port), I'll do some further testing with those to determine whether this is a general issue, or whether it's limited to the behaviour of the "fake" dedicated PHY port mode on these atheros switches.
Fix issues stamping boot on other ZFS drives, now you can boot after removing mirror drive. Submitted by: kmoore Obtained from: PC-BSD MFC after: 3 days Sponsored by: iXsystems
intr_bind() on x86. This has been requested by jhb and I strongly disagree with this, but as long as he is the x86 and interrupt subsystem maintainer I will follow his directives. The disagreement cames from what we should really consider as a public KPI. IMHO, if we really need a selection between the kernel functions, we may need an explicit protection like _KERNEL_KPI, which defines which subset of the kernel function might really be considered as part of the KPI (for thirdy part modules) and which not. As long as we don't have this mechanism I just consider any possible function as usable by thirdy part code, thus intr_bind() included. MFC after: 1 week
enum values and zeroes. This keeps clang happy (and is just good form). Submitted by: dim
Submitted by: glarkin MFC after: 3 days Sponsored by: iXsystems
Also note that loader.conf support is incomplete.
branch. This brings us very close to the 3.1 release, which is planned for May 14th. MFC after: 2 weeks
softclock_call_cc(). While there, move some common code to callout_cc_del(). Requested by: avg, jhb Reviewed by: jhb MFC after: 1 week
…th an <atomic> header that works with clang 3.1 (and, importantly, the pre-3.1 snapshot currently in head)