From: Jason Wessel <jason.wessel@windriver.com>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
kgdb-bugreport@lists.sourceforge.net,
Jesse Barnes <jbarnes@virtuousgeek.org>,
nouveau@lists.freedesktop.org
Subject: Re: [Nouveau] [PATCH] drm/nouveau/kms: Implement KDB debug hooks for nouveau KMS.
Date: Wed, 01 Sep 2010 06:35:15 -0500 [thread overview]
Message-ID: <4C7E3A73.5070503@windriver.com> (raw)
In-Reply-To: <1283335002.2741.5.camel@maxim-laptop>
On 09/01/2010 04:56 AM, Maxim Levitsky wrote:
> On Thu, 2010-08-19 at 13:55 -0400, Chris Ball wrote:
>
>> Hi,
>>
>> Here's a patch to add support for KMS debugging to Nouveau, along the
>> style of the previous patches for Intel¹ and Radeon². I'm only able
>> to test on nv50 here, so a test on nv04 would be much appreciated,
>> and I've published instructions on how to test here³. Thanks!
>>
>> - Chris.
>>
>
> Hi,
>
> I just tried that patch, but unfortunately nether with nor without it
> kdb seems not to work.
> It could be id10t error from my side, but I did test the kdb in the past
> with few KMS patches, and it seemed to work.
>
> Now I can't even get its prompt on the console.
>
> This is what I do:
>
> echo kbd | sudo tee /sys/module/kgdboc/parameters/kgdboc
> (also tried booting with kgdboc=kbd)
>
Try changing it to kgdboc=kms,kbd or the "echo kms,kbd"
When you use only the kbd, the kms feature is not activated.
Jason.
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Kgdb-bugreport mailing list
Kgdb-bugreport@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
next prev parent reply other threads:[~2010-09-01 11:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3iq9yqd7w.fsf@pullcord.laptop.org>
[not found] ` <4C5ACF3F.8050409@windriver.com>
[not found] ` <m3hbj0fju3.fsf_-_@pullcord.laptop.org>
2010-08-19 17:55 ` [PATCH] drm/nouveau/kms: Implement KDB debug hooks for nouveau KMS Chris Ball
[not found] ` <m3aaoimqrp.fsf_-_-0VGQAjvlmrQzNDMTQreKSUB+6BGkLq7r@public.gmane.org>
2010-08-21 2:22 ` Francisco Jerez
2010-08-23 20:50 ` Chris Ball
[not found] ` <m3k4nhqcia.fsf_-_-0VGQAjvlmrQzNDMTQreKSUB+6BGkLq7r@public.gmane.org>
2010-08-26 16:55 ` Francisco Jerez
2010-09-26 11:20 ` Jason Wessel
2010-09-01 9:56 ` Maxim Levitsky
2010-09-01 11:35 ` Jason Wessel [this message]
2010-09-02 10:46 ` [Nouveau] " Maxim Levitsky
2010-09-22 1:42 ` Maxim Levitsky
2010-09-22 14:03 ` Maxim Levitsky
2010-09-22 14:06 ` Maxim Levitsky
2010-09-22 17:07 ` Maxim Levitsky
2010-09-24 20:50 ` Maxim Levitsky
2010-09-24 20:58 ` Jason Wessel
2010-09-25 0:14 ` Maxim Levitsky
2010-09-25 4:08 ` Dmitry Torokhov
2010-10-05 20:56 ` Jason Wessel
2010-10-14 2:34 ` Maxim Levitsky
2010-10-20 16:01 ` sysrq filter and stuck keys [ was Re: [Nouveau] [PATCH] drm/nouveau/kms: Implement KDB debug hooks for nouveau KMS.] Jason Wessel
2010-10-23 2:29 ` Maxim Levitsky
2010-10-27 12:51 ` Jason Wessel
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=4C7E3A73.5070503@windriver.com \
--to=jason.wessel@windriver.com \
--cc=airlied@linux.ie \
--cc=jbarnes@virtuousgeek.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=maximlevitsky@gmail.com \
--cc=nouveau@lists.freedesktop.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 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.