Re: BIOS overwritten during resume (was: Re: Asus L5D resume on battery power)

[Pavel Machek]

Hi!

> > > It sounds to me like we run at 2GHz from batteries at resume time, and
> > > that causes bad things (tm),
> [-- snip --]
> 
> It seems that we write to the BIOS while moving the image, at least on my box,
> which is quite not correct, IMO.
...
> At the same time, from powernow-k8, I got this:
> 
> powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.00.09e)
> powernow-k8: found PSB header at 0xffff8100000fbb10
> 
> where ffff8100000fbb10 is the (virtual) address containing the PSB header
> (ie a part of the BIOS).  Hence, the PSB gets overwritten during resume (as
> well as some other BIOS stuff, it seems).
> 
> IMO this may lead to unexpected results, like the mysterious reboots during
> resume.

Well, I always thought that ROM-BIOS is expected to
be... well... read-only? Can you really write to your BIOS? [I know
about Flash-BIOSen, but they are certainly not writable by "normal"
write.] Plus we should overwrite it with same values...

Anyway, IMO bios should be marked as reserved (and we should not be
touching reserved pages). Can you verify that your BIOS is properly
marked reserved? [Ccing l-k, this might be interesting.]
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
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/