[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

Your message dated Sat, 13 Feb 2010 12:26:44 +0100
with message-id <20100213112644.GV2821@stro.at>
and subject line Re: Bug#536337: linux-image-2.6.30-1-amd64: nvclock operation results in 'freeing invalid memtype' log entries
has caused the Debian Bug report #536337,
regarding linux-image-2.6.30-1-amd64: nvclock operation results in 'freeing invalid memtype' log entries
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
536337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536337
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-1
Severity: normal


As my plain old NVidia graphics card operates its fan normally at full fan speed, I use a small script to set fanspeed temperature dependent via 'nvclock -f -F' once per minute. When using kernel 2.6.30-1-amd64, every script run causes dmesg and syslog entries like

Jul  9 01:35:01 blechtrottel kernel: [ 6973.776487] nvclock:13257 freeing invalid memtype fd000000-fd010000
Jul  9 01:35:01 blechtrottel kernel: [ 6973.948144] nvclock:13257 freeing invalid memtype fd010000-fd030000
Jul  9 01:35:01 blechtrottel kernel: [ 6973.991183] nvclock:13261 freeing invalid memtype fd000000-fd010000
Jul  9 01:35:02 blechtrottel kernel: [ 6974.145357] nvclock:13261 freeing invalid memtype fd010000-fd030000

I searched a little bit around and found http://lkml.org/lkml/2009/3/17/365 which looks a little bit like a similar issue, except that my machine seems to work normally except those log entries (glxgears shows same fps like on 2.6.29-2-amd64 where these logentries do NOT appear).

Regards,
Edgar

-- Package-specific info:

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.30-1-amd64 depends on:
ii  debconf [debconf-2.0]         1.5.26     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.93.3     tools for generating an initramfs
ii  module-init-tools             3.7-pre9-1 tools for managing Linux kernel mo

linux-image-2.6.30-1-amd64 recommends no packages.

Versions of packages linux-image-2.6.30-1-amd64 suggests:
ii  lilo                          1:22.8-7   LInux LOader - The Classic OS load
pn  linux-doc-2.6.30              <none>     (no description available)

-- debconf information:
  linux-image-2.6.30-1-amd64/preinst/initrd-2.6.30-1-amd64:
  linux-image-2.6.30-1-amd64/postinst/create-kimage-link-2.6.30-1-amd64: true
  linux-image-2.6.30-1-amd64/preinst/abort-overwrite-2.6.30-1-amd64:
  linux-image-2.6.30-1-amd64/postinst/kimage-is-a-directory:
  linux-image-2.6.30-1-amd64/preinst/lilo-initrd-2.6.30-1-amd64: true
  linux-image-2.6.30-1-amd64/prerm/removing-running-kernel-2.6.30-1-amd64: true
  linux-image-2.6.30-1-amd64/preinst/elilo-initrd-2.6.30-1-amd64: true
  linux-image-2.6.30-1-amd64/postinst/depmod-error-2.6.30-1-amd64: false
  linux-image-2.6.30-1-amd64/preinst/failed-to-move-modules-2.6.30-1-amd64:
  linux-image-2.6.30-1-amd64/postinst/old-system-map-link-2.6.30-1-amd64: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.30-1-amd64/postinst/bootloader-error-2.6.30-1-amd64:
  linux-image-2.6.30-1-amd64/preinst/lilo-has-ramdisk:
  linux-image-2.6.30-1-amd64/postinst/old-dir-initrd-link-2.6.30-1-amd64: true
  linux-image-2.6.30-1-amd64/postinst/old-initrd-link-2.6.30-1-amd64: true
  linux-image-2.6.30-1-amd64/prerm/would-invalidate-boot-loader-2.6.30-1-amd64: true
  linux-image-2.6.30-1-amd64/preinst/bootloader-initrd-2.6.30-1-amd64: true
  linux-image-2.6.30-1-amd64/preinst/overwriting-modules-2.6.30-1-amd64: true
  linux-image-2.6.30-1-amd64/postinst/depmod-error-initrd-2.6.30-1-amd64: false
  linux-image-2.6.30-1-amd64/preinst/abort-install-2.6.30-1-amd64:
  linux-image-2.6.30-1-amd64/postinst/bootloader-test-error-2.6.30-1-amd64:

--- End Message ---
--- Begin Message --- 
On Sat, 11 Jul 2009, Edgar Sippel wrote:

> 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*.
>  

closing as this is not a linux-2.6 bug.
thanks for your report.
 
> > > ** Tainted: P (1)
> > 
> > Using proprietary modules voids your waranty for the kernel.
> > 
>

--- End Message ---
Reply to: