From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related?
Date: Wed, 13 Jan 2010 17:13:42 +0000 [thread overview]
Message-ID: <201001131013.43005.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <d72eeaf61001041440s58b51b9j58e62af378b55224@mail.gmail.com>
On Wednesday 13 January 2010 12:15:00 am Émeric Maschino wrote:
> 2010/1/11 Bjorn Helgaas <bjorn.helgaas@hp.com>:
> > Right? I'm a bit confused because that should have been what you were
> > testing here: http://marc.info/?l=linux-ia64&m\x126290536216298&w=2,
> > unless you applied the patch by hand and made a mistake.
>
> I've probably incorrectly applied your patches without restarting from
> the original file at each attempt. Anyway, it's fine now, thanks.
>
> > I'm afraid I won't be much help with the DRM issue below. I think
> > you'll have better luck with the dri-devel people now. If this is
> > a regression and you can identify an old working kernel, that might
> > help.
>
> I've performed regression tests. The problem appears with kernel
> 2.6.30. Last working kernel is 2.6.29.6. I'm not a kernel developer,
> but could this be due to this commit
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h•5b12def42e83287c1bdb1411d99451753c1391?
Nice work identifying working and non-working versions!
I don't know how much time and energy you want to devote to this, but
I think there are two ways we can make progress:
1) Try to convince DRM folks to help debug this.
2) Use git bisect[1] between v2.6.29 and v2.6.30. This looks like
about 13 kernel rebuild/test cycles. I don't see the stable
releases like 2.6.29.6 in the git repo, but you won't lose much
by starting with 2.6.29.
[1] http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
Bjorn
next prev parent reply other threads:[~2010-01-13 17:13 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 ` Bjorn Helgaas [this message]
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
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=201001131013.43005.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.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