From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Linux v2.6.13-rc3
Date: Wed, 13 Jul 2005 12:59:04 +0200 [thread overview]
Message-ID: <200507131259.04855.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.58.0507122157070.17536@g5.osdl.org>
Hi,
On Wednesday, 13 of July 2005 07:05, Linus Torvalds wrote:
>
> Yes,
> it's _really_ -rc3 this time, never mind the confusion with the commit
> message last time (when the Makefile clearly said -rc2, but my over-eager
> fingers had typed in a commit message saying -rc3).
>
> There's a bit more changes here than I would like, but I'm putting my foot
> down now. Not only are a lot of people going to be gone next week for LKS
> and OLS, but we've gotten enough stuff for 2.6.13, and we need to calm
> down.
FYI, on my box (Asus L5D, Athlon 64 + nForce3, 64-bit kernel) there are two
regressions wrt -rc2 related to ACPI. First, the battery monitor does not work
(http://bugzilla.kernel.org/show_bug.cgi?id=4665)
and second, the box hangs solid during resume from disk if IO-APIC is not used
(http://bugzilla.kernel.org/show_bug.cgi?id=4416).
The problems have been known for quite some time and remain unresolved,
but apparently they have made it to mainline nevertheless. I understand
nobody else has reported them, but I also know of some people who run
Linux on the same hardware and 2.6.13 will not work for them if these
issues are present in it.
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
next prev parent reply other threads:[~2005-07-13 11:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 5:05 Linux v2.6.13-rc3 Linus Torvalds
2005-07-13 6:21 ` Russell King
2005-07-13 10:59 ` Rafael J. Wysocki [this message]
2005-07-13 18:53 ` Linus Torvalds
2005-07-13 19:45 ` Jose Luis Domingo Lopez
2005-07-13 14:27 ` Dmitry Torokhov
2005-07-13 17:31 ` Lee Revell
2005-07-13 17:51 ` Linus Torvalds
2005-07-13 18:05 ` Lee Revell
2005-07-13 22:18 ` Sebastian Kaergel
2005-08-04 21:04 ` Andrew Morton
2005-07-17 11:18 ` Borislav Petkov
2005-07-17 12:40 ` Alexey Dobriyan
[not found] <Pine.LNX.4.58.0507122157070.17536@g5.osdl.org.suse.lists.linux.kernel>
2005-07-13 12:32 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-07-21 5:30 Brown, Len
2005-07-21 10:09 ` Rafael J. Wysocki
2005-07-22 5:28 Brown, Len
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=200507131259.04855.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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