public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Ben Collins <ben.collins@ubuntu.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Daniel Holbach <daniel.holbach@ubuntu.com>
Subject: Re: 2.6.20-rc2: known unfixed regressions
Date: Fri, 29 Dec 2006 20:25:25 +0100	[thread overview]
Message-ID: <20061229192525.GU20714@stusta.de> (raw)
In-Reply-To: <1167415630.5348.599.camel@gullible>

On Fri, Dec 29, 2006 at 01:07:10PM -0500, Ben Collins wrote:
> On Thu, 2006-12-28 at 23:39 +0100, Adrian Bunk wrote:
> > This email lists some known regressions in 2.6.20-rc2 compared to 2.6.19.
> > 
> > If you find your name in the Cc header, you are either submitter of one
> > of the bugs, maintainer of an affectected subsystem or driver, a patch
> > of you caused a breakage or I'm considering you in any other way possibly
> > involved with one or more of these issues.
> > 
> > Due to the huge amount of recipients, please trim the Cc when answering.
> 
> > Subject    : i386: Oops in __find_get_block()
> > References : http://lkml.org/lkml/2006/12/16/138
> > Submitter  : Ben Collins <ben.collins@ubuntu.com>
> >              Daniel Holbach <daniel.holbach@ubuntu.com>
> > Status     : unknown
> 
> I believe this is the same bug as I've seen reported about gdb. I'd have
> to find the thread/information regarding it. Not sure if it was fixed
> already.

Subject    : BUG at fs/buffer.c:1235 when using gdb
References : http://lkml.org/lkml/2006/12/17/134
Submitter  : Andrew J. Barr <andrew.james.barr@gmail.com>
Fixed-By   : Jeremy Fitzhardinge <jeremy@goop.org>
Commit     : 8701ea957dd2a7c309e17c8dcde3a64b92d8aec0
Status     : fixed in -rc2

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-12-29 19:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-24  4:49 Linux 2.6.20-rc2 Linus Torvalds
2006-12-24 13:58 ` Alessandro Suardi
2006-12-24 14:49   ` Jeff Garzik
2006-12-24 17:13 ` Andreas Schwab
2006-12-25 21:02 ` swsusp testing wanted (was Re: Linux 2.6.20-rc2) Pavel Machek
2006-12-28 22:31 ` 2.6.20-rc2: known regressions with patches available Adrian Bunk
2006-12-28 22:39 ` 2.6.20-rc2: known unfixed regressions Adrian Bunk
2006-12-28 22:57   ` Greg KH
2006-12-28 23:07     ` Adrian Bunk
2006-12-28 23:17       ` Linus Torvalds
2006-12-28 23:30         ` Greg KH
2006-12-29  1:36   ` Horst H. von Brand
2006-12-29  4:51     ` David Miller
2006-12-29 12:58       ` Adrian Bunk
2006-12-29 12:53     ` Adrian Bunk
2006-12-29 18:07   ` Ben Collins
2006-12-29 19:25     ` Adrian Bunk [this message]
2006-12-30  1:21       ` Horst H. von Brand
2006-12-30  1:57         ` Adrian Bunk
2006-12-29 18:14   ` Daniel Barkalow
2006-12-29 19:22     ` Adrian Bunk
2006-12-29 20:18       ` Daniel Barkalow
2006-12-31  0:47 ` 2.6.20-rc2: known unfixed regressions (v2) Adrian Bunk
2006-12-31  9:44   ` Ismail Dönmez

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=20061229192525.GU20714@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=ben.collins@ubuntu.com \
    --cc=daniel.holbach@ubuntu.com \
    --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