From: Peter Schneider <pschneider1968@googlemail.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, regressions@leemhuis.info,
regressions@lists.linux.dev
Subject: Re: Kernel 6.8.4 regression: aacraid controller not initialized any more, system boot hangs
Date: Tue, 14 May 2024 15:23:44 +0200 [thread overview]
Message-ID: <f08ad152-eefa-4748-8a71-6b84117e19b3@googlemail.com> (raw)
In-Reply-To: <yq14jb0twk6.fsf@ca-mkp.ca.oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 1793 bytes --]
Hi Martin,
Am 14.05.2024 um 14:54 schrieb Martin K. Petersen:
>
> Peter,
>
>> Did you have any chance to look into this in more depth? Do you need
>> more information from me to tackle this issue? I'm not a kernel
>> developer, just a user, but I guess with proper instruction I would be
>> able to compile and test patches.
>
> I am afraid I haven't had a time to look further into this yet due to
> travel. The annual LSF/MM/BPF conference is taking place this week. I
> will get back to you as soon as possible.
Ok, great, so have a good time whereever this conference is going to take place! It isn't
very urgent, because in the meantime I can just continue to use the 6.5.13 kernel on my
Proxmox machine. I just wanted to ping you again so this wouldn't fall through the cracks.
> Before I make any recommendations wrt. firmware updates I would like to
> understand why a change intended to make scanning more resilient against
> device implementation errors has had the opposite effect. Especially
> since the change in question reverts to how Linux has scanned for
> devices for decades.
I'll leave everything as it is now, and won't change the crime scene until you tell me
what to do next.
Beste Grüße,
Peter Schneider
--
Climb the mountain not to plant your flag, but to embrace the challenge,
enjoy the air and behold the view. Climb it so you can see the world,
not so the world can see you. -- David McCullough Jr.
OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244
Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@googlemail.com
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@gmail.com
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2024-05-14 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 5:19 Kernel 6.8.4 regression: aacraid controller not initialized any more, system boot hangs Peter Schneider
2024-05-09 1:38 ` Martin K. Petersen
2024-05-09 2:12 ` Peter Schneider
2024-05-09 4:18 ` Peter Schneider
2024-05-14 7:07 ` Peter Schneider
2024-05-14 12:54 ` Martin K. Petersen
2024-05-14 13:23 ` Peter Schneider [this message]
2024-05-21 2:30 ` [PATCH] scsi: core: Handle devices which return an unusually large VPD page count Martin K. Petersen
2024-05-21 13:32 ` Peter Schneider
2024-05-23 22:57 ` Bart Van Assche
2024-05-24 8:10 ` Christoph Hellwig
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=f08ad152-eefa-4748-8a71-6b84117e19b3@googlemail.com \
--to=pschneider1968@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@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 read-only IMAP folder(s) and NNTP newsgroup(s).