On 11/03/2013 13:38, Konrad Rzeszutek Wilk wrote: >> With that I am still getting the issues (even with an insance delay of 100 >> seconds). >> Here is the serial log with various runs. > Any thoughts? Sorry for taking so long to answer but I got a one-week flu and still had to do my research duties :s
Anyway, as a matter of fact, I do have some thoughts. If you don't mind, the tests I would like you to make will be listed at the end of the message. >> [ 13.523878] initcall init_sg+0x0/0x1000 [sg] returned 0 after 5355 usecs >> ^G^G[ 13.621376] nouveau [ PTHERM][0000:00:0d.0] programmed thresholds [ >> 90(2), 95(3), 145(2), 135(5) ] >> [ 13.630487] nouveau 39079] nouveau [ PTHERM][0000:00:0d.0] Thermal >> management: automatic >> [ 13.646028] nouveau [ PTHERM][0000:00:0d.0] temperature (218 C) hit the >> 'downclock' threshold >> [ 13.654702] nouveau [ PTHERM][0000:00:0d.0] temperature (218 C) hit the >> 'critical' threshold >> [ 13.663296] nouveau [ PTHERM][0000:00:0d.0] temperature (218 C) hit the >> 'shutdown' threshold >> [ 13.671992] [TTM] Zone kernel: Available graphics memory: 1963774 kiB > Perhaps I've some insanely stupid BIOS? So, first of all, I indeed would like to see your vbios and I also would like to know the bitfield of some regs. The easiest way to do both is to grab and compile the envytools[0]. To grab your vbios, please do the following: nvagetbios > nv4c_vbios.rom To get the bitfield of the thermal-related regs: nvascan 15b0 10 > nv4c_therm_scan Please send me both of these files and I'll see what I can do. Sorry again for the very late answer (I'm slowly getting better). Martin [0] https://github.com/pathscale/envytools
