From: Adrian Bunk <bunk@stusta.de>
To: Tomek Koprowski <tomek@koprowski.org>
Cc: Jean Delvare <khali@linux-fr.org>,
Daniel Ritz <daniel.ritz@gmx.ch>, Daniel Drake <dsd@gentoo.org>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Linus Torvalds <torvalds@osdl.org>, Brice Goglin <brice@myri.com>,
"John W. Linville" <linville@tuxdriver.com>,
Bauke Jan Douma <bjdouma@xs4all.nl>,
gregkh@suse.de, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz, len.brown@intel.com,
linux-acpi@vger.kernel.org
Subject: Re: RFC: PCI quirks update for 2.6.16
Date: Fri, 8 Dec 2006 16:42:08 +0100 [thread overview]
Message-ID: <20061208154208.GB3356@stusta.de> (raw)
In-Reply-To: <200612072145.56861.tomek@koprowski.org>
On Thu, Dec 07, 2006 at 09:45:56PM +0100, Tomek Koprowski wrote:
> On Thursday 07 of December 2006 20:54, Jean Delvare wrote:
>
> > > Tomasz Koprowski (1):
> > > PCI: SMBus unhide on HP Compaq nx6110
> >
> > Bug #6944 might be related to this one, so I'd not include it in
> > 2.6.16-stable.
>
> Actually, the #6944 requires more investigation. I've noticed the
> kacpid going to 100% cpu without the unhide patch applied as well. It
> happens sometimes after dehibernation, putting the laptop to sleep
> and waking it up again resolves the issue. I can't figure out why.
>
> To be on the safe side I'd suggest dumping the patch, but I really
> don't think it should fix anything.
Thanks for this information, I've dropped it.
And this problem really be debugged and fixed in Linus' tree...
> Tomek
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
parent reply other threads:[~2006-12-08 15:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200612072145.56861.tomek@koprowski.org>]
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=20061208154208.GB3356@stusta.de \
--to=bunk@stusta.de \
--cc=bjdouma@xs4all.nl \
--cc=bjorn.helgaas@hp.com \
--cc=brice@myri.com \
--cc=daniel.ritz@gmx.ch \
--cc=dsd@gentoo.org \
--cc=gregkh@suse.de \
--cc=khali@linux-fr.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linville@tuxdriver.com \
--cc=tomek@koprowski.org \
--cc=torvalds@osdl.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