From: Jiri Slaby <jirislaby@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: mm-commits@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Tiago Vignatti <tiago.vignatti@nokia.com>,
Dave Airlie <airlied@redhat.com>,
kvm@vger.kernel.org
Subject: vga_arb warning [was: mmotm 2009-11-01-10-01 uploaded]
Date: Sun, 01 Nov 2009 22:47:05 +0100 [thread overview]
Message-ID: <4AEE01D9.8040902@gmail.com> (raw)
In-Reply-To: <200911011807.nA1I7o95016136@imap1.linux-foundation.org>
On 11/01/2009 07:07 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to
Hi, I got the following warning while booting an image in qemu-kvm:
WARNING: at fs/attr.c:158 notify_change+0x2da/0x310()
Hardware name:
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.32-rc5-mm1_64 #862
Call Trace:
[<ffffffff81038008>] warn_slowpath_common+0x78/0xb0
[<ffffffff8103804f>] warn_slowpath_null+0xf/0x20
[<ffffffff810d32ba>] notify_change+0x2da/0x310
[<ffffffff810c5b88>] ? fsnotify_create+0x48/0x60
[<ffffffff810c6d2b>] ? vfs_mknod+0xbb/0xe0
[<ffffffff812487b6>] devtmpfs_create_node+0x1e6/0x270
[<ffffffff811170d0>] ? sysfs_addrm_finish+0x20/0x280
[<ffffffff811175d6>] ? __sysfs_add_one+0x26/0xf0
[<ffffffff81117b6c>] ? sysfs_do_create_link+0xcc/0x160
[<ffffffff81241cf0>] device_add+0x1e0/0x5b0
[<ffffffff8124adb1>] ? pm_runtime_init+0xa1/0xb0
[<ffffffff81248f05>] ? device_pm_init+0x65/0x70
[<ffffffff812420d9>] device_register+0x19/0x20
[<ffffffff81242290>] device_create_vargs+0xf0/0x120
[<ffffffff812422ec>] device_create+0x2c/0x30
[<ffffffff810c0516>] ? __register_chrdev+0x86/0xf0
[<ffffffff81245599>] ? __class_create+0x69/0xa0
[<ffffffff814326e9>] ? mutex_lock+0x19/0x50
[<ffffffff811d4e23>] misc_register+0x93/0x170
[<ffffffff818994a0>] ? vga_arb_device_init+0x0/0x77
[<ffffffff818994b3>] vga_arb_device_init+0x13/0x77
[<ffffffff818994a0>] ? vga_arb_device_init+0x0/0x77
[<ffffffff810001e7>] do_one_initcall+0x37/0x190
[<ffffffff8187d6ce>] kernel_init+0x172/0x1c8
[<ffffffff81003c7a>] child_rip+0xa/0x20
[<ffffffff8187d55c>] ? kernel_init+0x0/0x1c8
[<ffffffff81003c70>] ? child_rip+0x0/0x20
---[ end trace 4eaa2a86a8e2da22 ]---
next parent reply other threads:[~2009-11-01 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200911011807.nA1I7o95016136@imap1.linux-foundation.org>
2009-11-01 21:47 ` Jiri Slaby [this message]
2009-11-04 5:48 ` vga_arb warning [was: mmotm 2009-11-01-10-01 uploaded] Andrew Morton
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=4AEE01D9.8040902@gmail.com \
--to=jirislaby@gmail.com \
--cc=airlied@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=tiago.vignatti@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).