All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 88415] New: [NVA8] nouveau GPU lockup when reclocking
Date: Wed, 14 Jan 2015 18:06:35 +0000	[thread overview]
Message-ID: <bug-88415-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4511 bytes --]

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

            Bug ID: 88415
           Summary: [NVA8] nouveau GPU lockup when reclocking
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: benedikt.morbach-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 112240
  --> https://bugs.freedesktop.org/attachment.cgi?id=112240&action=edit
full dmesg

kernel: 3.19-rc4
hardware: Thinkpad T510, Quadro NVS 3100M
full dmesg attached, nouveau parts below

What I did:
 1. downclocking before starting X
    -> '[0000:01:00.0] invalid/missing rammap entry' in dmesg

 2. start X
    -> working fine (could run glxgears, didn't try much else)

 3. returning to default performance level
    -> fine

 4. downclocking again
    -> lockup, broke it with sysrq and saved dmesg

Any other logs I should produce?
Do you want a more verbose dmesg?

dmesg | grep nouveau:
[   24.080412] nouveau  [  DEVICE][0000:01:00.0] BOOT0  : 0x0a8600a2
[   24.080417] nouveau  [  DEVICE][0000:01:00.0] Chipset: GT218 (NVA8)
[   24.080420] nouveau  [  DEVICE][0000:01:00.0] Family : NV50
[   24.112811] nouveau  [   VBIOS][0000:01:00.0] using image from PRAMIN
[   24.113012] nouveau  [   VBIOS][0000:01:00.0] BIT signature found
[   24.113016] nouveau  [   VBIOS][0000:01:00.0] version 70.18.45.00.09
[   24.114500] nouveau  [     PMC][0000:01:00.0] MSI interrupts enabled
[   24.114546] nouveau  [     PFB][0000:01:00.0] RAM type: DDR3
[   24.114549] nouveau  [     PFB][0000:01:00.0] RAM size: 512 MiB
[   24.114551] nouveau  [     PFB][0000:01:00.0]    ZCOMP: 960 tags
[   24.117885] nouveau  [    VOLT][0000:01:00.0] GPU voltage: 850000uv
[   24.147955] nouveau  [  PTHERM][0000:01:00.0] FAN control: none / external
[   24.147972] nouveau  [  PTHERM][0000:01:00.0] fan management: automatic
[   24.147978] nouveau  [  PTHERM][0000:01:00.0] internal sensor: yes
[   24.168063] nouveau  [     CLK][0000:01:00.0] 03: core 135 MHz shader 270
MHz memory 135 MHz
[   24.168070] nouveau  [     CLK][0000:01:00.0] 07: core 405 MHz shader 810
MHz memory 405 MHz
[   24.168074] nouveau  [     CLK][0000:01:00.0] 0f: core 606 MHz shader 1468
MHz memory 790 MHz
[   24.168117] nouveau  [     CLK][0000:01:00.0] --: core 405 MHz shader 810
MHz memory 405 MHz
[   24.168493] nouveau  [     DRM] VRAM: 512 MiB
[   24.168495] nouveau  [     DRM] GART: 1048576 MiB
[   24.168499] nouveau  [     DRM] TMDS table version 2.0
[   24.168501] nouveau  [     DRM] DCB version 4.0
[   24.168504] nouveau  [     DRM] DCB outp 00: 01800323 00010034
[   24.168506] nouveau  [     DRM] DCB outp 01: 02811300 00000000
[   24.168508] nouveau  [     DRM] DCB outp 02: 028223a6 0f220010
[   24.168510] nouveau  [     DRM] DCB outp 03: 02822362 00020010
[   24.168511] nouveau  [     DRM] DCB outp 04: 048333b6 0f220010
[   24.168513] nouveau  [     DRM] DCB outp 05: 04833372 00020010
[   24.168515] nouveau  [     DRM] DCB outp 06: 088443c6 0f220010
[   24.168517] nouveau  [     DRM] DCB outp 07: 08844382 00020010
[   24.168519] nouveau  [     DRM] DCB conn 00: 00000040
[   24.168521] nouveau  [     DRM] DCB conn 01: 00000100
[   24.168523] nouveau  [     DRM] DCB conn 02: 00101246
[   24.168524] nouveau  [     DRM] DCB conn 03: 00202346
[   24.168526] nouveau  [     DRM] DCB conn 04: 00410446
[   24.236201] nouveau  [     DRM] MM: using COPY for buffer copies
[   25.443491] nouveau  [     DRM] allocated 1600x900 fb: 0x70000, bo
ffff8800b8decc00
[   25.443614] fbcon: nouveaufb (fb0) is primary device
[   25.763829] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[   25.763831] nouveau 0000:01:00.0: registered panic notifier
[   25.766694] [drm] Initialized nouveau 1.2.1 20120801 for 0000:01:00.0 on
minor 0
[  107.585436] nouveau E[     PFB][0000:01:00.0] invalid/missing rammap entry
[  612.287829] nouveau E[     DRM] GPU lockup - switching to software fbcon
[  626.123229] nouveau E[  X[907]] failed to idle channel 0xcccc0000 [X[907]]
[  641.123107] nouveau E[  X[907]] failed to idle channel 0xcccc0000 [X[907]]
[  643.129470] nouveau E[   PFIFO][0000:01:00.0] channel 6 [X[907]] unload
timeout

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 5848 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2015-01-14 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 18:06 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-88415-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-01-14 18:09   ` [Bug 88415] [NVA8] nouveau GPU lockup when reclocking bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-14 18:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-14 18:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-14 18:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-88415-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.