linux-kernel - Re: HPET regression in 2.6.26 versus 2.6.25 -- experimental revert for 2.6.27 failed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 12 Aug 2008 17:31:07 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"David Witbrodt" <dawitbro@...global.net>
Cc:	linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	"Peter Zijlstra" <peterz@...radead.org>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, netdev <netdev@...r.kernel.org>
Subject: Re: HPET regression in 2.6.26 versus 2.6.25 -- experimental revert for 2.6.27 failed

On Tue, Aug 12, 2008 at 5:00 PM, David Witbrodt <dawitbro@...global.net> wrote:
> SUMMARY
>
> 1.  Ran 'git remote update', then built kernels for origin/master
> (Linus' linux-2.6 tree) and tip/master.  Both froze.
>
> 2.  Attempted a revert against tip/master, but the files involved
> changed quite a bit.  I _was_ able to build the kernel successfully,
> but it froze.  There have simply been too many changes since Feb. 22
> for my naive approach to work.
>
> 3.  When the revert failed, I panicked:  I thought that I might
> truly have made a mistake with the original 'git bisect' process
> I carried out.  After retracing the last few iterations of the
> process -- building and checking the last 3 kernels -- I found
> that the information I posted here WAS correct:  the problem
> commit # was the one I had found the first time.
>
> 4.  To see if I am totally incompetent, I used git to checkout the
> version of the sources at the problem commit, and then reverted
> those changes (same method used in step 2).  The kernel built
> and ran just fine:  no freeze, no need for "hpet=disabled".

can you post /proc/iomem?

YH
--
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/