From: "Kenneth R. Crudup" <kenny@panix.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Commit 25f12ae45fc1 ("maccess: rename probe_kernel_address to get_kernel_nofault") causing several OOPSes
Date: Fri, 26 Jun 2020 01:36:26 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.23.453.2006260127210.3063@xps-7390> (raw)
In-Reply-To: <CAHk-=wjDfQZN8BeM-21vZ=ALa5jaJSRjRei+_0ET9uruwaYwaw@mail.gmail.com>
On Sun, 21 Jun 2020, Linus Torvalds wrote:
> For me that patch makes no difference.
So ... it looks like this original issue (random crashes if this commit was
made and the ROMs thing isn't patched) is a red herring.
For some time now, my Thunderbolt adapter (Lenovo 2nd-Gen TB dock) sometimes
... "acts up" on reboots/powerons with my laptop (Dell XPS 13 2-in-1) if I
boot with it connected- I'll get random disconnects and/or lack of external
video and/or its internal devices will drop offline. I suspect these crashes
were related to the PCIe scribbling(?) somewhere(?) (even though I have IOMMU
turned on). I can't track it down, and I think the issue may lie somewhere
either with the Thunderbolt subsystem (my TB domain UUID gets regenerated on
every boot and is always changing) or a bug in this Dell's BIOS (probably
the likely culprit).
... in any case, I booted a fresh branch that does contain the commit in the
Subject: line, and w/o Christoph's ROMs patch and as long as I don't boot
with the TB adapter attached (or from a cold boot- SOMEtimes) it seems to
work. So, my apologies for wasting everyone's time.
-Kenny
--
Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Orange County CA
prev parent reply other threads:[~2020-06-26 8:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.22.394.2006181751270.9276@xps-7390>
2020-06-19 6:50 ` Christoph Hellwig
2020-06-19 6:57 ` Kenneth R. Crudup
2020-06-19 7:42 ` Christoph Hellwig
2020-06-19 7:45 ` Kenneth R. Crudup
2020-06-20 13:46 ` Kenneth R. Crudup
2020-06-20 16:49 ` Linus Torvalds
2020-06-20 17:50 ` Linus Torvalds
2020-06-21 19:33 ` Kenneth R. Crudup
2020-06-21 19:29 ` Kenneth R. Crudup
2020-06-21 19:44 ` Linus Torvalds
2020-06-26 8:36 ` Kenneth R. Crudup [this message]
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.2006260127210.3063@xps-7390 \
--to=kenny@panix.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®