From: Thomas Renninger <trenn@suse.de>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>,
Len Brown <lenb@kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Matthew Garrett <mjg@redhat.com>,
Alexey Starikovskiy <astarikovskiy@novell.com>
Subject: Re: mmotm 2010-07-27 - WARNING in ec_parse_io_ports()
Date: Wed, 28 Jul 2010 13:17:28 +0200 [thread overview]
Message-ID: <201007281317.29129.trenn@suse.de> (raw)
In-Reply-To: <10677.1280295051@localhost>
On Wednesday 28 July 2010 07:30:51 Valdis.Kletnieks@vt.edu wrote:
> On Tue, 27 Jul 2010 14:56:50 PDT, akpm@linux-foundation.org said:
> > The mm-of-the-moment snapshot 2010-07-27-14-56 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
>
> Seen during very early boot:
Yep, that's my fault.
I'll post a fix to Matthew's platform drivers list asap.
For now just ignore it. The warning is a false positive one and
is harmless.
Thanks for bringing this up!
Thomas
>
> [ 0.302450] ------------[ cut here ]------------
> [ 0.302458] WARNING: at drivers/acpi/ec.c:864
ec_parse_io_ports+0x7d/0x110()
> [ 0.302460] Hardware name: Latitude E6500
> [ 0.302462] Could not request EC data io port 2352
Interesting io port 0x930..., definitely not default.
You might want to double check with a fixed kernel if it
is registered correctly in /proc/ioports and the WARNING
vanishes. But no need to explicitly check, just have a look
when you try a newer one anyway. Thanks.
next prev parent reply other threads:[~2010-07-28 11:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 21:56 mmotm 2010-07-27-14-56 uploaded akpm
2010-07-28 5:30 ` mmotm 2010-07-27 - WARNING in ec_parse_io_ports() Valdis.Kletnieks
2010-07-28 11:17 ` Thomas Renninger [this message]
2010-07-28 5:42 ` mmotm 2010-07-27 - nouveau lockdep issues Valdis.Kletnieks
2010-07-28 6:03 ` Marcin Slusarz
2010-07-28 6:03 ` Marcin Slusarz
2010-07-28 15:54 ` mmotm 2010-07-27-14-56 uploaded (staging/iio) Randy Dunlap
2010-07-28 18:32 ` Jonathan Cameron
2010-07-28 19:07 ` [PATCH 0/3] staging:iio Build issue fixes Jonathan Cameron
2010-07-28 20:10 ` Randy Dunlap
[not found] ` <4C509DBE.7000603@cam.ac.uk>
2010-07-29 15:52 ` Randy Dunlap
2010-07-28 19:07 ` [PATCH 1/3] staging:iio: iio_sw_ring_helper_state - add dummy case for no buffer builds Jonathan Cameron
2010-07-28 19:07 ` [PATCH 2/3] staging:iio:lis3l02dq add a thresh_timestamp field to state for no ring case Jonathan Cameron
2010-07-28 22:23 ` mmotm 2010-07-27 - hda-intel audio fails to initialize Valdis.Kletnieks
2010-07-28 22:23 ` Valdis.Kletnieks
2010-07-29 5:37 ` Takashi Iwai
2010-07-29 16:05 ` Valdis.Kletnieks
2010-07-29 16:05 ` Valdis.Kletnieks
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=201007281317.29129.trenn@suse.de \
--to=trenn@suse.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=astarikovskiy@novell.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=rjw@sisk.pl \
/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.