public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Maier Gerfried <moali-ArvQUR6U0fYD0fefG/KofA@public.gmane.org>
To: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: Oops when unloading thermal
Date: Tue, 12 Nov 2002 08:01:37 +0100 (MET)	[thread overview]
Message-ID: <1037084497.3dd0a751f1bb9@sbox.tugraz.at> (raw)
In-Reply-To: <1036566482.3dc8bfd26902e-ArvQUR6U0fYD0fefG/KofA@public.gmane.org>

The patch from BK

| --- 1.9/drivers/acpi/bus.c	Mon Nov  4 09:59:35 2002
| +++ 1.10/drivers/acpi/bus.c	Fri Nov  8 14:33:09 2002
| @@ -1072,6 +1072,8 @@
| 		return_VALUE(result);
| 	}
| 
|+	device->driver = driver;
|+
| [...]

made the Oops disappear. Modules unload now as I expect them. Thanks for this 
suggestion!

Maier Gerfried








Zitiere moali-ArvQUR6U0fYD0fefG/KofA@public.gmane.org:

> Hello,
> 
> I was now able to compile a kernel which boots correctly with acpi
> enabled 
> (2.4.20-rc1 with the recent patch). Loading all the acpi-modules (fan,
> battery, 
> ac, thermal, prcessor,...) is done without any error, but when I try to
> unload 
> thermal
> 
> > modprobe -r thermal
> 
> Oops 0000
> CPU: 0
> EIP: 0010:[<d0a39490>] Not tainted
> EFLAGS: 00010286
> .
> .
> .
> code: Bad EIP value
> <0> Kernel panic: Attempted to kill idle task!
> In idle-task - not syncing
> 
> What can I do about this?
> 
> Thanks,
> Maier Gerfried


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      parent reply	other threads:[~2002-11-12  7:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06  7:08 Oops when unloading thermal moali-ArvQUR6U0fYD0fefG/KofA
     [not found] ` <1036566482.3dc8bfd26902e-ArvQUR6U0fYD0fefG/KofA@public.gmane.org>
2002-11-12  7:01   ` Maier Gerfried [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=1037084497.3dd0a751f1bb9@sbox.tugraz.at \
    --to=moali-arvqur6u0fyd0fefg/kofa@public.gmane.org \
    --cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@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