From: Luca Capello <luca-wlebWZzHoyE@public.gmane.org>
To: ML ACPI-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Badness in remove_proc_entry when 'rmmod battery'
Date: Mon, 17 May 2004 11:32:27 +0200 [thread overview]
Message-ID: <40A886AB.4020002@pca.it> (raw)
In-Reply-To: <6E0C289723A0564F9A8279E236E8565F07668DFA-4yWAQGcml64divtuJNk2fFDQ4js95KgL@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
on 05/17/04 08:58, Wang, Zhenyu Z wrote:
> Pls, see http://bugme.osdl.org/show_bug.cgi?id=2705
<cut>
> Subject: [ACPI] Badness in remove_proc_entry when 'rmmod battery'
>
> This showed up in my logs today when rmmod'ing the battery module:
>
> Badness in remove_proc_entry at fs/proc/generic.c:685
> Call Trace:
> [<c017964a>] remove_proc_entry+0x10a/0x150
> [<e1a09a4d>] acpi_battery_remove_fs+0x1d/0x2d [battery]
> [<e1a09bc5>] acpi_battery_remove+0x32/0x41 [battery]
> [<c02674d5>] acpi_driver_detach+0x39/0x7c
> [<c0267589>] acpi_bus_unregister_driver+0x12/0x51
> [<e1a09bde>] acpi_battery_exit+0xa/0x1e [battery]
> [<c012bace>] sys_delete_module+0x13e/0x180
> [<c014063a>] do_munmap+0x14a/0x190
> [<c010411b>] syscall_call+0x7/0xb
>
> Badness in remove_proc_entry at fs/proc/generic.c:685
> Call Trace:
> [<c017964a>] remove_proc_entry+0x10a/0x150
> [<e1a09a4d>] acpi_battery_remove_fs+0x1d/0x2d [battery]
> [<e1a09bc5>] acpi_battery_remove+0x32/0x41 [battery]
> [<c02674d5>] acpi_driver_detach+0x39/0x7c
> [<c0267589>] acpi_bus_unregister_driver+0x12/0x51
> [<e1a09bde>] acpi_battery_exit+0xa/0x1e [battery]
> [<c012bace>] sys_delete_module+0x13e/0x180
> [<c014063a>] do_munmap+0x14a/0x190
> [<c010411b>] syscall_call+0x7/0xb
problem already reported in the 'acpi-devel' mailing-list
http://sourceforge.net/mailarchive/message.php?msg_id=7591209
ATM it isn't solved in 2.6.6 (with no other ACPI patches).
Thx, bye,
Gismo / Luca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFAqIarVAp7Xm10JmkRAiuuAJ9rtdLt55V6tX8Oc8SMzRgRBe8irQCeNDf1
bWhaoiZ3PL3Hp2UKH1lGhnw=
=A0Jp
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next prev parent reply other threads:[~2004-05-17 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 6:58 Badness in remove_proc_entry when 'rmmod battery' Wang, Zhenyu Z
[not found] ` <6E0C289723A0564F9A8279E236E8565F07668DFA-4yWAQGcml64divtuJNk2fFDQ4js95KgL@public.gmane.org>
2004-05-17 9:32 ` Luca Capello [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-17 6:54 Jan De Luyck
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=40A886AB.4020002@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox