linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gene Heskett <gheskett@shentel.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "linux-rt-users" <linux-rt-users@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Julia Cartwright <julia@ni.com>, Daniel Wagner <wagi@monom.org>,
	tom.zanussi@linux.intel.com
Subject: Re: [ANNOUNCE] 4.19.72-rt25
Date: Mon, 7 Oct 2019 15:16:04 -0400	[thread overview]
Message-ID: <201910071516.04269.gheskett@shentel.net> (raw)
In-Reply-To: <201910071510.05101.gheskett@shentel.net>

On Monday 07 October 2019 15:10:05 Gene Heskett wrote:

> On Monday 16 September 2019 17:39:21 Steven Rostedt wrote:
> > Dear RT Folks,
> >
> > I'm pleased to announce the 4.19.72-rt25 stable release.
> >
> > **** <NOTE> ****
> >
> > As you probably have noticed, it has been a long time since I
> > released a stable 4.19-rt. The reason for this delay is that one of
> > my tests failed after merging with the latest stable upstream. I
> > refuse to push releases with a known bug in it, so I figured I would
> > find the bug before releasing. I only spend around 4 to 6 hours a
> > week on upstream stable RT as I have other responsibilities, and I
> > could not debug this bug during that time (after several weeks of
> > trying).
> >
> > The bug is a random NULL pointer dereference that only happens with
> > lockdep enabled and on 32bit x86. I also found that this bug existed
> > before the latest stable pull release but now it is much easier to
> > trigger.
> >
> > I have not been able to trigger this bug in the 64 bit kernel, and
> > as I rather do a release than waste more time on this bug and
> > postpone the release further, I am now doing that. As a consequence,
> > I am no longer supporting 32bit x86, as it is known to have this
> > bug.
> >
> > If you are interested in this, I am willing to send out the config I
> > am using and one of the dmesg crashes. Just ask.
> >
> > **** </NOTE> ****
> >
> >
> > This release is just an update to the new stable 4.19.72 version
> > and no RT specific changes have been made.
> >
> >
> > You can get this release via the git tree at:
> >
> >  
> > git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
> >
> >   branch: v4.19-rt
> >   Head SHA1: 9cd04ab6a9a162ac4189a80032261d243563ff45
>
> =====================================================================
>
> > Or to build 4.19.72-rt25 directly, the following patches should be
> > applied:
> >
> >   http://www.kernel.org/pub/linux/kernel/v4.x/linux-4.19.tar.xz
> >
> >   http://www.kernel.org/pub/linux/kernel/v4.x/patch-4.19.72.xz
> >
> >
> > http://www.kernel.org/pub/linux/kernel/projects/rt/4.19/patch-4.19.7
> >2- rt25.patch.xz
>
> Unfortunately, this does not work for the pi3-4 family. When its all
> pulled in and patched, there is no arch/arm/configs bcm2709_defconfig
> or bcm2711_defconfig for either a pi3b or the new pi4b.
>
> I'll go find the 5.2.14 announce and see if its any more complete.
Its disappeared.

> > Enjoy,
> >
> > -- Steve
>
> Cheers, Gene Heskett


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

  reply	other threads:[~2019-10-07 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 21:39 [ANNOUNCE] 4.19.72-rt25 Steven Rostedt
2019-10-07 19:10 ` Gene Heskett
2019-10-07 19:16   ` Gene Heskett [this message]
2019-10-09  7:23     ` Alexander Dahl
2019-10-09 10:21       ` Gene Heskett

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=201910071516.04269.gheskett@shentel.net \
    --to=gheskett@shentel.net \
    --cc=C.Emde@osadl.org \
    --cc=bigeasy@linutronix.de \
    --cc=jkacur@redhat.com \
    --cc=julia@ni.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tom.zanussi@linux.intel.com \
    --cc=wagi@monom.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).