From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel 2.6.32.60 64bit Crash/Hung
Date: Tue, 27 Jan 2015 06:34:35 -0800 [thread overview]
Message-ID: <20150127143435.GA31874@kroah.com> (raw)
In-Reply-To: <D76104AF467C9F418519BEF4906C06E40F6A5BF1@xmb-aln-x04.cisco.com>
On Tue, Jan 27, 2015 at 03:52:05AM +0000, Giridhara RP (grp) wrote:
> Hi Greg,
>
> Thanks for the quick turnaround. Which is the stable version? Kernel
> 2.6.32.60 was used in RHEL 6.2 and we thought this kernel version is
> stable.
What do you mean by "stable"?
Yes, it is "stable" if you have hardware that you bought before that
kernel was released, and you know how to support a kernel on your own,
but if you are doing this with newer hardware (as it seems you are), you
need to use a much newer kernel.
Again, the community can not help you out when you run old kernels like
this, only a company that you pay support to can (like Red Hat, if you
want to use their kernels, great, they will support you and you will pay
for it.)
So I strongly suggest, if you are doing this on your own, to use the
3.18 kernel release.
Best of luck,
greg k-h
next prev parent reply other threads:[~2015-01-27 14:34 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)
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 [this message]
2015-01-27 17:02 ` Giridhara RP (grp)
-- strict thread matches above, loose matches on Subject: below --
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=20150127143435.GA31874@kroah.com \
--to=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).