All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Winchester <kjwinchester@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Dave Airlie <airlied@redhat.com>
Subject: Re: linux-next: Tree for December 17 (Radeon DRM BUG)
Date: Fri, 19 Dec 2008 21:58:54 -0400	[thread overview]
Message-ID: <494C515E.9040403@gmail.com> (raw)
In-Reply-To: <21d7e9970812172247t3d67e6f0waffa99587e2e024b@mail.gmail.com>

Dave Airlie wrote:
> On Thu, Dec 18, 2008 at 10:14 AM, Kevin Winchester
> <kjwinchester@gmail.com> wrote:
>> Stephen Rothwell wrote:
>>> Hi all,
>>>
>>>
>> I get the following BUG in the radeon drm code with today's linux-next when
>> I run "startx".  I have not built or tested linux-next in a while, but the
>> problem definitely does not occur in mainline.
> 
> Do you have another X server running or just console?
> 
> can you get a full dmesg with
> 
> echo 1 > /sys/module/drm/parameters/debug
> 

I just tried today's next (20081219) and the problem seems to be fixed.

Thank you,

-- 
Kevin Winchester

      parent reply	other threads:[~2008-12-20  1:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 12:25 linux-next: Tree for December 17 Stephen Rothwell
2008-12-17 18:17 ` [BUILD-FAILURE] next-20081217-s390x-'struct device' has no member named 'knode_parent' Kamalesh Babulal
2008-12-18  9:47   ` Martin Schwidefsky
2008-12-18 17:17     ` Kamalesh Babulal
2008-12-18  0:13 ` linux-next: Tree for December 17 (DVB) Randy Dunlap
2008-12-18 17:19   ` Randy Dunlap
2008-12-18  0:14 ` linux-next: Tree for December 17 (Radeon DRM BUG) Kevin Winchester
2008-12-18  6:47   ` Dave Airlie
2008-12-18 19:00     ` Bartlomiej Zolnierkiewicz
2008-12-18 20:49       ` Dave Airlie
2008-12-18 22:09         ` Bartlomiej Zolnierkiewicz
2008-12-18 23:39           ` Dave Airlie
2008-12-19 19:45             ` Bartlomiej Zolnierkiewicz
2008-12-19 23:07     ` Kevin Winchester
2008-12-20  1:58     ` Kevin Winchester [this message]

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=494C515E.9040403@gmail.com \
    --to=kjwinchester@gmail.com \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.