From: Sami Korkalainen <sami.korkalainen@proton.me>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Stable <stable@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Networking <netdev@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [REGRESSION][BISECTED] Boot stall from merge tag 'net-next-6.2'
Date: Sat, 27 May 2023 04:07:56 +0000 [thread overview]
Message-ID: <NVN-hJsvHwaHe6R-y6XIYJp0FV7sCavgMjobFnseULT1wjgkOFNXbGBGT5iVjCfbtU7dW5xy2hIDoq0ASeNaXhvSY-g2Df4aHWVIMQ2c3TQ=@proton.me> (raw)
In-Reply-To: <ZHFaFosKY24-L7tQ@debian.me>
>Where is SCSI info?
Right there, under the text (It was so short, that I thought to put it in the message. Maybe I should have put that also in pastebin for consistency and clarity):
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: KINGSTON SVP200S Rev: C4
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: hp Model: CDDVDW TS-L633M Rev: 0301
Type: CD-ROM ANSI SCSI revision: 05
>I think networking changes shouldn't cause this ACPI regression, right?
Yeah, beats me, but that's what I got by bisecting. My expertise ends about here.
next prev parent reply other threads:[~2023-05-27 4:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 19:17 [REGRESSION][BISECTED] Boot stall from merge tag 'net-next-6.2' Sami Korkalainen
2023-05-27 1:17 ` Bagas Sanjaya
2023-05-27 4:07 ` Sami Korkalainen [this message]
2023-06-12 14:07 ` Bagas Sanjaya
2023-06-12 19:05 ` Sami Korkalainen
2023-06-12 19:50 ` Andrew Lunn
2023-06-21 6:07 ` Sami Korkalainen
2023-06-21 8:46 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-21 17:56 ` Linus Torvalds
2023-06-21 18:08 ` Linus Torvalds
2023-06-22 18:34 ` Thorsten Leemhuis
2023-06-21 17:57 ` Jason A. Donenfeld
2023-06-23 13:55 ` Ard Biesheuvel
2023-06-23 17:29 ` Linus Torvalds
2023-06-23 20:30 ` Jason A. Donenfeld
2023-06-23 21:52 ` Linus Torvalds
2023-06-23 22:55 ` Ard Biesheuvel
2023-06-23 23:02 ` Linus Torvalds
2023-06-25 15:36 ` David Laight
2023-06-25 14:40 ` Jason A. Donenfeld
2023-06-23 18:20 ` Sami Korkalainen
2023-06-23 18:38 ` Ard Biesheuvel
2023-06-23 19:01 ` Linus Torvalds
2023-06-21 18:49 ` Jason A. Donenfeld
2023-06-21 19:51 ` Linus Torvalds
2023-06-22 13:40 ` Jason A. Donenfeld
2023-06-22 19:25 ` Sami Korkalainen
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='NVN-hJsvHwaHe6R-y6XIYJp0FV7sCavgMjobFnseULT1wjgkOFNXbGBGT5iVjCfbtU7dW5xy2hIDoq0ASeNaXhvSY-g2Df4aHWVIMQ2c3TQ=@proton.me' \
--to=sami.korkalainen@proton.me \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafael@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.