public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "S.Çağlar Onur" <caglar@CS.Princeton.EDU>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
	"stable@kernel.org" <stable@kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Song, Youquan" <youquan.song@intel.com>
Subject: Re: [stable] Boot failure with 2.6.27.46 on Xeon E5620 (Westmere EP)
Date: Thu, 3 Jun 2010 09:40:39 -0700	[thread overview]
Message-ID: <20100603164039.GA7177@kroah.com> (raw)
In-Reply-To: <2293F1A2-B4DE-4C15-9BAC-CC2E546943D0@CS.Princeton.EDU>

On Wed, Jun 02, 2010 at 07:54:29PM -0400, "S.Çağlar Onur" wrote:
> Hi Suresh,
> 
> On May 25, 2010, at 8:24 PM, Suresh Siddha wrote:
> 
> > On Tue, 2010-05-25 at 13:51 -0700, Greg KH wrote:
> >> On Tue, May 25, 2010 at 04:32:16PM -0400, "S.Çağlar Onur" wrote:
> >>> Hi Greg,
> >>> 
> >>> On May 25, 2010, at 11:53 AM, Greg KH wrote:
> >>> 
> >>>> On Tue, May 25, 2010 at 11:10:28AM -0400, "S.Çağlar Onur" wrote:
> >>>>> Hi,
> >>>>> 
> >>>>> We are observing boot failures [1] & [2] on some of our servers (Dell
> >>>>> r410) with 2.6.27-stable kernels. I found following commit in upstream
> >>>>> tree via a quick search (but I haven't tried it yet) so I don't know
> >>>>> whether I'm on the right track or not. 
> >>>>> 
> >>>>> Please let me know if anything else is needed...
> >>>> 
> >>>> Has any .27 kernel worked on these machines?  If so, can you narrow it
> >>>> down to the patch that caused the problem?
> >>> 
> >>> I don't think any .27 kernel worked on those machines before. But in
> >>> any case I'll try (I don't have a physical access to those machines as
> >>> they are located in China) an older .27 release to see.
> >> 
> >> Ok, so it isn't a regression, which is what I want to know.
> >> 
> >> New hardware like this, probably will only work on newer kernel
> >> versions, so please use those instead :)
> > 
> > I can't think of any known issues in 2.6.27 that can lead to this kind
> > of boot failure on WSM-EP. Caglar, It will be nice if you can do git
> > bisect between working and non-working kernels.
> 
> Neither 2.6.27 nor 2.6.27.45 not able to boot those servers, according
> to the on-site admins the boot stuck at following stage[1].

Good, it's not a regression :)

Care to upgrade to a newer kernel version and see if that works?

thanks,

greg k-h

  reply	other threads:[~2010-06-03 16:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25 15:10 Boot failure with 2.6.27.46 on Xeon E5620 (Westmere EP) "S.Çağlar Onur"
2010-05-25 15:53 ` [stable] " Greg KH
2010-05-25 20:32   ` "S.Çağlar Onur"
2010-05-25 20:51     ` Greg KH
2010-05-26  0:24       ` Suresh Siddha
2010-05-26  3:29         ` "S.Çağlar Onur"
2010-05-26 13:23           ` Youquan Song
2010-11-18 21:24             ` "S.Çağlar Onur"
2010-11-18 21:54               ` Greg KH
2010-11-18 21:59                 ` "S.Çağlar Onur"
2010-11-18 22:06                   ` Greg KH
2010-06-02 23:54         ` "S.Çağlar Onur"
2010-06-03 16:40           ` Greg KH [this message]
2010-06-03 17:50             ` "S.Çağlar Onur"

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=20100603164039.GA7177@kroah.com \
    --to=greg@kroah.com \
    --cc=caglar@CS.Princeton.EDU \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=youquan.song@intel.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