public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Faye Pearson <faye-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
To: Prabhakar Reddy Gudla Venkata Siva
	<reddyg-3+M4TpyeDAP2fBVCVOL8/A@public.gmane.org>
Cc: acpi <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Compaq 1700, 2.4.18, acpi-7,24 - SUCCESS (I think)
Date: Thu, 15 Aug 2002 11:32:45 +0100	[thread overview]
Message-ID: <20020815103244.GA7621@clara.net> (raw)
In-Reply-To: <Pine.GSO.4.21.0208142004370.16304-100000-Bq+f90TzBY23n+kRt3O4EA@public.gmane.org>

Prabhakar Reddy Gudla Venkata Siva [reddyg-3+M4TpyeDAP2fBVCVOL8/A@public.gmane.org] wrote:
> Graham, nice to see that I am not all alone :) I too have the same status
> with the acpi-20020726 patch on a similar model (mine is 1720US).
> 
> However, my kernel just keeps repeating "schedule_task(): kevent has not
> started" after the alleged two "PCI Interrupt Link enabled" statements. It
> never freezes.

My kernel would freeze if I enabled Local APIC on Uniprocessor.  Since
ACPI does the IRQ routing this is probably what is confusing things.
It would be useful if the one could override the other if it's being
used.  I make mention of this on my website and my kernel patch's default
configuration has these options disabled.

Other people have mentioned a problem with losing interrupts on some
models of Compaq - I haven't suffered from this and there is a patch for
this which someone has made (which since I don't use it hasn't stuck in
my memory I'm afraid).

I do get the warning about the unknown device, but I ignored it as I
knew I didn't have the device.  I will remove it from my DSDT now I know
what's causing it ;)


Faye

-- 
Faye Pearson,
Software Development Manager,
ClaraNET Ltd.       Tel 020 7903 3000

Even God lends a hand to honest boldness.
		-- Menander


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

  parent reply	other threads:[~2002-08-15 10:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3974778@toto.iv>
     [not found] ` <3974778-Vqs2seESaO4@public.gmane.org>
2002-08-14 20:26   ` Compaq 1700, 2.4.18, acpi-7,24 - SUCCESS (I think) Graham Clark
     [not found]     ` <15706.48376.457358.298696-+pt9qS7RU9EeNw9RxQLXc5Vzexx5G7lz@public.gmane.org>
2002-08-15  0:18       ` Prabhakar Reddy Gudla Venkata Siva
     [not found]         ` <Pine.GSO.4.21.0208142004370.16304-100000-Bq+f90TzBY23n+kRt3O4EA@public.gmane.org>
2002-08-15 10:32           ` Faye Pearson [this message]
2002-08-16  8:58           ` Ducrot Bruno
     [not found]             ` <20020816085840.GD10248-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2002-08-16 21:32               ` Prabhakar Reddy Gudla Venkata Siva
     [not found]                 ` <Pine.GSO.4.21.0208161730480.24869-100000-Bq+f90TzBY23n+kRt3O4EA@public.gmane.org>
2002-08-19  8:42                   ` Ducrot Bruno
2002-08-12 14:49 Hyung K. Kim (±èÇü±Ô)

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=20020815103244.GA7621@clara.net \
    --to=faye-6jsjyq0qj1reowh0uzbu5w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=reddyg-3+M4TpyeDAP2fBVCVOL8/A@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