mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, David.Woodhouse@intel.com,
	dwmw2@infradead.org, eric@anholt.net, ben@decadent.org.uk,
	gregkh@suse.de
Subject: Re: [PATCH] intel-agp.c: Fix crash when accessing nonexistent GTT  entries in i915
Date: Sun, 21 Mar 2010 16:30:20 +0100	[thread overview]
Message-ID: <ca2dc2821003210830h2025df79r477cca7d81ddd28d@mail.gmail.com> (raw)
In-Reply-To: <20100321135836.GA11661@zhen-devel.sh.intel.com>

On Sun, Mar 21, 2010 at 2:58 PM, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> On 2010.03.20 14:04:56 +0100, Miguel Ojeda wrote:
>> On Fri, Mar 19, 2010 at 9:27 PM, Andrew Morton
>> <akpm@linux-foundation.org> wrote:
>> > On Thu, 11 Mar 2010 16:54:26 +0100
>> > Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
>> >
>> >> Attached dmesg, lspci -vv, config and xorg.
>> >>
>> >> When the X server crashes, the kernel does not report anything
>> >
>> > This seems to have gone all quiet?
>>
>> It seems so, I was about to ping Zhenyu.
>
> Could you try recent X.org intel driver release? Your failure X log
> showed some pretty old UMS driver's render flush time out message,
> I think whose version never has been well tested with new kms/gem stuff.
>

Sure. Debian Stable got version 2.3.

>>
>> >
>> > As this was a 2.6.32->2.6.32.4 regression, I assume that it's also a
>> > 2.6.32->2.6.33 regression?
>>
>> Yep. All kernels I tested since 2.6.32.4 crash, including 2.6.32.10,
>> 2.6.33 and 2.6.34-rc1. See my original message for more details about
>> the crash.
>>
>
> Could you bisect? I doubt it's caused by David's patch, as if it is, you
> will have trouble at early agp init time, instead of current problem looks
> like something causing rendering hang..and I can't think of how mapping GTT
> to a scratch page could cause problem in case GTT bar is truely 256K.

I bisected in order to find the commit 5877960869333e42ebeb733e8d9d5630ff96d350.

I don't know if such commit is really the true problem (does not seem
so if you are right); however, it is the commit that breaks the X
server as I stated in the original message.

>
> --
> Open Source Technology Center, Intel ltd.
>
> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAkumJgwACgkQsQQaM014GCe2cgCbB8LJnqn7n7J++lA8Pd+TfBQb
> 2BQAn2sYv0DZuSniLTcf9F3cX+cGIgVl
> =gQHY
> -----END PGP SIGNATURE-----
>
>

  reply	other threads:[~2010-03-21 15:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 22:09 Miguel Ojeda
2010-03-11  7:31 ` Miguel Ojeda
2010-03-11  8:34   ` Zhenyu Wang
2010-03-11 15:54     ` Miguel Ojeda
2010-03-19 20:27       ` Andrew Morton
2010-03-20 13:04         ` Miguel Ojeda
2010-03-21 13:58           ` Zhenyu Wang
2010-03-21 15:30             ` Miguel Ojeda [this message]
2010-03-23  0:57               ` Andrew Morton
2010-03-23  4:14                 ` Christian Kujau
2010-03-23 11:40                   ` Miguel Ojeda
2010-03-24 18:14                     ` Andrew Morton
2010-03-24 19:07                       ` Miguel Ojeda
2010-03-25 16:55                       ` Miguel Ojeda
2010-04-27 17:57                         ` Andrew Morton
2010-04-27 20:06                           ` Miguel Ojeda
2010-04-27 20:26                             ` Andrew Morton
2010-04-27 21:07                               ` Miguel Ojeda
2010-03-23 10:02                 ` Miguel Ojeda
2010-04-28  7:49       ` Dave Airlie

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=ca2dc2821003210830h2025df79r477cca7d81ddd28d@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=David.Woodhouse@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=ben@decadent.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=eric@anholt.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhenyuw@linux.intel.com \
    /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

all inboxes | Powered by JetHome®