Bug#536337: linux-image-2.6.30-1-amd64: nvclock operation results in 'freeing invalid memtype' log entries

[Edgar Sippel <for.your.spam.only@web.de>]

On Fri, Jul 10, 2009 at 09:08:53PM +0200, Bastian Blank wrote:

Thanks for your quick response,
 
> This means that nvclock access some address space, which have no valid
> definition. As it runs with root priviledges, it may do so via /dev/mem.
> Access to PCI resources is now handled via
> /sys/bus/pci/devices/$id/resource*.
 
does this mean there was a change in PCI device access in between 2.6.29 
and 2.6.30? Elder kernels do not show these logfile entries.
AFAIK is nvclock not run with root privileges in standard setup when... 

> > ** Tainted: P (1)
> 
> Using proprietary modules voids your waranty for the kernel.
> 

...the NVidia driver is used:
 -rwxr-xr-x 1 root root 113756 24. Feb 10:01 /usr/bin/nvclock
nvclock is called via script belonging to my user via cron:
* * * * * /home/justme/bin/fanspeed.sh
Best regards,
Edgar