All of lore.kernel.org
 help / color / mirror / Atom feed
From: poma <pomidorabelisima-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Nouveau List <nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: Testers needed for NVAA/NVAC kernel patch
Date: Wed, 03 Dec 2014 16:56:17 +0100	[thread overview]
Message-ID: <547F32A1.8080102@gmail.com> (raw)
In-Reply-To: <20141202222923.GA32384@Normandy>

On 02.12.2014 23:29, Pierre Moreau wrote:
> Hello everyone,
> 
> I would need testers to check that this patch doesn't break working
> NVAA/NVAC configurations. It fixes an issue where some NVAC would hang on boot;
> if similar issues exist on NVAA, it may fix them too.
> You will find the patch below in two different versions: one will apply on Ben
> Skeggs' repository, the other one will apply on a regular Linux tree.
> 
> Thanks in advance,
> 
> Pierre Moreau
> 


git://people.freedesktop.org/~darktama/nouveau
commented the following "dumb" lines & patched with "If you are using Ben Skeggs' repository"

/NV/nouveau/drm/nouveau_gem.c: In function ‘validate_list’:
/NV/nouveau/drm/nouveau_gem.c:447:22: error: ‘struct drm_gem_object’ has no member named ‘dumb’
   WARN_ONCE(nvbo->gem.dumb,
                      ^
include/asm-generic/bug.h:121:27: note: in definition of macro ‘WARN_ONCE’
  int __ret_warn_once = !!(condition);   \
                           ^
/NV/nouveau/drm/nouveau_display.c: In function ‘nouveau_display_dumb_create’:
/NV/nouveau/drm/nouveau_display.c:879:9: error: ‘struct drm_gem_object’ has no member named ‘dumb’
  bo->gem.dumb = true;
         ^
/NV/nouveau/drm/nouveau_display.c: In function ‘nouveau_display_dumb_map_offset’:
/NV/nouveau/drm/nouveau_display.c:900:18: error: ‘struct drm_gem_object’ has no member named ‘dumb’
   WARN_ONCE(!(gem->dumb || gem->import_attach),
                  ^
include/asm-generic/bug.h:121:27: note: in definition of macro ‘WARN_ONCE’
  int __ret_warn_once = !!(condition);   \
                           ^
/NV/nouveau/drm/nouveau_display.c: In function ‘nouveau_display_dumb_create’:
/NV/nouveau/drm/nouveau_display.c:879:9: error: ‘struct drm_gem_object’ has no member named ‘dumb’
  bo->gem.dumb = true;
         ^

# dmesg | grep nouveau
[   25.348109] nouveau: module verification failed: signature and/or  required key missing - tainting kernel
[   25.392337] fb: switching to nouveaufb from VESA VGA
[   25.410386] nouveau  [  DEVICE][0000:01:00.0] BOOT0  : 0x0ace80b1
[   25.410408] nouveau  [  DEVICE][0000:01:00.0] Chipset: MCP79/MCP7A (NVAC)
[   25.410419] nouveau  [  DEVICE][0000:01:00.0] Family : NV50
[   25.426804] nouveau  [   VBIOS][0000:01:00.0] using image from PRAMIN
[   25.427343] nouveau  [   VBIOS][0000:01:00.0] BIT signature found
[   25.427361] nouveau  [   VBIOS][0000:01:00.0] version 62.79.78.00.00
[   25.450604] nouveau 0000:01:00.0: irq 26 for MSI/MSI-X
[   25.450635] nouveau  [     PMC][0000:01:00.0] MSI interrupts enabled
[   25.450698] nouveau  [     PFB][0000:01:00.0] RAM type: stolen system memory
[   25.450710] nouveau  [     PFB][0000:01:00.0] RAM size: 256 MiB
[   25.450719] nouveau  [     PFB][0000:01:00.0]    ZCOMP: 0 tags
[   25.482512] nouveau  [  PTHERM][0000:01:00.0] FAN control: none / external
[   25.482581] nouveau  [  PTHERM][0000:01:00.0] fan management: automatic
[   25.482602] nouveau  [  PTHERM][0000:01:00.0] internal sensor: yes
[   25.502658] nouveau  [     CLK][0000:01:00.0] 03: core 200 MHz shader 400 MHz vdec 200 MHz
[   25.502684] nouveau  [     CLK][0000:01:00.0] 05: core 300 MHz shader 600 MHz vdec 300 MHz
[   25.502701] nouveau  [     CLK][0000:01:00.0] 07: core 350 MHz shader 800 MHz vdec 350 MHz
[   25.502717] nouveau  [     CLK][0000:01:00.0] 0f: core 450 MHz shader 1100 MHz vdec 450 MHz
[   25.502753] nouveau  [     CLK][0000:01:00.0] --: core 450 MHz shader 1100 MHz vdec 450 MHz
[   25.503536] nouveau  [     DRM] VRAM: 256 MiB
[   25.503550] nouveau  [     DRM] GART: 1048576 MiB
[   25.503570] nouveau  [     DRM] TMDS table version 2.0
[   25.503584] nouveau  [     DRM] DCB version 4.0
[   25.503599] nouveau  [     DRM] DCB outp 00: 02000300 0000001e
[   25.503616] nouveau  [     DRM] DCB outp 01: 01011322 00000030
[   25.503631] nouveau  [     DRM] DCB outp 02: 02022332 00020010
[   25.503645] nouveau  [     DRM] DCB conn 00: 00000000
[   25.503659] nouveau  [     DRM] DCB conn 01: 00001131
[   25.503672] nouveau  [     DRM] DCB conn 02: 00002261
[   25.548615] nouveau  [     DRM] MM: using M2MF for buffer copies
[   25.637542] nouveau  [     DRM] allocated 800x600 fb: 0x50000, bo ffff8800bc6d3c00
[   25.637949] fbcon: nouveaufb (fb0) is primary device
[   25.705760] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[   25.705791] [drm] Initialized nouveau 1.2.1 20120801 for 0000:01:00.0 on minor 1

# grep -w connected /var/log/Xorg.0.log
[    34.783] (II) NOUVEAU(0): Output HDMI-1 connected

# modinfo nouveau -n
/lib/modules/3.18.0-0.rc7.git0.1.fc22.x86_64/updates/nouveau.ko


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

      reply	other threads:[~2014-12-03 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 22:29 Testers needed for NVAA/NVAC kernel patch Pierre Moreau
2014-12-03 15:56 ` poma [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=547F32A1.8080102@gmail.com \
    --to=pomidorabelisima-re5jqeeqqe8avxtiumwx3w@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.