public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	video4linux@list.redhat.com,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Robert Fitzsimons <robfitz@273k.net>, Len Brown <lenb@kernel.org>,
	Thierry Volpiatto <tvolpiatt@neuf.fr>, Andi Kleen <ak@suse.de>,
	discuss@x86-64.org, Ioan Ionita <opslynx@gmail.com>
Subject: Re: [4/4] 2.6.22-rc3: known regressions
Date: Tue, 29 May 2007 14:53:00 +0200	[thread overview]
Message-ID: <465C222C.3020203@googlemail.com> (raw)
In-Reply-To: <465C188F.9000900@googlemail.com>

Hi all,

Here is a list of some known regressions in 2.6.22-rc3.

Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions



V4L

Subject    : V4L ABI breakage
References : http://lkml.org/lkml/2007/5/14/42
Submitter  : Robert Fitzsimons <robfitz@273k.net>
Caused-By  : Hans Verkuil <hverkuil@xs4all.nl>
             Mauro Carvalho Chehab <mchehab@infradead.org>
             commit 206ebaf32795cf1582b1e2ff2ec6a560c9e986b8
Workaround : http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git;a=commitdiff;h=15ac2d293b08b6975c6ca1a80eb839d4cb0dddbf
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

--
"Najbardziej brakowało mi twojego milczenia."
-- Andrzej Sapkowski "Coś więcej"



  parent reply	other threads:[~2007-05-29 12:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <465C188F.9000900@googlemail.com>
2007-05-29 12:52 ` [3/4] 2.6.22-rc3: known regressions Michal Piotrowski
2007-05-29 21:47   ` [PATCH] NOHZ: prevent multiplication overflow - stop timer for huge timeouts Thomas Gleixner
2007-05-29 23:02     ` David Miller
2007-05-31  2:33   ` [3/4] 2.6.22-rc3: known regressions Linus Torvalds
2007-05-31  4:51     ` Antonino A. Daplas
2007-05-31  5:54       ` Tero Roponen
2007-05-31  6:04         ` [PATCH] neofb: Fix pseudo_palette array overrun in neofb_setcolreg Antonino A. Daplas
2007-06-05 11:09         ` Antonino A. Daplas
2007-06-05 11:34         ` [PATCH] [RESEND] " Antonino A. Daplas
2007-05-29 12:53 ` Michal Piotrowski [this message]
2007-06-09 11:38   ` [4/4] 2.6.22-rc3: known regressions Mauro Carvalho Chehab
2007-05-29 12:56 ` [2/4] " Michal Piotrowski
2007-05-29 15:01   ` Stephen Hemminger
2007-05-31  2:22   ` Linus Torvalds
2007-05-31 22:08     ` Mike Miller (OS Dev)
2007-05-31 22:22       ` Linus Torvalds
2007-05-31 22:39         ` Mike Miller (OS Dev)
2007-05-31 22:50           ` Andrew Morton
2007-05-31 23:12             ` Linus Torvalds
2007-05-31 23:17               ` Roland Dreier
2007-05-31 23:34                 ` Andrew Morton

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=465C222C.3020203@googlemail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=discuss@x86-64.org \
    --cc=hverkuil@xs4all.nl \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=opslynx@gmail.com \
    --cc=robfitz@273k.net \
    --cc=torvalds@linux-foundation.org \
    --cc=tvolpiatt@neuf.fr \
    --cc=video4linux@list.redhat.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