All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Hang loading initrd since last Friday.
Date: Thu, 4 May 2023 10:22:46 -0700	[thread overview]
Message-ID: <a227583c-ef41-e954-fd4c-0cdb23c77222@candelatech.com> (raw)
In-Reply-To: <f12a8f23-5aac-b615-300c-38001b9583c2@candelatech.com>

On 5/3/23 16:49, Ben Greear wrote:
> On 5/2/23 21:46, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 03.05.23 04:31, Bagas Sanjaya wrote:
>>> On Tue, May 02, 2023 at 02:03:33PM -0700, Ben Greear wrote:
>>>>
>>>> Pulling today's upstream 6.3+ tree, my system now hangs loading initrd.
>>
>> Just to understand this properly: you mean after the boot loader said it
>> loaded the initramfs, not when the kernel starts using it?
> 
> I am bisecting...it appears to be .config related.  If I skip enabling things
> during bisect, then I do not see the problem.  But I copied my original buggy .config
> into an otherwise good kernel commit, and now it fails.  I'm manually bisecting
> the .config settings....

I had enabled this option:  CONFIG_HYPERV_VTL_MODE

And that makes it not boot.  Not sure that is expected or not, but I will simply un-select it
and continue on, as I do not actually need that feature.

Thanks,
Ben


  parent reply	other threads:[~2023-05-04 17:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 21:03 Hang loading initrd since last Friday Ben Greear
2023-05-03  2:31 ` Bagas Sanjaya
2023-05-03  4:46   ` Linux regression tracking (Thorsten Leemhuis)
2023-05-03 23:49     ` Ben Greear
2023-05-04 16:38       ` Raghavendra K T
2023-05-04 16:44         ` Jens Axboe
2023-05-04 18:48           ` Raghavendra K T
2023-05-04 18:49             ` Jens Axboe
2023-05-04 17:22       ` Ben Greear [this message]
2023-05-04 17:59         ` Michael Kelley (LINUX)
2023-05-04 23:46           ` Ben Greear
2023-05-05  0:04             ` Michael Kelley (LINUX)

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=a227583c-ef41-e954-fd4c-0cdb23c77222@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=bagasdotme@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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.