All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	devel@driverdev.osuosl.org, Kay Sievers <kay.sievers@vrfy.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: show_uevent() and general protection fault
Date: Fri, 17 Aug 2012 10:56:44 +0800	[thread overview]
Message-ID: <20120817025644.GA25843@localhost> (raw)
In-Reply-To: <CACVXFVPL4HON7Ec7SxGLgBDJtJExTJihc1cfVQt05WukU54AEQ@mail.gmail.com>

On Fri, Aug 17, 2012 at 10:44:37AM +0800, Ming Lei wrote:
> On Fri, Aug 17, 2012 at 10:29 AM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> 
> >
> > Something obviously wrong here:
> >
> >         env->buflen == 12
> >         env->envp_idx == 1627389952
> >         env->env[0] == NULL
> >
> > I'm not sure where it comes from, but if it's possible for random
> 
> Maybe you can print out the device name by dev_err in show_uevent
> under the situation.

Here it is:

[   68.721580] pci_link PNP0C0F:03: uevent 13 env[1627389952]: PNP0C0F:03/.../PNP0C0F:03

dev_err(dev, "uevent %d env[%d]: %s/.../%s\n", env->buflen, env->envp_idx, top_kobj->name, dev->kobj.name);

Thanks,
Fengguang

      reply	other threads:[~2012-08-17  2:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13  7:59 show_uevent() and general protection fault Fengguang Wu
2012-07-13  8:31 ` Fengguang Wu
2012-07-13  8:46   ` Fengguang Wu
2012-07-17  1:33     ` Greg Kroah-Hartman
2012-07-18  5:15       ` Fengguang Wu
2012-08-16 17:27         ` Greg Kroah-Hartman
2012-08-17  2:06           ` Fengguang Wu
2012-08-17  2:29             ` Fengguang Wu
2012-08-17  2:44               ` Ming Lei
2012-08-17  2:56                 ` Fengguang Wu [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=20120817025644.GA25843@localhost \
    --to=fengguang.wu@intel.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=tom.leiming@gmail.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 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.