Sending the revert patch to Dave after receiving his green light for
this, and will investigate the issue on my side. I should be able to find a
gk107 somewhere...
On Wed, Aug 12, 2015 at 12:35 PM, Alexandre Courbot gnu...@gmail.com wrote:
Mmm in that case it is probably best to revert that
Hi,
I think I've done about 10 reboots with the commit reverted and I never
experienced the crash. But with 4.2.0-rc6 I get the crash on about every
other reboot.
Probably relevant: the computer on which the crash occurs has two GPUs (one
Intel and one Nvidia). The Intel one is actually being
I'm guessing that optimus is the operative difference, not the
specific chip. Basically something that can be put to sleep via
ACPI...
On Tue, Aug 11, 2015 at 11:53 PM, Alexandre Courbot gnu...@gmail.com wrote:
Sending the revert patch to Dave after receiving his green light for
this, and will
Right, that 0xbad0da00 is indicative of something being offline that
should not be at that time. I have sent the revert patch. Thanks Eric
for reporting this!
On Wed, Aug 12, 2015 at 1:00 PM, Ilia Mirkin imir...@alum.mit.edu wrote:
I'm guessing that optimus is the operative difference, not the
Mmm in that case it is probably best to revert that commit for the
time being. It was targeting GM20B (and maybe other Maxwells too) so
reverting it should not hurt anyone at the moment. I think Ben is on
holidays for now, is there anyone else who can send a pull request to
Dave Airlie for this?
Indeed, and I am actually surprised to see one here. I will
double-check that patch.
Eric, would you be able to give an estimate of the repro rate for this
issue? More testing with and without the patch would be welcome, it'd
be good to know whether it is actually the culprit or not.
On Mon, Aug
Hi,
I am testing Linux v4.2-rc5 and I am sporadically getting crashes shortly after
startup in gk104_fifo_intr_runlist(). What I've found is that the 'mask' value
read from offset 0x2a00 comes back as '0xbad0da00'. This causes the 'engn'
variable to be assigned the value 9, which is invalid;
Alexandre, could you take a look? 0xbad* generally comes from bad mmio
reads.
On Aug 9, 2015 1:08 PM, Eric Biggers ebigge...@gmail.com wrote:
Hi,
I am testing Linux v4.2-rc5 and I am sporadically getting crashes shortly
after
startup in gk104_fifo_intr_runlist(). What I've found is that the
