Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system
At Mon, 07 Feb 2011 19:45:09 +0100, Adam Sloboda wrote: At Mon, 7 Feb 2011 17:27:49 +, maximilian attems wrote: On Mon, Feb 07, 2011 at 05:48:25PM +0100, Adam Sloboda wrote: The regression was introduced in 2.6.32-29 Right changelog has it: * USB: Retain device power/wakeup setting across reconfiguration; don't enable remote wakeup by default (Closes: #605246) So it can be worked around by script (in addition to /proc/acpi/wakeup setup) on boot *and* each wakeup which sets /sys/bus/usb/devices/.../power/wakeup to enabled again. I just noticed that /etc/pm/sleep.d script does not work after resume, only immediately before suspend. How is it possible that userspace script gets overriden? I can see in the log that the script enabled these devices and they are disabled again after that: /etc/pm/sleep.d/wakeup resume suspend: Allowing PHILIPS device to wake up Allowing APC device to wake up success. -- 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/87bp2mokmu.wl...@disorder.sk
Re: [Secure-testing-team] For discussion: security support strategy for the wheezy kernel
On Mon, Feb 07, 2011 at 05:15:07PM -0500, Michael Gilbert wrote: On Mon, Feb 7, 2011 at 5:09 PM, Julien Cristau wrote: What does that buy us? ??It means instead of dealing with bugs on an ongoing basis, you get them all at the same time and get to bisect along many kernel versions at once instead of just one. ??It means problems don't get reported (and fixed) upstream until it's too late. ??It means any package that could use a newer kernel interface doesn't get any testing. ??I'm sure there's plenty of others. Bugs can be submitted and dealt with in experimental just as well as in unstable. Realistically people don't generally go randomly installing things from experimental so the testing coverage we get from having unstable and testing is substantially reduced - we get to deal with everything in the freeze instead, plus all the effects of running an old kernel which isn't being actively developed. -- 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/20110208130359.gc29...@sirena.org.uk
Uploading linux-2.6 2.6.37-1 to unstable
I intend to upload linux-2.6 and linux-kbuild-2.6 based on upstream version 2.6.37, later this week. linux-latest-2.6 will also be updated. Note that the OpenVZ, VServer and Xen flavours have been dropped and will not come back. OpenVZ and VServer users should migrate to LXC (Linux containers, using the cgroups and namespace features). Xen support in mainline Linux is improving and it should be usable as the dom0 kernel soon. AUFS will be included for use in Debian Live if there is a version compatible with 2.6.37. 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/20110208151623.gd21...@decadent.org.uk
Bug#612463: linux-image-2.6.32-5-vserver-powerpc: Vserver functionality not working at all
Package: linux-2.6 Version: 2.6.32-30 Severity: grave Justification: renders package unusable Vserver containers seems not working at all. The error message I get when I try to run a vserver is: # vserver net start can not change context: migrate kernel feature missing and 'compat' API disabled: Function not implemented /proc/uptime can not be accessed. Usually, this is caused by procfs-security. Please read the FAQ for more details http://linux-vserver.org/Proc-Security Failed to start vserver 'net' The vhost configuration was done under Lenny, and does not work anymore after upgrading to Squeeze. Whatever I try to do that relates to Vserver fails saying “Function not implemented”… as an example: # setattr --~hide /proc/uptime /proc/uptime: Function not implemented Web searches indicate that this kind of error (especially the first one that more explicit) happens when the vserver patch is not applied to the kernel. I know vserver is deprecated but it should only be removed in Wheezy. As Squeeze Release Notes do not contain any alert about it, I filed this bug as being grave. -- Package-specific info: ** Version: Linux version 2.6.32-5-vserver-powerpc (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 09:36:52 UTC 2011 ** Command line: root=/dev/mapper/poutchi-root ro ** Not tainted ** Kernel log: [4.997387] ohci_hcd 0001:10:19.0: irq 28, io mem 0x8008 [5.076966] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [5.083116] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.089056] usb usb2: Product: OHCI Host Controller [5.094952] usb usb2: Manufacturer: Linux 2.6.32-5-vserver-powerpc ohci_hcd [5.100944] usb usb2: SerialNumber: 0001:10:19.0 [5.108878] usb usb2: configuration #1 chosen from 1 choice [5.115721] hub 2-0:1.0: USB hub found [5.122484] hub 2-0:1.0: 2 ports detected [5.307542] device-mapper: uevent: version 1.0.3 [5.317952] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-de...@redhat.com [5.429920] firewire_core: created device fw0: GUID 000393fffe7cf2ec, S400 [5.505471] usb 2-1: new full speed USB device using ohci_hcd and address 2 [5.718500] usb 2-1: New USB device found, idVendor=152d, idProduct=2336 [5.725068] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5 [5.731487] usb 2-1: Product: JM20336 SATA, USB Combo [5.737901] usb 2-1: Manufacturer: JMicron [5.744216] usb 2-1: SerialNumber: 14D082896788 [5.754069] usb 2-1: configuration #1 chosen from 1 choice [5.899180] SCSI subsystem initialized [5.943976] Initializing USB Mass Storage driver... [5.951105] scsi0 : SCSI emulation for USB Mass Storage devices [5.969770] usbcore: registered new interface driver usb-storage [5.977548] usb-storage: device found at 2 [5.977565] usb-storage: waiting for device to settle before scanning [6.002684] USB Mass Storage support registered. [6.556742] kjournald starting. Commit interval 5 seconds [6.563250] EXT3-fs: mounted filesystem with ordered data mode. [7.149604] eth0: Link is up at 100 Mbps, full-duplex. [9.609964] udev[201]: starting version 164 [ 10.497647] PowerMac i2c bus pmu 2 registered [ 10.558944] PowerMac i2c bus pmu 1 registered [ 10.634595] PowerMac i2c bus mac-io 0 registered [ 10.653989] PowerMac i2c bus uni-n 1 registered [ 10.663891] PowerMac i2c bus uni-n 0 registered [ 11.033760] usb-storage: device scan complete [ 11.038784] scsi 0:0:0:0: Direct-Access SAMSUNG HM160HI PQ: 0 ANSI: 2 CCS [ 11.298576] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB) [ 11.309527] sd 0:0:0:0: [sda] Write Protect is off [ 11.315666] sd 0:0:0:0: [sda] Mode Sense: 00 38 00 00 [ 11.315677] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 11.337338] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 11.343545] sda: sda1 sda5 sda6 [ 11.975512] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 11.981825] sd 0:0:0:0: [sda] Attached SCSI disk [ 15.493581] EXT3 FS on dm-0, internal journal [ 16.153603] loop: module loaded [ 18.454497] Adding 364536k swap on /dev/mapper/poutchi-swap_1. Priority:-1 extents:1 across:364536k [ 21.332596] kjournald starting. Commit interval 5 seconds [ 21.339493] EXT3 FS on dm-5, internal journal [ 21.345931] EXT3-fs: mounted filesystem with ordered data mode. [ 21.397194] kjournald starting. Commit interval 5 seconds [ 21.404115] EXT3 FS on dm-4, internal journal [ 21.410593] EXT3-fs: mounted filesystem with ordered data mode. [ 21.471404] kjournald starting. Commit interval 5 seconds [ 21.478671] EXT3 FS on dm-2, internal journal [ 21.485531] EXT3-fs: mounted filesystem with ordered data mode. [ 21.542790] kjournald starting. Commit interval 5 seconds [ 21.550192] EXT3 FS on dm-3,
Re: Uploading linux-2.6 2.6.37-1 to unstable
Ben Hutchings b...@decadent.org.uk writes: Note that the OpenVZ, VServer and Xen flavours have been dropped and will not come back. Does this mean that it would be a good day to start testing the dom0 support of plain 2.6.37 to make sure regressions will be minimal? (I am assuming 2.6.37 does support dom0 now). -- 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/84aai6xx21@sauna.l.org
Bug#611827: xserver-xorg-input-evdev: mice and touchpad losing sync and lagging (MORE INFO)
This is the contents of my Xorg.log. It seems the appropriate synaptics module is being unloaded... perhaps this is causing the issue? (II) LoadModule: evdev (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so (II) Module evdev: vendor=X.Org Foundation compiled for 1.7.6.901, module version = 2.3.2 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 7.0 (**) Power Button: always reports core events (**) Power Button: Device: /dev/input/event4 (II) Power Button: Found keys (II) Power Button: Configuring as keyboard (II) XINPUT: Adding extended input device Power Button (type: KEYBOARD) (**) Option xkb_rules evdev (**) Option xkb_model pc105 (**) Option xkb_layout us (II) config/udev: Adding input device Sleep Button (/dev/input/event5) (**) Sleep Button: Applying InputClass evdev keyboard catchall (**) Sleep Button: always reports core events (**) Sleep Button: Device: /dev/input/event5 (II) Sleep Button: Found keys (II) Sleep Button: Configuring as keyboard (II) XINPUT: Adding extended input device Sleep Button (type: KEYBOARD) (**) Option xkb_rules evdev (**) Option xkb_model pc105 (**) Option xkb_layout us (II) config/udev: Adding input device Video Bus (/dev/input/event7) (**) Video Bus: Applying InputClass evdev keyboard catchall (**) Video Bus: always reports core events (**) Video Bus: Device: /dev/input/event7 (II) Video Bus: Found keys (II) Video Bus: Configuring as keyboard (II) XINPUT: Adding extended input device Video Bus (type: KEYBOARD) (**) Option xkb_rules evdev (**) Option xkb_model pc105 (**) Option xkb_layout us (II) config/udev: Adding input device Power Button (/dev/input/event3) (**) Power Button: Applying InputClass evdev keyboard catchall (**) Power Button: always reports core events (**) Power Button: Device: /dev/input/event3 (II) Power Button: Found keys (II) Power Button: Configuring as keyboard (II) XINPUT: Adding extended input device Power Button (type: KEYBOARD) (**) Option xkb_rules evdev (**) Option xkb_model pc105 (**) Option xkb_layout us (II) config/udev: Adding input device Lid Switch (/dev/input/event2) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event1) (**) AT Translated Set 2 keyboard: Applying InputClass evdev keyboard catchall (**) AT Translated Set 2 keyboard: always reports core events (**) AT Translated Set 2 keyboard: Device: /dev/input/event1 (II) AT Translated Set 2 keyboard: Found keys (II) AT Translated Set 2 keyboard: Configuring as keyboard (II) XINPUT: Adding extended input device AT Translated Set 2 keyboard (type: KEYBOARD) (**) Option xkb_rules evdev (**) Option xkb_model pc105 (**) Option xkb_layout us (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event8) (**) SynPS/2 Synaptics TouchPad: Applying InputClass evdev touchpad catchall (**) SynPS/2 Synaptics TouchPad: Applying InputClass touchpad catchall (II) LoadModule: synaptics (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so (II) Module synaptics: vendor=X.Org Foundation compiled for 1.7.6.901, module version = 1.2.2 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 7.0 (II) Synaptics touchpad driver version 1.2.2 (**) Option Device /dev/input/event8 (II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472 (II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448 (II) SynPS/2 Synaptics TouchPad: pressure range 0 - 255 (II) SynPS/2 Synaptics TouchPad: finger width range 0 - 0 (II) SynPS/2 Synaptics TouchPad: buttons: left right middle double triple (--) SynPS/2 Synaptics TouchPad: touchpad found (**) SynPS/2 Synaptics TouchPad: always reports core events (II) XINPUT: Adding extended input device SynPS/2 Synaptics TouchPad (type: TOUCHPAD) (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1 (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 0 (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000 (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4 (--) SynPS/2 Synaptics TouchPad: touchpad found (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1) (**) SynPS/2 Synaptics TouchPad: Applying InputClass touchpad catchall (II) Synaptics touchpad driver version 1.2.2 SynPS/2 Synaptics TouchPad no synaptics event device found (**) Option Device /dev/input/mouse1 Query no Synaptics: 6003C8 (--) SynPS/2 Synaptics TouchPad: no supported touchpad found (EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware. (EE) PreInit failed for input device SynPS/2 Synaptics TouchPad (II) UnloadModule: synaptics (II) config/udev: Adding input device PC Speaker (/dev/input/event6) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/event0) (**) Macintosh mouse button emulation: Applying InputClass evdev pointer
Re: Uploading linux-2.6 2.6.37-1 to unstable
On Tue, Feb 08, 2011 at 07:20:38PM +0200, Timo Juhani Lindfors wrote: Ben Hutchings b...@decadent.org.uk writes: Note that the OpenVZ, VServer and Xen flavours have been dropped and will not come back. Does this mean that it would be a good day to start testing the dom0 support of plain 2.6.37 to make sure regressions will be minimal? (I am assuming 2.6.37 does support dom0 now). The backend drivers have not yet been merged, so it's not yet very useful as dom0. 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/20110208180237.ge21...@decadent.org.uk
Processed: severity of 612463 is important
Processing commands for cont...@bugs.debian.org: severity 612463 important Bug #612463 [linux-2.6] linux-image-2.6.32-5-vserver-powerpc: Vserver functionality not working at all Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 612463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612463 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.129719031421081.transcr...@bugs.debian.org
Re: Uploading linux-2.6 2.6.37-1 to unstable
Ben Hutchings b...@decadent.org.uk writes: The backend drivers have not yet been merged, so it's not yet very useful as dom0. ok. Is there still hope that they will get merged before wheezy is released or would now be a good time to start looking at KVM migration plans? -- 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/8462suxspr@sauna.l.org
Re: Uploading linux-2.6 2.6.37-1 to unstable
On Tue, Feb 08, 2011 at 08:54:24PM +0200, Timo Juhani Lindfors wrote: Ben Hutchings b...@decadent.org.uk writes: The backend drivers have not yet been merged, so it's not yet very useful as dom0. ok. Is there still hope that they will get merged before wheezy is released or would now be a good time to start looking at KVM migration plans? I think they will, e.g. netback is going through review now and I would expect it to be merged in time for 2.6.39. Apparently Linux 2.6.38 will have enough functionality in dom0 that blkback and netback can be implemented in userland in qemu. 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/20110208191432.gf21...@decadent.org.uk
Re: Uploading linux-2.6 2.6.37-1 to unstable
On Tue, 2011-02-08 at 19:14 +, Ben Hutchings wrote: On Tue, Feb 08, 2011 at 08:54:24PM +0200, Timo Juhani Lindfors wrote: Ben Hutchings b...@decadent.org.uk writes: The backend drivers have not yet been merged, so it's not yet very useful as dom0. ok. Is there still hope that they will get merged before wheezy is released or would now be a good time to start looking at KVM migration plans? I think they will, e.g. netback is going through review now and I would expect it to be merged in time for 2.6.39. Yes, I'm actively working on it and hope to get it in for 2.6.39. Apparently Linux 2.6.38 will have enough functionality in dom0 that blkback and netback can be implemented in userland in qemu. I think that's the case, yes. The qemu-xen in Squeeze doesn't have the backends, in case someone was planning to try a new kernel on Squeeze. Ian. -- Ian Campbell A mouse is an elephant built by the Japanese. signature.asc Description: This is a digitally signed message part
Bug#589667: More information on RedHat Bug
Information in this bug report may help: https://bugzilla.redhat.com/show_bug.cgi?id=576246 -- 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/20110208230621.gc...@canoga.com
Bug#612537: linux-2.6: dmesg error PM: Error -22 checking image file
Package: linux-2.6 Severity: minor The following message is actually a debug message because CONFIG_PM_DEBUG=y in the current kernel. Should this be disabled? More information: http://www-947.ibm.com/support/entry/portal/docdisplay?brand=508lndocid=MIGR-5085026 -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20110208234745.6033.25807.report...@cpengapp1.canoga.com
Bug#612541: linux-2.6: Failed to resume link error reported by ata
Package: linux-2.6 Severity: normal I get the following messages on the kernel logs reported by the ata subsystem. Everything works as expected so I don't think it is too serious. However, not sure how this affects disk performance, etc. [3.423305] ata2.00: failed to resume link (SControl 0) [3.599683] ata4: failed to resume link (SControl 0) [3.610467] ata4: SATA link down (SStatus 4 SControl 0) [3.743434] ata1.01: failed to resume link (SControl 0) [3.754244] ata1.00: SATA link down (SStatus 0 SControl 300) [3.754258] ata1.01: SATA link down (SStatus 0 SControl 0) [4.450199] ata2.01: failed to resume link (SControl 0) [4.460986] ata2.00: SATA link down (SStatus 0 SControl 0) [4.461000] ata2.01: SATA link down (SStatus 0 SControl 0) -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20110209004110.6344.76586.report...@cpengapp1.canoga.com
