From: Christoph Hellwig <hch@lst.de>
To: Jason Adriaanse <jason_a69@yahoo.co.uk>
Cc: robin.murphy@arm.com, baolu.lu@linux.intel.com, hch@lst.de,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [regression] Bug 217218 - Trying to boot Linux version 6-2.2 kernel with Marvell SATA controller 88SE9235
Date: Sun, 16 Apr 2023 08:55:03 +0200 [thread overview]
Message-ID: <20230416065503.GB6410@lst.de> (raw)
In-Reply-To: <04a94830-f626-2cd7-d220-7ba3025a409c@yahoo.co.uk>
Hi Jason,
sorry for the late reply. I had some email issues and am still
recovering from the backlog.
On Fri, Mar 31, 2023 at 10:20:37AM +0800, Jason Adriaanse wrote:
> Hi Christoph and Robin,
>
> Christoph - I would like to send you more dmesg information but as my boot
> device cannot be detected that information is not being written to disk. Is
> there any way to specifically write boot debug information to say a USB
> device with some kernel parameters?
I don't know of any good way. pstore has some ways to save kernel
messages, but it doesn't work to well with normal block devices in
case of crashes.
I'm a bit lost at the moment.
Two ideas I have, would be to
1) boot with the intel_iommu=off kernel command line
3) build a kernel with CONFIG_INTEL_IOMMU
and see if that works and report the dmesg.
next prev parent reply other threads:[~2023-04-16 6:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a79ea7f5-6a41-a6c9-cfec-ba01aa2a3cfa@leemhuis.info>
2023-03-28 1:22 ` [regression] Bug 217218 - Trying to boot Linux version 6-2.2 kernel with Marvell SATA controller 88SE9235 Christoph Hellwig
2023-03-30 12:18 ` Robin Murphy
2023-03-31 2:20 ` Jason Adriaanse
2023-04-16 6:55 ` Christoph Hellwig [this message]
2023-04-22 6:25 ` Jason Adriaanse
2023-04-24 13:20 ` Robin Murphy
2023-04-24 13:44 ` Jason Adriaanse
2023-04-24 14:07 ` Robin Murphy
2023-04-25 4:17 ` Jason Adriaanse
2023-04-25 11:37 ` Robin Murphy
2023-04-25 13:58 ` Jason Adriaanse
2023-05-22 10:26 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 11:01 ` Robin Murphy
2023-05-22 11:33 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-02 13:07 ` Thorsten Leemhuis
2023-06-06 9:24 ` Christoph Hellwig
2023-06-06 10:26 ` Jason Adriaanse
2023-04-16 6:41 ` Christoph Hellwig
2023-04-17 11:21 ` Robin Murphy
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=20230416065503.GB6410@lst.de \
--to=hch@lst.de \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jason_a69@yahoo.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=robin.murphy@arm.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).