Bug#615103: Converting /etc/lilo.conf to UUID scheme generates world-readable file
Package: lilo Version: 1:23.1-1 Severity: grave Tags: security Justification: user security hole Hello, Today update of LiLo to version 1:23.1-1 also brought the conversion ot the old /dev/sdX paths in /etc/lilo.conf to libata compatible paths. While the installation itself went, well, I stumbled about a warning message from lilo after parsing the newly generated conffile: |Warning: /etc/lilo.conf should be readable only for root if using PASSWORD When checking file permissions afterwards, I found the file being world-readable: |blechtrottel:/etc# ls -l lilo.conf |-rw-r--r-- 1 root root 4617 25. Feb 19:18 lilo.conf This makes the protection via PASSWORD completely useless - if any logged in user can read /etc/lilo.conf, he could also change boot parameters of the system, e.g. booting his own OS. Best regards, Edgar -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-3-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 lilo depends on: ii debconf [debconf-2.0]1.5.38 Debian configuration management sy ii dpkg 1.15.8.10 Debian package management system ii libc62.11.2-11 Embedded GNU C Library: Shared lib ii libdevmapper1.02.1 2:1.02.48-5 The Linux Kernel Device Mapper use ii mbr 1.1.10-2Master Boot Record for IBM-PC comp lilo recommends no packages. Versions of packages lilo suggests: ii lilo-doc 1:23.1-1 LInux LOader - Documentation for t -- debconf information: liloconfig/fstab_broken: liloconfig/banner: liloconfig/use_lba32: true liloconfig/configuring_base: * lilo/diskid_uuid: true * lilo/runme: = false liloconfig/wipe_old_liloconf: false liloconfig/activate_error: lilo/new-config: lilo/link2: liloconfig/maintitle: liloconfig/mbr_error: liloconfig/lilo_warning: liloconfig/no_changes: * lilo/add_large_memory: false liloconfig/liloconf_incompatible: lilo/bad_bitmap: lilo/upgrade: liloconfig/liloconf_exists: * lilo/link1: liloconfig/use_current_lilo: true liloconfig/instruction: liloconfig/select_bitmap: /boot/debian.bmp liloconfig/lilo_error: liloconfig/odd_fstab: liloconfig/install_from_root_device: true liloconfig/make_active_partition: true liloconfig/install_mbr: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610638: boinc-client: Only partly fixed in 6.12.14+dfsg-1
Hello, I can confirm the fix - installed 6.12.15+dfsg-1 t'day and got no more error messages, so I'd suggest closing this bug. -- Best regards, Edgar Sippel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610638: boinc-client: Only partly fixed in 6.12.14+dfsg-1
Package: boinc-client Version: 6.12.14+dfsg-1 Severity: normal Today I updated to latest testing version 6.12.14+dfsg-1 and saw following dpkg output during update: |boinc-client (6.12.14+dfsg-1) wird eingerichtet ... | |Konfigurationsdatei »/etc/boinc-client/cc_config.xml« | == Modifiziert (von Ihnen oder von einem Skript) seit der Installation. | == Paketverteiler hat eine aktualisierte Version herausgegeben. | Wie möchten Sie vorgehen? Ihre Wahlmöglichkeiten sind: |Y oder I : Die Version des Paket-Betreuers installieren |N oder O : Die momentan installierte Version beibehalten | D : Die Unterschiede zwischen den Versionen anzeigen | Z : Eine Shell starten, um die Situation zu begutachten | Der Standardweg ist das Beibehalten der momentanen Version. |*** cc_config.xml (Y/I/N/O/D/Z) [Vorgabe=N] ? d |--- /etc/boinc-client/cc_config.xml 2011-01-28 20:53:45.0 +0100 |+++ /etc/boinc-client/cc_config.xml.dpkg-new2011-02-17 19:36:33.0 +0100 |@@ -27,7 +27,7 @@ [...] |-gui_rpc_debug0/gui_rpc_debug |+gui_rpc_debug0/guirpc_debug [...] |(END) So it seems as if somebody took care of this issue, but unfortunately not completely, so to get boinc-client working correctly still manual rework is necessary. Please correct also the close-tag. -- Package-specific info: -- Contents of /etc/default/boinc-client: # This file is /etc/default/boinc-client, it is a configuration file for the # /etc/init.d/boinc-client init script. # Set this to 1 to enable and to 0 to disable the init script. ENABLED=1 # Set this to 1 to enable advanced scheduling of the BOINC core client and # all its sub-processes (reduces the impact of BOINC on the system's # performance). SCHEDULE=1 # The BOINC core client will be started with the permissions of this user. BOINC_USER=boinc # This is the data directory of the BOINC core client. BOINC_DIR=/var/lib/boinc-client # This is the location of the BOINC core client, that the init script uses. # If you do not want to use the client program provided by the boinc-client # package, you can specify here an alternative client program. #BOINC_CLIENT=/usr/local/bin/boinc BOINC_CLIENT=/usr/bin/boinc # Here you can specify additional options to pass to the BOINC core client. # Type 'boinc --help' or 'man boinc' for a full summary of allowed options. #BOINC_OPTS=--allow_remote_gui_rpc BOINC_OPTS= -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-3-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 boinc-client depends on: ii adduser 3.112+nmu2 add and remove users and groups ii ca-certificates 20090814+nmu2Common CA certificates ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy ii libc6 2.11.2-11Embedded GNU C Library: Shared lib ii libcurl37.21.3-1 Multi-protocol file transfer libra ii libgcc1 1:4.4.5-10 GCC support library ii libssl0.9.8 0.9.8o-5 SSL shared libraries ii libstdc++6 4.4.5-10 The GNU Standard C++ Library v3 ii python 2.5.4-9 An interactive high-level object-o ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime boinc-client recommends no packages. Versions of packages boinc-client suggests: pn boinc-app-setinone (no description available) pn boinc-manager none (no description available) -- Configuration Files: /etc/boinc-client/cc_config.xml changed: !-- This is the configuration file cc_config.xml of the BOINC core client. For a complete list of all available options and logging flags and their meaning see: http://boinc.berkeley.edu/trac/wiki/ClientMessages -- cc_config options /options log_flags task1/task file_xfer1/file_xfer sched_ops1/sched_ops cpu_sched0/cpu_sched cpu_sched_debug0/cpu_sched_debug rr_simulation0/rr_simulation debt_debug0/debt_debug task_debug0/task_debug work_fetch_debug0/work_fetch_debug unparsed_xml0/unparsed_xml state_debug0/state_debug file_xfer_debug0/file_xfer_debug sched_op_debug0/sched_op_debug http_debug0/http_debug proxy_debug0/proxy_debug time_debug0/time_debug http_xfer_debug0/http_xfer_debug benchmark_debug0/benchmark_debug poll_debug0/poll_debug gui_rpc_debug0/gui_rpc_debug scrsave_debug0/scrsave_debug app_msg_send0/app_msg_send app_msg_receive0/app_msg_receive mem_usage_debug0/mem_usage_debug network_status_debug0/network_status_debug checkpoint_debug0/checkpoint_debug /log_flags /cc_config /etc/boinc-client/global_prefs_override.xml changed:
Bug#585695: nvidia-kernel-source: Manual built of module does not consider already set KVERS and KSRC environment variables
Package: nvidia-kernel-source Version: 195.36.24-1 Severity: important Tags: squeeze The latest change in debian/rules applies a new behaviour of the build script which makes manual building the module not working anymore according to documentation README.debian method #3: I'm using several different kernels on my machine, and normally I build the nvidia packages for all of them by just setting the respective environment variables KVERS and KSRC to the different values and then building the modules one after another manually by calling /usr/src/modules/nvidia-kernel/debian/rules binary_modules. The latest changes in version 195.36.24-2 do not consider these already set variables anymore but, as far as I understood the script takes the version from the target of /usr/src/linux, which, on my machine always points to the 'main' kernel, meaning the one currently in testing. So, compiling for different versions always needs a change of that symlink including the risk of letting this point to a wrong version afterwards when forgetting to re-set it. Please, either update the documentation to give the user a hint why building does not work as he's used to or (preferrably) let the script check if these variables are already set and consider them. Best regards, Edgar -- Package-specific info: uname -a: Linux blechtrottel 2.6.32-3-amd64 #1 SMP Thu Feb 25 07:33:41 UTC 2010 x86_64 GNU/Linux /proc/version: Linux version 2.6.32-3-amd64 (Debian 2.6.32-9) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Thu Feb 25 07:33:41 UTC 2010 /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 195.36.24 Thu Apr 22 19:10:14 PDT 2010 GCC version: gcc version 4.3.4 (Debian 4.3.4-10) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: nVidia Corporation G80 [GeForce 8800 GTS] [10de:0193] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:e825] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 25 Region 0: Memory at fd00 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at c000 (64-bit, prefetchable) [size=256M] Region 3: Memory at fa00 (64-bit, non-prefetchable) [size=32M] Region 5: I/O ports at bc00 [size=128] [virtual] Expansion ROM at fe6e [disabled] [size=128K] Capabilities: access denied Kernel driver in use: nvidia -- 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.32-3-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 nvidia-kernel-source depends on: ii debhelper 7.4.20 helper programs for debian/rules ii make 3.81-8 An utility for Directing compilati ii quilt 0.48-7 Tool to work with series of patche Versions of packages nvidia-kernel-source recommends: ii kernel-package 12.033 A utility for building Linux kerne ii module-assistant 0.11.3 tool to make module package creati ii nvidia-glx 195.36.24-1 NVIDIA binary Xorg driver ii nvidia-kernel-common 20100522+1 NVIDIA binary kernel module suppor nvidia-kernel-source suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560700: libnjb5: Deprecated SYSFS{}-syntax in /etc/udev/libnjb.rules
Package: libnjb5
Version: 2.2.5-4.2
Severity: important
Good afternoon,
today after upgrading udev to version 149-1 at next boot several warning
messages saying deprecated
SYSFS{}-syntax was used in udev RULES files ran over my screen - one source of
them is
/etc/udec/libnjb.rules where SYSFS{} is still used instead of ATTR{} or ATTRS{}.
As udev maintainer claims {SYSFS} support will be removed in future udev
versions, syntax should
be adopted to current udev syntax.
Best regards,
Edgar
-- 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.30-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 libnjb5 depends on:
ii libc62.10.2-2GNU C Library: Shared libraries
ii libusb-0.1-4 2:0.1.12-13 userspace USB programming library
ii udev 149-1 /dev/ and hotplug management daemo
libnjb5 recommends no packages.
libnjb5 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560703: libdjconsole-data: Deprecated SYSFS{}-syntax in /etc/udev/rules.d/45-hpdjconsole.rules
Package: libdjconsole-data
Version: 0.1.3-1
Severity: important
Good afternoon,
today after upgrading udev to version 149-1 a bunch of warning messages ran
over my screen at
next boot, complaining about deprecated SYSFS{}-syntax in udev RULES-files. One
source of them
was /etc/udev/rules.d/45-hpdjconsele.rules.
As udev maintainer claims to remove SYSFS{} support in future versions, please
switch to current
udev syntax using ATTR{} or ATTRS{}.
Best regards,
Edgar
-- 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.30-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
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519517: mixxx: Successor version 1.7.0 upstream released - please integrate
Package: mixxx Version: 1.6.1-1 Severity: normal Since Aug 6th 2009, a completely new version of mixxx is available upstream with many nice-to-have features, e.g. a completely new MIDI mapping and scripting system. Changelog from http://mixxxblog.blogspot.com/2009/08/mixxx-170-released.html: Improved MIDI device support: MIDI learning wizard MIDI mapping editor Upgraded, faster mapping system MIDI output now fully supported on Windows, OS X, and Linux. QtScript/JavaScript-based MIDI Scripting Environment - Script complex behaviour for your MIDI controller! Added full support for the Stanton SCS.3d and SCS.1m on all platforms. Hercules MK2 and RMX improvements Added Mixman DM2 mappings for Linux and OS X. Vinyl Control: Scratching responsiveness improved, with needle-skip prevention option added. Signal quality indicators added to vinyl control preferences. Improved support for soundcards with multiple stereo inputs Convenience features: The default skin is now widescreen, and fits nicely on netbook sized screens. Stereo master VU meter added. Cue points are now saved in the library for each track, with auto-recall cue option added to preferences. Support for more platforms: 64-Bit Windows and a Universal OS X package for 10.4+! Over 100 bug fixes and more! I would like to see this version in Debian - would it be possible to integrate? Best regards, Edgar Sippel -- 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.30-1-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 mixxx depends on: ii libasound2 1.0.20-4shared library for ALSA applicatio ii libc62.9-25 GNU C Library: Shared libraries ii libdjconsole00.1.3-1 Hercules DJ Console access library ii libgcc1 1:4.4.1-1 GCC support library ii libgl1-mesa-glx [lib 7.5.1-1 A free implementation of the OpenG ii libglu1-mesa [libglu 7.5.1-1 The OpenGL utility library (GLU) ii libid3tag0 0.15.1b-10 ID3 tag reading library from the M ii libmad0 0.15.1b-4 MPEG audio decoder library ii libogg0 1.1.4~dfsg-1Ogg bitstream library ii libportaudio219+svn20071022-3+b1 Portable audio I/O - shared librar ii libqt4-opengl4:4.5.2-2 Qt 4 OpenGL module ii libqt4-qt3support4:4.5.2-2 Qt 3 compatibility library for Qt ii libqt4-xml 4:4.5.2-2 Qt 4 XML module ii libqtcore4 4:4.5.2-2 Qt 4 core module ii libqtgui44:4.5.2-2 Qt 4 GUI module ii libsndfile1 1.0.18-2+squeeze1 Library for reading/writing audio ii libstdc++6 4.4.1-1 The GNU Standard C++ Library v3 ii libvorbis0a 1.2.0.dfsg-6The Vorbis General Audio Compressi ii libvorbisfile3 1.2.0.dfsg-6The Vorbis General Audio Compressi ii mixxx-data 1.6.1-1 Digital Disc Jockey Interface -- d mixxx recommends no packages. Versions of packages mixxx suggests: ii acroread [pdf-viewer] 9.1.3-0.2Adobe Acrobat Reader: Portable Doc ii kpdf [pdf-viewer] 4:3.5.9-3+lenny1 PDF viewer for KDE -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547483: cpufreqd: Please integrate new upstream release 2.3.4
On Sun, Sep 20, 2009 at 08:23:52PM +0900, Mattia Dongili wrote: On Sun, Sep 20, 2009 at 09:54:29AM +0200, Edgar Sippel wrote: [New upstream release] you're right... sorry for the long delay. Never mind... -Allow labels for sensor features this one is not and I agree it's a nice feature to have. ...this one is the one I'd like to have most - to give my S939 Opteron thermal throttling (which does not work without labels as my K8temp sensors do have corresponding names like my M/B sensors) (information from upstream homepage http://www.linux.it/~malattia/wiki/index.php/Cpufreqd) guess what, this is still me ;) Ooops, didn't check that anayway ;-) will do! Thank you very much in advance! -- Best regards, Edgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547483: cpufreqd: Please integrate new upstream release 2.3.4
Package: cpufreqd Version: 2.3.3-4 Severity: wishlist There's a new upstream release available (2.3.4) which contains at least two interesting changes: -Make the acpi thermal comaptible with kernels 2.6.25 when the type has changed from ACPI Thermal Zone to acpitz -Allow labels for sensor features (information from upstream homepage http://www.linux.it/~malattia/wiki/index.php/Cpufreqd) Please integrate new version to unstable. Best Regards, Edgar Sippel -- 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.30-1-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 cpufreqd depends on: ii libc6 2.9-25 GNU C Library: Shared libraries ii libcpufreq0 005-1 shared library to deal with the cp pn libsensors3 none (no description available) ii libsysfs2 2.1.0-6interface library to sysfs ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip Versions of packages cpufreqd recommends: ii acpid 1.0.10-2 Utilities for using ACPI power man Versions of packages cpufreqd suggests: ii cpufrequtils 005-1 utilities to deal with the cpufreq -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536337: linux-image-2.6.30-1-amd64: nvclock operation results in 'freeing invalid memtype' log entries
Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-2 Severity: normal 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' Regards, Edgar -- Package-specific info: ** Version: Linux version 2.6.30-1-amd64 (Debian 2.6.30-2) (wa...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-13) ) #1 SMP Wed Jul 8 15:21:55 UTC 2009 ** Command line: BOOT_IMAGE=Linux-2-6-30-1 ro root=303 ** Tainted: P (1) ** Kernel log: [28864.888038] nvclock:6778 freeing invalid memtype fd00-fd01 [28865.040181] nvclock:6778 freeing invalid memtype fd01-fd03 [28924.101033] nvclock:6857 freeing invalid memtype fd00-fd01 [28924.233081] nvclock:6857 freeing invalid memtype fd01-fd03 [28924.289240] nvclock:6861 freeing invalid memtype fd00-fd01 [28924.429425] nvclock:6861 freeing invalid memtype fd01-fd03 [28924.474341] nvclock:6867 freeing invalid memtype fd00-fd01 [28924.603614] nvclock:6867 freeing invalid memtype fd01-fd03 [28984.664436] nvclock:6928 freeing invalid memtype fd00-fd01 [28984.806426] nvclock:6928 freeing invalid memtype fd01-fd03 [28984.854532] nvclock:6932 freeing invalid memtype fd00-fd01 [28984.980851] nvclock:6932 freeing invalid memtype fd01-fd03 [29044.059480] nvclock:6995 freeing invalid memtype fd00-fd01 [29044.195242] nvclock:6995 freeing invalid memtype fd01-fd03 [29044.237527] nvclock:6999 freeing invalid memtype fd00-fd01 [29044.368627] nvclock:6999 freeing invalid memtype fd01-fd03 [29044.413498] nvclock:7005 freeing invalid memtype fd00-fd01 [29044.538449] nvclock:7005 freeing invalid memtype fd01-fd03 [29104.608367] nvclock:7071 freeing invalid memtype fd00-fd01 [29104.745610] nvclock:7071 freeing invalid memtype fd01-fd03 [29104.783266] nvclock:7075 freeing invalid memtype fd00-fd01 [29104.908636] nvclock:7075 freeing invalid memtype fd01-fd03 [29104.969708] nvclock:7081 freeing invalid memtype fd00-fd01 [29105.099919] nvclock:7081 freeing invalid memtype fd01-fd03 [29164.171520] nvclock:7146 freeing invalid memtype fd00-fd01 [29164.353930] nvclock:7146 freeing invalid memtype fd01-fd03 [29164.393648] nvclock:7150 freeing invalid memtype fd00-fd01 [29164.527312] nvclock:7150 freeing invalid memtype fd01-fd03 [29164.568785] nvclock:7156 freeing invalid memtype fd00-fd01 [29164.694058] nvclock:7156 freeing invalid memtype fd01-fd03 [29224.751051] nvclock:7222 freeing invalid memtype fd00-fd01 [29224.891105] nvclock:7222 freeing invalid memtype fd01-fd03 [29224.934732] nvclock:7226 freeing invalid memtype fd00-fd01 [29225.062021] nvclock:7226 freeing invalid memtype fd01-fd03 [29225.119322] nvclock:7232 freeing invalid memtype fd00-fd01 [29225.260869] nvclock:7232 freeing invalid memtype fd01-fd03 [29284.318228] nvclock:7289 freeing invalid memtype fd00-fd01 [29284.452801] nvclock:7289 freeing invalid memtype fd01-fd03 [29284.49] nvclock:7293 freeing invalid memtype fd00-fd01 [29284.624147] nvclock:7293 freeing invalid memtype fd01-fd03 [29284.666873] nvclock:7299 freeing invalid memtype fd00-fd01 [29284.793818] nvclock:7299 freeing invalid memtype fd01-fd03 [29344.862720] nvclock:7356 freeing invalid memtype fd00-fd01 [29345.002801] nvclock:7356 freeing invalid memtype fd01-fd03 [29345.044331] nvclock:7360 freeing invalid memtype fd00-fd01 [29345.173230] nvclock:7360 freeing invalid memtype fd01-fd03 [29404.242319] nvclock:7449 freeing invalid memtype fd00-fd01 [29404.393256] nvclock:7449 freeing invalid memtype fd01-fd03 [29404.440727] nvclock:7453 freeing invalid memtype fd00-fd01 [29404.569870] nvclock:7453 freeing invalid memtype fd01-fd03 [29404.613316] nvclock:7459 freeing invalid memtype fd00-fd01 [29404.743705] nvclock:7459 freeing invalid memtype fd01-fd03 [29464.817027] nvclock:7534 freeing invalid memtype fd00-fd01 [29464.989700] nvclock:7534 freeing invalid memtype fd01-fd03 [29465.033435] nvclock:7538 freeing invalid memtype fd00-fd01 [29465.166924] nvclock:7538 freeing invalid memtype fd01-fd03 [29465.221229] nvclock:7544 freeing invalid memtype fd00-fd01 [29465.366080] nvclock:7544 freeing invalid memtype fd01-fd03 [29524.431912] nvclock:7609 freeing invalid memtype fd00-fd01 [29524.613478] nvclock:7609 freeing invalid memtype fd01-fd03 [29524.652651] nvclock:7613 freeing invalid memtype fd00-fd01 [29524.780188] nvclock:7613 freeing invalid memtype fd01-fd03 [29584.848437] nvclock:7675 freeing invalid memtype fd00-fd01 [29585.030053]
Bug#536337: linux-image-2.6.30-1-amd64: nvclock operation results in 'freeing invalid memtype' log entries
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536337: linux-image-2.6.30-1-amd64: nvclock operation results in 'freeing invalid memtype' log entries
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 fd00-fd01 Jul 9 01:35:01 blechtrottel kernel: [ 6973.948144] nvclock:13257 freeing invalid memtype fd01-fd03 Jul 9 01:35:01 blechtrottel kernel: [ 6973.991183] nvclock:13261 freeing invalid memtype fd00-fd01 Jul 9 01:35:02 blechtrottel kernel: [ 6974.145357] nvclock:13261 freeing invalid memtype fd01-fd03 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: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525516: udev: eth0 stopped working - renamed to eth3 (driver: e100)
Same here, using kernel 2.6.29-1-686 from unstable.
Old entry in /etc/udev/rules.d/70-persistent-net.rules was
# PCI device 1039:0900 (sis900)
ACTION==add, SUBSYSTEM==net, DRIVERS==?*,
SYSFS{address}==00:0a:e6:d5:5f:99, NAME=eth0
which led, approximately due to the fact that the SYSFS entry is no more
recognized correctly by udev 0.141-1 to creating a new rule for the same
device
# PCI device 0x1039:0x0900 (sis900)
SUBSYSTEM==net, ACTION==add, DRIVERS==?*,
ATTR{address}==00:0a:e6:d5:5f:99, ATTR{type}==1, KERNEL==eth*,
NAME=eth1
and so the network interface was renamed from eth0 to eth1 (which had no
configuration in /etc/network/interfaces), resulting in system starting up
with no valid network interface at all after next reboot.
Isn't it possible to at least deploy a warning message to the user at udev
update, containing a hint that he SHALL review 70-persistent-net.rules for
entries containing deprecated values which may lead to non-working
networking?
--
Best regards,
Edgar Sippel
mailto:dont.spam...@gmx.de
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#372564: kwalletmanager very often crashes at KDE Logout
Package: kwalletmanager Version: 4:3.5.3-1 Followup-For: Bug #372564 I experience the same problem here on my system since the update to kdeutils-3.5.3; when I log on to KDE on my local machine kwalletmanager asks for the password (kontact and konqueror start automatically and request information from a wallet), after entering the password information is given, so it seems that the wallet has been opened, but the symbol in kicker never appears. When I'm ending the KDE session, either by 'Log off user' or by 'shut down system', I receive a SIGSEGV from kwalletmanager and the system hangs, mostly until the OK button is pressed, but I also experienced twice that I had to manually kill the X-server. It is not possible to manually start configuration of kwalletmanager by selecting from K-menu or by entering 'kwalletmanager %u' in a shell, only via the control center the settings for kwalletmanager can be reached. But when I start a KDE application remote via SSH -Y on my windows machine (there's the cygwin X server running), kwalletmanager starts normally, its icon is shown for the specified time and when I end the application kwalletmanager ends itself normally, too. Best regards, Edgar -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kwalletmanager depends on: ii kdelibs4c2a 4:3.5.3-1 core libraries and binaries for al ii libc6 2.3.6-13 GNU C Library: Shared libraries ii libgcc1 1:4.1.0-4 GCC support library ii libqt3-mt 3:3.3.6-2 Qt GUI Library (Threaded runtime v ii libstdc++64.1.0-4The GNU Standard C++ Library v3 kwalletmanager recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#325053: kernel-image-2.6.11-1-k7: USB Multimedia Keyboard IBM Rapid Access III - special keys have no function anymore
Package: kernel-image-2.6.11-1-k7 Version: 2.6.11-7 Severity: normal Hi there, today I upgraded my system from the sarge kernel 2.6.8-2-k7 to actual testing kernel 2.6.11-1-k7 and recognized after rebooting and reinstalling nvidia graphics driver that the special keys on my IBM Rapid Access III keyboard all have no function (showkey -s gives no output for them). With the former kernel 2.6.8-2-k7 also not all keys functioned, but at least the multimedia control keys an the Back- and Forward-Keys near the cursor-pad (as on IBM ThinkPads) were usuable. I don't know that much about usb keyboards and the hid-input driver, so I don't even know how to get any debug output. But if anyone can teach me how to see why the driver doesn't generate keycodes for these keys I could try do make them work again. Some information about the keyboard can be found on http://www-1.ibm.com/support/docview.wss?rs=0context=HW88Kq1=Rapid+Access+IIIuid=psg1MIGR-4V4QVCloc=de_DEcs=utf-8cc=delang=de+en Best regards, Edgar -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-image-2.6.11-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii fileutils 5.2.1-2The GNU file management utilities ii initrd-tools 0.1.81.1 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo kernel-image-2.6.11-1-k7 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
