public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@akamai.com>
To: Andrew Cooks <acooks@gmail.com>
Cc: Jim Cromie <jim.cromie@gmail.com>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: Bug involving dynamic_debug and '-p' modifier
Date: Sat, 16 Mar 2013 22:42:46 -0400	[thread overview]
Message-ID: <51452DA6.5050302@akamai.com> (raw)
In-Reply-To: <CAJtEV7YfgcxuEAj+a8SbNmsoMHaEgY1RQ1RoR=8nAi4=8qwT_w@mail.gmail.com>

Hi Andrew,

Thanks for the bug report. I need to send a patch to update the maintainers
file...

Haven't had a chance to look into this yet. Will get back to you.

Thanks,

-Jason



On 03/11/2013 10:28 PM, Andrew Cooks wrote:
> On Tue, Mar 12, 2013 at 9:14 AM, Andrew Cooks <acooks@gmail.com> wrote:
>> Hi Jason
>>
>> When I specify a '-p' modifier in the dynamic debug options in the
>> kernel command line, I get a kernel panic during boot. The panic
>> happens after userspace starts doing graphical stuff, but I haven't
>> been able to pinpoint exactly what.
>>
>> If I use '=_' instead of '-p', or boot to a recovery mode, or change
>> the modifier after booting using debugfs, the panic doesn't occur. For
>> example, booting to runlevel 3 with '=_', then flipping the same
>> modifier to first to '+p' and then to '-p', before starting X does not
>> result in a panic.
>>
>> Booting to runlevel 3 (or even 1!), with '-p' results in a panic, but
>> 'rdshell' is OK.
>>
>> I also tried the Red Hat kernel (just because it's installed - I
>> haven't figured out how to tell the package manager that I don't want
>> a kernel). This also panics, but it says that '-p' is not supported.
>>
>> Please let me know if you need me to do any other tests.
>>
>> '-p', panic: http://pastebin.com/8yAcBQdY
>> '-p', rdshell, no panic: http://pastebin.com/Hi2a7BZA
>>
>> --
>> a.
> Jason's mail bounced, so redirecting to Jim Cromie, who made the most
> recent significant changes to dynamic_debug...
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


      reply	other threads:[~2013-03-17  2:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  1:14 Bug involving dynamic_debug and '-p' modifier Andrew Cooks
2013-03-12  2:28 ` Andrew Cooks
2013-03-17  2:42   ` Jason Baron [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=51452DA6.5050302@akamai.com \
    --to=jbaron@akamai.com \
    --cc=acooks@gmail.com \
    --cc=jim.cromie@gmail.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