From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: udev broken by recent ACPI git commits
Date: Mon, 13 Nov 2006 21:56:02 +0100 [thread overview]
Message-ID: <200611132156.02989.rjw@sisk.pl> (raw)
In-Reply-To: <200611130616.38174.len.brown@intel.com>
On Monday, 13 November 2006 12:16, Len Brown wrote:
> > 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?
The BIOS version is F.02 ...
> What do you see if you add the patch below to the ACPICA patch?
... and the patch helps (ie. with this patch on top of 2.6.19-rc3 with
acpi-acpica-20061011-2.6.19-rc4.diff applied the box boots normally).
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
prev parent reply other threads:[~2006-11-13 20:59 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
2006-11-13 20:56 ` Rafael J. Wysocki [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=200611132156.02989.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.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