From: Frederic Weisbecker <fweisbec@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915,agp/intel: Do not clear stolen entries
Date: Sun, 23 Jan 2011 02:12:23 +0100 [thread overview]
Message-ID: <20110123011221.GB1805@nowhere> (raw)
In-Reply-To: <1295607537-877-1-git-send-email-chris@chris-wilson.co.uk>
On Fri, Jan 21, 2011 at 10:58:57AM +0000, Chris Wilson wrote:
> We can only utilize the stolen portion of the GTT if we are in sole
> charge of the hardware. This is only true if using GEM and KMS,
> otherwise VESA continues to access stolen memory.
>
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Reported-by: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
Applied on top of -rc2, it crashes the kernel early on
boot with an unhandle page request.
I don't have a serial line and it's too early for netconsole,
so I wrote the stacktrace I saw with printk delayed.
i830_write_entry
intel_gtt_clar_range
intel_fake_agp_insert_entries
agp_bind_memory
?agp_generic_alloc_pages
?intelfb_pci_register
?raw_spin_unlock_irqrestore
?local_pci_probe
?pci_device_probe
?driver_probe_device
?__driver_attach
?bus_for_each_dev
?driver_attach
?__driver_attach
?bus_add_driver
?pci_device_remove
?driver_register
?raw_spin_lock_init
?pci_register_driver
?intelfb_init
?do_one_initcall
?radix_tree_lookup
?irq_to_desc
?intelfb_init
?kernel_init
Given the ip (c12ccf12) it must be:
c12ccef0 <i830_write_entry>:
c12ccef0: 55 push %ebp
c12ccef1: 81 f9 01 00 01 00 cmp $0x10001,%ecx
c12ccef7: 89 e5 mov %esp,%ebp
c12ccef9: b9 01 00 00 00 mov $0x1,%ecx
c12ccefe: 53 push %ebx
c12cceff: bb 07 00 00 00 mov $0x7,%ebx
c12ccf04: 0f 45 d9 cmovne %ecx,%ebx
c12ccf07: 09 c3 or %eax,%ebx
c12ccf09: c1 e2 02 shl $0x2,%edx
c12ccf0c: 03 15 8c 5e d5 c1 add 0xc1d55e8c,%edx
c12ccf12: 89 1a mov %ebx,(%edx) <--- here
c12ccf14: 5b pop %ebx
c12ccf15: 5d pop %ebp
c12ccf16: c3 ret
c12ccf17: 89 f6 mov %esi,%esi
c12ccf19: 8d bc 27 00 00 00 00 lea 0x0(%edi,%eiz,1),%edi
So, it seems to be the actual writel() that faults.
next prev parent reply other threads:[~2011-01-23 1:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 18:12 [BISECTED] agp/intel: revert "Remove confusion of stolen entries not stolen memory" Arnd Bergmann
2010-12-20 18:53 ` Chris Wilson
2010-12-20 19:47 ` Arnd Bergmann
2010-12-20 19:52 ` Chris Wilson
2010-12-20 20:52 ` Arnd Bergmann
2010-12-20 21:06 ` Chris Wilson
2010-12-20 21:54 ` Arnd Bergmann
2010-12-20 22:08 ` Dave Airlie
2011-01-20 23:24 ` Frederic Weisbecker
2011-01-21 10:58 ` [PATCH] drm/i915,agp/intel: Do not clear stolen entries Chris Wilson
2011-01-21 16:26 ` Jiri Olsa
2011-01-23 1:12 ` Frederic Weisbecker [this message]
2011-01-23 11:01 ` Chris Wilson
2011-01-23 17:59 ` Frederic Weisbecker
2011-01-24 7:40 ` Hugh Dickins
2011-01-24 10:10 ` Chris Wilson
2011-01-26 21:39 ` Arnd Bergmann
2011-01-28 22:00 ` Hugh Dickins
2011-01-29 2:59 ` Mario Kleiner
2011-01-30 0:28 ` Hugh Dickins
2011-01-30 4:13 ` Mario Kleiner
2011-01-30 9:55 ` Chris Wilson
2011-01-31 10:57 ` [PATCH] drm/i915: Suppress spurious vblank interrupts Chris Wilson
2011-02-01 17:34 ` Hugh Dickins
2011-02-01 17:46 ` Chris Wilson
2011-02-01 17:46 ` Jesse Barnes
2011-02-01 18:08 ` Jesse Barnes
2011-02-01 18:46 ` Hugh Dickins
2011-02-01 19:32 ` Jesse Barnes
2011-02-02 3:37 ` Hugh Dickins
2011-02-02 17:18 ` Jesse Barnes
2011-02-08 19:52 ` Hugh Dickins
2011-02-10 10:16 ` [PATCH] drm/i915/tv: Use polling rather than interrupt-based hotplug Chris Wilson
2011-02-11 6:34 ` Hugh Dickins
2011-02-11 18:21 ` [PATCH] drm/i915: Suppress spurious vblank interrupts Mario Kleiner
2011-02-14 17:41 ` Hugh Dickins
2011-06-18 4:40 ` Hugh Dickins
2011-01-30 8:52 ` [PATCH] drm/i915,agp/intel: Do not clear stolen entries Chris Clayton
2011-01-21 16:05 ` [BISECTED] agp/intel: revert "Remove confusion of stolen entries not stolen memory" Jiri Olsa
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=20110123011221.GB1805@nowhere \
--to=fweisbec@gmail.com \
--cc=arnd@arndb.de \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kernel@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