Bug#583895: linux-image-2.6.32-5-xen-amd64: does not boot Package: linux-2.6 Version: 2.6.32-13 Severity: important
Kind of hard to debug without console output indeed. Does the kernel boot without xen? Have you tried 2.6.32-27? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/84sjyzm589@sauna.l.org
Bug#593245: linux-image-2.6.32-5-xen-amd64_2.6.32-20_amd64.deb can't start VM's due to udev rule mismatch
With $ dpkg-query -W linux-image-$(uname -r) linux-image-2.6.32-5-xen-amd64 2.6.32-27 I see $ find /dev|grep evt /dev/.udev/db/misc:xen/evtchn /dev/xen/evtchn Does everything work if you create evtchn manually with mknod /dev/xen/evtchn c 10 57? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/84oc9nm4zi@sauna.l.org
Bug#603835: linux-image-2.6.32-5-amd64: page allocation failures while transferring data with virtio
On Wed, 2010-11-17 at 23:57 +, Ben Hutchings wrote: On Wed, 2010-11-17 at 19:44 +0100, Frederik Himpe wrote: Package: linux-2.6 Version: 2.6.32-27 Severity: important I've got a KVM virtual machine which is using bacula-fd to back-up its files to another virtual machine. Regularly, while back-ing up, backtraces start appearing in the kernel logs and bacula-fd starts eating up a huge amount of memory. [...] And why is it the kernel's fault if bacula eats all the memory? If the only problem is that bacula is eating all memory, than the kernel OOM kernel should kill it instead of letting virtio networking die. However, seeing how much similar problem reports with page allocation failures in virtio there are on the web, not involving bacula, I would rather suspect the problem is in virtio itself. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576838#69 also indicates that this bug was actually not fixed in reality, and that using another network driver works around the problem. -- Frederik Himpe fhi...@vub.ac.be Vrije Universiteit Brussel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1290067067.29412.4.ca...@defected.localdomain
Processed (with 1 errors): blank
Processing commands for cont...@bugs.debian.org: package xen-linux-system-2.6.32-5-xen-amd64 Limiting to bugs with field 'package' containing at least one of 'xen-linux-system-2.6.32-5-xen-amd64' Limit currently set to 'package':'xen-linux-system-2.6.32-5-xen-amd64' reassign 602935 linux-2.6 Bug #602935 [xen-linux-system-2.6.32-5-xen-amd64] xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27 Bug reassigned from package 'xen-linux-system-2.6.32-5-xen-amd64' to 'linux-2.6'. package: linux-2.6' does not match at least one of xen-linux-system-2.6.32-5-xen-amd64 Failed to clear fixed versions and reopen on 602935: limit failed for bugs: 602935. thanks Stopping processing here. Please contact me if you need assistance. -- 602935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.12900682776953.transcr...@bugs.debian.org
Bug#602418: linux-image-2.6.32-5-xen-amd64: with xen 4.0, fork()/clone() fails with ENOMEM during X startup with nv driver
On Thu, Nov 18, 2010 at 09:40:43AM +0200, Timo Juhani Lindfors wrote: Hmm. So you are running an X server in the dom0 or in a domU? In the dom0. -- Lionel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101118081905.gc24...@capsaicin.mamane.lu
Processed: blank
Processing commands for cont...@bugs.debian.org: package xen-linux-system-2.6.32-5-xen-amd64 linux-2.6 Limiting to bugs with field 'package' containing at least one of 'xen-linux-system-2.6.32-5-xen-amd64', 'linux-2.6' Limit currently set to 'package':'xen-linux-system-2.6.32-5-xen-amd64', 'linux-2.6' reassign 602935 linux-2.6 Bug #602935 [linux-2.6] xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27 Ignoring request to reassign bug #602935 to the same package thanks Stopping processing here. Please contact me if you need assistance. -- 602935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129006985915529.transcr...@bugs.debian.org
Bug#603670: early kernel panic as node under kvm (div-by-zero in pvclock_tsc_khz)
Hi again, with qemu-kvm from experimental (0.13.0+dfsg-2) you can use: -cpu kvm64,-kvmclock as kvm option to disable kvmclock. for libvirt use the following in your domain config: domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' ... qemu:commandline qemu:arg value='-cpu'/ qemu:arg value='kvm64,-kvmclock'/ /qemu:commandline /domain (You may have to replace kvm64 with another cpu model) I tried using clocksource= in the linux boot commandline, and had no luck with any value i tried. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ce4f06a.6040...@stbuehler.de
Bug#602418: linux-image-2.6.32-5-xen-amd64: with xen 4.0, fork()/clone() fails with ENOMEM during X startup with nv driver
On Thu, 2010-11-18 at 09:19 +0100, Lionel Elie Mamane wrote: On Thu, Nov 18, 2010 at 09:40:43AM +0200, Timo Juhani Lindfors wrote: Hmm. So you are running an X server in the dom0 or in a domU? In the dom0. Please could you try the kernel at http://xenbits.xen.org/people/ianc/ and see if it resolves your issue. (it's currently -26 based and I really should rebase to -27 but I don't think your issue is new in -27 so it's an interesting experiment) Ian. -- Ian Campbell Numeric stability is probably not all that important when you're guessing. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1290072791.31507.5192.ca...@zakaz.uk.xensource.com
Bug#603903: initramfs-tools: Documentation for modules=list in initramfs.conf is unclear
Package: initramfs-tools Version: 0.98.5 Severity: normal Tags: patch The documentation is vague about how the list of modules is derived. Hopefully this makes things clearer without requiring the user to delve into the source code Cheers, Tim. --- /tmp/initramfs.conf.orig2010-11-18 10:12:43.176859335 + +++ /tmp/initramfs.conf 2010-11-18 10:26:11.172917839 + @@ -8,13 +8,16 @@ # # MODULES: [ most | netboot | dep | list ] # +# Modules listed in /etc/initramfs-tools/modules and +# /usr/share/initramfs-tools/modules.d/* are always loaded. +# # most - Add most filesystem and all harddrive drivers. # # dep - Try and guess which modules to load. # # netboot - Add the base modules, network modules, but skip block devices. # -# list - Only include modules from the 'additional modules' list +# list - Only modules explicity listed in /etc/initramfs-tools/modules etc. # MODULES=most --- /tmp/initramfs.conf.5.orig 2010-11-18 10:08:00.093469868 + +++ /tmp/initramfs.conf.5 2010-11-18 10:27:48.585080195 + @@ -22,6 +22,10 @@ .TP \fB MODULES Specifies the modules for the initramfs image. + +Modules listed in \fI/etc/initramfs-tools/modules\fP and +\fI/usr/share/initramfs-tools/modules.d/*\fP are always loaded. + The default setting is \fImost\fP. \fImost\fP adds most file system, all ide, sata, scsi and usb drivers. @@ -30,8 +34,8 @@ \fInetboot\fP adds the base modules, network modules, but skips block devices. -\fIlist\fP includes only modules from the additional modules list to load them -early. +\fIlist\fP don't load any additional modules beyond those contained in +\fI/etc/initramfs-tools/modules\fP etc. .TP \fB BUSYBOX -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101118102935.13178.52075.report...@ermintrude.seoss.co.uk
Bug#583895: linux-image-2.6.32-5-xen-amd64: does not boot Package: linux-2.6 Version: 2.6.32-13 Severity: important
I confirm this is fixed now. Il giorno 18/nov/2010, alle ore 09.00, Timo Juhani Lindfors ha scritto: Kind of hard to debug without console output indeed. Does the kernel boot without xen? Have you tried 2.6.32-27? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/63ab7870-d1c2-4cd0-a819-ed2ca06f0...@fantacast.it
Bug#583895: marked as done (linux-image-2.6.32-5-xen-amd64: does not boot Package: linux-2.6 Version: 2.6.32-13 Severity: important)
Your message dated Thu, 18 Nov 2010 12:57:16 +0200 with message-id 84zkt6lx0z@sauna.l.org and subject line Re: linux-image-2.6.32-5-xen-amd64: does not boot Package: linux-2.6 Version: 2.6.32-13 Severity: important has caused the Debian Bug report #583895, regarding linux-image-2.6.32-5-xen-amd64: does not boot Package: linux-2.6 Version: 2.6.32-13 Severity: important 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 ow...@bugs.debian.org immediately.) -- 583895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-5-xen-amd64 Information provided here is from -13 since -14 fails to boot on this host. Unfortunately this is a colocated box so I do not have access to the console on boot to troubleshoot the issue. Unfortunately -13 is unusable too due to the netback uevent bug which prevents domUs from allocating virtual interfaces, as you can see from the kernel log. -12 is the last usable version for me. I am not sure if there is a way to debug boot issues without console access. Luca -- Package-specific info: ** Version: Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-13) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-10) ) #1 SMP Mon May 17 20:24:46 UTC 2010 ** Command line: root=/dev/sda1 ro console=tty0 ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 144.996881] block drbd1: conn( Unconnected - WFConnection ) [ 221.819339] IPv6 addrconf: prefix with wrong length 56 [ 343.429706] IPv6 addrconf: prefix with wrong length 56 [ 543.892635] IPv6 addrconf: prefix with wrong length 56 [ 744.420344] IPv6 addrconf: prefix with wrong length 56 [ 944.920444] IPv6 addrconf: prefix with wrong length 56 [ 1145.428152] IPv6 addrconf: prefix with wrong length 56 [ 1345.929270] IPv6 addrconf: prefix with wrong length 56 [ 1546.501395] IPv6 addrconf: prefix with wrong length 56 [ 1747.014514] IPv6 addrconf: prefix with wrong length 56 [ 1947.591862] IPv6 addrconf: prefix with wrong length 56 [ 2148.048379] IPv6 addrconf: prefix with wrong length 56 [ 2348.549435] IPv6 addrconf: prefix with wrong length 56 [ 2549.103801] IPv6 addrconf: prefix with wrong length 56 [ 2749.562366] IPv6 addrconf: prefix with wrong length 56 [ 2950.068159] IPv6 addrconf: prefix with wrong length 56 [ 3150.577516] IPv6 addrconf: prefix with wrong length 56 [ 3294.415920] IPv6 addrconf: prefix with wrong length 56 [ 3307.428029] block drbd1: Handshake successful: Agreed network protocol version 91 [ 3307.428093] block drbd1: conn( WFConnection - WFReportParams ) [ 3307.428183] block drbd1: Starting asender thread (from drbd1_receiver [1738]) [ 3307.428603] block drbd1: data-integrity-alg: not-used [ 3307.428690] block drbd1: drbd_sync_handshake: [ 3307.428726] block drbd1: self E87601C33D2B727A:BEDA1E33B761AB23:1FBC064966A8E907:7011F55EB6036E4A bits:0 flags:0 [ 3307.428790] block drbd1: peer BC611BE8E01B6E2E:BEDA1E33B761AB23:1FBC064966A8E907:7011F55EB6036E4A bits:0 flags:0 [ 3307.428854] block drbd1: uuid_compare()=100 by rule 90 [ 3307.428889] block drbd1: Split-Brain detected, dropping connection! [ 3307.428928] block drbd1: helper command: /sbin/drbdadm split-brain minor-1 [ 3307.433802] block drbd1: meta connection shut down by peer. [ 3307.433840] block drbd1: conn( WFReportParams - NetworkFailure ) [ 3307.433881] block drbd1: asender terminated [ 3307.433914] block drbd1: Terminating drbd1_asender [ 3307.442684] block drbd1: helper command: /sbin/drbdadm split-brain minor-1 exit code 0 (0x0) [ 3307.442745] block drbd1: conn( NetworkFailure - Disconnecting ) [ 3307.442785] block drbd1: error receiving ReportState, l: 4! [ 3307.443952] block drbd1: Connection closed [ 3307.443991] block drbd1: conn( Disconnecting - StandAlone ) [ 3307.444085] block drbd1: receiver terminated [ 3307.444118] block drbd1: Terminating drbd1_receiver [ 3307.449363] block drbd1: role( Secondary - Primary ) [ 3308.126611] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [ 3308.126684] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [ 3308.130157] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [ 3308.130228] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. [ 3308.192821] physdev match: using
Processed: blank
Processing commands for cont...@bugs.debian.org: package linux-2.6 Limiting to bugs with field 'package' containing at least one of 'linux-2.6' Limit currently set to 'package':'linux-2.6' retitle 592487 linux-image-2.6.32-5-xen-686: dom0 under virtualbox: APIC write causes WARNING Bug #592487 [linux-2.6] linux-image-2.6.32-5-xen-686: dump Changed Bug title to 'linux-image-2.6.32-5-xen-686: dom0 under virtualbox: APIC write causes WARNING' from 'linux-image-2.6.32-5-xen-686: dump' thanks Stopping processing here. Please contact me if you need assistance. -- 592487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129007895528229.transcr...@bugs.debian.org
Bug#603811: (no subject)
anyone to help me with this problem? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ce518a9.2020...@gmail.com
Bug#603811: linux-image-2.6.26-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds)
You meantion SCHED_IDLE only in the subject but don't elaborate it in the bug report itself. What do you mean by it exactly? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/84r5eilskc@sauna.l.org
Bug#603858: Mount options for proc conflict with /etc/fstab breaking /etc/init.d/mountall.sh
severity 603858 important thanks Steve Langasek vor...@debian.org writes: On Wed, Nov 17, 2010 at 11:04:15PM +0100, Goswin von Brederlow wrote: Package: initramfs-tools Version: 0.93.4 Severity: critical File: /usr/share/initramfs-tools/init Tags: patch How in the world does this count as critical? The /etc/init.d/mountall.sh script reports a red FAILED because of that. This is the only symptom you describe, and that's certainly not critical! Usualy a FAILED message also means the script returns an error, which in turn means insserv stops executing depending scripts in that runlevel and skips to the next. Looking closer at the script I see now that mountall.sh does not report errors through its exit code. So it just makes it impossible to see if something real failed to mount because proc always fails to mount. Sorry for the severity. MfG Goswin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87eiaissyj@frosties.localnet
Processed: Re: Bug#603858: Mount options for proc conflict with /etc/fstab breaking /etc/init.d/mountall.sh
Processing commands for cont...@bugs.debian.org: severity 603858 important Bug #603858 [initramfs-tools] Mount options for proc conflict with /etc/fstab breaking /etc/init.d/mountall.sh Ignoring request to change severity of Bug 603858 to the same value. thanks Stopping processing here. Please contact me if you need assistance. -- 603858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.129008420622667.transcr...@bugs.debian.org
Bug#603903: initramfs-tools: Documentation for modules=list in initramfs.conf is unclear
On Thu, Nov 18, 2010 at 10:29:35AM +, Tim Small wrote: Package: initramfs-tools Version: 0.98.5 Severity: normal Tags: patch The documentation is vague about how the list of modules is derived. Hopefully this makes things clearer without requiring the user to delve into the source code Cheers, Tim. thanks a lot very appreciated. --- /tmp/initramfs.conf.orig 2010-11-18 10:12:43.176859335 + +++ /tmp/initramfs.conf 2010-11-18 10:26:11.172917839 + @@ -8,13 +8,16 @@ # # MODULES: [ most | netboot | dep | list ] # +# Modules listed in /etc/initramfs-tools/modules and +# /usr/share/initramfs-tools/modules.d/* are always loaded. +# # most - Add most filesystem and all harddrive drivers. # # dep - Try and guess which modules to load. # # netboot - Add the base modules, network modules, but skip block devices. # -# list - Only include modules from the 'additional modules' list +# list - Only modules explicity listed in /etc/initramfs-tools/modules etc. # not sure if that is overly verbose for a config file, will wait on verdict of comaintainer. MODULES=most --- /tmp/initramfs.conf.5.orig2010-11-18 10:08:00.093469868 + +++ /tmp/initramfs.conf.5 2010-11-18 10:27:48.585080195 + @@ -22,6 +22,10 @@ .TP \fB MODULES Specifies the modules for the initramfs image. + +Modules listed in \fI/etc/initramfs-tools/modules\fP and +\fI/usr/share/initramfs-tools/modules.d/*\fP are always loaded. + ok cool The default setting is \fImost\fP. \fImost\fP adds most file system, all ide, sata, scsi and usb drivers. @@ -30,8 +34,8 @@ \fInetboot\fP adds the base modules, network modules, but skips block devices. -\fIlist\fP includes only modules from the additional modules list to load them -early. +\fIlist\fP don't load any additional modules beyond those contained in +\fI/etc/initramfs-tools/modules\fP etc. .TP \fB BUSYBOX you scratch the important _early_ and repost a possible location. not sure, this should be reworded without the location and by keeping the early. can you do a second pass? just the manpage is a good start, can allways merge the other seperately. thank you -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101118124604.gf27...@vostochny.stro.at
Bug#603811: (no subject)
On Thu, Nov 18, 2010 at 01:14:33PM +0100, masterdead wrote: anyone to help me with this problem? you were asked to properly submit info with reportbug. currently there is zero info related to up to date 2.6.32 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101118130016.gg27...@vostochny.stro.at
Bug#581715: Ok, I paste inline
Sorry!!!
Here my configuration files.
Ciao, Filippo.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental') Architecture: i386 (i686)
Kernel: Linux 2.6.33-2-686 (SMP w/1 CPU core)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages eeepc-acpi-scripts depends on:
ii acpi-support 0.137-5scripts for handling many
ACPI eve ii acpi-support-base 0.137-5scripts for
handling base ACPI eve ii acpid 1:2.0.6-1
Advanced Configuration and Power I ii pm-utils
1.3.0-2utilities and scripts for power ma ii
rfkill0.4-1 tool for enabling and
disabling wi
eeepc-acpi-scripts recommends no packages.
Versions of packages eeepc-acpi-scripts suggests:
ii alsa-utils1.0.23-3 Utilities for configuring
and usin pn libnotify-bin none (no description
available)
-- Configuration Files:
/etc/acpi/actions/hotkey.sh changed:
PKG=eeepc-acpi-scripts
FUNC_LIB=/usr/share/$PKG/functions.sh
DEFAULT=/etc/default/$PKG
[ -e $FUNC_LIB ] || exit 0
case $(runlevel) in
*0|*6)
exit 0
;;
esac
BACKLIGHT=/sys/class/backlight/eeepc/brightness
if [ -e $DEFAULT ]; then . $DEFAULT; fi
. $FUNC_LIB
. /etc/acpi/lib/notify.sh
code=$3
value=$(test x$1 = x- cat $BACKLIGHT || echo 0x$3)
acpi=
acpiwrite=
ACPITEST=/lib/init/rw/eeepc-acpi-scripts.acpi-ignore
case $code in
# Soft buttons 3 4 are special.
# They're always reported as hotkeys (901, at least).
# This will probably break when button events are added for these
keys. 001[cd])
;;
*)
if test -f $ACPITEST; then
read acpi $ACPITEST
else
acpiwrite=$(test x$1 = x- echo hotkey || echo -)
fi
test $1 = $acpi exit 0
;;
esac
seen_hotkey() { test $acpi = button; }
handle_mute_toggle() {
/etc/acpi/actions/volume.sh toggle
}
handle_volume_up() {
/etc/acpi/actions/volume.sh up
}
handle_volume_down() {
/etc/acpi/actions/volume.sh down
}
show_wireless() {
if /etc/acpi/actions/wireless.sh detect; then
status=Off
else
status=On
fi
notify wireless Wireless $status
}
handle_blank_screen() {
if [ -S /tmp/.X11-unix/X0 ]; then
detect_x_display
if [ -n $XAUTHORITY ]; then
xset dpms force off
fi
fi
}
show_bluetooth() {
if bluetooth_is_on; then
notify bluetooth 'Bluetooth On'
else
notify bluetooth 'Bluetooth Off'
fi
}
handle_bluetooth_toggle() {
. /etc/acpi/lib/bluetooth.sh
if [ -e $BT_CTL ] || [ $BLUETOOTH_FALLBACK_TO_HCITOOL =
yes ]; then toggle_bluetooth
show_bluetooth
else
notify error 'Bluetooth unavailable'
fi
}
show_camera() {
if camera_is_on; then
notify camera 'Camera Enabled'
else
notify camera 'Camera Disabled'
fi
}
handle_camera_toggle() {
. /etc/acpi/lib/camera.sh
if [ -e $CAM_CTL ]; then
toggle_camera
show_camera
else
notify error 'Camera unavailable'
fi
}
show_brightness() {
# final digit of ACPI code is brightness level in hex
level=$(($value 0xF))
# convert hex digit to percent
percent=$(((100 * $level + 8) / 15))
notify brightness Brightness $percent% fast
}
handle_shengine() {
. /etc/acpi/lib/shengine.sh
handle_shengine $@
}
handle_touchpad_toggle() {
. /etc/acpi/lib/touchpad.sh
toggle_touchpad
case $? in
0)
notify touchpad 'Touchpad on'
;;
1)
notify touchpad 'Touchpad off'
;;
esac
}
handle_vga_toggle() {
/etc/acpi/actions/vga-toggle.sh
}
handle_gsm_toggle() {
/etc/acpi/actions/gsm.sh toggle
if /etc/acpi/actions/gsm.sh detect; then
notify gsm GSM off
else
notify gsm GSM on
fi
}
case $(cat /sys/class/dmi/id/product_name) in
[79]*|1000H)
case $code in
ZOOM)
code=001b # soft button 2
;;
esac
;;
*)
case $code in
ZOOM)
code=0038 # Fn-F4
;;
esac
;;
esac
case $code in
# Fn + key:
# 700/900-series key/1000-series key - function
# -- = not available
# F1/F1 - suspend
# (not a hotkey, not handled here)
# F2/F2 - toggle wireless
001[01]|WLAN)
notify wireless 'Wireless ...'
if grep -q '^H.*\brfkill\b' /proc/bus/input/devices; then
:
else
/etc/acpi/actions/wireless.sh toggle
fi
show_wireless
if ! /etc/acpi/actions/wireless.sh detect; then
wakeup_wicd
fi
;;
# --/F3 - touchpad toggle
0037)
if [ ${FnF_TOUCHPAD} != 'NONE' ]; then
Re: Security: auto-loading protocol modules
On Thu, 2010-11-18 at 03:33 +, Ben Hutchings wrote: [...] +alias net-pf-36 af_802154 I have no idea of the security state of this. I was able to create AF_IEEE802154 sockets on system with no suitable devices. According to Vince Sanders who works on both Linux and 802.15.4 hardware though not yet together, The guys who submited it did so despite our objections and their reserch project ended there and then. The commit log doesn't show any work by the current maintainers in the last year, though there has been some recent work in their git repository. I think this alias should also be removed for now. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#603811: (no subject)
i forgot symptoms: System randomly unresponsive, sometimes keyboard input will yield repeated keystrokes. SSH session will stop echoing. And basically system freezes over to 2-10 minutes. I believe this bug relates to #517449 Proper report witch reportbug? How to? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ce52e92.3080...@gmail.com
Processed: tagging 602078
Processing commands for cont...@bugs.debian.org: tags 602078 - moreinfo Bug #602078 [linux-2.6] linux-image-2.6.36-trunk-amd64: Wake-up does a full restart ! Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 602078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128991513810557.transcr...@bugs.debian.org
Bug#603811: (no subject)
On Thu, Nov 18, 2010 at 02:48:02PM +0100, masterdead wrote: i forgot symptoms: System randomly unresponsive, sometimes keyboard input will yield repeated keystrokes. SSH session will stop echoing. And basically system freezes over to 2-10 minutes. I believe this bug relates to #517449 Proper report witch reportbug? How to? boot latest 2.6.32, open a console and send in from a console: reportbug -N 603811 as you have been already told yesterday. No I won't repeat myself a third time. We do not have access to cristall balls telling us the state of your box. thank you. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101118144553.gh27...@vostochny.stro.at
linux-kbuild-2.6_2.6.36-1~experimental.1_multi.changes ACCEPTED into experimental
Accepted: linux-kbuild-2.6.36_2.6.36-1~experimental.1_i386.deb to main/l/linux-kbuild-2.6/linux-kbuild-2.6.36_2.6.36-1~experimental.1_i386.deb linux-kbuild-2.6_2.6.36-1~experimental.1.diff.gz to main/l/linux-kbuild-2.6/linux-kbuild-2.6_2.6.36-1~experimental.1.diff.gz linux-kbuild-2.6_2.6.36-1~experimental.1.dsc to main/l/linux-kbuild-2.6/linux-kbuild-2.6_2.6.36-1~experimental.1.dsc linux-kbuild-2.6_2.6.36.orig.tar.gz to main/l/linux-kbuild-2.6/linux-kbuild-2.6_2.6.36.orig.tar.gz Override entries for your package: linux-kbuild-2.6.36_2.6.36-1~experimental.1_i386.deb - optional devel linux-kbuild-2.6_2.6.36-1~experimental.1.dsc - source devel Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pj6a2-dc...@franck.debian.org
Processed: reopening 572535
Processing commands for cont...@bugs.debian.org:
reopen 572535
Bug #572535 {Done: Rene Engelhard r...@debian.org} [linux-2.6] btrfs-tools:
Wrong size shown of btrfs partition after migrating from ext4
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
572535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.129010130322577.transcr...@bugs.debian.org
Bug#603944: retry mounting of root
Package: initramfs-tools
Version: 0.98
When using multipath, it is possible that mountroot() will race with
udev's renaming of /dev/disk/by-uuid/{rootfs-uuid} from /dev/sd?? to
/dev/mapper/something. After multipath has grabbed the /dev/sd?? and
until udev completes the rename, mounting
/dev/disk/by-uuid/{rootfs-uuid} will fail with -EBUSY.
Here is a patch I've been using successfully for awhile. Colin Watson
has suggested that:
A poll/retry loop is generally a suboptimal way to do this kind of
thing; what we really want is to wait for udev to tell us that it has
finished with the event that triggered renaming of the device.
which does seem cleaner.
thanks,
-serge
diff -Nru initramfs-tools-0.98ubuntu2/debian/changelog
initramfs-tools-0.98ubuntu3/debian/changelog
--- initramfs-tools-0.98ubuntu2/debian/changelog2010-08-20
03:48:58.0 -0500
+++ initramfs-tools-0.98ubuntu3/debian/changelog2010-08-24
22:31:31.0 -0500
@@ -1,3 +1,14 @@
+initramfs-tools (0.98ubuntu3) maverick; urgency=low
+
+ * Add retries to mountroot(). This is particularly needed when we
+use multipath, because it is possible that mountroot() will race
+with udev's renaming of /dev/disk/by-uuid/{rootfs-uuid} from
+/dev/sd?? to /dev/mapper/something. After multipath has grabbed
+the /dev/sd?? and until udev completes the rename, mounting
+/dev/disk/by-uuid/{rootfs-uuid} will fail with -EBUSY.
+
+ -- Serge Hallyn serge.hal...@canonical.com Tue, 24 Aug 2010 22:17:57 -0500
+
initramfs-tools (0.98ubuntu2) maverick; urgency=low
* The ramzswap device changed its interface so that the disk size needs to
diff -Nru initramfs-tools-0.98ubuntu2/scripts/local
initramfs-tools-0.98ubuntu3/scripts/local
--- initramfs-tools-0.98ubuntu2/scripts/local 2010-08-20 03:48:58.0
-0500
+++ initramfs-tools-0.98ubuntu3/scripts/local 2010-08-24 22:16:17.0
-0500
@@ -86,10 +86,19 @@
# FIXME This has no error checking
[ -n ${FSTYPE} ] modprobe ${FSTYPE}
- # FIXME This has no error checking
# Mount root
- mount ${roflag} ${FSTYPE:+-t ${FSTYPE} }${ROOTFLAGS} ${ROOT} ${rootmnt}
- mountroot_status=$?
+ tries=0
+ ret=1
+ while [ $tries -lt 10 -a $ret -ne 0 ]; do
+ mount ${roflag} ${FSTYPE:+-t ${FSTYPE} }${ROOTFLAGS} ${ROOT}
${rootmnt}
+ ret=$?
+ if [ $ret -ne 0 ]; then
+ echo failed attempt $tries to mount $ROOT as root
+ sleep 1
+ tries=$((tries+1))
+ fi
+ done
+ mountroot_status=$ret
if [ $LOOP ]; then
if [ $mountroot_status != 0 ]; then
if [ ${FSTYPE} = ntfs ] || [ ${FSTYPE} = vfat ]; then
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101118174249.ga24...@hallyn.com
Re: Minutes of the Debian linux-2.6 Group Meeting
On Thu, Nov 18, 2010 at 11:23:39 -0800, Kees Cook wrote: On Thu, Nov 11, 2010 at 13:52:12 +, maximilian attems wrote: LSM: Enable AppArmor? as well as/instead of Tomoyo? --- As the LSM need to be built we can't enable them. This needs a technical solution were code can be disregarded as init sections or similar. AppArmor seems more popular as Opensuse and Ubuntu uses it. Technicaly Tomoyo is said to be cleaner. What do you mean by can't here? You can build _all_ of them, actually. The active LSM is just selected at boot-time through the kernel command line arguments. If it's a concern over kernel size, upstream specifically removed the ability to make the LSM modular, so this means that no additional LSMs will ever be available in Debian? See the second sentence. This needs a technical solution where code can be disregarded as init sections or similar. So your kernel has a bunch of LSMs builtin, but at boot time one of them is selected and you release the memory taken by the rest of them instead of keeping the code lying there unused. Cheers, Julien signature.asc Description: Digital signature
Re: Minutes of the Debian linux-2.6 Group Meeting
On Thu, Nov 11, 2010 at 13:52:12 +, maximilian attems wrote: LSM: Enable AppArmor? as well as/instead of Tomoyo? --- As the LSM need to be built we can't enable them. This needs a technical solution were code can be disregarded as init sections or similar. AppArmor seems more popular as Opensuse and Ubuntu uses it. Technicaly Tomoyo is said to be cleaner. What do you mean by can't here? You can build _all_ of them, actually. The active LSM is just selected at boot-time through the kernel command line arguments. If it's a concern over kernel size, upstream specifically removed the ability to make the LSM modular, so this means that no additional LSMs will ever be available in Debian? NX bit emulation and 32-bit mmap randomization -- We don't want to carry intrusive patches. The NX patch was rejected as such by upstream and thus we won't take it either. Why? These patches are well maintained, and touch areas of the kernel that do not change much (making them very easy to merge). Why leave non-PAE x86 users out in the code when so many other distros use some form of this patchset? I've worked to make sure they only touch CONFIG_X86_32, so they're extremely minimal. Currently we recommend PAE for bigger boxes but do not default to it. Action item by bwh and waldi to default Debian Installer to it and deprecate non PAE 686. This sounds great, regardless. Upstream status of the other patch is unknown, maks will consult Kees. In my mind, they[1] are a single patch -- the 32-bit mmap randomization is better named ASCII Armor ASLR, which doesn't have much value, IMO. The entropy is extremely low compared to upstream ASLR, but it would be actually 0 if left out in the nx-emu case. As such, it is only enabled on systems that are using nx-emu. I intend to try to get it upstreamed, but it's pretty far down on my TODO list[1]. Thanks, -Kees [1] http://git.kernel.org/?p=linux/kernel/git/frob/linux-2.6-roland.git;a=shortlog;h=refs/heads/fedora/x86-nx-emulation http://git.kernel.org/?p=linux/kernel/git/frob/linux-2.6-roland.git;a=shortlog;h=refs/heads/fedora/32bit-mmap-exec-randomization (this one is still missing one additional patch from me...) [2] https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening#Upstream%20Hardening -- Kees Cook@debian.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101118192339.gf13...@outflux.net
Re: Minutes of the Debian linux-2.6 Group Meeting
On Thu, Nov 18, 2010 at 11:23:39AM -0800, Kees Cook wrote: On Thu, Nov 11, 2010 at 13:52:12 +, maximilian attems wrote: LSM: Enable AppArmor? as well as/instead of Tomoyo? --- As the LSM need to be built we can't enable them. This needs a technical solution were code can be disregarded as init sections or similar. AppArmor seems more popular as Opensuse and Ubuntu uses it. Technicaly Tomoyo is said to be cleaner. What do you mean by can't here? You can build _all_ of them, actually. The active LSM is just selected at boot-time through the kernel command line arguments. If it's a concern over kernel size, upstream specifically removed the ability to make the LSM modular, so this means that no additional LSMs will ever be available in Debian? Julien already explained what this is about. We don't like to bloat the kernel with features that most people won't use. (It was controversial enough when we built IPv6 in.) And each possible LSM will only be used by a minority of users. NX bit emulation and 32-bit mmap randomization -- We don't want to carry intrusive patches. The NX patch was rejected as such by upstream and thus we won't take it either. Why? These patches are well maintained, and touch areas of the kernel that do not change much (making them very easy to merge). Why leave non-PAE x86 users out in the code when so many other distros use some form of this patchset? I've worked to make sure they only touch CONFIG_X86_32, so they're extremely minimal. [...] Then you should convince upstream that these are good and unintrusive. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101118200555.gf8...@decadent.org.uk
Re: Minutes of the Debian linux-2.6 Group Meeting
On Thu, Nov 18, 2010 at 12:03:33PM -0800, Kees Cook wrote: Hi, On Thu, Nov 18, 2010 at 08:37:44PM +0100, Julien Cristau wrote: On Thu, Nov 18, 2010 at 11:23:39 -0800, Kees Cook wrote: On Thu, Nov 11, 2010 at 13:52:12 +, maximilian attems wrote: LSM: Enable AppArmor? as well as/instead of Tomoyo? --- As the LSM need to be built we can't enable them. This needs a technical solution were code can be disregarded as init sections or similar. AppArmor seems more popular as Opensuse and Ubuntu uses it. Technicaly Tomoyo is said to be cleaner. What do you mean by can't here? You can build _all_ of them, actually. The active LSM is just selected at boot-time through the kernel command line arguments. If it's a concern over kernel size, upstream specifically removed the ability to make the LSM modular, so this means that no additional LSMs will ever be available in Debian? See the second sentence. This needs a technical solution where code can be disregarded as init sections or similar. So your kernel has a bunch of LSMs builtin, but at boot time one of them is selected and you release the memory taken by the rest of them instead of keeping the code lying there unused. Right, my point was that upstream expressly moved away from that ability, which means, if combined with the other only if in upstream statements, the Debian kernel will only ever be built with one LSM. Now, don't get me wrong, I'd hugely prefer there be an __init-like way to handle this, and it actually touches on the constification work too. Still, blocking until the feature exists seems unfun. :) I'm intending to work on this feature myself (and submit it upstream). Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101118200650.gg8...@decadent.org.uk
Re: Minutes of the Debian linux-2.6 Group Meeting
Hi, On Thu, Nov 18, 2010 at 08:37:44PM +0100, Julien Cristau wrote: On Thu, Nov 18, 2010 at 11:23:39 -0800, Kees Cook wrote: On Thu, Nov 11, 2010 at 13:52:12 +, maximilian attems wrote: LSM: Enable AppArmor? as well as/instead of Tomoyo? --- As the LSM need to be built we can't enable them. This needs a technical solution were code can be disregarded as init sections or similar. AppArmor seems more popular as Opensuse and Ubuntu uses it. Technicaly Tomoyo is said to be cleaner. What do you mean by can't here? You can build _all_ of them, actually. The active LSM is just selected at boot-time through the kernel command line arguments. If it's a concern over kernel size, upstream specifically removed the ability to make the LSM modular, so this means that no additional LSMs will ever be available in Debian? See the second sentence. This needs a technical solution where code can be disregarded as init sections or similar. So your kernel has a bunch of LSMs builtin, but at boot time one of them is selected and you release the memory taken by the rest of them instead of keeping the code lying there unused. Right, my point was that upstream expressly moved away from that ability, which means, if combined with the other only if in upstream statements, the Debian kernel will only ever be built with one LSM. Now, don't get me wrong, I'd hugely prefer there be an __init-like way to handle this, and it actually touches on the constification work too. Still, blocking until the feature exists seems unfun. :) Thanks, -Kees -- Kees Cook@debian.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101118200333.gg13...@outflux.net
Re: Minutes of the Debian linux-2.6 Group Meeting
On Thu, Nov 18, 2010 at 08:06:50PM +, Ben Hutchings wrote: On Thu, Nov 18, 2010 at 12:03:33PM -0800, Kees Cook wrote: Now, don't get me wrong, I'd hugely prefer there be an __init-like way to handle this, and it actually touches on the constification work too. Still, blocking until the feature exists seems unfun. :) I'm intending to work on this feature myself (and submit it upstream). Great! That'll be nice to have. -Kees -- Kees Cook@debian.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101118200933.gi13...@outflux.net
Re: Minutes of the Debian linux-2.6 Group Meeting
On Thu, Nov 18, 2010 at 08:05:55PM +, Ben Hutchings wrote: On Thu, Nov 18, 2010 at 11:23:39AM -0800, Kees Cook wrote: Why? These patches are well maintained, and touch areas of the kernel that do not change much (making them very easy to merge). Why leave non-PAE x86 users out in the code when so many other distros use some form of this patchset? I've worked to make sure they only touch CONFIG_X86_32, so they're extremely minimal. [...] Then you should convince upstream that these are good and unintrusive. I intend to, but I'm certainly not the only one who can attempt it. I was hoping to get more people looking at and using the code as a first step. -Kees -- Kees Cook@debian.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101118201059.gj13...@outflux.net
Bug#603957: linux-2.6: consider raising CONFIG_HZ to 1000
Package: linux-2.6 Version: 2.6.32-27 Severity: wishlist Hi, I think I mentioned this a while back on irc, but filing here for reference. clock_gettime(CLOCK_MONOTONIC) is expensive, so people want to use CLOCK_MONOTONIC_COARSE instead. See e.g. http://lists.x.org/pipermail/xorg-devel/2010-August/012483.html However X would like millisecond granularity, which means HZ=1000 instead of the current 250, in order to be able to use the coarse timer. Maybe something to consider for wheezy? Cheers, Julien -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature
Bug#582975: Getting GPU hung here too
Hi! I started to get GPU hung problems here too (with X being killed). dmesg says: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 28966 at 28956) and the xorg log is attached. Kernel is a 2.6.36 vanilla. Package versions: ii xserver-common2:1.7.7-9 common files used by various X servers ii xserver-xorg 1:7.5+8 the X.Org X server ii xserver-xorg-core 2:1.7.7-9Xorg X server - core server ii xserver-xorg-input-evdev 1:2.3.2-6 X.Org X server -- evdev input driver ii xserver-xorg-input-kbd1:1.4.0-2 X.Org X server -- keyboard input driver ii xserver-xorg-input-mouse 1:1.5.0-2 X.Org X server -- mouse input driver ii xserver-xorg-input-synaptics 1.2.2-2 Synaptics TouchPad driver for X.Org server ii xserver-xorg-video-intel 2:2.13.0-2 X.Org X server -- Intel i8xx, i9xx display driver Can I give more info or do anything else to help, please? Thank you! Best regards, Nelson X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.25-dsa-ia32 i686 Debian Current Operating System: Linux orthrus 2.6.36.naoliv1 #1 SMP PREEMPT Thu Oct 21 01:21:37 BRST 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.36.naoliv1 root=/dev/sda5 ro quiet Build Date: 12 November 2010 12:21:56AM xorg-server 2:1.7.7-9 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.21.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Nov 18 23:51:40 2010 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device Generic Video Card (**) |--Input Device Generic Keyboard (**) |--Input Device Configured Mouse (**) |--Input Device Synaptics Touchpad (**) Option DontZap off (**) Option BlankTime 3 (**) Option StandbyTime 5 (**) Option SuspendTime 7 (**) Option OffTime 10 (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/X11R6/lib/X11/fonts/misc does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi/ does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/Type1 does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/100dpi does not exist. Entry deleted from font path. (WW) The directory /usr/X11R6/lib/X11/fonts/75dpi does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (**) Extension Composite is enabled (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. (WW) Disabling Generic Keyboard (WW) Disabling Configured Mouse (II) Loader magic: 0x81ecca0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:0:2:0) 8086:27a2:1028:01d4 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xeff0/524288, 0xd000/268435456, 0xefec/262144, I/O @ 0xeff8/8 (--) PCI:
Bug#603981: initramfs-tools: Load PowerMac G5 thermal modules
Package: initramfs-tools
Version: 0.98.5
Severity: important
Tags: patch
On iMac and PowerMac G5 machines, about a minute after boot, fans run at
full speed producing jet engine noise. Thermal modules do not get loaded
as they were in Lenny.
diff -Nru ./hooks/thermal ../initramfs-tools-0.98.5/hooks/thermal
--- ./hooks/thermal 2010-09-23 14:43:51.0 -0400
+++ ../initramfs-tools-0.98.5/hooks/thermal 2010-11-18 10:55:47.0 -0500
@@ -22,19 +22,33 @@
case $DPKG_ARCH in
# copy the right modules
powerpc|ppc64)
- if [ -e /sys/bus/ps3_system_bus/ ]; then
- exit 0
- fi
- manual_add_modules therm_pm72
+
+ # Only PowerMac G5 machines need these modules
+
+ MODEL=`grep model /proc/cpuinfo 2/dev/null`; MODEL=${MODEL##*: }
+
+ case $MODEL in
+ RackMac3,1|PowerMac7,2|PowerMac7,3)
+ force_load therm_pm72
+ ;;
+ PowerMac8,1|PowerMac8,2)
+ force_load windfarm_pm81
+ ;;
+ PowerMac11,2)
+ force_load windfarm_pm112
+ ;;
+ PowerMac12,1)
+ force_load windfarm_pm121
+ ;;
+ *)
+ exit 0
+ ;;
+ esac
manual_add_modules windfarm_core
manual_add_modules windfarm_cpufreq_clamp
manual_add_modules windfarm_lm75_sensor
manual_add_modules windfarm_max6690_sensor
manual_add_modules windfarm_pid
- manual_add_modules windfarm_pm121
- manual_add_modules windfarm_pm112
- manual_add_modules windfarm_pm81
- manual_add_modules windfarm_pm91
manual_add_modules windfarm_smu_controls
manual_add_modules windfarm_smu_sat
manual_add_modules windfarm_smu_sensors
signature.asc
Description: OpenPGP digital signature
Re: Security: auto-loading protocol modules
On Thu, 2010-11-18 at 03:33 +, Ben Hutchings wrote: Unlike device or filesystem modules, most protocol modules may be auto- loaded on behalf of local users without any special capabilities. This means that security vulnerabilities in such protocol modules may be exploitable by local users even on a system where there is no need for the protocol. Protocol modules are requested via module aliases generated from the protocol-family, protocol and type numbers passed to socket(). Administrators can of course blacklist the modules or disable their aliases, but there is an ever-growing list of protocols. There has been some discussion upstream of providing a means to disable or restrict this auto-loading altogether, but this is currently unresolved. [...] It looks like DECnet is not in great shape w.r.t security and is not at all widely used. You appear to be maintaining both kernel (upstream) and userland (in Debian). What do you think of moving the module alias into dnet-common, so systems without that package are not vulnerable to security flaws in the decnet module? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: Security: auto-loading protocol modules
On Thu, 2010-11-18 at 03:33 +, Ben Hutchings wrote: Unlike device or filesystem modules, most protocol modules may be auto- loaded on behalf of local users without any special capabilities. This means that security vulnerabilities in such protocol modules may be exploitable by local users even on a system where there is no need for the protocol. Protocol modules are requested via module aliases generated from the protocol-family, protocol and type numbers passed to socket(). Administrators can of course blacklist the modules or disable their aliases, but there is an ever-growing list of protocols. There has been some discussion upstream of providing a means to disable or restrict this auto-loading altogether, but this is currently unresolved. [...] The AX.25 protocol modules (ax25, netrom, rose) have not had a great security record recently, and are not widely used. What do you think of moving the module aliases into ax25-tools, so systems without that package are not vulnerable to security flaws in the kernel modules? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#603981: initramfs-tools: Load PowerMac G5 thermal modules
The first patch did not include PowerMac9,1. Corrected patch is attached
to this message.
Thanks,
Milan
diff -Nru ./hooks/thermal ../initramfs-tools-0.98.5/hooks/thermal
--- ./hooks/thermal 2010-09-23 14:43:51.0 -0400
+++ ../initramfs-tools-0.98.5/hooks/thermal 2010-11-18 21:54:21.0 -0500
@@ -22,19 +22,36 @@
case $DPKG_ARCH in
# copy the right modules
powerpc|ppc64)
- if [ -e /sys/bus/ps3_system_bus/ ]; then
- exit 0
- fi
- manual_add_modules therm_pm72
+
+ # Only PowerMac G5 machines need these modules
+
+ MODEL=`grep model /proc/cpuinfo 2/dev/null`; MODEL=${MODEL##*: }
+
+ case $MODEL in
+ RackMac3,1|PowerMac7,2|PowerMac7,3)
+ force_load therm_pm72
+ ;;
+ PowerMac8,1|PowerMac8,2)
+ force_load windfarm_pm81
+ ;;
+ PowerMac9,1)
+ force_load windfarm_pm91
+ ;;
+ PowerMac11,2)
+ force_load windfarm_pm112
+ ;;
+ PowerMac12,1)
+ force_load windfarm_pm121
+ ;;
+ *)
+ exit 0
+ ;;
+ esac
manual_add_modules windfarm_core
manual_add_modules windfarm_cpufreq_clamp
manual_add_modules windfarm_lm75_sensor
manual_add_modules windfarm_max6690_sensor
manual_add_modules windfarm_pid
- manual_add_modules windfarm_pm121
- manual_add_modules windfarm_pm112
- manual_add_modules windfarm_pm81
- manual_add_modules windfarm_pm91
manual_add_modules windfarm_smu_controls
manual_add_modules windfarm_smu_sat
manual_add_modules windfarm_smu_sensors
signature.asc
Description: OpenPGP digital signature
Re: Security: auto-loading protocol modules
Finally, x25 (*not* ax25) appears to have no applications in Debian. Google Code Search found only 4 hits for AF_X25 or PF_X25 outside of the kernel, header files or language bindings: ean - X.400 message handling software http://www.google.com/codesearch/p?hl=en#C_8T3NZHV74/pub/Apps/ean.tar.Z|yKhWeFXFTsk/ Supports BSD and SunOS 4.x. isode - ISO Development Environment http://www.google.com/codesearch/p?hl=en#Zt3wT8KZVSw/pub/unix/osi/isode-6.8.tar.Z|QdgFXEHCFMY/isode-interim/ Supports BSD and SVR2/3. x25d - replacements for the SUN supplied x29 and ybts.inetd http://www.google.com/codesearch/p?hl=en#yhcp39oOAbE/Comm/x25d.tar.gz|JTz9HiI-i1Q/ Supports SunOS with SunLink. c-kermit - remote terminal and file transfer program http://www.google.com/codesearch/p?hl=en#xjmb5K7Fhaw/kermit/ftp/archives/cku211.tar.Z|IaOxNeZiGO8/ [The above page is very slow in Iceweasel, so try downloading http://www.columbia.edu/kermit/ftp/archives/cku211.tar.Z ] X.25 code only supports SunOS with SunLink. If I've counted correctly, there are 0 applications for Linux X.25. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#576274: Status
Greetings, Is this still an active thread? What progress is there at the moment? I have the same problem with my laptop currently. Losing what you have open and needing to reboot is painful. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ce6230e.3090...@eastlink.ca
