mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: airlied@redhat.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, mjg@redhat.com
Cc: maciej.rutecki@gmail.com
Subject: 2.6.39-rc1 nouveau regression (bisected)
Date: Thu, 14 Apr 2011 19:05:59 +0200	[thread overview]
Message-ID: <20110414170559.GA10768@comet.dominikbrodowski.net> (raw)
In-Reply-To: <20110407151129.GA24977@comet.dominikbrodowski.net>

Thought about CCing Linus to show him that 2.6.39-rcX isn't as "calm"
to everyone, but then chose to CC Maciej instead: Would you be so kind and
add this to your regression list? Thanks!

Since commit 38f1cff

    From: Dave Airlie <airlied@redhat.com>
    Date: Wed, 16 Mar 2011 11:34:41 +1000
    Subject: [PATCH] Merge commit '5359533801e3dd3abca5b7d3d985b0b33fd9fe8b' into dr

    This commit changed an internal radeon structure, that meant a new driver
    in -next had to be fixed up, merge in the commit and fix up the driver.

    Also fixes a trivial nouveau merge.

    Conflicts:
        drivers/gpu/drm/nouveau/nouveau_mem.c

booting my atom/NM10/ION2 system crashes hard during boot, right after
blanking the screen, and before the initramfs gets loaded. I just
re-checked: both parent commits ( 5359533 and 4819d2e ) do indeed work
just fine, but the merge commit ( 38f1cff ) fails, same as tip ( 85f2e68 ).

My previous reports (Apr 03, Apr 07) seem to have gotten lost (or ignored,
or both).

Best,
	Dominik

  reply	other threads:[~2011-04-14 17:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03 18:12 2.6.39-rc1 noveau trouble and regression (bad commit: 38f1cff0863809587b5fd10ecd0c24c8b543a48c ) Dominik Brodowski
2011-04-07 15:11 ` Dominik Brodowski
2011-04-14 17:05   ` Dominik Brodowski [this message]
2011-04-14 19:02     ` 2.6.39-rc1 nouveau regression (bisected) 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=20110414170559.GA10768@comet.dominikbrodowski.net \
    --to=linux@dominikbrodowski.net \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=mjg@redhat.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 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®