public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan@hell.org.pl>
To: "Georg C. F. Greve" <greve@gnu.org>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>,
	Martin Loschwitz <madkiss@madkiss.org>,
	linux-kernel@vger.kernel.org, "Brown, Len" <len.brown@intel.com>,
	acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] Re: PROBLEM: ACPI freezes 2.6.1 on boot
Date: Thu, 22 Jan 2004 13:08:54 +0100	[thread overview]
Message-ID: <20040122120854.GB3534@hell.org.pl> (raw)
In-Reply-To: <m3ptddgckg.fsf@reason.gnu-hamburg>

Thus wrote Georg C. F. Greve:
> So the problem we've been seeing seems to be related to the
> interaction between local APIC support and ACPI.

We've definitely had those problems before (with ASUS L3800C), there's 
even a patch fixing this issue (attached below) you might try.
I guess that's another of those lost and forgotten bugzilla bugs :)

-- 
Karol 'sziwan' Kozimor
sziwan@hell.org.pl


diff -Bru linux-2.6.0-test8/arch/i386/kernel/apic.c patched/arch/i386/kernel/apic.c
--- linux-2.6.0-test8/arch/i386/kernel/apic.c	2003-10-18 05:43:36.000000000 +0800
+++ patched/arch/i386/kernel/apic.c	2003-10-30 23:17:50.000000000 +0800
@@ -836,8 +836,8 @@
 {
 	unsigned int lvtt1_value, tmp_value;
 
-	lvtt1_value = SET_APIC_TIMER_BASE(APIC_TIMER_BASE_DIV) |
-			APIC_LVT_TIMER_PERIODIC | LOCAL_TIMER_VECTOR;
+	lvtt1_value = APIC_LVT_TIMER_PERIODIC | LOCAL_TIMER_VECTOR;
+
 	apic_write_around(APIC_LVTT, lvtt1_value);
 
 	/*
diff -Bru linux-2.6.0-test8/drivers/acpi/bus.c patched/drivers/acpi/bus.c
--- linux-2.6.0-test8/drivers/acpi/bus.c	2003-10-18 05:43:19.000000000 +0800
+++ patched/drivers/acpi/bus.c	2003-10-30 23:20:32.000000000 +0800
@@ -589,6 +589,7 @@
 
 	ACPI_FUNCTION_TRACE("acpi_bus_init");
 
+	disable_APIC_timer();
 	status = acpi_initialize_subsystem();
 	if (ACPI_FAILURE(status)) {
 		printk(KERN_ERR PREFIX "Unable to initialize the ACPI Interpreter\n");
@@ -643,6 +644,7 @@
 		goto error1;
 	}
 
+	enable_APIC_timer();
 	printk(KERN_INFO PREFIX "Interpreter enabled\n");
 
 	/*
@@ -672,6 +674,7 @@
 error1:
 	acpi_terminate();
 error0:
+	enable_APIC_timer();
 	return_VALUE(-ENODEV);
 }
 

  reply	other threads:[~2004-01-22 12:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 16:32 PROBLEM: ACPI freezes 2.6.1 on boot Nakajima, Jun
2004-01-21 21:21 ` Georg C. F. Greve
2004-01-21 22:29   ` Georg C. F. Greve
2004-01-22 12:08     ` Karol Kozimor [this message]
2004-01-22 13:59       ` [ACPI] " Mikael Pettersson
2004-01-22 14:05         ` Karol Kozimor
2004-01-22 17:15         ` Linus Torvalds
2004-01-22 17:49           ` Mikael Pettersson
2004-01-22 14:08       ` Georg C. F. Greve
2004-01-22 14:26         ` Georg C. F. Greve
  -- strict thread matches above, loose matches on Subject: below --
2004-01-21 18:56 Linus Torvalds
2004-01-21 21:15 ` Georg C. F. Greve
2004-01-21 21:51   ` [ACPI] " Sérgio Monteiro Basto
2004-01-21 22:33     ` Georg C. F. Greve
2004-01-21 23:31       ` Sérgio Monteiro Basto
2004-01-22 10:32         ` Georg C. F. Greve
2004-01-22 14:16 Yu, Luming
2004-01-22 18:23 Pallipadi, Venkatesh
2004-01-22 18:37 ` Mikael Pettersson
2004-01-22 19:05   ` Linus Torvalds
2004-01-23 13:19     ` Maciej W. Rozycki

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=20040122120854.GB3534@hell.org.pl \
    --to=sziwan@hell.org.pl \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=greve@gnu.org \
    --cc=jun.nakajima@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madkiss@madkiss.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