From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202261] general protection fault: 0000 [#1] PREEMPT SMP Workqueue: events ttm_bo_delayed_workqueue
Date: Mon, 14 Jan 2019 21:10:29 +0000 [thread overview]
Message-ID: <bug-202261-2300-qOAlWNz6uL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202261-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202261
--- Comment #4 from Johannes Hirte (johannes.hirte@datenkhaos.de) ---
(In reply to Michel Dänzer from comment #3)
> Looks like https://bugs.freedesktop.org/109234 =>
> https://lists.freedesktop.org/archives/dri-devel/2019-January/202909.html
> and follow-ups.
Yes, looks like it's this bug.
From https://lists.linuxfoundation.org/pipermail/iommu/2019-January/032651.html
> Hmm, I wonder if we are not actually using swiotlb in the end,
> can you check if your dmesg contains this line or not?
>
> PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
No, it isn't. I can't find anything about SWIOTLB or PCI-DMA in dmesg.
Just testing the patch. I don't have a reproducer, but it could be
suspend/resume related.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-01-14 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 14:22 [Bug 202261] New: general protection fault: 0000 [#1] PREEMPT SMP Workqueue: events ttm_bo_delayed_workqueue bugzilla-daemon
2019-01-14 14:24 ` [Bug 202261] " bugzilla-daemon
2019-01-14 14:25 ` bugzilla-daemon
2019-01-14 17:20 ` bugzilla-daemon
2019-01-14 21:10 ` bugzilla-daemon [this message]
2019-01-16 18:12 ` bugzilla-daemon
2019-01-18 20:32 ` bugzilla-daemon
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=bug-202261-2300-qOAlWNz6uL@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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