mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nish.aravamudan@gmail.com
Cc: greg@kroah.com, linux-kernel@vger.kernel.org, akpm@osdl.org,
	torvalds@osdl.org, stable@kernel.org, sparclinux@vger.kernel.org
Subject: Re: Linux 2.6.20.3
Date: Tue, 13 Mar 2007 15:20:54 -0700 (PDT)	[thread overview]
Message-ID: <20070313.152054.31641425.davem@davemloft.net> (raw)
In-Reply-To: <29495f1d0703131458j18f9aee1tcd9a2b2ff6ecdf41@mail.gmail.com>

From: "Nish Aravamudan" <nish.aravamudan@gmail.com>
Date: Tue, 13 Mar 2007 14:58:24 -0700

> On 3/13/07, Nish Aravamudan <nish.aravamudan@gmail.com> wrote:
> > On 3/13/07, Greg KH <greg@kroah.com> wrote:
> > > We (the -stable team) are announcing the release of the 2.6.20.3 kernel.
> > > It contains a number of bugfixes and all 2.6.20 users are recommended to
> > > upgrade.
> > >
> > > The diffstat and short summary of the fixes are below.
> > >
> > > I'll also be replying to this message with a copy of the patch between
> > > 2.6.20.2 and 2.6.20.3.
> >
> > Compared to 2.6.20.1 (will try 2.6.20.2 as well), I now get:
> 
> err, duh -- this is a Sun Ultra 60, debian testing install.

Figure out if 2.6.20.2 does it too, then please try to git bisect
it down further.

I took a quick look and the two sparc64 commits between 2.6.20.1
and 2.6.20.2 are benign, a fix for E450 interrupts and a kenvctrld
fix which is for a driver for hardware your ultra60 doesn't have. :)

There is a decent amount of raid and nfs fixes in here, do you
use either?

Another commit that might be relevant is:

commit 530b09160744a12450fdacb2b78779c9830a29c8
Author: Aristeu Sergio Rozanski Filho <aristeu.sergio@gmail.com>
Date:   Thu Mar 1 19:02:55 2007 -0500

    tty_io: fix race in master pty close/slave pty close path

Hmmm...

Please let us know if you can narrow it down further.

  reply	other threads:[~2007-03-13 22:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-13 18:33 Greg KH
2007-03-13 18:34 ` Greg KH
2007-03-13 21:57 ` Nish Aravamudan
2007-03-13 21:58   ` Nish Aravamudan
2007-03-13 22:20     ` David Miller [this message]
2007-03-13 22:51       ` Nish Aravamudan
2007-03-14  0:29         ` Nish Aravamudan
2007-03-14  5:40           ` Bill Irwin
2007-03-14  5:41             ` David Miller
2007-03-14  5:40           ` David Miller
2007-03-14  1:29 ` mdew .

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=20070313.152054.31641425.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nish.aravamudan@gmail.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=stable@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

all inboxes | Powered by JetHome®