From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111122] 2500U: Graphics corruption on kernel 5.2
Date: Mon, 26 Aug 2019 15:53:24 +0000 [thread overview]
Message-ID: <bug-111122-502-jiW56TAWsU@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111122-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 784 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111122
--- Comment #25 from andreaskem@web.de ---
Apparently, Lenovo released a new BIOS update for my laptop (Thinkpad E485)
today. The changelog mentions, "Sync IOAPICID in IVRS and APIC ACPI tables
(Linux)." I installed the update and removed both the ivrs_ioapic[32]=00:14.0
flag, as well as the iommu=pt flag from my kernel command line for testing. To
my surprise, the laptop booted just fine and from what I can tell, the
graphical corruption seems to be gone. In the meantime, the kernel and mesa
were updated a few times and I cannot pinpoint what, exactly, fixed my issues.
-> mesa 19.1.5
-> kernel 5.2.10.arch1-1
-> llvm-libs 8.0.1-3
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1545 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-26 15:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 6:56 [Bug 111122] 2500U: Graphics corruption on kernel 5.2 bugzilla-daemon
2019-07-13 6:57 ` bugzilla-daemon
2019-07-13 7:03 ` bugzilla-daemon
2019-07-14 4:59 ` bugzilla-daemon
2019-07-15 16:42 ` bugzilla-daemon
2019-07-22 7:45 ` bugzilla-daemon
2019-07-22 12:30 ` bugzilla-daemon
2019-08-02 13:28 ` bugzilla-daemon
2019-08-08 8:43 ` bugzilla-daemon
2019-08-08 9:30 ` bugzilla-daemon
2019-08-08 13:47 ` bugzilla-daemon
2019-08-09 3:30 ` bugzilla-daemon
2019-08-09 7:21 ` bugzilla-daemon
2019-08-09 10:06 ` bugzilla-daemon
2019-08-10 17:46 ` bugzilla-daemon
2019-08-12 8:19 ` bugzilla-daemon
2019-08-12 14:49 ` bugzilla-daemon
2019-08-13 8:15 ` bugzilla-daemon
2019-08-15 9:26 ` bugzilla-daemon
2019-08-15 19:15 ` bugzilla-daemon
2019-08-16 22:15 ` bugzilla-daemon
2019-08-18 2:18 ` bugzilla-daemon
2019-08-18 10:22 ` bugzilla-daemon
2019-08-19 23:31 ` bugzilla-daemon
2019-08-21 9:21 ` bugzilla-daemon
2019-08-26 10:14 ` bugzilla-daemon
2019-08-26 15:53 ` bugzilla-daemon [this message]
2019-08-26 18:27 ` bugzilla-daemon
2019-08-26 18:28 ` bugzilla-daemon
2019-09-19 9:32 ` bugzilla-daemon
2019-09-20 1:39 ` bugzilla-daemon
2019-09-23 17:31 ` bugzilla-daemon
2019-11-19 9: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-111122-502-jiW56TAWsU@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.