From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dave Airlie <airlied@gmail.com>, Dave Airlie <airlied@linux.ie>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
dri-devel@lists.sf.net
Subject: Re: hung bootup with "drm/radeon/kms: move radeon KMS on/off switch out of staging."
Date: Thu, 4 Feb 2010 17:36:02 +0000 [thread overview]
Message-ID: <20100204173602.GA19855@srcf.ucam.org> (raw)
In-Reply-To: <20100204170826.GA16397@elte.hu>
On Thu, Feb 04, 2010 at 06:08:26PM +0100, Ingo Molnar wrote:
> Well, once i applied the revert i got no more hangs or crashes today, in lots
> of bootups. This is fully repeatable - if i re-apply that commit with the
> config i sent the hang happens again.
If you leave the commit applied, use that config and then enable Radeon
KMS under staging, do you get the hang?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-02-04 17:36 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 2:20 [git pull] drm fixes Dave Airlie
2010-02-01 2:53 ` Dave Airlie
2010-02-02 8:17 ` [crash, PATCH] Revert "drm/radeon/kms: move radeon KMS on/off switch out of staging." Ingo Molnar
2010-02-02 8:25 ` Dave Airlie
2010-02-02 15:44 ` Ingo Molnar
2010-02-04 20:39 ` Dave Airlie
2010-02-04 20:46 ` Ingo Molnar
2010-02-04 21:14 ` Dave Airlie
2010-02-05 0:43 ` Dave Airlie
2010-02-05 7:32 ` Ingo Molnar
2010-02-02 8:35 ` Dave Airlie
2010-02-02 8:37 ` Dave Airlie
2010-02-02 15:42 ` Ingo Molnar
2010-02-02 15:46 ` Ingo Molnar
2010-02-02 20:34 ` Dave Airlie
2010-02-04 6:26 ` Ingo Molnar
2010-02-04 6:39 ` Dave Airlie
2010-02-04 7:36 ` Ingo Molnar
2010-02-04 7:49 ` Dave Airlie
2010-02-04 7:17 ` hung bootup with " Ingo Molnar
2010-02-04 16:48 ` Matthew Garrett
2010-02-04 17:08 ` Ingo Molnar
2010-02-04 17:15 ` Linus Torvalds
2010-02-04 17:36 ` Ingo Molnar
2010-02-04 17:36 ` Matthew Garrett [this message]
2010-02-04 17:54 ` Ingo Molnar
2010-02-04 17:59 ` Matthew Garrett
2010-02-04 18:12 ` Ingo Molnar
2010-02-04 18:15 ` Matthew Garrett
2010-02-04 18:56 ` Ingo Molnar
2010-02-04 19:00 ` Matthew Garrett
2010-02-04 19:19 ` Ingo Molnar
2010-02-04 19:28 ` Jerome Glisse
2010-02-04 20:34 ` Ingo Molnar
2010-02-04 18:30 ` Alex Deucher
2010-02-04 19:06 ` Ingo Molnar
2010-02-04 19:18 ` Alex Deucher
2010-02-04 19:24 ` Linus Torvalds
2010-02-04 19:34 ` Dave Airlie
2010-02-04 20:27 ` Ingo Molnar
2010-02-04 19:32 ` Ingo Molnar
2010-02-04 19:53 ` Jesse Barnes
2010-02-04 20:22 ` Ingo Molnar
2010-02-04 20:27 ` david
2010-02-04 20:33 ` Jesse Barnes
2010-02-04 20:57 ` Ingo Molnar
2010-02-04 20:48 ` Matthew Garrett
2010-02-04 21:05 ` Ingo Molnar
2010-02-04 21:09 ` Matthew Garrett
2010-02-05 7:56 ` Ingo Molnar
2010-02-05 8:34 ` Dave Airlie
2010-02-05 9:00 ` Ingo Molnar
2010-02-05 9:18 ` Dave Airlie
2010-02-05 10:47 ` Ingo Molnar
2010-02-04 21:23 ` Andrew Morton
2010-02-04 21:34 ` Jesse Barnes
2010-02-04 21:35 ` Dave Airlie
2010-02-06 11:10 ` Felipe Contreras
2010-02-02 8:58 ` [crash, PATCH] Revert " Domenico Andreoli
2010-02-02 11:59 ` Jerome Glisse
2010-02-02 15:11 ` Domenico Andreoli
2010-02-02 11:56 ` Jerome Glisse
2010-02-02 15:42 ` Ingo Molnar
2010-02-02 23:15 ` Jerome Glisse
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=20100204173602.GA19855@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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).