Comment 70 for bug 1158689

Hello again, Ilia,

> Can you grab envytools (https://github.com/envytools/envytools) and run

bad news (or maybe expected from what we have been seeing earlier):

[aloew@aloew-lap envytools-master]$ ./nva/nvapeek 10200c
WARN: Can't probe 0000:01:00.0
PCI init failure!

[aloew@aloew-lap envytools-master]$ ./nva/nvapoke 10200c 10
WARN: Can't probe 0000:01:00.0
PCI init failure!

> and see what's in dmesg?

No additional output in dmesg - probably because of the "PCI init failure"...

> Do you see additional MMIO read/write failures, or is it
> all good? What does the peek return? (I'm wondering if it's an initialization
> order issue or something.)

As above - and additionally, during the boot process, I also see the following messages in dmesg:

nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000000 FAULT at 0x00fd94
nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000000 FAULT at 0x103d94
(...)
nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000010 FAULT at 0x10200c

> What issues are you seeing with the blob driver?

As stated earlier: Every more recent version of NVidia's driver after their 295.09 causes unpredictable complete hangs at some point in time - sooner or later, but consistently (especially on GUI actions that initiate screen changes like closing windows or using the scrollbar). Fan runs at 100% and the only thing I can still do is a hard power-off...

> I'd also still be interested in knowing whether a previously-known-good
> version of the blob still works.

I am 99.9% certain it does, as my Windows install with NVidia 285.09 driver also still runs fine, while any more recent Windows driver from NVidia hangs with the same symptoms as their Linux "blob" - I had just checked this last week with their latest Windows version 331.82, once again without any luck.

Will try to do a new install of old RHEL 6.1 or 6.2 onto a USB HDD either later today or tomorrow night and report back about this.

Is there anything else that we can try to find out why the above memory addresses seemingly cannot be accessed on my card?

Could this be a motherboard layout issue by Toshiba or some defective chips that NVidia has sold anyway to OEM manufacturers?

Maybe indeed you could ask your new friends/contacts at NVidia about this?

And please let me know if I shall check some other commands using the "envytools" (nice name!)...

Many thanks one more time & best regards,
Andreas