[arch-dev-public] kernel26 2.6.25-1 enters [testing]

[Andreas Radke]

Am Sun, 20 Apr 2008 10:27:02 +0200
schrieb Pierre Schmitz <pierre at archlinux.de>:

> Am Samstag, 19. April 2008 18:09:08 schrieb Thomas Bächler:
> > If there are any problems due to the configuration changes or new
> > kernel bugs, please let me know.
> 
> I got the following error when using the nvidia driver: 
> 
> 
> NVRM: bad caching on address 0xffff81007c91a000: actual 0x173 !=
> expected 0x17b
> NVRM: please see the README section on Cache Aliasing for more
> information NVRM: bad caching on address 0xffff81007c91b000: actual
> 0x173 != expected 0x17b
> NVRM: bad caching on address 0xffff81007cbad000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb4000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb5000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb6000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb7000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb8000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbb9000: actual 0x173 !=
> expected 0x17b
> NVRM: bad caching on address 0xffff81007cbba000: actual 0x173 !=
> expected 0x17b
> 
> Even when using the 173.08 beta driver which is meant for kernel
> 2.6.25 I got the same errors. Any ideas?

Same here:

NVRM: bad caching on address 0xffff81022ce78000: actual 0x173 != expected 0x17b
NVRM: please see the README section on Cache Aliasing for more information
NVRM: bad caching on address 0xffff81022ce79000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7a000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7b000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7c000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7d000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7e000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022ce7f000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022c47a000: actual 0x173 != expected 0x17b
NVRM: bad caching on address 0xffff81022cac1000: actual 0x173 !=
expected 0x17b

but seems to work fine so far.

-Andy