On Fri, Jul 10, 2009 at 07:14:03PM +0200, Edgar Sippel wrote:
> As to be seen below, this behaviour still continues after upgrading to latest
> version 2.6.30-2
> - every run of nvclock results in a bunch of logfile entries complaining
> about 'freeing invalid
> memtype'
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*.
> ** Tainted: P (1)
Using proprietary modules voids your waranty for the kernel.
Bastian
--
It would be illogical to assume that all conditions remain stable.
-- Spock, "The Enterprise Incident", stardate 5027.3
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
