| 1 |
On 15/12/2019 01:54, Andrew Udvare wrote: |
| 2 |
> On 12/12/2019 10:18, Daniel Frey wrote: |
| 3 |
>> |
| 4 |
>> I have just installed fresh new gentoo installs with 5.4.2 and both |
| 5 |
>> machines use nvidia-drivers - I have not seen this at all. |
| 6 |
>> |
| 7 |
>> I have been doing a fair bit of compiling on one of the machines and |
| 8 |
>> haven't had any hiccups whatsoever. |
| 9 |
>> |
| 10 |
>> Dan |
| 11 |
>> |
| 12 |
> |
| 13 |
> Thanks for the reply. |
| 14 |
> |
| 15 |
> I think I have found the issue in another 3rd party blob-ish driver from |
| 16 |
> Magewell, which is for my capture card. I removed the capture card |
| 17 |
> (since this would stop the module from loading) and my system has not |
| 18 |
> had a panic since. I have not tried to upgrade back to 5.4.2 yet but as |
| 19 |
> I said before I was getting the error on 5.4.0 too. |
| 20 |
> |
| 21 |
> Andrew |
| 22 |
> |
| 23 |
|
| 24 |
For anyone interested, here are some pictures of the panics: |
| 25 |
|
| 26 |
https://i.imgsafe.org/5e/5e20756985.jpeg (unknown) |
| 27 |
https://i.imgsafe.org/5e/5e20754111.jpeg (find_css_set) |
| 28 |
|
| 29 |
The driver in question is the one named ProCapture. I am fairly certain |
| 30 |
this is the cause of the recent panics. |
| 31 |
|
| 32 |
I have had some issues with overclocking my system (both CPU and memory) |
| 33 |
but I do not think this is related. Just for good measure I reseated all |
| 34 |
my RAM modules. I am currently running 3.7 GHz (from 3.5) with memory |
| 35 |
overclocked to 2667 MHz. Does not seem to have an issue. |
| 36 |
|
| 37 |
Andrew |
Archives
