mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: carbonated beverage <ramune@net-ronin.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI/Panic 2.6.8-rc3
Date: Sat, 7 Aug 2004 20:37:19 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0408072036280.19619@montezuma.fsmlabs.com> (raw)
In-Reply-To: <20040805003426.GA18820@net-ronin.org>

On Wed, 4 Aug 2004, carbonated beverage wrote:

> Reported this a while ago, but tried it again, still getting oops
> when doing an rmmod of the ACPI processor module.
>
> Hardware: IBM T30, P4 2.4GHz, 256MiB, Debian/stable, did an rmmod processor.
>
> Note: Oops below was copied by hand, so may not be fully reliable.  Also,
> EIP was screwy, so no idea what was executing.

It should be fixed before 2.6.8, a patch has already been sent to the big
wigs.

Index: linux-2.6.8-rc1-mm1/drivers/acpi/processor.c
===================================================================
RCS file: /home/cvsroot/linux-2.6.8-rc1-mm1/drivers/acpi/processor.c,v
retrieving revision 1.1.1.1
diff -u -p -B -r1.1.1.1 processor.c
--- linux-2.6.8-rc1-mm1/drivers/acpi/processor.c	14 Jul 2004 04:56:25 -0000	1.1.1.1
+++ linux-2.6.8-rc1-mm1/drivers/acpi/processor.c	20 Jul 2004 15:31:46 -0000
@@ -2372,8 +2372,10 @@ acpi_processor_remove (
 	pr = (struct acpi_processor *) acpi_driver_data(device);

 	/* Unregister the idle handler when processor #0 is removed. */
-	if (pr->id == 0)
+	if (pr->id == 0) {
 		pm_idle = pm_idle_save;
+		synchronize_kernel();
+	}

 	status = acpi_remove_notify_handler(pr->handle, ACPI_DEVICE_NOTIFY,
 		acpi_processor_notify);

      reply	other threads:[~2004-08-08  0:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  0:34 carbonated beverage
2004-08-08  0:37 ` Zwane Mwaikambo [this message]

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=Pine.LNX.4.58.0408072036280.19619@montezuma.fsmlabs.com \
    --to=zwane@linuxpower.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ramune@net-ronin.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

all inboxes | Powered by JetHome®