Re: HPET regression in 2.6.26 versus 2.6.25

[David Witbrodt]

Had a bit of a scare tonight, about possibly wasting the time of you
good folks.

My desktop machine (mboard = Gigabyte GA-M59SLI-S5) was built last
year, in May 2007.  It runs 2.6.26 with no HPET regression, as mentioned.

The troublesome machine (mboard = ECS AMD690GM-M2) was built this year,
in May or June.  I actually bought two identical motherboards, which
were on sale at a very nice price, so I could make 2 "servers" for my
home network.

One machine (call it "fileserver") is in working order, and is the
machine I've been using for all of the testing I've done in this bug
thread.  The other ECS machine (call it "webserver") was not really
in working condition -- actually, it is OK, just not hooked up while
I've been backing up files from an older Pentium 4 machine and a
Pentium 3 machine.

The "scare" has to do with the CPU/BIOS situation.  The webserver uses
an AMD Athlon 64 X2 3600+, fully recognized by the mboard BIOS.  The 
fileserver uses a very new model:  AMD X2 4850e.  The ECS mboard runs
this CPU fine, but the BIOS does not "recognize" it.

I asked ECS about the possibility of a BIOS update in early June.  The
response:
=========================

ECS Support(USA) Posted : GMT 2008/06/14 00:19:14
Thank for your question. It is hard to say if there will be a BIOS 
version to support your CPU. But for sure we will pass this along to 
the engineering department in Taipei. Thanks.
=========================

The last update for this mboard I know of was from Dec. 2007:
http://www.ecsusa.com/ECSWebSite/Products/ProductsDetail.aspx?detailid=789&DetailName=Bios&MenuID=46&LanID=9

Tonight, fearing that some peculiarity of the CPU might be causing the
problem instead of the motherboard hardware itself, I got the other
machine (ECS mboard + Athlon 64 X2 3600) running and tested the
2.6.27-rc1 kernel on it:  froze on boot, but ran with "hpet=disabled".

Well, at least I'm glad I didn't waste everybody's time on some weird 
exception.  Of course, this bug is not really a problem for me at all 
at the present:  I can easily run 2.6.25 kernels on these two boxes, and
even 2.6.26+ kernels with "hpet=disabled" if need be.  I just would like
to see this issue fixed on the hardware I own, thinking in terms of the
future.  The Debian Developers are trying to get 2.6.26 into the next 
stable release, but right now it looks like anyone with this ECS 
motherboard who would try to install Linux from media with 2.6.26 would 
have a seizure... their machine, that is.  ;)


Dave W.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/