All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: Jochen Voss <voss@seehuhn.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Dave Airlie <airlied@linux.ie>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Jesse Barnes <jesse.barnes@intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.37-rc7
Date: Wed, 22 Dec 2010 20:18:55 +0200	[thread overview]
Message-ID: <20101222181855.GA4244@laptop> (raw)
In-Reply-To: <20101221233022.GA9188@seehuhn.de>

Hi,

On Tue, 21 Dec 2010 23:30:30 +0000, Jochen Voss wrote:
> On Tue, Dec 21, 2010 at 11:52:17AM -0800, Linus Torvalds wrote:
> > I'm still nervous about some of the regression reports for intel
> > graphics, so please keep testing and reporting. This is the last -rc
> > before xmas (or whatever your holiday may be), so now you all have a
> > few free days when you have nothing better to do than test out an -rc
> > release, right?
>
> For reference, the regression I reported yesterday
> (message id "20101220140615.GA3035@automatix",
> http://www.spinics.net/lists/kernel/msg1126718.html
> on the web) is still present: -rc7 only shows a blank
> screen on my system, -rc7 with 541cc966 reverted works
> without problems.
>

I can confirm the regression: a completely-blank screen right after the
grub prompt.

Printing kernel output using early_printk() all along ('earlyprintk=
serial,keep') shows that the rest of the kernel internally goes on with
its booting process as usual.

Reverting the mentioned 541cc966 commit solves the problem; the bug is
reproducible in both qemu and real hardware.

regards,

-- 
Darwish
http://darwish.07.googlepages.com

  reply	other threads:[~2010-12-22 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21 19:52 Linux 2.6.37-rc7 Linus Torvalds
2010-12-21 23:30 ` Jochen Voss
2010-12-22 18:18   ` Ahmed S. Darwish [this message]
2010-12-22 18:42     ` Jesse Barnes
  -- strict thread matches above, loose matches on Subject: below --
2010-12-22  3:56 Sedat Dilek

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=20101222181855.GA4244@laptop \
    --to=darwish.07@gmail.com \
    --cc=airlied@linux.ie \
    --cc=chris@chris-wilson.co.uk \
    --cc=jesse.barnes@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=voss@seehuhn.de \
    /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.