1812

I did rc 2 and 4 and sent privately to another member by request but didn't publicly post because I no longer have proliant hardware with the RMRR issue so I can't validate the new bzimages myself anymore. But I'm still happy to do them, but I'm not sure how often I will end up doing the RC's as one never knows when they are likely to change to the next one. BUT, anyone can do this, and should if they want every single RC!

thanks for the feedback. I don't have any windows machines on my network. only 1 linux mint and the rest are macOS. so maybe from one of those...

is this CIFS error a thing I need to worry about? updated this machine from 6.5.3

great vid, but curious why no benchmarks???

That is actually a high number of my contacts with company employees, 80% I imagine. I first called 2 weeks ago looking into the service. They wanted 135/mo plus 25/mo for no cap plus a 100 dollar tech visit “to check my lines and make sure they can handle it.” I asked for technical details of checking my lines, and how their techs in India can determine signal strength I’m receiving from there but yet they need to send someone out and charge me. All I got back was attitude so I asked to be transferred to their business department. Their business department tried to interrogate me on my “belief that I needed gig speed” because “I have lots of business that do just fine with a 75/15 plan.” I asked again for a gig quote and they quoted me a 100mbps package with a phone that I didn’t ask for. So they got hung up on ad well. Yesterday it was a 5 minute call, super sweet/easy rep, 20 bucks more a month (total 69/mo) with no cap and no tech visit. and their first 2 levels of tech support are like talking to random people on the street about planetary physics. It’s not proportional ootb sadly, at the moment. The contacted speeds are 1000/35 but over the course of the next week or so, I’ll work my way up the technician ladder and get someone to increase upload. They can do it, but only if you pester them enough and find he right person. Shouldn’t have to be that way, but welcome to Comcast!

Seems to have worked... why does everyone dump on Comcast again?

any generic one that is supported by osx. I bought several from micro center for 8 bucks a pop.

okie dokie

Changed Status to Open

call trace persists in 6.6 rc 2, diagnostics attached gsobackup-diagnostics-20180911-1638.zip

I've had nothing but inconsistent hdmi audio after a few sub-revisions starting aroud 13.2 I think. I've gone to usb audio as well and not looking back.

if you have an onboard p410/whatever controller, try disabling it in the bios. they can sometimes cause conflicts with other hba's.

This is interesting because I saw something similar once about a month ago when I had uefi set in unRaid but legacy was still enabled in bios. Setting bios to uefi only fixed it. I thought it was just the quirk of one of my servers.

1060 is fine. this call trace isn't helping you out: Sep 10 14:15:43 Tower kernel: vfio-pci 0000:02:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Sep 10 14:15:44 Tower kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Sep 10 14:15:44 Tower kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.49-unRAID #1 Sep 10 14:15:44 Tower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X79 Extreme6/GB, BIOS P1.30 05/16/2012 Sep 10 14:15:44 Tower kernel: Call Trace: Sep 10 14:15:44 Tower kernel: <IRQ> Sep 10 14:15:44 Tower kernel: dump_stack+0x5d/0x79 Sep 10 14:15:44 Tower kernel: __report_bad_irq+0x32/0xac Sep 10 14:15:44 Tower kernel: note_interrupt+0x1d4/0x225 Sep 10 14:15:44 Tower kernel: handle_irq_event_percpu+0x39/0x3f Sep 10 14:15:44 Tower kernel: handle_irq_event+0x33/0x51 Sep 10 14:15:44 Tower kernel: handle_fasteoi_irq+0x8c/0xfc Sep 10 14:15:44 Tower kernel: handle_irq+0x1c/0x1f Sep 10 14:15:44 Tower kernel: do_IRQ+0x3b/0xbb Sep 10 14:15:44 Tower kernel: common_interrupt+0x7d/0x7d Sep 10 14:15:44 Tower kernel: </IRQ> Sep 10 14:15:44 Tower kernel: RIP: 0010:poll_idle+0x4d/0x58 Sep 10 14:15:44 Tower kernel: RSP: 0018:ffffffff81c03ec0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffad Sep 10 14:15:44 Tower kernel: RAX: 0000000080200000 RBX: 0000000000000000 RCX: 000000000000012d Sep 10 14:15:44 Tower kernel: RDX: 0000000000000000 RSI: ffffffff81c56480 RDI: ffff88083fc28440 Sep 10 14:15:44 Tower kernel: RBP: ffff88083fc28440 R08: 0000069eb7774340 R09: 0000000000000018 Sep 10 14:15:44 Tower kernel: R10: ffffffff81c03e90 R11: 0000000000000000 R12: ffffffff81c56480 Sep 10 14:15:44 Tower kernel: R13: 0000000000000000 R14: ffffffff81c56498 R15: 0000018e873e2d67 Sep 10 14:15:44 Tower kernel: cpuidle_enter_state+0x9d/0x135 Sep 10 14:15:44 Tower kernel: do_idle+0x11a/0x179 Sep 10 14:15:44 Tower kernel: cpu_startup_entry+0x18/0x1a Sep 10 14:15:44 Tower kernel: start_kernel+0x3dc/0x3e4 Sep 10 14:15:44 Tower kernel: secondary_startup_64+0xa5/0xb0 Sep 10 14:15:44 Tower kernel: handlers: Sep 10 14:15:44 Tower kernel: [<ffffffff8141aae7>] usb_hcd_irq Sep 10 14:15:44 Tower kernel: Disabling IRQ #16 Sep 10 14:16:25 Tower kernel: vfio-pci 0000:02:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Sep 10 14:16:25 Tower kernel: br0: port 2(vnet0) entered blocking state Sep 10 14:16:25 Tower kernel: br0: port 2(vnet0) entered disabled state Sep 10 14:16:25 Tower kernel: device vnet0 entered promiscuous mode Sep 10 14:16:25 Tower kernel: br0: port 2(vnet0) entered blocking state Sep 10 14:16:25 Tower kernel: br0: port 2(vnet0) entered forwarding state Sep 10 14:16:25 Tower kernel: kvm: SMP vm created on host with unstable TSC; guest TSC will not be reliable Sep 10 14:16:26 Tower kernel: vfio_ecap_init: 0000:02:00.0 hiding ecap 0x19@0x900 Sep 10 14:16:26 Tower acpid: input device has been disconnected, fd 8 Sep 10 14:16:26 Tower acpid: input device has been disconnected, fd 6 Sep 10 14:16:26 Tower acpid: input device has been disconnected, fd 7 Sep 10 14:16:26 Tower acpid: input device has been disconnected, fd 4 I'm not good with call traces, but I suspect that your card is conflicting with something else in the bios. You can try moving it to a different slot, or see what IRQ it's on in your bios and adjust accordingly. But before that, look into updating your bios because its from: 05/16/2012. It may help resolve several other errors that appear in your syslogs and/or resolve the issue of failure to passthrough/lockup on it's own. after that, since you only have 1 gpu, you may have to follow the steps in the video below

isolating cpus and emulator pinning is the first place to start if you haven't already done so.