[14:12] <s10gopal> apw, jsalisbury why Rafael is not accepting that his commit is causing the problem?
[14:33] <jsalisbury> s10gopal, He just wants more "Proof".  I'm working on a new test kernel for you to do that.  Should have something ready soon.
[14:54] <s10gopal> jsalisbury, if git bisect result is not correct then it is used ?
[15:19] <s10gopal> why it is used ?
[15:43] <JimBuntu> s10gopal, this is the kernel. Please don't expect one of the devs to blindly accept pretty much anything. They take things pretty seriously and the last thing they want is the blame for fixing something for 3% of the users that then inadvertently causes issues for some other group. They generally also try not to only side-step an issue and would rather figure out the root cause and fix that, or give that person/group time to do so.
[17:56] <Daegalus> Hi, I just wanted to heck if anyone that knows more about kernels saw my USB-C/PCIe/TBT issue from yesterday that I posted?
[18:05] <apw> Daegalus, probabally best to post your ubuntu bug number
[18:07] <Daegalus> Well, I was asking for advice on where to put it/classify it because I wasn't 100% sure it was a kernel/module but i can post it and then link it @apw
[18:08] <apw> the kernel is as good a guess as any with that kind of "none of my usb-c works now" kind of bugs
[18:08] <Daegalus> cool, I will then post the bug and link it here in a bit
[18:55] <Daegalus> @apw https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496 is that sufficient?
[18:55] <ubot5`> Ubuntu bug 1765496 in linux (Ubuntu) "USB-3/PCIe Root/Thunderbolt fail to load" [Undecided,New]
[19:28] <Daegalus> @jsalisbury did as you instructed for the bug, its still a problem in upstream.
[19:30] <jsalisbury> Daegalus, ok, thanks.  Does booting back into the prior kernel make the bug go away?  It should if the regression was introduced by the kernel.
[19:31] <Daegalus> i am double checking now, im installing the one from the kernelMainline folders as i might have confused 4.15.0-13 with 4.13
[19:31] <jsalisbury> Daegalus, ack.  It should actually still be selectable from the GRUB menu, I would think.
[19:32] <Daegalus> 4.15.0-13 4.15.0-15 and 4.16.0-041600 are the only versions in my /boot folder
[19:33] <jsalisbury> Daegalus, ok.  If we can identify this as a regression, we can bisect to find the commit that caused it.
[19:34] <Daegalus> should i get 4.13 or 4.13.16 ? 
[19:36] <jsalisbury> Daegalus, you shouldn't have to, if you were on 4.15 when the bug didn't exist.
[19:38] <Daegalus> already did it, same problem on 4.13, so its not the kernel, could it be a module? its why i originally posted in here asking for help on figuring out the best place to file the bug
[19:39] <jsalisbury> Daegalus, Hmm, kernel modules are tied to specific kernel versions, so it probably is not the kernel.
[19:40] <jsalisbury> Daegalus, could it be a HW or cabel problem?
[19:41] <Daegalus> damn, ok, sorry for the mistake then. Just by the errors in dmesg it seemed like one. Ummm, not sure, it was working on Friday evening when i left, I shut off my computer, started it on monday, no external monitors and errors in my dmesg. I had upgraded the kernel on Friday, but didn't reboot and figured my shutoff/start will take care of upgrading that for me. So its why i thought it was a kernel problem
[19:42] <Daegalus> I'll go see if i can get a new cable and see if thats the issue
[19:49] <jsalisbury> Daegalus, The cable is worth checking.  Just to confirm, are you running uname -a from a terminal to confirm your booted into the prior kernel?
[19:50] <Daegalus> Yes
[20:01] <Daegalus> @jsalisbury just got a cable from IT, no go. im gonna boot into the original windows partition on this and see if i can figure something out from that side. Definitely seems to be something either in the firmware or the bios. Imma do some digging, but thank you for helping out with the kernel part. I will close the ticket in a little while after I check some stuff
[20:02] <jsalisbury> Daegalus, thanks.  If you think it's still the kernel, just post to the bug and I'll follow up. 
[20:30] <Daegalus> @jalisbury found the problem I think. Dell released a thunderbolt firmware update that failed to install. I jumped into windows to force reinstall it And hoping that fixes it but it's definitely on my end. Thought I'd give you an update