Bug#561203: threads and fork on machine with VIPT-WB cache
On Fri, Jun 04, 2010 at 12:44:55PM +0200, Thibaut VARENE wrote:
> On Fri, Jun 4, 2010 at 7:21 AM, dann frazier <firstname.lastname@example.org> wrote:
> > On Fri, Jun 04, 2010 at 10:03:07AM +0900, NIIBE Yutaka wrote:
> >> Modestas Vainius wrote:
> >>>> Note that Debian's buildds run a UP kernel, so as soon as those fixes
> >>>> go upstream we can pull them in. Thanks for all your work here!
> >>> Well, as long as this is unfixed or at least "common", I don't see how hppa
> >>> can be considered to be a release arch. Is that UP patch available somewhere?
> >> My case and my analysis talked about UP kernel, and John David Anglin
> >> made a patch:
> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561203#144
> >> After that, the discussion went to SMP cases.
> >> It would be better to evaluate the patch again, and make sure it works
> >> for UP case and fix failures of buildd, then apply for Linux in Debian
> >> (only) for HPPA.
> >> I know that the patch is not that ideal because it touches
> >> architecture independent part of Linux, but it is worth for Linux in
> >> Debian (or Linux for the HPPA machine of buildd, at least).
> > I'm happy to test the patch if necessary to help push this change
> > upstream. However, we do need the change to go upstream before we can
> > include it in the Debian kernel.
> Just for reference, I've summarized the test cases and related patches here:
Cool - that is helpful. I've updated the kernel on peri/penalosa with
the various patches listed there that have gone upstream, but I'm not
seeing better results with any failing packages.
btw, I thought it would be useful to edit that page and tag each patch
with its status in Debian (in-official-kernel, installed-on-buildds,
etc), but the page appears to be immutable.