linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 214259] Discrete Thunderbold Controller 8086:1137 throws DMAR and XHCI errors and is only partially functional
Date: Thu, 03 Nov 2022 15:45:11 +0000	[thread overview]
Message-ID: <bug-214259-208809-usyzZ1V71y@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214259-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=214259

Bjorn Helgaas (bjorn@helgaas.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bjorn@helgaas.com

--- Comment #25 from Bjorn Helgaas (bjorn@helgaas.com) ---
I don't know the connection to the DMAR faults, but from the first log
(https://bugzilla.kernel.org/attachment.cgi?id=298567):

  BIOS-e820: [mem 0x000000006bc00000-0x00000000efffffff] reserved
  pci_bus 0000:00: root bus resource [mem 0x71000000-0xdfffffff window]

This entire PCI host bridge aperture is "reserved" in the E820 map, which means
we won't allocate any PCI BARs in that area, which means hot-add won't work.

The current workaround for this is https://git.kernel.org/linus/d341838d776a
("x86/PCI: Disable E820 reserved region clipping via quirks"), which appeared
in v5.19.

I think the underlying issue is that this machine has EFI, Linux converts the
EFI memory map to E820 format, and it converts EFI_MEMORY_MAPPED_IO to
E820_TYPE_RESERVED.  EFI_MEMORY_MAPPED_IO means "the OS must map this memory
for use by EFI runtime services."  It does *not* mean "the OS can never use
this memory."  I think Linux should omit EFI_MEMORY_MAPPED_IO areas completely
from the E820 map.

This is basically the same issue as bug #216565.  I attached a patch there to
omit EFI_MEMORY_MAPPED_IO.

I would love to hear from anybody with a Clevo machine that shows similar
problems.  If you can, please boot with the patch at
https://bugzilla.kernel.org/attachment.cgi?id=303123 with the "efi=debug"
kernel parameter, open new bugzilla with the complete dmesg log, and assign it
to me.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-11-03 15:45 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 13:44 [Bug 214259] New: Discrete Thunderbold Controller 8086:1137 throws DMAR and XHCI errors and is only partially functional bugzilla-daemon
2021-09-01 13:45 ` [Bug 214259] " bugzilla-daemon
2021-09-01 13:45 ` bugzilla-daemon
2021-09-01 13:46 ` bugzilla-daemon
2021-09-01 13:47 ` bugzilla-daemon
2021-09-01 13:48 ` bugzilla-daemon
2021-09-01 13:48 ` bugzilla-daemon
2021-09-01 13:50 ` bugzilla-daemon
2021-09-01 13:52 ` bugzilla-daemon
2021-09-01 13:52 ` bugzilla-daemon
2021-09-01 13:52 ` bugzilla-daemon
2021-09-01 13:53 ` bugzilla-daemon
2021-09-01 13:53 ` bugzilla-daemon
2021-09-01 13:53 ` bugzilla-daemon
2021-09-01 17:40 ` bugzilla-daemon
2021-09-28 16:24 ` bugzilla-daemon
2021-10-08  8:32 ` bugzilla-daemon
2021-10-08  8:33 ` bugzilla-daemon
2022-05-19 18:32 ` bugzilla-daemon
2022-05-23 13:25 ` bugzilla-daemon
2022-05-23 16:33 ` bugzilla-daemon
2022-07-07 21:13 ` bugzilla-daemon
2022-07-07 21:16 ` bugzilla-daemon
2022-07-28 16:32 ` bugzilla-daemon
2022-07-28 20:56 ` bugzilla-daemon
2022-11-03 15:45 ` bugzilla-daemon [this message]
2022-11-03 17:19 ` bugzilla-daemon
2022-11-04 10:16 ` bugzilla-daemon
2022-11-04 10:21 ` bugzilla-daemon
2022-11-04 10:42 ` bugzilla-daemon
2022-11-04 10:44 ` bugzilla-daemon
2022-11-04 21:13 ` bugzilla-daemon
2022-11-05 18:28 ` bugzilla-daemon
2022-11-07 13:15 ` bugzilla-daemon
2022-11-07 13:16 ` bugzilla-daemon
2022-11-07 14:08 ` bugzilla-daemon
2022-11-07 14:31 ` bugzilla-daemon
2022-11-07 16:15 ` bugzilla-daemon
2022-11-07 16:34 ` bugzilla-daemon
2022-11-07 16:52 ` bugzilla-daemon
2022-11-07 16:55 ` bugzilla-daemon
2022-11-07 17:40 ` bugzilla-daemon
2022-11-07 17:44 ` bugzilla-daemon
2022-11-07 17:45 ` bugzilla-daemon
2022-11-07 17:47 ` 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-214259-208809-usyzZ1V71y@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).