linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kenneth R. Crudup" <kenny@panix.com>
To: mika.westerberg@linux.intel.com
Cc: linux-usb@vger.kernel.org, "Kenneth R. Crudup" <kenny@panix.com>
Subject: I get a new Thunderbolt domain UUID on every boot
Date: Sun, 5 Jul 2020 14:52:04 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.23.453.2007051446170.4280@xps-7390> (raw)


Does anyone know why my machine (Dell XPS 7390 2-in-1, i7-1065G7 CPU) gets a
new Thunderbolt domain UUID on every boot?

----
$ sudo boltctl domains | wc -l
3320
$ sudo boltctl domains | tail -20
 o domain 815fe31a-99fd-8680-ffff-ffffffffffff
   |- bootacl:  0/0
   `- security: unknown

 o domain 703bafdf-6a33-8680-ffff-ffffffffffff
   |- bootacl:  0/0
   `- security: unknown

 o domain 91c55303-9244-8680-ffff-ffffffffffff
   |- bootacl:  0/0
   `- security: unknown

 * domain0 800e6342-557e-8680-ffff-ffffffffffff
   |- bootacl:  0/0
   `- security: iommu

 * domain1 9128366f-c373-8680-ffff-ffffffffffff
   |- bootacl:  0/0
   `- security: iommu
$
----
$ egrep '(THUNDER|USB4)' .config
# CONFIG_MDIO_THUNDER is not set
CONFIG_USB4_NET=m
# CONFIG_USB_HSIC_USB4604 is not set
CONFIG_INTEL_WMI_THUNDERBOLT=y
CONFIG_USB4=y
$
----
I did see this, too:
$  dmesg | fgrep -i thunderbolt
[    1.114106] thunderbolt 0000:00:0d.2: 0: uid crc8 mismatch (expected: 0x8e, got: 0xe7)
[    1.657866] thunderbolt 0000:00:0d.3: 0: uid crc8 mismatch (expected: 0x8e, got: 0xe7)
----

Thanks,

	-Kenny

-- 
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Orange County CA

             reply	other threads:[~2020-07-05 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05 21:52 Kenneth R. Crudup [this message]
2020-07-20 10:07 ` I get a new Thunderbolt domain UUID on every boot Mika Westerberg
2020-07-20 12:43   ` Kenneth R. Crudup
2020-07-21 10:28     ` Mika Westerberg
2020-10-17 21:58       ` Kenneth R. Crudup

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=alpine.DEB.2.23.453.2007051446170.4280@xps-7390 \
    --to=kenny@panix.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    /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).