[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110712041938.GO27254@1wt.eu>
Date: Tue, 12 Jul 2011 06:19:38 +0200
From: Willy Tarreau <w@....eu>
To: "MINOURA Makoto / ?$BL'1: ?$B??" <minoura@...inux.co.jp>
Cc: john stultz <johnstul@...ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Faidon Liambotis <paravoid@...ian.org>,
linux-kernel@...r.kernel.org, stable@...nel.org,
Nikola Ciprich <nikola.ciprich@...uxbox.cz>,
seto.hidetoshi@...fujitsu.com,
Hervé Commowick <hcommowick@...sec.fr>,
Rand@...per.es
Subject: Re: 2.6.32.21 - uptime related crashes?
On Tue, Jul 12, 2011 at 11:49:57AM +0900, MINOURA Makoto / ?$BL'1: ?$B?? wrote:
>
> |> In <1310434819.30337.21.camel@...k-vm>
> |> john stultz <johnstul@...ibm.com> wrote:
>
> > I'm working on a debug patch that will hopefully trip sched_clock
> > overflows very early to see if we can't shake these issues out.
>
> Thanks. I hope that'll help.
That certainly will. What currently makes this bug hard to fix is that
it takes around 7 months to test a possible fix. We don't even know if
more recent kernels are affected, it's possible that 2.6.32-stable is
the only one that people don't reboot for an update in 7 months :-/
We need to make this bug more visible, so John's patch will be very
welcome !
Regards,
Willy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists