All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: akpm@linux-foundation.org, Thomas Gleixner <tglx@linutronix.de>,
	"David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, e1000-devel@lists.sourceforge.net,
	netdev@vger.kernel.org
Subject: mmotm 2010-07-19 - e1000e vs. pm_qos_update_request issues
Date: Tue, 20 Jul 2010 16:35:25 -0400	[thread overview]
Message-ID: <6182.1279658125@localhost> (raw)
In-Reply-To: Your message of "Mon, 19 Jul 2010 16:38:09 PDT." <201007200007.o6K07Xbg028863@imap1.linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1966 bytes --]

On Mon, 19 Jul 2010 16:38:09 PDT, akpm@linux-foundation.org said:
> The mm-of-the-moment snapshot 2010-07-19-16-37 has been uploaded to
> 
>    http://userweb.kernel.org/~akpm/mmotm/

Throws a warning at boot:

[    1.786060] WARNING: at kernel/pm_qos_params.c:264 pm_qos_update_request+0x28/0x54()
[    1.786088] Hardware name: Latitude E6500
[    1.787045] pm_qos_update_request() called for unknown object
[    1.787966] Modules linked in:
[    1.788940] Pid: 1, comm: swapper Not tainted 2.6.35-rc5-mmotm0719 #1
[    1.790035] Call Trace:
[    1.791121]  [<ffffffff81037335>] warn_slowpath_common+0x80/0x98
[    1.792205]  [<ffffffff810373e1>] warn_slowpath_fmt+0x41/0x43
[    1.793279]  [<ffffffff81057c14>] pm_qos_update_request+0x28/0x54
[    1.794347]  [<ffffffff8134889e>] e1000_configure+0x421/0x459
[    1.795393]  [<ffffffff8134afbd>] e1000_open+0xbd/0x37c
[    1.796436]  [<ffffffff8105743a>] ? raw_notifier_call_chain+0xf/0x11
[    1.797491]  [<ffffffff8145f948>] __dev_open+0xae/0xe2
[    1.798547]  [<ffffffff8145f997>] dev_open+0x1b/0x49
[    1.799612]  [<ffffffff8146e36e>] netpoll_setup+0x84/0x259
[    1.800685]  [<ffffffff81b5037c>] init_netconsole+0xbc/0x21f
[    1.801744]  [<ffffffff81b5026c>] ? sir_wq_init+0x0/0x35
[    1.802793]  [<ffffffff81b502c0>] ? init_netconsole+0x0/0x21f
[    1.803845]  [<ffffffff810002ff>] do_one_initcall+0x7a/0x12f
[    1.804885]  [<ffffffff81b2ccae>] kernel_init+0x138/0x1c2
[    1.805915]  [<ffffffff81003554>] kernel_thread_helper+0x4/0x10
[    1.806937]  [<ffffffff81590e00>] ? restore_args+0x0/0x30
[    1.807955]  [<ffffffff81b2cb76>] ? kernel_init+0x0/0x1c2
[    1.808958]  [<ffffffff81003550>] ? kernel_thread_helper+0x0/0x10
[    1.809958] ---[ end trace 84b562a00a60539e ]---

Looks like a repeat of something I reported against -mmotm 2010-05-11, though a
WARNING rather than an outright crash - the traceback is pretty much identical.
 I have *no* idea why -rc3-mmotm0701 doesn't whinge similarly.


[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2010-07-20 20:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 23:38 mmotm 2010-07-19-16-37 uploaded akpm
2010-07-20 20:35 ` Valdis.Kletnieks [this message]
2010-07-20 21:07   ` mmotm 2010-07-19 - e1000e vs. pm_qos_update_request issues Andrew Morton
2010-07-20 21:07     ` Andrew Morton
2010-07-21  7:12     ` [PATCH] " Florian Mickler
2010-07-21 22:12       ` mark gross
2010-07-22  4:05       ` Valdis.Kletnieks
2010-07-22 21:58         ` Rafael J. Wysocki
2010-07-22 22:37       ` Jeff Kirsher
2010-07-22 22:37         ` Jeff Kirsher
2010-07-21 22:09     ` mark gross
2010-07-21 22:09       ` mark gross
2010-07-20 20:41 ` mmotm 2010-07-19-16-37 uploaded Valdis.Kletnieks
2010-07-20 20:38   ` Jarod Wilson
     [not found]   ` <201007201350.28961.dmitry.torokhov@gmail.com>
2010-07-20 21:11     ` Valdis.Kletnieks
2010-07-20 21:41       ` Jarod Wilson
2010-07-25 18:00         ` Mauro Carvalho Chehab
2010-07-21 12:54 ` mmotm 2010-07-19 - more pm_qos woes - audio this time Valdis.Kletnieks
2010-07-21 12:54   ` Valdis.Kletnieks
2010-07-21 12:59   ` Mark Brown
2010-07-21 12:59     ` [alsa-devel] " Mark Brown

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=6182.1279658125@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.