From: Luca Capello <luca-wlebWZzHoyE@public.gmane.org>
To: ML ACPI-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [2.6.6] Oops when unloading processor module
Date: Sat, 05 Jun 2004 01:40:14 +0200 [thread overview]
Message-ID: <40C1085E.8030705@pca.it> (raw)
In-Reply-To: <20040604232817.GA11305-5HFq4VzZ2RFeoWH0uzbU5w@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
on 06/05/2004 01:28 AM, Wichert Akkerman wrote:
> Since the IWP2100 driver has some issues with the acpi processor
> module entering C3 I tried to unload the processor module which
> resulted in the oops below.
problem already reported in the 'acpi-devel' mailing-list
http://sourceforge.net/mailarchive/message.php?msg_id=7591209
http://sourceforge.net/mailarchive/message.php?msg_id=8493052
ATM it's still not solved in 2.6.6 (with no other ACPI patches) and it
still happens on my ASUS M6842NWH.
Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFAwQheVAp7Xm10JmkRAmyQAJ4wjSDIvI70hKRmD4bGbXpepvjEpQCeKedD
ZFlnqf6q6z2yYFxopQQStIY=
=3CeK
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
next prev parent reply other threads:[~2004-06-04 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 23:28 [2.6.6] Oops when unloading processor module Wichert Akkerman
2004-06-04 23:28 ` Wichert Akkerman
[not found] ` <20040604232817.GA11305-5HFq4VzZ2RFeoWH0uzbU5w@public.gmane.org>
2004-06-04 23:40 ` Luca Capello [this message]
2004-06-05 1:34 ` Herbert Xu
2004-06-05 1:34 ` Herbert Xu
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=40C1085E.8030705@pca.it \
--to=luca-wlebwzzhoye@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 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.