From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
Tejun Heo <htejun@gmail.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Rodney Gordon II <meff@spherevision.org>,
sparclinux@vger.kernel.org, David Miller <davem@davemloft.net>,
Mikael Pettersson <mikpe@it.uu.se>,
Mark Fortescue <mark@mtfhpc.demon.co.uk>,
William Lee Irwin III <wli@holomorphy.com>,
Andi Kleen <ak@suse.de>,
discuss@x86-64.org, Ioan Ionita <opslynx@gmail.com>
Subject: Re: [2/2] 2.6.22-rc5: known regressions
Date: Sun, 17 Jun 2007 16:23:43 +0200 [thread overview]
Message-ID: <467543EF.6080605@googlemail.com> (raw)
In-Reply-To: <46754153.6040404@googlemail.com>
Hi all,
Here is a list of some known regressions in 2.6.22-rc5.
Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions
SATA/PATA
Subject : libata IT821X driver still fails! Hard-freezes system
References : http://lkml.org/lkml/2007/6/14/82
Submitter : Rodney Gordon II <meff@spherevision.org>
Status : unknown
Sparc64
Subject : random invalid instruction occourances on sparc32 (sun4c)
References : http://lkml.org/lkml/2007/6/17/111
Submitter : Mark Fortescue <mark@mtfhpc.demon.co.uk>
Status : problem is being debugged
Subject : 2.6.22-rc broke X on Ultra5
References : http://lkml.org/lkml/2007/5/22/78
Submitter : Mikael Pettersson <mikpe@it.uu.se>
Handled-By : David Miller <davem@davemloft.net>
Status : problem is being debugged
x86-64
Subject : x86-64 2.6.22-rc2 random segfaults
References : http://lkml.org/lkml/2007/5/24/275
Submitter : Ioan Ionita <opslynx@gmail.com>
Status : Unknown
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
parent reply other threads:[~2007-06-17 14:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <46754153.6040404@googlemail.com>]
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=467543EF.6080605@googlemail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=discuss@x86-64.org \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=meff@spherevision.org \
--cc=mikpe@it.uu.se \
--cc=opslynx@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wli@holomorphy.com \
/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;
as well as URLs for NNTP newsgroup(s).