From: Mike Galbraith <efault@gmx.de>
To: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [drm:qxl] BUG: sleeping function called from invalid context - qxl_bo_kmap_atomic_page()...splat
Date: Thu, 11 May 2017 19:24:03 +0200 [thread overview]
Message-ID: <1494523443.25131.12.camel@gmx.de> (raw)
In-Reply-To: <1494297462.20252.9.camel@gmx.de>
On Tue, 2017-05-09 at 04:37 +0200, Mike Galbraith wrote:
> On Mon, 2017-05-08 at 16:48 -0300, Gabriel Krisman Bertazi wrote:
>
> > Thanks for reporting this. Can you confirm the following patch prevents
> > the issue?
>
> Nope, it still gripes.
The reason for this gripe is that we find that we don't have memory
reserved.. a tad too late.
Xorg-2252 [000] .... 135.409756: qxl_release_map <-qxl_cursor_atomic_update
Xorg-2252 [000] .... 135.409756: qxl_bo_kmap_atomic_page <-qxl_release_map
Xorg-2252 [000] .... 135.409757: qxl_bo_kmap_atomic_page: ENTER
Xorg-2252 [000] .... 135.409757: ttm_mem_io_lock <-qxl_bo_kmap_atomic_page
Xorg-2252 [000] .... 135.409757: ttm_mem_io_reserve <-qxl_bo_kmap_atomic_page
Xorg-2252 [000] .... 135.409757: qxl_ttm_io_mem_reserve <-ttm_mem_io_reserve
Xorg-2252 [000] .... 135.409757: ttm_mem_io_unlock <-qxl_bo_kmap_atomic_page
Xorg-2252 [000] .... 135.409757: qxl_bo_kmap_atomic_page: PREEMPTION DISABLED
Xorg-2252 [000] ...1 135.409758: qxl_bo_kmap <-qxl_cursor_atomic_update
Xorg-2252 [000] ...1 135.409758: ttm_bo_kmap <-qxl_bo_kmap <== too late
Xorg-2252 [000] ...1 135.409758: ttm_mem_io_reserve <-ttm_bo_kmap
Xorg-2252 [000] ...1 135.409758: qxl_ttm_io_mem_reserve <-ttm_mem_io_reserve
Xorg-2252 [000] ...1 135.409759: ioremap_nocache <-ttm_bo_kmap <== game over
Xorg-2252 [000] ...1 135.409759: __ioremap_caller <-ioremap_nocache
Xorg-2252 [000] ...1 135.409759: walk_system_ram_range <-__ioremap_caller
Xorg-2252 [000] ...1 135.409759: find_next_iomem_res <-walk_system_ram_range
Xorg-2252 [000] ...1 135.409759: _raw_read_lock <-find_next_iomem_res
Xorg-2252 [000] ...1 135.409760: reserve_memtype <-__ioremap_caller
Xorg-2252 [000] ...1 135.409760: pat_pagerange_is_ram <-reserve_memtype
Xorg-2252 [000] ...1 135.409761: walk_system_ram_range <-pat_pagerange_is_ram
Xorg-2252 [000] ...1 135.409761: find_next_iomem_res <-walk_system_ram_range
Xorg-2252 [000] ...1 135.409761: _raw_read_lock <-find_next_iomem_res
Xorg-2252 [000] ...1 135.409761: kmem_cache_alloc_trace <-reserve_memtype
Xorg-2252 [000] ...1 135.409761: __might_sleep <-kmem_cache_alloc_trace
Xorg-2252 [000] ...1 135.409762: ___might_sleep <-__might_sleep
next prev parent reply other threads:[~2017-05-11 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 10:33 [drm:qxl] BUG: sleeping function called from invalid context - qxl_bo_kmap_atomic_page()...splat Mike Galbraith
2017-05-08 19:48 ` Gabriel Krisman Bertazi
2017-05-09 2:37 ` Mike Galbraith
2017-05-11 17:24 ` Mike Galbraith [this message]
2017-05-15 4:20 ` Gabriel Krisman Bertazi
2017-05-18 20:40 ` Gabriel Krisman Bertazi
2017-05-19 2:02 ` Mike Galbraith
2017-05-19 17:59 ` Gabriel Krisman Bertazi
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=1494523443.25131.12.camel@gmx.de \
--to=efault@gmx.de \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=krisman@collabora.co.uk \
--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