From: Luca Capello <luca-wlebWZzHoyE@public.gmane.org>
To: ML ACPI-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ASUS M6800N: problem when removing 'ac' module
Date: Sat, 20 Mar 2004 13:26:09 +0100 [thread overview]
Message-ID: <405C3861.8090803@pca.it> (raw)
In-Reply-To: <405C26C2.70603-wlebWZzHoyE@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
on 03/20/04 12:10, Luca Capello wrote:
> I'm on '2.6.5-rc1 + ACPI DSDT in initrd + eciadsl USB patch' and I get this
> message when I 'rmmod ac' or 'modprobe -r ac':
actually, this happens with all ACPI modules:
=====
Badness in remove_proc_entry at fs/proc/generic.c:664
Call Trace:
[<c0182b4c>] remove_proc_entry+0x11c/0x160
[<e20df328>] acpi_ac_remove_fs+0x49/0x6d [ac]
[<e20df5e9>] acpi_ac_remove+0x86/0xa5 [ac]
[<c02e920a>] acpi_driver_detach+0x64/0xbd
[<c02e9352>] acpi_bus_unregister_driver+0x3d/0x93
[<e20df63d>] cleanup_module+0x35/0x55 [ac]
[<c01326fb>] sys_delete_module+0x12b/0x170
[<c014905a>] do_munmap+0x13a/0x180
[<c01490e3>] sys_munmap+0x43/0x70
[<c010935b>] syscall_call+0x7/0xb
Badness in remove_proc_entry at fs/proc/generic.c:664
Call Trace:
[<c0182b4c>] remove_proc_entry+0x11c/0x160
[<e2177eb5>] acpi_battery_remove_fs+0x49/0x6d [battery]
[<e2178185>] acpi_battery_remove+0x86/0xa5 [battery]
[<c02e920a>] acpi_driver_detach+0x64/0xbd
[<c02e9352>] acpi_bus_unregister_driver+0x3d/0x93
[<e21781d9>] acpi_battery_exit+0x35/0x55 [battery]
[<c01326fb>] sys_delete_module+0x12b/0x170
[<c01490e3>] sys_munmap+0x43/0x70
[<c010935b>] syscall_call+0x7/0xb
Badness in remove_proc_entry at fs/proc/generic.c:664
Call Trace:
[<c0182b4c>] remove_proc_entry+0x11c/0x160
[<e2177eb5>] acpi_battery_remove_fs+0x49/0x6d [battery]
[<e2178185>] acpi_battery_remove+0x86/0xa5 [battery]
[<c02e920a>] acpi_driver_detach+0x64/0xbd
[<c02e9352>] acpi_bus_unregister_driver+0x3d/0x93
[<e21781d9>] acpi_battery_exit+0x35/0x55 [battery]
[<c01326fb>] sys_delete_module+0x12b/0x170
[<c01490e3>] sys_munmap+0x43/0x70
[<c010935b>] syscall_call+0x7/0xb
Badness in remove_proc_entry at fs/proc/generic.c:664
Call Trace:
[<c0182b4c>] remove_proc_entry+0x11c/0x160
[<e2212c1a>] acpi_thermal_remove_fs+0x49/0x6d [thermal]
[<e22130a4>] acpi_thermal_remove+0xce/0xea [thermal]
[<c02e920a>] acpi_driver_detach+0x64/0xbd
[<c02e9352>] acpi_bus_unregister_driver+0x3d/0x93
[<e22130f5>] acpi_thermal_exit+0x35/0x55 [thermal]
[<c01326fb>] sys_delete_module+0x12b/0x170
[<c01490e3>] sys_munmap+0x43/0x70
[<c010935b>] syscall_call+0x7/0xb
Badness in remove_proc_entry at fs/proc/generic.c:664
Call Trace:
[<c0182b4c>] remove_proc_entry+0x11c/0x160
[<e2204561>] acpi_processor_remove_fs+0x49/0x6d [processor]
[<e2204abc>] acpi_processor_remove+0x96/0xc3 [processor]
[<c02e920a>] acpi_driver_detach+0x64/0xbd
[<c02e9352>] acpi_bus_unregister_driver+0x3d/0x93
[<e2204b8f>] acpi_processor_exit+0x3f/0x5f [processor]
[<c01326fb>] sys_delete_module+0x12b/0x170
[<c01490e3>] sys_munmap+0x43/0x70
[<c010935b>] syscall_call+0x7/0xb
Badness in remove_proc_entry at fs/proc/generic.c:664
Call Trace:
[<c0182b4c>] remove_proc_entry+0x11c/0x160
[<e218d865>] acpi_button_exit+0x45/0x55 [button]
[<c01326fb>] sys_delete_module+0x12b/0x170
[<c01490e3>] sys_munmap+0x43/0x70
[<c010935b>] syscall_call+0x7/0xb
Badness in remove_proc_entry at fs/proc/generic.c:664
Call Trace:
[<c0182b4c>] remove_proc_entry+0x11c/0x160
[<e216e861>] asus_acpi_exit+0x1d/0x2a [asus_acpi]
[<c01326fb>] sys_delete_module+0x12b/0x170
[<c01490e3>] sys_munmap+0x43/0x70
[<c010935b>] syscall_call+0x7/0xb
=====
Please take care that it doesn't happen with other modules (like 'ehci_hcd' or
'joydev').
Solutions?
Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFAXDhhVAp7Xm10JmkRAhABAJ44Z2VbSQgZN9zxS/Bzl16s67CmEACfa+PA
GCw83WzhvIBLpfJoIuh7qjI=
=FMOT
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-20 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 11:10 ASUS M6800N: problem when removing 'ac' module Luca Capello
[not found] ` <405C26C2.70603-wlebWZzHoyE@public.gmane.org>
2004-03-20 12:26 ` Luca Capello [this message]
2004-03-23 21:44 ` Luca Capello
-- strict thread matches above, loose matches on Subject: below --
2004-03-22 2:04 Li, Shaohua
[not found] ` <571ACEFD467F7749BC50E0A98C17CDD803300B9D-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-03-23 12:00 ` Luca Capello
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=405C3861.8090803@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.