From: Dominik Brodowski <linux@dominikbrodowski.net>
To: airlied@redhat.com, dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.39-rc1 noveau trouble and regression (bad commit: 38f1cff0863809587b5fd10ecd0c24c8b543a48c )
Date: Sun, 3 Apr 2011 20:12:06 +0200 [thread overview]
Message-ID: <20110403181206.GA19291@comet.dominikbrodowski.net> (raw)
Hey,
After bisecting for a day, I'm pretty confident that the commit
38f1cff0863809587b5fd10ecd0c24c8b543a48c introduced an error which
causes one of my computers to hang during boot -- only a blank
screen appears. The initramfs never gets run.
The system consists of an Atom D525 with Intel NM10 + NVIDIA GT218/ION2
chipset.
Best,
Dominik
next reply other threads:[~2011-04-03 18:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 18:12 Dominik Brodowski [this message]
2011-04-07 15:11 ` 2.6.39-rc1 noveau trouble and regression (bad commit: 38f1cff0863809587b5fd10ecd0c24c8b543a48c ) Dominik Brodowski
2011-04-14 17:05 ` 2.6.39-rc1 nouveau regression (bisected) Dominik Brodowski
2011-04-14 19:02 ` Marcin Slusarz
2011-04-15 6:11 ` Dominik Brodowski
2011-04-16 22:12 ` Nigel Cunningham
2011-04-16 23:50 ` Kyle Spaans
2011-04-17 15:12 ` Kyle Spaans
2011-04-17 15:45 ` Marcin Slusarz
2011-04-17 16:24 ` Kyle Spaans
2011-04-17 16:49 ` Marcin Slusarz
2011-04-18 20:02 ` 2.6.39-rc1 nouveau(?) " Marcin Slusarz
2011-04-18 20:27 ` Linus Torvalds
2011-04-19 21:47 ` Marcin Slusarz
2011-04-19 21:50 ` [PATCH 1/2] drm/nouveau: fix notifier memory corruption bug Marcin Slusarz
2011-04-19 21:52 ` [PATCH 2/2] drm/nouveau: fix allocation of notifier object Marcin Slusarz
2011-04-19 22:34 ` 2.6.39-rc1 nouveau(?) regression (bisected) Ben Skeggs
2011-04-20 14:18 ` Kyle Spaans
2011-04-22 16:29 ` Dominik Brodowski
2011-04-17 16:23 ` 2.6.39-rc1 nouveau " Marcin Slusarz
2011-04-17 17:20 ` Dominik Brodowski
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=20110403181206.GA19291@comet.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).