From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Toralf F?rster <toralf.foerster@gmx.de>,
Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null'
Date: Fri, 29 Jan 2010 13:45:51 +0000 [thread overview]
Message-ID: <20100129134551.GR19799@ZenIV.linux.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.00.1001261416430.15694@twin.jikos.cz>
On Tue, Jan 26, 2010 at 02:17:32PM +0100, Jiri Kosina wrote:
> > > Please, find out which file is causing this, if it's reproducible.
> > >
> > I reproduced the msg :
> > "ACPI: Please implement acpi_video_bus_ROM_seq_show" by :
> > by
> > $> head -c 10 /proc/acpi/video/VID/info
> >
> > After suspend to disk and wakeup however the file /proc/acpi/video/VID/ROM was
> > the culprit.
> >
> > The trace however I can't reproduce until now.
*snort*
The message is caused by
printk(KERN_INFO PREFIX "Please implement %s\n", __func__);
seq_printf(seq, "<TODO>\n");
in acpi_video_bus_ROM_seq_show(), so it's not surprising. Shouldn't spew
to syslog, but other than that it's a non-issue. Stack trace, OTOH, is
something very different; something is trying to generate 2Mb of contents
in a single ->show(). Which is definitely not that one - "<TODO>\n" is
not going to eat that much ;-)
next prev parent reply other threads:[~2010-01-29 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 19:16 kernel error : 'find /proc/ -type f | xargs -n 1 head -c 10 >/dev/null' Toralf Förster
2010-01-21 20:35 ` Alexey Dobriyan
2010-01-21 21:19 ` Toralf Förster
2010-01-26 13:17 ` Jiri Kosina
2010-01-28 1:39 ` Zhang Rui
2010-01-29 13:45 ` Al Viro [this message]
2010-01-28 4:51 ` Américo Wang
2010-01-29 13:38 ` Al Viro
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=20100129134551.GR19799@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=toralf.foerster@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox