[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080820035130.38426b00.billfink@mindspring.com>
Date: Wed, 20 Aug 2008 03:51:30 -0400
From: Bill Fink <billfink@...dspring.com>
To: "Yinghai Lu" <yhlu.kernel@...il.com>
Cc: "David Witbrodt" <dawitbro@...global.net>,
"Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
"Peter Zijlstra" <peterz@...radead.org>,
"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 -- found another user
with the same regression
On Tue, 19 Aug 2008, Yinghai Lu wrote:
> On Tue, Aug 19, 2008 at 9:51 PM, David Witbrodt <dawitbro@...global.net> wrote:
> > While reading drivers/char/hpet.c and looking at the functions
> > used there, I discovered request_region(), and realized that it
> > would be difficult to compare the entire iomem_resource tree to
> > a dummy tree only containing resources added by insert_resource()
> > and request_resource(). It might be simpler to have my tiny
> > e820_reserve_resources() replacement add each resource to 3 trees
> > -- the real iomem_resource tree, and 2 dummy trees -- which could
> > then be compared for differences just before the kernel locks up.
>
> with reverting patch that change insert_resource to request_resource...
> 2.6.26 or 2.6.27-rcX still hange somewhere.
This is true if he reverted just the 3def3d6d... commit, but if he
also reverts the similar, and immediately following, 1e934dda...
commit, then his 2.6.26 kernel runs fine.
-Bill
--
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