linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Keith Packard <keithp@keithp.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 3.0.0-rc2 fails to boot on Atom appliance (bisected, drm/i915)
Date: Mon, 06 Jun 2011 21:00:28 -0700	[thread overview]
Message-ID: <4DEDA25C.5010405@candelatech.com> (raw)
In-Reply-To: <20110606172402.72ddb29b@jbarnes-desktop>

On 06/06/2011 05:24 PM, Jesse Barnes wrote:
> On Mon, 06 Jun 2011 16:59:02 -0700
> Ben Greear<greearb@candelatech.com>  wrote:
>
>> On 06/06/2011 04:41 PM, Keith Packard wrote:
>>> On Mon, 06 Jun 2011 16:26:25 -0700, Ben Greear<greearb@candelatech.com>   wrote:
>>>> On 06/06/2011 01:09 PM, Ben Greear wrote:
>>>>> Anyone seen something like this?  For what it's worth, it seems
>>>>> that -rc1 had the same problem. I'll start bisecting soon if
>>>>> the problem isn't already resolved somehow...
>>>>
>>>> I bisected this problem down to this commit:
>>>
>>> This should be fixed by this patch:
>>>
>>> -------------------- drivers/gpu/drm/i915/intel_display.c ---------------------
>>> index f553ddf..bb1b59b 100644
>>> @@ -7675,6 +7675,7 @@ static void intel_init_display(struct drm_device *dev)
>>>    			dev_priv->display.update_wm = NULL;
>>>    		} else
>>>    			dev_priv->display.update_wm = pineview_update_wm;
>>> +		dev_priv->display.init_clock_gating = gen3_init_clock_gating;
>>>    	} else if (IS_G4X(dev)) {
>>>    		dev_priv->display.update_wm = g4x_update_wm;
>>>    		dev_priv->display.init_clock_gating = g4x_init_clock_gating;
>>>
>>> This hasn't been merged yet, but should be soon.
>>
>> I tried adding that, but the problem stays the same.
>>
>> Any other patches I should try?
>
> Are you sure you booted the right kernel and that it built&  installed
> correctly?

I double checked, but I tried to cheat a bit and just applied that patch on
top of -rc2 instead of on top of the patch that breaks things according to
bisect.  Maybe there is more than one problem.  I'll try tweaking that single
patch tomorrow.

And, I built and booted twice to make sure I didn't screw up..but it had been
a long day of bisecting, so maybe I still messed up some how.

>
> You could add an:
>    if (dev_priv->display.init_clock_gating)
> above the call to display.init_clock_gating in intel_init_clock_gating
> to be sure it's the same problem...

Ok, can try that too.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2011-06-07  4:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 20:09 3.0.0-rc2 fails to boot on Atom appliance Ben Greear
2011-06-06 23:26 ` 3.0.0-rc2 fails to boot on Atom appliance (bisected, drm/i915) Ben Greear
2011-06-06 23:41   ` Keith Packard
2011-06-06 23:59     ` Ben Greear
2011-06-07  0:24       ` Jesse Barnes
2011-06-07  4:00         ` Ben Greear [this message]
2011-06-07 17:09           ` Ben Greear

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=4DEDA25C.5010405@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=keithp@keithp.com \
    --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).