All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Jerry Cooperstein
	<coop-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Cc: "nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	"dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: drm/nouveau contiguous bo check produces lots of output
Date: Mon, 11 Nov 2013 16:57:48 +0100	[thread overview]
Message-ID: <5280FE7C.3030704@canonical.com> (raw)
In-Reply-To: <5280F855.1020900-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>

op 11-11-13 16:31, Jerry Cooperstein schreef:
> Hi:
>
> commit bd9c5a2016307164c419c5e24a46921c10e620a0
>
> (drm/nouveau: require contiguous bo for framebuffer)
> produces about 2000 lines of
>
> nouveau E[     DRM] framebuffer requires contiguous bo
>
> on system boot and more on shutdown, but I don't see other
> negative effects.  I tried deploying a trivial patch removing the check and saw
> no other problems.
>
> Is this a problem you have heard about?
>
> My hardware is an NVIDIA Geoforce G98 (8400 GS), lspci -v gives:
>
> 01:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS] (rev a1) (prog-if 00 [VGA controller])
>     Subsystem: ASUSTeK Computer Inc. Device 8278
>     Flags: bus master, fast devsel, latency 0, IRQ 16
>     Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
>     Memory at d0000000 (64-bit, prefetchable) [size=256M]
>     Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
>     I/O ports at cc00 [size=128]
>     Expansion ROM at fe9e0000 [disabled] [size=128K]
>     Capabilities: [60] Power Management version 3
>     Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
>     Capabilities: [78] Express Endpoint, MSI 00
>     Capabilities: [100] Virtual Channel
>     Capabilities: [128] Power Budgeting <?>
>     Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
>     Kernel driver in use: nouveau
>     Kernel modules: nouveau
>
> This appeared in the 3.12 rc kernels and is in 3.12.0
>
> If there is anything I can do to help you debug this please let me know.
> I don't understand the drm code well enough to dive in deep on my own.
It's a paranoia patch and any bo should not be created with NOUVEAU_GEM_TILE_NONCONTIG flag.
Even if it happens to work it will fail on any sufficiently fragmented vram.

What driver versions do you use?

~Maarten

       reply	other threads:[~2013-11-11 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5280F855.1020900@linuxfoundation.org>
     [not found] ` <5280F855.1020900-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
2013-11-11 15:57   ` Maarten Lankhorst [this message]
2013-11-11 16:05     ` drm/nouveau contiguous bo check produces lots of output Jerry Cooperstein
     [not found]       ` <52810037.9010509-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
2013-11-11 16:52         ` Maarten Lankhorst

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=5280FE7C.3030704@canonical.com \
    --to=maarten.lankhorst-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
    --cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=coop-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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.