All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc - A. Dahlhaus" <mad@wol.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: bderzhavets@yahoo.com, Xen-devel <xen-devel@lists.xensource.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: Fw: Re: Problems with load the most recent 2.6.29-rc6 &	Xen unstable on ASUS P5K Premium
Date: Tue, 03 Mar 2009 20:13:45 +0100	[thread overview]
Message-ID: <49AD8169.5080301@wol.de> (raw)
In-Reply-To: <49AD7DB3.3040207@goop.org>

Jeremy Fitzhardinge schrieb:
> Boris Derzhavets wrote:
>> >I probably shouldn't have been operating machinery yesterday.
>> >The crash is probably because I committed the e820 memory 
>> rearranging >stuff into the wrong branch, but something may have 
>> broken us from >tip/master as well.
>> >   J
>>
>> Kernel was already broken at *2/28/09
>> *
>>
> Thanks, that's a useful reference.  I'm in the middle of a bisect at 
> the moment, so I should nail down what went wrong fairly soon.
>
>    J
The second test i did with console=ttyS0,9600n8 kernel param didn't show 
output from the kernel.

Marc

  reply	other threads:[~2009-03-03 19:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 18:05 Fw: Re: Problems with load the most recent 2.6.29-rc6 & Xen unstable on ASUS P5K Premium Boris Derzhavets
2009-03-03 18:57 ` Jeremy Fitzhardinge
2009-03-03 19:13   ` Marc - A. Dahlhaus [this message]
2009-03-03 20:08   ` M A Young
2009-03-03 20:20     ` M A Young
2009-03-03 22:00       ` Jeremy Fitzhardinge
2009-03-04  0:11         ` Marc - A. Dahlhaus
2009-03-04  0:41           ` Jeremy Fitzhardinge
2009-03-04 11:37           ` Boris Derzhavets
2009-03-04 12:51             ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
2009-03-04 15:55               ` Boris Derzhavets
2009-03-05  1:51       ` Jeremy Fitzhardinge

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=49AD8169.5080301@wol.de \
    --to=mad@wol.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=bderzhavets@yahoo.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.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 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.