From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Busch, Keith" <keith.busch@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jiang Liu <jiang.liu@linux.intel.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
Subject: Re: Regression: Kernel unbootable since commit 4d6b4e6 - found by bisection
Date: Mon, 21 Dec 2015 16:45:41 -0600 [thread overview]
Message-ID: <56788115.7030209@lwfinger.net> (raw)
In-Reply-To: <B58D82457FDA0744A320A2FC5AC253B93D38A3F6@fmsmsx104.amr.corp.intel.com>
On 12/21/2015 03:24 PM, Busch, Keith wrote:
>> Since early in the 4.3-rcx series, my Dell Latitude D600 with a 32-bit kernel
>> fails to boot. Unfortunately, I did not discover this until late in the 4.4-rcX
>> cycle. The symptom is that the kernel echos the "Loading initial ramdisk ..."
>> message and then hangs.
>>
>> The problem was bisected to commit 4d6b4es" x86/PCI/ACPI: Use common interface
>> to support PCI host bridge" from Jiang Liu <jiang.liu@linux.intel.com>. The
>> bisection was tested by reverting the commit in question. I have not yet tried
>> to analyze the patch to see where it might be going wrong.
>>
>> Please suggest any trial prints to debug this issue.
>
> Does this fix help you? It is included with the most recent 4.4 rc.
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=727ae8be30b428082d3519817f4fb98b712d457d
Yes, that patch does fix my problem even though the commit message says it is
needed for legacy AMD platforms. My laptop has a Celeron CPU, but the same
considerations must apply.
Thanks,
Larry
next prev parent reply other threads:[~2015-12-21 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 21:24 Regression: Kernel unbootable since commit 4d6b4e6 - found by bisection Busch, Keith
2015-12-21 22:45 ` Larry Finger [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-21 17:40 Larry Finger
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=56788115.7030209@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bhelgaas@google.com \
--cc=hanjun.guo@linaro.org \
--cc=jiang.liu@linux.intel.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.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