From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jacek Luczak <difrost.kernel@gmail.com>
Cc: astarikovskiy@suse.de, len.brown@intel.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] GPE storm detected on FS Amilo Pro
Date: Thu, 22 Jan 2009 13:22:41 +0100 [thread overview]
Message-ID: <200901221322.41970.rjw@sisk.pl> (raw)
In-Reply-To: <497847D0.4050700@gmail.com>
On Thursday 22 January 2009, Jacek Luczak wrote:
> Hi Rafael,
>
> > So everything appears to be OK except that your hardware has a problem,
> > which is correctly worked around and the message just tells you what happens.
>
> Most probably yes, but I'm using that kernel really shortly so there might be
> some issues that I didn't noticed. This of course doesn't mean that here we have
> bug, I was just bit confused with that message.
>
> >> NOTE: In git kernel I've noticed that after boot and obtaining IP from DHCP I've
> >> got such message:
> >>
> >> Jan 21 14:44:32 difrost kernel: sky2 eth0: enabling interface
> >> Jan 21 14:44:33 difrost kernel: sky2 eth0: Link is up at 100 Mbps, full duplex,
> >> flow control rx
> >> Jan 21 14:45:36 difrost kernel: ACPI: EC: missing confirmations, switch off
> >> interrupt mode.
> >>
> >> This is not fully reproducible, didn't shown on [4].
> >
> > This may be related to the issue behind the GPM storm message.
>
> Is it sth serious? I'm really lost here.
No, I don't think it's serious. As long as everything works, there's not need
to worry. :-)
Thanks,
Rafael
next prev parent reply other threads:[~2009-01-22 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 14:46 [ACPI] GPE storm detected on FS Amilo Pro Jacek Luczak
2009-01-21 16:00 ` Rafael J. Wysocki
2009-01-22 10:17 ` Jacek Luczak
2009-01-22 12:22 ` Rafael J. Wysocki [this message]
2009-01-21 20:50 ` Alexey Starikovskiy
2009-01-22 10:25 ` Jacek Luczak
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=200901221322.41970.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=astarikovskiy@suse.de \
--cc=difrost.kernel@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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