ose summary lines, I think the upstream changes are:
commit 08ec0c58fb8a05d3191d5cb6f5d6f81adb419798 (v2.6.38-rc1~480^2~1)
Author: John Stultz
Date: Tue Jul 27 17:00:00 2010 -0700
x86: Improve TSC calibration using a delayed workqueue
commit f12a15be63d1de9a35971f35f06b73088fa25c3a (v2.6.36
On Tue, 2011-11-29 at 13:26 +0100, Clarinet wrote:
> > Using an older "known-good" kernel, could you build and run the test
> > case at the end of Documentation/rtc.txt a few times and see if it
> > triggers the same problem?
> >
> > I'm suspicious that the setting the alarm is whats tripping the B
On Mon, 2011-11-21 at 22:31 +0100, Jiri Polach wrote:
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index cb9a104..77b5273 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -640,7 +640,7 @@ config HPET_TIMER
> > Choose N to continue using the legacy 8254 timer.
>
first bad commit was among them). Having this
> >>>> solved I have been able to bisect without "skipping". The result is
> >>>> surprising (at least for me) - believe it or not, the first bad commit
> >>>> is 6610e089 "RTC: Rework RTC code to use
On Fri, 2011-11-18 at 00:42 +0100, Jiri Polach wrote:
> On 11/17/2011 9:32 PM, John Stultz wrote:
> > On Wed, 2011-11-16 at 23:49 +0100, Clarinet wrote:
> >> Hi all,
> >>
> >>>> Result of bisecting: v2.6.38-rc1 exhibits the problem. v2.6.37 and
>
bootable and the first bad commit was among them). Having this
> solved I have been able to bisect without "skipping". The result is
> surprising (at least for me) - believe it or not, the first bad commit
> is 6610e089 "RTC: Rework RTC code to use timerqueue for events" fr
6 matches
Mail list logo
