From: "Huang\, Ying" <ying.huang@intel.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ye Xiaolong <xiaolong.ye@intel.com>, LKP ML <lkp@01.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [x86/KASLR] ed9f007ee6: -- System halted
Date: Wed, 29 Jun 2016 13:29:28 -0700 [thread overview]
Message-ID: <87y45nyc0n.fsf@yhuang-mobile.sh.intel.com> (raw)
In-Reply-To: <CAE9FiQVMq+fBDyZpghSndmYu6dF0Am4h9nWn1_fJjwOR5VKHug@mail.gmail.com> (Yinghai Lu's message of "Wed, 29 Jun 2016 13:08:55 -0700")
Hi, Yinghai,
Yinghai Lu <yinghai@kernel.org> writes:
> On Tue, Jun 28, 2016 at 12:49 PM, Yinghai Lu <yinghai@kernel.org> wrote:
>> On Mon, Jun 27, 2016 at 10:43 PM, Ye Xiaolong <xiaolong.ye@intel.com> wrote:
>>> On Mon, Jun 27, 2016 at 11:59:37AM -0700, Yinghai Lu wrote:
>>>>output is:
>>>>
>>>>early console in setup code
>>>>early console in extract_kernel
>>>>input_data: 0x0000000008fbb276
>>>>input_len: 0x00000000018c6e00
>>>>output: 0x0000000001000000
>>>>output_len: 0x0000000009867c98
>>>>kernel_total_size: 0x0000000008769000
>>>>booted via startup_32()
>>>>Physical KASLR using RDTSC...
>>>>Virtual KASLR using RDTSC...
>>>>
>>>>Decompressing Linux...
>>>>
>>>>XZ-compressed data is corrupt
>>>>
>>>> -- System halted
>>>>
>>>>Can you apply attached debug patch and send out dmesg?
>>>
>>> There are 4 patches you attached, do you mean to apply them all based on
>>> commit ed9f007ee6? I tried and seemed they can't apply clearly on it.
>>
>
> Please check attached updated debug patches.
>
> You should apply them after ed9f007ee6 in following sequence
>
> revert_79063a7.patch
> early_console_more_2_2x.patch
> early_console_more_2_2x_add_0.patch
> early_console_more_2_2x_add_1.patch
If you could provide a git branch for that, that will be easier for us
to test and more accurate for you to get the right patch to be tested.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2016-06-29 20:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57712812.r6MdDSquaCRYkMnh%xiaolong.ye@intel.com>
2016-06-27 18:59 ` Yinghai Lu
[not found] ` <20160628054354.GA9620@yexl-desktop>
[not found] ` <CAE9FiQV50UhjJDH89C_T7f2vxFDm7Hpjn78ZKtnfeygQcsf23w@mail.gmail.com>
2016-06-29 20:08 ` Yinghai Lu
2016-06-29 20:29 ` Huang, Ying [this message]
2016-06-30 4:49 ` [LKP] " Yinghai Lu
2016-06-30 6:58 ` Ye Xiaolong
2016-07-01 0:24 ` Yinghai Lu
2016-07-01 4:06 ` Baoquan He
2016-07-01 4:46 ` Baoquan He
2016-07-01 7:50 ` Baoquan He
2016-07-01 12:16 ` Ye Xiaolong
2016-07-01 13:14 ` Baoquan He
2016-07-01 13:25 ` Baoquan He
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=87y45nyc0n.fsf@yhuang-mobile.sh.intel.com \
--to=ying.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=xiaolong.ye@intel.com \
--cc=yinghai@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
all inboxes | Powered by JetHome®