xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <liuw@liuw.name>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Console is not working with 2.6.38.4 Dom0 and Xen unstable
Date: Wed, 4 May 2011 10:31:06 +0800	[thread overview]
Message-ID: <BANLkTinB+qcF9A7nmnRAq7aNbFVRi10o4g@mail.gmail.com> (raw)
In-Reply-To: <20110503150518.GE7207@dumpdata.com>

On Tue, May 3, 2011 at 11:05 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
>
> Hmm, not seeing the drm messages. Did you compile with the CONFIG_DRM_I915_KMS=y
>
> Also you might want to run with 'drm.debug=255' just to see where it stops working correctly.
>

CONFIG_DRM_I915_KMS=m, that's my original setting.

After I set CONFIG_DRM_I915_KMS=y and added drm.debug=255 to the
command line. The kernel hangs with
"[drm:i915_get_vblank_timestamp], crtc 0 is disabled", repeating forever.

If I don't add drm.debug=255, it boots smoothly. And the VGA console
shows up. Hooray! :-)

-- 
Best regards
Wei Liu
Twitter: @iliuw
Site: http://liuw.name

  reply	other threads:[~2011-05-04  2:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30  9:13 Console is not working with 2.6.38.4 Dom0 and Xen unstable Wei Liu
2011-04-30  9:59 ` Pasi Kärkkäinen
2011-04-30 10:27   ` Wei Liu
2011-04-30 10:41     ` Pasi Kärkkäinen
2011-04-30 11:17       ` Wei Liu
2011-04-30 11:40         ` Pasi Kärkkäinen
2011-05-02 11:31           ` Wei Liu
2011-05-02 13:54             ` Wei Liu
2011-05-02 14:10             ` Konrad Rzeszutek Wilk
2011-05-03  3:28               ` Wei Liu
2011-05-03 15:05                 ` Konrad Rzeszutek Wilk
2011-05-04  2:31                   ` Wei Liu [this message]
2011-05-03 13:21 ` Ian Campbell
2011-05-03 13:49   ` Wei Liu

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=BANLkTinB+qcF9A7nmnRAq7aNbFVRi10o4g@mail.gmail.com \
    --to=liuw@liuw.name \
    --cc=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).