https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #42 from secan (secancri...@gmail.com) ---
Hello Andy,
So this is what I did. Due to the fact that Redhat is very peculiar when it
comes to patching, I went the kpatch way (the method that RH recommends).
Unfortunately the patch
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #43 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to secan from comment #42)
> So this is what I did. Due to the fact that Redhat is very peculiar when it
> comes to patching, I went the kpatch way (the method that RH
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #45 from secan (secancri...@gmail.com) ---
Created attachment 297577
--> https://bugzilla.kernel.org/attachment.cgi?id=297577=edit
dmesg log
--
You may reply to this email to add a comment.
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #44 from secan (secancri...@gmail.com) ---
Hello Andy,
As requested, I've added the kernel boot flags, and attached the "dmesg"
output.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #46 from Andy Shevchenko (andy.shevche...@gmail.com) ---
(In reply to secan from comment #44)
> Hello Andy,
>
> As requested, I've added the kernel boot flags, and attached the "dmesg"
> output.
Okay, in your case device seems to be
