mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: shuah.khan@hp.com
Cc: Yinghai Lu <yinghai@kernel.org>, CAI Qian <caiqian@redhat.com>,
	Takashi Iwai <tiwai@suse.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Vivek Goyal <vgoyal@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: crash dump memory reservation regression
Date: Fri, 31 Aug 2012 09:37:05 -0700	[thread overview]
Message-ID: <0809406a-1043-47c8-b271-9ddb2ce35dba@email.android.com> (raw)
In-Reply-To: <1346428774.2864.16.camel@lorien2>

Kernel Summit is this week... people are away.

Shuah Khan <shuah.khan@hp.com> wrote:

>On Mon, 2012-03-12 at 22:42 -0700, H. Peter Anvin wrote:
>> On 03/12/2012 10:31 PM, Yinghai Lu wrote:
>> > 
>> > Solution will be:
>> > 1.  remove the good_end setting for 64 bit again. and root cause S4
>resume.
>> 
>> This would by far be the best.
>> 
>> 	-hpa
>> 
>
>Any resolution on this issue. Has this been fixed? I haven't seen this
>message on the systems I am running the upstream kernel on, and would
>like to get a commit ID (if any) that fixed the problem.
>
>Thanks,
>-- Shuah

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.

  reply	other threads:[~2012-08-31 16:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5535e246-b7c0-4f69-a27b-1abbadd42db0@zmail14.collab.prod.int.phx2.redhat.com>
2012-03-12  3:00 ` CAI Qian
2012-03-13  5:31   ` Yinghai Lu
2012-03-13  5:42     ` H. Peter Anvin
2012-08-31 15:59       ` Shuah Khan
2012-08-31 16:37         ` H. Peter Anvin [this message]
2012-08-31 16:42           ` Takashi Iwai
2012-08-31 16:50             ` Shuah Khan
2012-03-13 14:26     ` Vivek Goyal
2012-03-13 21:28       ` Yinghai Lu
2012-03-21  8:17     ` Dave Young
2012-03-26 10:32     ` Cong Wang

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=0809406a-1043-47c8-b271-9ddb2ce35dba@email.android.com \
    --to=hpa@zytor.com \
    --cc=caiqian@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=shuah.khan@hp.com \
    --cc=tiwai@suse.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vgoyal@redhat.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

Powered by JetHome