From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 14941] New: ioremap leak in DRM
Date: Mon, 10 Mar 2008 11:15:36 -0700 (PDT) [thread overview]
Message-ID: <bug-14941-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=14941
Summary: ioremap leak in DRM
Product: xorg
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: pq-X3B1VOXEql0@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Nouveau is leaking one ioremap per X start. Apparently it is the kernel fifo,
since it always mapped from the beginning of VRAM, and has size 0x8000 or 32kB.
My hardware is NV20 (gf3). DRM and DDX from git around 9th March.
I found this while mmiotracing nouveau. I start the trace, load drm.ko and
nouveau.ko, start X three times in a row, unload nouveau.ko and drm.ko. Now
when I stop mmiotracing, it reports three non-unmapped io-mappings as described
above.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2008-03-10 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 18:15 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-14941-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-03-10 18:26 ` [Bug 14941] ioremap leak in DRM bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-10 19:24 ` [Bug 14941] ioremap leak/oddity " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-10 20:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-10 20:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-10 22:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-03-12 22:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-03-25 3:06 ` 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-14941-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.