Bug#612298: repeated columns on VGA/Radeon head
Package: linux-2.6 Version: 2.6.37-1~experimental.1 Severity: normal This problem occurs when booting 2.6.37, but not with 2.6.36. I have three Radeon cards (HD 4350 / RV710), all using the free driver in a Zaphod configuration. I have three different screens connected, two DVI and one VGA. The VGA screen works fine on tty, but in X, there's some weirdness with repeated columns of pixels. I made a video to illustrate the effect, as it's hard to describe: http://scratch.madduck.net/__tmp__weird_screen.avi. That's all for now as I do not have the time to debug this further at the moment. -- Package-specific info: ** Version: Linux version 2.6.37-trunk-amd64 (Debian 2.6.37-1~experimental.1) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-10) ) #1 SMP Thu Jan 6 14:13:28 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.37-trunk-amd64 root=/dev/mapper/albatross-root ro ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 106.376539] 30b 0b 01 02 28 20 18 6b e8 0d 99 a0 57 47 98 26 ( .kWG. [ 106.376541] 310 48 4c bf ef 80 31 4f 45 4f 61 4f 81 8f 01 01 .HL...1OEOaO [ 106.376542] 301 01 01 01 01 01 4e 0c 80 c0 20 e0 1d 10 38 38 ..N... ...88 [ 106.376544] 313 00 33 e6 10 00 00 18 56 13 20 f8 30 58 1f 20 ..3.V. .0X. [ 106.376545] 320 40 13 00 33 e6 10 00 00 18 c3 1e 00 20 41 00 @..3 A. [ 106.376547] 320 30 10 60 13 00 33 e6 10 00 00 18 00 00 00 fd 0.`..3. [ 106.376548] 300 38 4b 1e 55 ff 01 0a ff ff ff ff ff ff ff ff .8K.U... [ 106.376549] [ 106.429282] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 94 [ 106.429284] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [ 106.429286] 300 ff ff ff ff ff ff 00 25 b2 10 88 06 01 00 00 %... [ 106.429288] 30b 0b 01 02 28 20 18 6b e8 0d 99 a0 57 47 98 26 ( .kWG. [ 106.429289] 310 48 4c bf ef 80 31 4f 45 4f 61 4f 81 8f 01 01 .HL...1OEOaO [ 106.429291] 301 01 01 01 01 01 4e 0c 80 c0 20 e0 1d 10 38 38 ..N... ...88 [ 106.429292] 313 00 33 e6 10 00 00 18 56 13 20 f8 30 58 1f 20 ..3.V. .0X. [ 106.429293] 320 40 13 00 33 e6 10 00 00 18 c3 1e 00 20 41 00 @..3 A. [ 106.429295] 320 30 10 60 13 00 33 e6 10 00 00 18 00 00 00 fd 0.`..3. [ 106.429296] 300 38 4b 1e 55 ff 01 0a ff ff ff ff ff ff ff ff .8K.U... [ 106.429297] [ 106.482079] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 94 [ 106.482081] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [ 106.482083] 300 ff ff ff ff ff ff 00 25 b2 10 88 06 01 00 00 %... [ 106.482085] 30b 0b 01 02 28 20 18 6b e8 0d 99 a0 57 47 98 26 ( .kWG. [ 106.482086] 310 48 4c bf ef 80 31 4f 45 4f 61 4f 81 8f 01 01 .HL...1OEOaO [ 106.482087] 301 01 01 01 01 01 4e 0c 80 c0 20 e0 1d 10 38 38 ..N... ...88 [ 106.482089] 313 00 33 e6 10 00 00 18 56 13 20 f8 30 58 1f 20 ..3.V. .0X. [ 106.482090] 320 40 13 00 33 e6 10 00 00 18 c3 1e 00 20 41 00 @..3 A. [ 106.482092] 320 30 10 60 13 00 33 e6 10 00 00 18 00 00 00 fd 0.`..3. [ 106.482093] 300 38 4b 1e 55 ff 01 0a ff ff ff ff ff ff ff ff .8K.U... [ 106.482094] [ 106.534807] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 94 [ 106.534808] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [ 106.534810] 300 ff ff ff ff ff ff 00 25 b2 10 88 06 01 00 00 %... [ 106.534812] 30b 0b 01 02 28 20 18 6b e8 0d 99 a0 57 47 98 26 ( .kWG. [ 106.534813] 310 48 4c bf ef 80 31 4f 45 4f 61 4f 81 8f 01 01 .HL...1OEOaO [ 106.534815] 301 01 01 01 01 01 4e 0c 80 c0 20 e0 1d 10 38 38 ..N... ...88 [ 106.534816] 313 00 33 e6 10 00 00 18 56 13 20 f8 30 58 1f 20 ..3.V. .0X. [ 106.534817] 320 40 13 00 33 e6 10 00 00 18 c3 1e 00 20 41 00 @..3 A. [ 106.534819] 320 30 10 60 13 00 33 e6 10 00 00 18 00 00 00 fd 0.`..3. [ 106.534820] 300 38 4b 1e 55 ff 01 0a ff ff ff ff ff ff ff ff .8K.U... [ 106.534821] [ 106.534824] radeon :04:00.0: VGA-1: EDID block 0 invalid. [ 106.534826] [drm:radeon_vga_detect] *ERROR* VGA-1: probed a monitor but no|invalid EDID [ 106.589319] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 94 [ 106.589321] [drm:drm_edid_block_valid] *ERROR* Raw EDID: [ 106.589322] 300 ff ff ff ff ff ff 00 25 b2 10 88 06 01 00 00 %... [ 106.589324] 30b 0b 01 02 28 20 18 6b e8 0d 99 a0 57 47 98 26 ( .kWG. [ 106.589325] 310 48 4c bf ef 80 31 4f 45 4f 61 4f 81 8f 01 01 .HL...1OEOaO [ 106.589327] 301 01 01 01 01 01 4e 0c 80 c0 20 e0 1d 10 38 38 ..N... ...88 [ 106.589328] 313 00 33 e6 10 00 00 18 56 13 20 f8 30 58 1f 20 ..3.V. .0X. [ 106.589329] 320 40 13 00 33 e6 10 00 00 18 c3 1e 00 20 41 00 @..3 A. [ 106.589331] 320 30 10 60 13 00 33 e6 10 00 00 18 00 00 00 fd 0.`..3. [ 106.589332] 300 38 4b 1e 55 ff 01 0a ff ff ff ff ff ff ff ff
Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system
Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade to squeeze I can't wake up the PC anymore with USB dongle (remote control) and probably the same thing applies to UPS backup. It's nVidia ION based motherboard. /proc/acpi/wakeup is properly configured: USB0 S4 enabled pci::00:04.0 I can confirm that it works properly when I revert back to this package: linux-image-2.6.32-5-686_2.6.32-18_i386.deb Regards, Adam -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 04:01:41 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=dbf6fadb-e76b-4d90-a5a7-496552cd5d8d ro quiet splash ** Tainted: P (1) * Proprietary module has been loaded. ** Kernel log: [ 114.108659] ehci_hcd :00:06.1: PCI INT B - Link[UB12] - GSI 22 (level, low) - IRQ 22 [ 114.108707] ehci_hcd :00:06.1: setting latency timer to 64 [ 114.108717] ehci_hcd :00:06.1: EHCI Host Controller [ 114.108749] ehci_hcd :00:06.1: new USB bus registered, assigned bus number 2 [ 114.108805] ehci_hcd :00:06.1: debug port 1 [ 114.108822] ehci_hcd :00:06.1: cache line size of 32 is not supported [ 114.108853] ehci_hcd :00:06.1: irq 22, io mem 0xf9f7e800 [ 114.120051] ehci_hcd :00:06.1: USB 2.0 started, EHCI 1.00 [ 114.120119] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 114.120129] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 114.120139] usb usb2: Product: EHCI Host Controller [ 114.120146] usb usb2: Manufacturer: Linux 2.6.32-5-686 ehci_hcd [ 114.120153] usb usb2: SerialNumber: :00:06.1 [ 114.120399] usb usb2: configuration #1 chosen from 1 choice [ 114.120507] hub 2-0:1.0: USB hub found [ 114.120536] hub 2-0:1.0: 6 ports detected [ 114.139873] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 114.139951] ohci_hcd :00:04.0: PCI INT A - Link[LUB0] - GSI 23 (level, low) - IRQ 23 [ 114.139995] ohci_hcd :00:04.0: setting latency timer to 64 [ 114.140043] ohci_hcd :00:04.0: OHCI Host Controller [ 114.140256] ohci_hcd :00:04.0: new USB bus registered, assigned bus number 3 [ 114.140314] ohci_hcd :00:04.0: irq 23, io mem 0xf9f7f000 [ 114.198085] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 114.198098] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 114.198107] usb usb3: Product: OHCI Host Controller [ 114.198114] usb usb3: Manufacturer: Linux 2.6.32-5-686 ohci_hcd [ 114.198122] usb usb3: SerialNumber: :00:04.0 [ 114.198602] usb usb3: configuration #1 chosen from 1 choice [ 114.198832] hub 3-0:1.0: USB hub found [ 114.198862] hub 3-0:1.0: 6 ports detected [ 114.199047] ohci_hcd :00:06.0: PCI INT A - Link[UB11] - GSI 21 (level, low) - IRQ 21 [ 114.199093] ohci_hcd :00:06.0: setting latency timer to 64 [ 114.199102] ohci_hcd :00:06.0: OHCI Host Controller [ 114.199132] ohci_hcd :00:06.0: new USB bus registered, assigned bus number 4 [ 114.199171] ohci_hcd :00:06.0: irq 21, io mem 0xf9f7d000 [ 114.254065] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [ 114.254074] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 114.254081] usb usb4: Product: OHCI Host Controller [ 114.254086] usb usb4: Manufacturer: Linux 2.6.32-5-686 ohci_hcd [ 114.254091] usb usb4: SerialNumber: :00:06.0 [ 114.254304] usb usb4: configuration #1 chosen from 1 choice [ 114.254404] hub 4-0:1.0: USB hub found [ 114.254434] hub 4-0:1.0: 6 ports detected [ 114.269685] uhci_hcd: USB Universal Host Controller Interface driver [ 114.784078] usb 3-2: new low speed USB device using ohci_hcd and address 2 [ 115.007075] usb 3-2: New USB device found, idVendor=0471, idProduct=206c [ 115.007084] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 115.007091] usb 3-2: Product: MCE USB IR Receiver- Spinel plusf0r ASUS [ 115.007096] usb 3-2: Manufacturer: PHILIPS [ 115.007290] usb 3-2: configuration #1 chosen from 1 choice [ 115.029315] input: PHILIPS MCE USB IR Receiver- Spinel plusf0r ASUS as /devices/pci:00/:00:04.0/usb3/3-2/3-2:1.0/input/input6 [ 115.029664] philips_asus 0003:0471:206C.0003: input: USB HID v1.00 Keyboard [PHILIPS MCE USB IR Receiver- Spinel plusf0r ASUS] on usb-:00:04.0-2/input0 [ 115.332034] usb 3-6: new full speed USB device using ohci_hcd and address 3 [ 115.535087] usb 3-6: New USB device found, idVendor=0cf3, idProduct=3002 [ 115.535094] usb 3-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 115.535284] usb 3-6: configuration #1 chosen from 1 choice [ 115.896035] usb 4-2: new low speed USB device using ohci_hcd and address 2 [ 116.146786] usb 4-2: New USB device found, idVendor=051d, idProduct=0002 [ 116.146793] usb 4-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [
Re: Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system
On Mon, 07 Feb 2011 15:24:06 +0100 Adam Sloboda j...@disorder.sk wrote: bisogna attivarla sui tre pc Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade to squeeze I can't wake up the PC anymore with USB dongle (remote control) and probably the same thing applies to UPS backup. It's nVidia ION based motherboard. /proc/acpi/wakeup is properly configured: USB0S4 enabled pci::00:04.0 I can confirm that it works properly when I revert back to this package: linux-image-2.6.32-5-686_2.6.32-18_i386.deb Regards, Adam -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 04:01:41 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=dbf6fadb-e76b-4d90-a5a7-496552cd5d8d ro quiet splash ** Tainted: P (1) * Proprietary module has been loaded. ** Kernel log: [ 114.108659] ehci_hcd :00:06.1: PCI INT B - Link[UB12] - GSI 22 (level, low) - IRQ 22 [ 114.108707] ehci_hcd :00:06.1: setting latency timer to 64 [ 114.108717] ehci_hcd :00:06.1: EHCI Host Controller [ 114.108749] ehci_hcd :00:06.1: new USB bus registered, assigned bus number 2 [ 114.108805] ehci_hcd :00:06.1: debug port 1 [ 114.108822] ehci_hcd :00:06.1: cache line size of 32 is not supported [ 114.108853] ehci_hcd :00:06.1: irq 22, io mem 0xf9f7e800 [ 114.120051] ehci_hcd :00:06.1: USB 2.0 started, EHCI 1.00 [ 114.120119] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 114.120129] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 114.120139] usb usb2: Product: EHCI Host Controller [ 114.120146] usb usb2: Manufacturer: Linux 2.6.32-5-686 ehci_hcd [ 114.120153] usb usb2: SerialNumber: :00:06.1 [ 114.120399] usb usb2: configuration #1 chosen from 1 choice [ 114.120507] hub 2-0:1.0: USB hub found [ 114.120536] hub 2-0:1.0: 6 ports detected [ 114.139873] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 114.139951] ohci_hcd :00:04.0: PCI INT A - Link[LUB0] - GSI 23 (level, low) - IRQ 23 [ 114.139995] ohci_hcd :00:04.0: setting latency timer to 64 [ 114.140043] ohci_hcd :00:04.0: OHCI Host Controller [ 114.140256] ohci_hcd :00:04.0: new USB bus registered, assigned bus number 3 [ 114.140314] ohci_hcd :00:04.0: irq 23, io mem 0xf9f7f000 [ 114.198085] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 114.198098] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 114.198107] usb usb3: Product: OHCI Host Controller [ 114.198114] usb usb3: Manufacturer: Linux 2.6.32-5-686 ohci_hcd [ 114.198122] usb usb3: SerialNumber: :00:04.0 [ 114.198602] usb usb3: configuration #1 chosen from 1 choice [ 114.198832] hub 3-0:1.0: USB hub found [ 114.198862] hub 3-0:1.0: 6 ports detected [ 114.199047] ohci_hcd :00:06.0: PCI INT A - Link[UB11] - GSI 21 (level, low) - IRQ 21 [ 114.199093] ohci_hcd :00:06.0: setting latency timer to 64 [ 114.199102] ohci_hcd :00:06.0: OHCI Host Controller [ 114.199132] ohci_hcd :00:06.0: new USB bus registered, assigned bus number 4 [ 114.199171] ohci_hcd :00:06.0: irq 21, io mem 0xf9f7d000 [ 114.254065] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [ 114.254074] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 114.254081] usb usb4: Product: OHCI Host Controller [ 114.254086] usb usb4: Manufacturer: Linux 2.6.32-5-686 ohci_hcd [ 114.254091] usb usb4: SerialNumber: :00:06.0 [ 114.254304] usb usb4: configuration #1 chosen from 1 choice [ 114.254404] hub 4-0:1.0: USB hub found [ 114.254434] hub 4-0:1.0: 6 ports detected [ 114.269685] uhci_hcd: USB Universal Host Controller Interface driver [ 114.784078] usb 3-2: new low speed USB device using ohci_hcd and address 2 [ 115.007075] usb 3-2: New USB device found, idVendor=0471, idProduct=206c [ 115.007084] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 115.007091] usb 3-2: Product: MCE USB IR Receiver- Spinel plusf0r ASUS [ 115.007096] usb 3-2: Manufacturer: PHILIPS [ 115.007290] usb 3-2: configuration #1 chosen from 1 choice [ 115.029315] input: PHILIPS MCE USB IR Receiver- Spinel plusf0r ASUS as /devices/pci:00/:00:04.0/usb3/3-2/3-2:1.0/input/input6 [ 115.029664] philips_asus 0003:0471:206C.0003: input: USB HID v1.00 Keyboard [PHILIPS MCE USB IR Receiver- Spinel plusf0r ASUS] on usb-:00:04.0-2/input0 [ 115.332034] usb 3-6: new full speed USB device using ohci_hcd and address 3 [ 115.535087] usb 3-6: New USB device found, idVendor=0cf3, idProduct=3002 [ 115.535094] usb 3-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 115.535284] usb 3-6: configuration #1 chosen from 1 choice [ 115.896035] usb 4-2: new low speed USB device using ohci_hcd
Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system
On Mon, Feb 07, 2011 at 03:24:06PM +0100, Adam Sloboda wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade to squeeze I can't wake up the PC anymore with USB dongle (remote control) and probably the same thing applies to UPS backup. It's nVidia ION based motherboard. /proc/acpi/wakeup is properly configured: USB0S4 enabled pci::00:04.0 I can confirm that it works properly when I revert back to this package: linux-image-2.6.32-5-686_2.6.32-18_i386.deb Regards, Adam this is old, could you try to track down to a more specific version. 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/20110207145813.gn19...@vostochny.stro.at
Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system
At Mon, 7 Feb 2011 14:58:14 +, maximilian attems wrote: On Mon, Feb 07, 2011 at 03:24:06PM +0100, Adam Sloboda wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade to squeeze I can't wake up the PC anymore with USB dongle (remote control) and probably the same thing applies to UPS backup. It's nVidia ION based motherboard. /proc/acpi/wakeup is properly configured: USB0 S4 enabled pci::00:04.0 I can confirm that it works properly when I revert back to this package: linux-image-2.6.32-5-686_2.6.32-18_i386.deb Regards, Adam this is old, could you try to track down to a more specific version. Thank you. There is no other version in the apt repository, I have nothing to test. I was very lucky to find this package on my laptop. -- 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/87hbcfop11.wl...@disorder.sk
Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system
On Mon, Feb 07, 2011 at 04:14:18PM +0100, Adam Sloboda wrote: At Mon, 7 Feb 2011 14:58:14 +, maximilian attems wrote: On Mon, Feb 07, 2011 at 03:24:06PM +0100, Adam Sloboda wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade to squeeze I can't wake up the PC anymore with USB dongle (remote control) and probably the same thing applies to UPS backup. It's nVidia ION based motherboard. /proc/acpi/wakeup is properly configured: USB0S4 enabled pci::00:04.0 I can confirm that it works properly when I revert back to this package: linux-image-2.6.32-5-686_2.6.32-18_i386.deb Regards, Adam this is old, could you try to track down to a more specific version. Thank you. There is no other version in the apt repository, I have nothing to test. I was very lucky to find this package on my laptop. There were *many* changes since, use http://snapshot.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/20110207160614.go19...@vostochny.stro.at
Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system
At Mon, 7 Feb 2011 16:06:14 +, maximilian attems wrote: There is no other version in the apt repository, I have nothing to test. I was very lucky to find this package on my laptop. There were *many* changes since, use http://snapshot.debian.org/ Sure, I am not disputing that. But where are the packages? -- 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/87fwrzolro.wl...@disorder.sk
Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system
On Mon, Feb 07, 2011 at 05:24:43PM +0100, Adam Sloboda wrote: At Mon, 7 Feb 2011 16:06:14 +, maximilian attems wrote: There is no other version in the apt repository, I have nothing to test. I was very lucky to find this package on my laptop. There were *many* changes since, use http://snapshot.debian.org/ Sure, I am not disputing that. But where are the packages? Use aboves link put linux-2.6 as source and download. see http://snapshot.debian.org/package/linux-2.6/ -- 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/20110207162750.gp19...@vostochny.stro.at
Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system
At Mon, 7 Feb 2011 16:27:51 +, maximilian attems wrote: On Mon, Feb 07, 2011 at 05:24:43PM +0100, Adam Sloboda wrote: At Mon, 7 Feb 2011 16:06:14 +, maximilian attems wrote: There is no other version in the apt repository, I have nothing to test. I was very lucky to find this package on my laptop. There were *many* changes since, use http://snapshot.debian.org/ Sure, I am not disputing that. But where are the packages? Use aboves link put linux-2.6 as source and download. see http://snapshot.debian.org/package/linux-2.6/ The regression was introduced in 2.6.32-29 Regards, Adam -- 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/87ei7joko6.wl...@disorder.sk
Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system
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) -- 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/20110207172749.gq19...@vostochny.stro.at
Bug#612300: marked as done (linux-image-2.6.32-5-686: USB devices can't wakeup the system)
Your message dated Mon, 7 Feb 2011 18:44:22 + with message-id 20110207184422.gb21...@decadent.org.uk and subject line Re: Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system has caused the Debian Bug report #612300, regarding linux-image-2.6.32-5-686: USB devices can't wakeup the system 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.) -- 612300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade to squeeze I can't wake up the PC anymore with USB dongle (remote control) and probably the same thing applies to UPS backup. It's nVidia ION based motherboard. /proc/acpi/wakeup is properly configured: USB0 S4 enabled pci::00:04.0 I can confirm that it works properly when I revert back to this package: linux-image-2.6.32-5-686_2.6.32-18_i386.deb Regards, Adam -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 04:01:41 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=dbf6fadb-e76b-4d90-a5a7-496552cd5d8d ro quiet splash ** Tainted: P (1) * Proprietary module has been loaded. ** Kernel log: [ 114.108659] ehci_hcd :00:06.1: PCI INT B - Link[UB12] - GSI 22 (level, low) - IRQ 22 [ 114.108707] ehci_hcd :00:06.1: setting latency timer to 64 [ 114.108717] ehci_hcd :00:06.1: EHCI Host Controller [ 114.108749] ehci_hcd :00:06.1: new USB bus registered, assigned bus number 2 [ 114.108805] ehci_hcd :00:06.1: debug port 1 [ 114.108822] ehci_hcd :00:06.1: cache line size of 32 is not supported [ 114.108853] ehci_hcd :00:06.1: irq 22, io mem 0xf9f7e800 [ 114.120051] ehci_hcd :00:06.1: USB 2.0 started, EHCI 1.00 [ 114.120119] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 114.120129] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 114.120139] usb usb2: Product: EHCI Host Controller [ 114.120146] usb usb2: Manufacturer: Linux 2.6.32-5-686 ehci_hcd [ 114.120153] usb usb2: SerialNumber: :00:06.1 [ 114.120399] usb usb2: configuration #1 chosen from 1 choice [ 114.120507] hub 2-0:1.0: USB hub found [ 114.120536] hub 2-0:1.0: 6 ports detected [ 114.139873] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 114.139951] ohci_hcd :00:04.0: PCI INT A - Link[LUB0] - GSI 23 (level, low) - IRQ 23 [ 114.139995] ohci_hcd :00:04.0: setting latency timer to 64 [ 114.140043] ohci_hcd :00:04.0: OHCI Host Controller [ 114.140256] ohci_hcd :00:04.0: new USB bus registered, assigned bus number 3 [ 114.140314] ohci_hcd :00:04.0: irq 23, io mem 0xf9f7f000 [ 114.198085] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 114.198098] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 114.198107] usb usb3: Product: OHCI Host Controller [ 114.198114] usb usb3: Manufacturer: Linux 2.6.32-5-686 ohci_hcd [ 114.198122] usb usb3: SerialNumber: :00:04.0 [ 114.198602] usb usb3: configuration #1 chosen from 1 choice [ 114.198832] hub 3-0:1.0: USB hub found [ 114.198862] hub 3-0:1.0: 6 ports detected [ 114.199047] ohci_hcd :00:06.0: PCI INT A - Link[UB11] - GSI 21 (level, low) - IRQ 21 [ 114.199093] ohci_hcd :00:06.0: setting latency timer to 64 [ 114.199102] ohci_hcd :00:06.0: OHCI Host Controller [ 114.199132] ohci_hcd :00:06.0: new USB bus registered, assigned bus number 4 [ 114.199171] ohci_hcd :00:06.0: irq 21, io mem 0xf9f7d000 [ 114.254065] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [ 114.254074] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 114.254081] usb usb4: Product: OHCI Host Controller [ 114.254086] usb usb4: Manufacturer: Linux 2.6.32-5-686 ohci_hcd [ 114.254091] usb usb4: SerialNumber: :00:06.0 [ 114.254304] usb usb4: configuration #1 chosen from 1 choice [ 114.254404] hub 4-0:1.0: USB hub found [ 114.254434] hub 4-0:1.0: 6 ports detected [ 114.269685] uhci_hcd: USB Universal Host Controller Interface driver [ 114.784078] usb 3-2: new low speed USB device using ohci_hcd and address 2 [ 115.007075] usb 3-2: New USB device found, idVendor=0471, idProduct=206c [ 115.007084] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 115.007091] usb 3-2: Product: MCE USB IR Receiver- Spinel plusf0r ASUS [ 115.007096] usb 3-2: Manufacturer: PHILIPS [
Bug#612300: linux-image-2.6.32-5-686: USB devices can't wakeup the system
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. -- 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/87d3n3of9m.wl...@disorder.sk
Re: For discussion: security support strategy for the wheezy kernel
Michael Gilbert michael.s.gilb...@gmail.com schrieb: Hi, So, my proposal in a nutshell is to only upload upstream 2.6.32 point releases to wheezy/sid for the next 12-18 months. At that time, reevaluate and determine what the next longterm cadence kernel will be, and then once that is reasonable stabilized in experimental, finally upload it to unstable for the final stages of wheezy development (perhaps a few months before the freeze). No way. The idea of unstable is to get the current upstream code in shape and that won't be achieved with staying with an old kernel. Whatever the technical solution to testing-security kernel might be, it needs to be based on following the upstream kernel development. Cheers, Moritz -- 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/slrnil0dh0.3dh@inutil.org
Re: For discussion: security support strategy for the wheezy kernel
On Mon, Feb 07, 2011 at 07:12:48PM +0100, Moritz Mühlenhoff wrote: Michael Gilbert michael.s.gilb...@gmail.com schrieb: Hi, So, my proposal in a nutshell is to only upload upstream 2.6.32 point releases to wheezy/sid for the next 12-18 months. At that time, reevaluate and determine what the next longterm cadence kernel will be, and then once that is reasonable stabilized in experimental, finally upload it to unstable for the final stages of wheezy development (perhaps a few months before the freeze). No way. The idea of unstable is to get the current upstream code in shape and that won't be achieved with staying with an old kernel. Whatever the technical solution to testing-security kernel might be, it needs to be based on following the upstream kernel development. Totally agreed. We should be tracking current upstream releases, and not just in experimental (which can now be used for upstream release candidates). 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/20110207211415.gc21...@decadent.org.uk
Bug#612340: linux-image-2.6.32-5-686: kernel 2.6.32-5 hang with call trace about inotify_inode_queue
Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream After upgrade from debian 5, I am unable to boot with kernel 2.6.32-5. I can boot with the older kernel 2.6.22. It's maybe due to newer PATA drivers. I don't have all data for resolve because the problem is displayed during boot. But the end of kernel output says : CALL TRACE: fsnotify open_execve do_execve sys_execve sysenter_do_call and the content of EIP tell inotify_inode_queue. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] [1106:3099] Subsystem: VIA Technologies, Inc. Device [1106:] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Region 0: Memory at e000 (32-bit, prefetchable) [size=256M] Capabilities: [a0] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=none Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: agpgart-via Kernel modules: via-agp 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] [1106:b099] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: dde0-dfef Prefetchable memory behind bridge: d5b0-ddcf Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel modules: shpchp 00:06.0 Multimedia audio controller [0401]: Creative Labs SB Live! EMU10k1 [1102:0002] (rev 08) Subsystem: Creative Labs CT4832 SBLive! Value [1102:8027] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (500ns min, 5000ns max) Interrupt: pin A routed to IRQ 17 Region 0: I/O ports at e400 [size=32] Capabilities: [dc] Power Management version 1 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: EMU10K1_Audigy Kernel modules: snd-emu10k1 00:06.1 Input device controller [0980]: Creative Labs SB Live! Game Port [1102:7002] (rev 08) Subsystem: Creative Labs Gameport Joystick [1102:0020] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 Region 0: I/O ports at ec00 [size=8] Capabilities: [dc] Power Management version 1 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: Emu10k1_gameport Kernel modules: emu10k1-gp 00:07.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c810 [1000:0001] (rev 12) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (2000ns min, 16000ns max), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 18 Region 0: I/O ports at e800 [size=256] Region 1: Memory at df00 (32-bit, non-prefetchable) [size=256] Kernel driver in use: sym53c8xx Kernel modules: sym53c8xx 00:08.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8029(AS) [10ec:8029] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Re: [Secure-testing-team] For discussion: security support strategy for the wheezy kernel
On Mon, 7 Feb 2011 19:12:48 +0100, Moritz Mühlenhoff wrote: Michael Gilbert michael.s.gilb...@gmail.com schrieb: Hi, So, my proposal in a nutshell is to only upload upstream 2.6.32 point releases to wheezy/sid for the next 12-18 months. At that time, reevaluate and determine what the next longterm cadence kernel will be, and then once that is reasonable stabilized in experimental, finally upload it to unstable for the final stages of wheezy development (perhaps a few months before the freeze). No way. The idea of unstable is to get the current upstream code in shape and that won't be achieved with staying with an old kernel. I'm not sure if there's a precise definition of unstable other than the statement at [0], but it seems to be whatever teams make of it. It's perfectly ok to upload only stable versions (if that's what the team wants to do), and its perfectly ok to upload the most unstable thing ever, but then the consequences of that have to be dealt with. I guess what I'm saying is that each team can decide specifically how they want to use unstable, so the kernel team can deviate from the status quo if they decide to; that is if I can make a sufficiently convincing argument. Also, my suggestion does involve eventually moving to a newer kernel in the wheezy development cycle; just a while from now, rather than rushing in to things. Whatever the technical solution to testing-security kernel might be, it needs to be based on following the upstream kernel development. 2.6.32.x is in fact an upstream kernel currently being developed ;) Best wishes, Mike [0] http://www.debian.org/releases/unstable/ -- 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/20110207162831.fbd75367.michael.s.gilb...@gmail.com
Re: [Secure-testing-team] For discussion: security support strategy for the wheezy kernel
On Mon, Feb 7, 2011 at 16:28:31 -0500, Michael Gilbert wrote: On Mon, 7 Feb 2011 19:12:48 +0100, Moritz Mühlenhoff wrote: Michael Gilbert michael.s.gilb...@gmail.com schrieb: Hi, So, my proposal in a nutshell is to only upload upstream 2.6.32 point releases to wheezy/sid for the next 12-18 months. At that time, reevaluate and determine what the next longterm cadence kernel will be, and then once that is reasonable stabilized in experimental, finally upload it to unstable for the final stages of wheezy development (perhaps a few months before the freeze). No way. The idea of unstable is to get the current upstream code in shape and that won't be achieved with staying with an old kernel. I'm not sure if there's a precise definition of unstable other than the statement at [0], but it seems to be whatever teams make of it. unstable is where debian development work happens. It's perfectly ok to upload only stable versions (if that's what the team wants to do), and its perfectly ok to upload the most unstable thing ever, but then the consequences of that have to be dealt with. I guess what I'm saying is that each team can decide specifically how they want to use unstable, so the kernel team can deviate from the status quo if they decide to; that is if I can make a sufficiently convincing argument. Also, my suggestion does involve eventually moving to a newer kernel in the wheezy development cycle; just a while from now, rather than rushing in to things. 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. Whatever the technical solution to testing-security kernel might be, it needs to be based on following the upstream kernel development. 2.6.32.x is in fact an upstream kernel currently being developed ;) No it's not. Go read the definition of development. I'm sorry, but your proposal is insane. Cheers, Julien signature.asc Description: Digital signature
Re: [Secure-testing-team] For discussion: security support strategy for the wheezy kernel
2011/2/7 Ben Hutchings wrote: On Mon, Feb 07, 2011 at 07:12:48PM +0100, Moritz Mühlenhoff wrote: Michael Gilbert michael.s.gilb...@gmail.com schrieb: Hi, So, my proposal in a nutshell is to only upload upstream 2.6.32 point releases to wheezy/sid for the next 12-18 months. At that time, reevaluate and determine what the next longterm cadence kernel will be, and then once that is reasonable stabilized in experimental, finally upload it to unstable for the final stages of wheezy development (perhaps a few months before the freeze). No way. The idea of unstable is to get the current upstream code in shape and that won't be achieved with staying with an old kernel. Whatever the technical solution to testing-security kernel might be, it needs to be based on following the upstream kernel development. Totally agreed. We should be tracking current upstream releases, and not just in experimental (which can now be used for upstream release candidates). What about introducing a new linux-2.6-stable kernel package as a compromise? That way users that want stability and security support in testing continue to have that as an option. Also, I will assume responsibility as the maintainer, so there will be hopefully very little impact to any other part of Debian. Also, I can look at generating d-i media for this kernel. Any thoughts on that? The only downside I can think of right away is introducing a huge code copy into the archive. Best wishes, Mike -- 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/AANLkTin7H+4DNM90YK-6hwLaaT+m=gcpukz6xs2gr...@mail.gmail.com
Re: [Secure-testing-team] For discussion: security support strategy for the wheezy kernel
On Mon, Feb 7, 2011 at 5:08 PM, Michael Gilbert wrote: What about introducing a new linux-2.6-stable kernel package as a compromise? That way users that want stability and security support in testing continue to have that as an option. Also, I will assume responsibility as the maintainer, so there will be hopefully very little impact to any other part of Debian. Also, I can look at generating d-i media for this kernel. Any thoughts on that? The only downside I can think of right away is introducing a huge code copy into the archive. Also the same effect can be achieved by apt-pinning the squeeze kernel. Best wishes, Mike -- 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/AANLkTinNLPeSzJn+VhYMFn6om0duiYrX6=m6zjn2x...@mail.gmail.com
Re: [Secure-testing-team] For discussion: security support strategy for the wheezy kernel
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. Whatever the technical solution to testing-security kernel might be, it needs to be based on following the upstream kernel development. 2.6.32.x is in fact an upstream kernel currently being developed ;) No it's not. Go read the definition of development. I'm sorry, but your proposal is insane. Is this kind of negativity really necessary? I'm trying to guide a discussion on a real problem, and I'm an engineer, so I never present problems without at least an idea about a solution. It may not be the best, but you start at something and work toward bettering it until you have something good. Best wishes, Mike -- 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/AANLkTimiCaXv+Yhgg=UW7=1miK-Y5=aLwp9=psvh1...@mail.gmail.com
Bug#612340: linux-image-2.6.32-5-686: kernel 2.6.32-5 hang with call trace about inotify_inode_queue
On Mon, 2011-02-07 at 21:35 +0100, Stephane Purnelle wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: important Tags: upstream Really, you tested an upstream version too? After upgrade from debian 5, I am unable to boot with kernel 2.6.32-5. I can boot with the older kernel 2.6.22. It's maybe due to newer PATA drivers. I don't have all data for resolve because the problem is displayed during boot. We really need you to capture the full console messages via netconsole, serial console, or a photograph. But the end of kernel output says : CALL TRACE: fsnotify open_execve do_execve sys_execve sysenter_do_call and the content of EIP tell inotify_inode_queue. Do you mean inotify_inode_queue_event? 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: For discussion: security support strategy for the wheezy kernel
On Mon, 7 Feb 2011 22:54:53 -0500 Michael Gilbert wrote: Even playing the numbers game with a bit more thoughtful analysis with the LWN data, lenny looks a lot better. It can be seen that lenny (2.6.26) was vulnerable to 69% (36 out of 52) of the vulnerabilities listed there, and squeeze (2.6.32) was vulnerable to 98% (51 out of 52). In my opinion that's a rather substantial difference, and thus a problem worth pondering. Minor correction: lenny was vulnerable to 67% (35 out of 51) and squeeze was vulnerable to 98% (50 out of 51). I had missed the issue that was fixed in 2.6.20 and didn't affect either releases. Best wishes, Mike -- 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/20110207230314.c81daa29.michael.s.gilb...@gmail.com
Bug#585085: Issue detected in Squeeze
This issue is present in the newly released Squeeze. Using kernel: 2.6.32-5-amd64 nfs-common: 1.2.2-4 nfs-kernel-server: 1.2.2-4 Workaround is by downgrading to lenny's version of nfs-comon and nfs-kernel-server: nfs-common: 1.1.2-6lenny2 nfs-kernel-server: 1.1.2-6lenny2
Bug#607879: System hangs up with mmap.c:873!
Fortunately, after some trial and error, I successfully built a linux-headers-2.6.32-5-common_2.6.32-30a~test package with the following two commands: export UPSTREAMVERSION=2.6.32-5 fakeroot make -f debian/rules.real binary-arch-featureset Is this the right way? To partially answer my own question: No, the resulting package is not useable. I had to use the following list of commands to build a package that worked for me: export VERSION=2.6.32 export UPSTREAMVERSION=2.6.32-5 export KERNEL_ARCH=x86 fakeroot make -f debian/rules.real binary-arch-featureset I still would like to know the official and supported way to build the linux-headers-x.y.z-a-common package. Ben? The good thing is that the patch series Ben provided seems to fix the problem. At least I did no longer run into this bug for more than a week now. Thanks Ronny -- 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/201102080838.41003.ronny.stand...@gmx.net
