All of lore.kernel.org
 help / color / mirror / Atom feed
From: grp@cisco.com (Giridhara RP (grp))
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel 2.6.32.60 64bit Crash/Hung
Date: Tue, 27 Jan 2015 04:56:42 +0000	[thread overview]
Message-ID: <D76104AF467C9F418519BEF4906C06E40F6A5C87@xmb-aln-x04.cisco.com> (raw)
In-Reply-To: <12694.1422333909@turing-police.cc.vt.edu>

-----Original Message-----
From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks at vt.edu] 
Sent: Tuesday, January 27, 2015 10:15 AM
To: Giridhara RP (grp)
Cc: Greg KH; kernelnewbies at kernelnewbies.org
Subject: Re: Kernel 2.6.32.60 64bit Crash/Hung

On Tue, 27 Jan 2015 04:06:00 +0000, "Giridhara RP (grp)" said:

> Which kernel version should I use to solve this crash/panic?

That will depend on exactly why you're still running a 2.6.32 kernel from 6 years ago. Remember - the fact it's all the way up to 2.6.32.65 doesn't mean you have all the bugfixes.  It only means you have all the bugfixes that qualified for the -stable side of the fence (which is a small fraction of all the fixes that have happened in the past 6 years).

-----------------------
Hi Valdis,

We were running 2.6.32.60 assuming it's a stable build and my assumption was wrong :(. Should I go ahead with stable 3.18.3 [2015-01-16 ].

Thanks
Giri

  reply	other threads:[~2015-01-27  4:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  0:06 Kernel 2.6.32.60 64bit Crash/Hung Giridhara RP (grp)
2015-01-27  2:48 ` Greg KH
2015-01-27  3:52   ` Giridhara RP (grp)
2015-01-27  4:01     ` Valdis.Kletnieks at vt.edu
2015-01-27  4:06       ` Giridhara RP (grp)
2015-01-27  4:45         ` Valdis.Kletnieks at vt.edu
2015-01-27  4:56           ` Giridhara RP (grp) [this message]
2015-01-27  7:00             ` Anand Moon
2015-01-27  8:09               ` Giridhara RP (grp)
2015-01-27  8:25               ` Jan Niggemann
2015-01-27  8:37                 ` Hinnerk van Bruinehsen
2015-01-27 14:34     ` Greg KH
2015-01-27 17:02       ` Giridhara RP (grp)
2015-01-27  0:29 Giridhara RP (grp)
2015-01-30  5:36 Giridhara RP (grp)

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=D76104AF467C9F418519BEF4906C06E40F6A5C87@xmb-aln-x04.cisco.com \
    --to=grp@cisco.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.