From: "Émeric Maschino" <emeric.maschino@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be
Date: Tue, 02 Feb 2010 21:05:10 +0000 [thread overview]
Message-ID: <d72eeaf61002021305m3a56c813o7cf8661753a9a635@mail.gmail.com> (raw)
In-Reply-To: <d72eeaf61001041440s58b51b9j58e62af378b55224@mail.gmail.com>
> Simply reverting commit f1a2a9b6189f9f5c27672d4d32fec9492c6486b2 from
> kernel 2.6.33-rc4 makes the problem go away. But I bet this is not the
> right way to fix it ;-)
>
> Is there something else I can try?
I've been asked at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bugT6655#51 to file a
bug report to track this issue. Here's the link:
http://bugzilla.kernel.org/show_bug.cgi?id\x15212
Émeric
prev parent reply other threads:[~2010-02-02 21:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 22:40 [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-04 23:50 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-07 23:02 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-07 23:57 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-08 20:06 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-08 23:55 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-09 11:46 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-11 17:54 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-11 18:23 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Luck, Tony
2010-01-11 18:35 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-11 21:18 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-11 21:40 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-13 7:15 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-13 17:13 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-14 0:10 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this Dave Airlie
2010-01-14 8:50 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-14 8:54 ` Émeric Maschino
2010-01-18 15:44 ` Émeric Maschino
2010-01-22 22:19 ` Émeric Maschino
2010-02-02 21:05 ` Émeric Maschino [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=d72eeaf61002021305m3a56c813o7cf8661753a9a635@mail.gmail.com \
--to=emeric.maschino@gmail.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox