Nouveau - Jan 2014 - [Bug 73744] New: Constant lock ups with NVIDIA GeForce 8400 GS

https://bugs.freedesktop.org/show_bug.cgi?id=73744

          Priority: medium
            Bug ID: 73744
          Assignee: nouveau at lists.freedesktop.org
           Summary: Constant lock ups with NVIDIA GeForce 8400 GS
        QA Contact: xorg-team at lists.x.org
          Severity: blocker
    Classification: Unclassified
                OS: Linux (All)
          Reporter: grave_123 at riseup.net
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: Driver/nouveau
           Product: xorg

Hello,

I am currently using the non-free NVIDIA drivers with a GeForce 8400 GS. My
screen locks up whenever I use Nouveau to the point where I have to
hard-shutdown my machine. I can't afford hardware damage so I'm
temporarily
using the non-free drivers.

Anyway ...

I am not sure what specifically causes the lock ups. I can not get to an
emergency terminal to determine the cause in the moment either. At first,
everything but the mouse cursor and sound seizes up and then those two seize up
and there's excessive HDD activity. My only choice is to press and hold the
pwr
button and wait for it to shutdown.

I don't currently have a log file for the issue. I will switch back to
Nouveau
once I get a response of some kind. Haha.


OS: Ubuntu GNU/Linux x86-64 13.10
Linux: 3.11.0-15-generic
Graphics Card: NVIDIA GeForce 8400 GS
X.Org version: 1.14.5

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140117/7723e89a/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> ---
It'd be great to see a dmesg from an affected boot. One issue that has
recently
been identified is that some cards are missing a PCRYPT unit -- you can test
out this theory by booting with nouveau.config=PCRYPT=0

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140117/1ed4f084/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #2 from grave_123 at riseup.net ---
Thank you for your response and (Hopefully) continued response!

I will send a txt output of a dmesg later on today as well as try out that test
with PCRYPT and send a log of that output as well! :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140118/daad4773/attachment-0001.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #3 from grave_123 at riseup.net ---
Created attachment 92359
  --> https://bugs.freedesktop.org/attachment.cgi?id=92359&action=edit
dmesg_log

Here's the dmesg log when using Nouveau.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140118/9b5af291/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

Ilia Mirkin <imirkin at alum.mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Constant lock ups with      |[NVA8] Constant lock ups
                   |NVIDIA GeForce 8400 GS      |with NVIDIA GeForce 8400 GS

--- Comment #4 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Ah, interesting. This is a different 8400 GS than I thought (marketing names
are so misleading). That PCRYPT=0 thing will do nothing useful. But.... it
might still be the same issue I thought it might be, just not as visible in
kernel messages.

Can you grab a copy of envytools (https://github.com/envytools/envytools) build
it, and run

nvapeek 1540
nvapeek 154c

and report back with the results of those commands? (You can do this while on
blob drivers as well as nouveau, doesn't matter.) Additionally, try booting
with nouveau.config=PCE0=0 in the kernel cmdline and see if that fixes your
issues. (That should cause it to use M2MF instead of COPY for buffer copies.)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140118/e5584873/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #5 from grave_123 at riseup.net ---
Created attachment 92364
  --> https://bugs.freedesktop.org/attachment.cgi?id=92364&action=edit
nvapeek output with envytools

This is the output for nvapeek with the commands ran in the exact order posted.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140118/96a3c486/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> ---
OK, yeah, it's not at all the thing I thought it might be -- your PCOPY
engine
is intact:

$ lookup -a a8 1540 f2010001
PBUS.HWUNITS_0 => { TPC_MASK = 0x1 | PART_MASK = 0x1 | MP_MASK = 0x2 | UNK28
|
UNK29 | VDEC | UNK31 }
$ lookup -a a8 154c 0000023d
PBUS.HWUNITS_1 => { PCIE_VERSION = 2 | PCI_CLASS = DISPLAY | PDISPLAY | UNK3
0x3 | PVLD | PCIE_SPEED = 2P5GT | PCOPY }

So... it's something else. Sorry, that's of little help to you.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140118/a96eab73/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #7 from grave_123 at riseup.net ---
(In reply to comment #6)
> OK, yeah, it's not at all the thing I thought it might be -- your PCOPY
> engine is intact:
> 
> $ lookup -a a8 1540 f2010001
> PBUS.HWUNITS_0 => { TPC_MASK = 0x1 | PART_MASK = 0x1 | MP_MASK = 0x2 |
UNK28
> | UNK29 | VDEC | UNK31 }
> $ lookup -a a8 154c 0000023d
> PBUS.HWUNITS_1 => { PCIE_VERSION = 2 | PCI_CLASS = DISPLAY | PDISPLAY |
UNK3
> = 0x3 | PVLD | PCIE_SPEED = 2P5GT | PCOPY }
> 
> So... it's something else. Sorry, that's of little help to you.
Okay, so what do we do now? :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140118/3e2d836b/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #8 from Ilia Mirkin <imirkin at alum.mit.edu> ---
There was an issue that suggested that 3.10.x worked well for someone but they
started seeing issues with nva8 on 3.11. Perhaps you can try a 3.10.x kernel.
See bug #69029. If this turns out to help, then do a bisect to figure out the
offending commit.

Also it'd be interesting to see a log after the hang happens -- see if you
can
ssh into the machine after the screen hangs.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140128/05cdb906/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #9 from grave_123 at riseup.net ---
(In reply to comment #8)
> There was an issue that suggested that 3.10.x worked well for someone but
> they started seeing issues with nva8 on 3.11. Perhaps you can try a 3.10.x
> kernel. See bug #69029. If this turns out to help, then do a bisect to
> figure out the offending commit.
> 
> Also it'd be interesting to see a log after the hang happens -- see if
you
> can ssh into the machine after the screen hangs.
If I can SSH into the machine, what information would you want me to snag in
order to work further towards solving this issue? I have SSH set up right now.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140201/d5f82bbf/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #10 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to comment #9)
> If I can SSH into the machine, what information would you want me to snag
in
> order to work further towards solving this issue? I have SSH set up right
> now.
See if there's anything interesting dmesg I guess? It also would mean that
the
machine is fine, just the display has hung.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140201/dff895eb/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #11 from grave_123 at riseup.net ---
(In reply to comment #10)
> (In reply to comment #9)
> > If I can SSH into the machine, what information would you want me to
snag in
> > order to work further towards solving this issue? I have SSH set up
right
> > now.
> 
> See if there's anything interesting dmesg I guess? It also would mean
that
> the machine is fine, just the display has hung.
Alright I'll switch back to nouveau and report back when it happens! :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140202/9f9f6037/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #12 from grave_123 at riseup.net ---
Hey! The screen locked up and did something far worse than before. I was indeed
able to SSH into my machine and I tried to make a log for dmesg but it was
consumed by UFW output.

However ...

I did manage to cp all of my Xorg logs and found an interesting seg fault!
Attached the log file.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140208/fb62ea8f/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #13 from grave_123 at riseup.net ---
Created attachment 93667
  --> https://bugs.freedesktop.org/attachment.cgi?id=93667&action=edit
Log file with segfault in it

Not sure if this info for Xorg is helpful to the Nouveau folks but, shit,
it's
something.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140208/32ca9160/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #14 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to comment #13)
> Created attachment 93667 [details]
> Log file with segfault in it
> 
> Not sure if this info for Xorg is helpful to the Nouveau folks but, shit,
> it's something.
Nope, that's just a crash that happens when the GPU locks up. The DDX
isn't
very good at handling that.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140210/c62e7272/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #15 from grave_123 at riseup.net ---
Created attachment 93820
  --> https://bugs.freedesktop.org/attachment.cgi?id=93820&action=edit
dmesg from latest lock up

I think I got something good here! Here's the dmesg from the latest lock up.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140211/f0107f2d/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #16 from Ilia Mirkin <imirkin at alum.mit.edu> ---
The relevant bits:

TRAP_MP_EXEC - TP 0 MP 1: INVALID_OPCODE at 07fcc0 warp 0, opcode 0d0d0d0d
0d0d0d0d
 TRAP
ch 5 [0x003fc34000 compiz[2897]] subc 3 class 0x8597 mthd 0x0f04 data
0x3f800000
PGRAPH TLB flush idle timeout fail
PGRAPH_STATUS  : 0x00c00c03 BUSY DISPATCH CCACHE_UNK4 STRMOUT_GSCHED_UNK5 TPVP
MP
PGRAPH_VSTATUS0: 0x00000208 CCACHE UNK5
PGRAPH_VSTATUS1: 0x00005600
PGRAPH_VSTATUS2: 0x00000000
TRAP_MP_EXEC - TP 0 MP 1: TIMEOUT at 07fcc0 warp 0, opcode 0d0d0d0d 0d0d0d0d
 TRAP
ch 5 [0x003fc34000 compiz[2897]] subc 3 class 0x8597 mthd 0x0f04 data
0x3f800000
TRAP_MP_EXEC - TP 0 MP 1: TIMEOUT at 07fcc0 warp 0, opcode 0d0d0d0d 0d0d0d0d
 TRAP
ch 5 [0x003fc34000 compiz[2897]] subc 3 class 0x8597 mthd 0x0f04 data
0x3f800000
PGRAPH TLB flush idle timeout fail
PGRAPH_STATUS  : 0x00c00c03 BUSY DISPATCH CCACHE_UNK4 STRMOUT_GSCHED_UNK5 TPVP
MP
PGRAPH_VSTATUS0: 0x00000208 CCACHE UNK5
PGRAPH_VSTATUS1: 0x00005600
PGRAPH_VSTATUS2: 0x00000000
TRAP_MP_EXEC - TP 0 MP 1: TIMEOUT at 07fcc0 warp 0, opcode 0d0d0d0d 0d0d0d0d
 TRAP

So it looks like the code got overwritten with 0x0d (13) bytes. Never seen a
TIMEOUT error before -- neat. Not sure what to make of it though.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140211/5ccf5286/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #17 from grave_123 at riseup.net ---
(In reply to comment #16)
> The relevant bits:
> 
> TRAP_MP_EXEC - TP 0 MP 1: INVALID_OPCODE at 07fcc0 warp 0, opcode 0d0d0d0d
> 0d0d0d0d
>  TRAP
> ch 5 [0x003fc34000 compiz[2897]] subc 3 class 0x8597 mthd 0x0f04 data
> 0x3f800000
> PGRAPH TLB flush idle timeout fail
> PGRAPH_STATUS  : 0x00c00c03 BUSY DISPATCH CCACHE_UNK4 STRMOUT_GSCHED_UNK5
> TPVP MP
> PGRAPH_VSTATUS0: 0x00000208 CCACHE UNK5
> PGRAPH_VSTATUS1: 0x00005600
> PGRAPH_VSTATUS2: 0x00000000
> TRAP_MP_EXEC - TP 0 MP 1: TIMEOUT at 07fcc0 warp 0, opcode 0d0d0d0d
0d0d0d0d
>  TRAP
> ch 5 [0x003fc34000 compiz[2897]] subc 3 class 0x8597 mthd 0x0f04 data
> 0x3f800000
> TRAP_MP_EXEC - TP 0 MP 1: TIMEOUT at 07fcc0 warp 0, opcode 0d0d0d0d
0d0d0d0d
>  TRAP
> ch 5 [0x003fc34000 compiz[2897]] subc 3 class 0x8597 mthd 0x0f04 data
> 0x3f800000
> PGRAPH TLB flush idle timeout fail
> PGRAPH_STATUS  : 0x00c00c03 BUSY DISPATCH CCACHE_UNK4 STRMOUT_GSCHED_UNK5
> TPVP MP
> PGRAPH_VSTATUS0: 0x00000208 CCACHE UNK5
> PGRAPH_VSTATUS1: 0x00005600
> PGRAPH_VSTATUS2: 0x00000000
> TRAP_MP_EXEC - TP 0 MP 1: TIMEOUT at 07fcc0 warp 0, opcode 0d0d0d0d
0d0d0d0d
>  TRAP
> 
> So it looks like the code got overwritten with 0x0d (13) bytes. Never seen
a
> TIMEOUT error before -- neat. Not sure what to make of it though.
I hope this was a good chunk of info here. Thanks for the SSH idea by the way.
Saved a thrashing on my hardware! So what's up now? What's the plan? :))

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140211/67535513/attachment-0001.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

--- Comment #18 from grave_123 at riseup.net ---
Hey, I'm still getting this issue to this day with Ubuntu 14.04

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/nouveau/attachments/20140506/2eabdeb7/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=73744

Christopher M. Penalver <christopher.m.penalver at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #19 from Christopher M. Penalver <christopher.m.penalver at
gmail.com> ---
grave_123 at riseup.net, given you are using a downstream version of nouveau, it
will help immensely if you filed a new report with Ubuntu by ensuring you have
the package xdiagnose installed, and that you click the Yes button for
attaching additional debugging information running the following from a
terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160223/dfcd385c/attachment.html>