No disagreement on viability of the offspring and their subsequent ability to mate further down, only a disagreement about percentage between single digit up to “half” in the current breed (as it exists in the USA). I believe it’s notably diluted from the original cross for reasons I stated in my other reply, but I’m curious about my red since she’s considerably more dingo-esque than my blue.
Anecdotal evidence is the best evidence, right?
Right, but they’re no longer half dingo after the multitude of generations has passed in whichever pedigree, because for whichever innate temperament traits you might desire, along with the inability to selectively breed for physical ones with a wild dog, you wouldn’t take a second generation heeler and cross a dingo back in just to keep the percentage up. I don’t honestly know the whole history but it’s conceivable that enough of the original breed starters contained sufficient “dingo” to keep the content up.
I thought I had read that one of the various tests…wisdom panel maybe…was providing results indicating wild crosses, including dingo. My thinking was that any significant percentage would show, but time will tell, since we have whichever brand that was, and just need to collect and run the sample.
They are not, it’s just some breed representation thing, and they certainly look more dingoey than a Jack Russel, but at least in the United States, it’s likely to be trace amounts. Source, I own two, but admittedly neither have had any sort of genetic test so I guess my hearsay is as good as yours…I should find out, I honestly wouldn’t be surprised if they had up to a quarter dingo somehow.
I seem to recall a VMware complaint similar to this too, and there was a ring buffer tuning to do to fix it… But that error message doesn’t seem quite right to match it.
TX queue timeouts can be caused by several things, but I wonder if you’re not seeing an end result of a spammy Ethernet flow control implementation where the device can’t transmit because the link is continuously paused.
If so, there may be rx_xoff counters viewable from within proxmox, or “ethtool -s enp1s0f0” would tell you where the device is seeing pause frames from the switch on a regular Linux host.
The link down tends to be a reaction by the driver to recover from a hung queue, so if it’s not flow control, there could be a driver/firmware upgrade possible, or a series of tunables if there’s a bug somewhere in packet handling land resulting in the NIC itself hanging.