public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-acpi@vger.kernel.org
Subject: Re: udev broken by recent ACPI git commits
Date: Mon, 13 Nov 2006 06:16:37 -0500	[thread overview]
Message-ID: <200611130616.38174.len.brown@intel.com> (raw)
In-Reply-To: <200611030039.28762.len.brown@intel.com>

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]

> Please test that the latest ACPICA patch works on your system and shout if it doesn't.
> In particular, if you've got an nx6325 like Rafael's, it would be interesting to know
> if you see the same issue.
> 
> You can snag the latest ACPICA patch vs  top of Linus' tree via git or plain patch here:
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git acpica
> http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/test/2.6.19/acpi-acpica-20061011-2.6.19-rc4.diff.gz

Rafael,
What BIOS version is running on your nx6325?
What do you see if you add the patch below to the ACPICA  patch?

thanks,
-Len


[-- Attachment #2: git.diff --]
[-- Type: text/x-diff, Size: 601 bytes --]

diff --git a/arch/i386/kernel/acpi/boot.c b/arch/i386/kernel/acpi/boot.c
diff --git a/arch/x86_64/kernel/time.c b/arch/x86_64/kernel/time.c
index 328bd73..d39cd90 100644
--- a/arch/x86_64/kernel/time.c
+++ b/arch/x86_64/kernel/time.c
@@ -513,6 +513,9 @@ static unsigned long get_cmos_time(void)
 		if (acpi_gbl_FADT.header.revision >= FADT2_REVISION_ID &&
 					acpi_gbl_FADT.century)
 			extyear = CMOS_READ(acpi_gbl_FADT.century);
+printk("get_cmos_time(): acpi_gbl_FADT.century %d extyear %d\n",
+	acpi_gbl_FADT.century, extyear);
+extyear = 0;
 #endif
 	} while (sec != CMOS_READ(RTC_SECONDS));
 

  parent reply	other threads:[~2006-11-13 11:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 23:04 udev broken by recent ACPI git commits Rafael J. Wysocki
2006-11-01  5:16 ` Len Brown
2006-11-01  8:35   ` Len Brown
2006-11-01 10:47     ` Rafael J. Wysocki
2006-11-01 13:03       ` Alexey Starikovskiy
2006-11-01 17:44         ` Rafael J. Wysocki
2006-11-01 19:27           ` Alexey Starikovskiy
2006-11-01 20:00             ` Rafael J. Wysocki
2006-11-02  0:12               ` Henrique de Moraes Holschuh
2006-11-03  5:39       ` Len Brown
2006-11-03  7:58         ` Rafael J. Wysocki
2006-11-03  8:22           ` Rafael J. Wysocki
2006-11-13 11:16         ` Len Brown [this message]
2006-11-13 20:56           ` Rafael J. Wysocki

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=200611130616.38174.len.brown@intel.com \
    --to=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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