From: Martin Peres <martin.peres@free.fr>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: airlied@linux.ie, bskeggs@redhat.com, marcin.slusarz@gmail.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: nouveau shuts the machine down with v3.9-rc1 (temperature (72 C) hit the 'shutdown' threshold).
Date: Tue, 12 Mar 2013 00:00:39 +0100 [thread overview]
Message-ID: <513E6217.2020309@free.fr> (raw)
In-Reply-To: <20130311123835.GA23154@phenom.dumpdata.com>
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
prev parent reply other threads:[~2013-03-11 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 18:40 nouveau shuts the machine down with v3.9-rc1 (temperature (72 C) hit the 'shutdown' threshold) Konrad Rzeszutek Wilk
2013-03-04 19:21 ` Martin Peres
2013-03-04 21:41 ` Konrad Rzeszutek Wilk
[not found] ` <5135D375.9060006@free.fr>
[not found] ` <20130305154404.GA15271@phenom.dumpdata.com>
2013-03-11 12:38 ` Konrad Rzeszutek Wilk
2013-03-11 23:00 ` Martin Peres [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=513E6217.2020309@free.fr \
--to=martin.peres@free.fr \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox