Re: [Pkg-xen-devel] Graphics driver fixes for squeeze kernel-xen ?
On Sun, Aug 22, 2010 at 01:16:20AM +0300, Pasi Kärkkäinen wrote: > On Sat, Aug 21, 2010 at 10:27:16PM +0100, Ian Campbell wrote: > > On Sat, 2010-08-21 at 23:52 +0300, Pasi Kärkkäinen wrote: > > > On Tue, Aug 17, 2010 at 09:28:32PM +0200, Bastian Blank wrote: > > > > Please send such mails to the maintainer of the package, not me. > > > > > > > > On Tue, Aug 17, 2010 at 08:55:33PM +0300, Pasi Kärkkäinen wrote: > > > > > Is there a plan to update the dom0-capable kernel to the latest > > > > > version from xen/stable-2.6.32.x branch? > > > > > > > > On the way. > > > > > > > > > > Oh, kernel update form xen/stable-2.6.32.x will bring > > > Xen PV-on-HVM drivers aswell.. > > > > These drivers have also been backported to the regular 2.6.32 flavour > > for Squeeze so you won't need the Xen flavour to get this functionality. > > > > Oh nice! Thanks. > Btw which kernel release in squeeze/testing adds these pv-on-hvm drivers? -- Pasi -- 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/20100823141131.gi2...@reaktio.net
Re: [Pkg-xen-devel] Graphics driver fixes for squeeze kernel-xen ?
On Mon, 2010-08-23 at 17:11 +0300, Pasi Kärkkäinen wrote: > On Sun, Aug 22, 2010 at 01:16:20AM +0300, Pasi Kärkkäinen wrote: > > On Sat, Aug 21, 2010 at 10:27:16PM +0100, Ian Campbell wrote: > > > On Sat, 2010-08-21 at 23:52 +0300, Pasi Kärkkäinen wrote: > > > > On Tue, Aug 17, 2010 at 09:28:32PM +0200, Bastian Blank wrote: > > > > > Please send such mails to the maintainer of the package, not me. > > > > > > > > > > On Tue, Aug 17, 2010 at 08:55:33PM +0300, Pasi Kärkkäinen wrote: > > > > > > Is there a plan to update the dom0-capable kernel to the latest > > > > > > version from xen/stable-2.6.32.x branch? > > > > > > > > > > On the way. > > > > > > > > > > > > > Oh, kernel update form xen/stable-2.6.32.x will bring > > > > Xen PV-on-HVM drivers aswell.. > > > > > > These drivers have also been backported to the regular 2.6.32 flavour > > > for Squeeze so you won't need the Xen flavour to get this functionality. > > > > > > > Oh nice! Thanks. > > > > Btw which kernel release in squeeze/testing adds these pv-on-hvm drivers? It will be in 2.6.32-21 which AIUI will be uploaded to Sid shortly. Sorry, it was misleading of me to suggest it was already in Squeeze. -- Ian Campbell Who goeth a-borrowing goeth a-sorrowing. -- Thomas Tusser -- 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/1282573339.12544.790.ca...@zakaz.uk.xensource.com
linux-kbuild-2.6_2.6.35-1~experimental.1_multi.changes ACCEPTED
Accepted: linux-kbuild-2.6.35_2.6.35-1~experimental.1_i386.deb to main/l/linux-kbuild-2.6/linux-kbuild-2.6.35_2.6.35-1~experimental.1_i386.deb linux-kbuild-2.6_2.6.35-1~experimental.1.diff.gz to main/l/linux-kbuild-2.6/linux-kbuild-2.6_2.6.35-1~experimental.1.diff.gz linux-kbuild-2.6_2.6.35-1~experimental.1.dsc to main/l/linux-kbuild-2.6/linux-kbuild-2.6_2.6.35-1~experimental.1.dsc linux-kbuild-2.6_2.6.35.orig.tar.gz to main/l/linux-kbuild-2.6/linux-kbuild-2.6_2.6.35.orig.tar.gz Override entries for your package: linux-kbuild-2.6.35_2.6.35-1~experimental.1_i386.deb - optional devel linux-kbuild-2.6_2.6.35-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/e1onynp-0003dx...@franck.debian.org
Processed (with 1 errors): Re: Bug#594089: keyboard-configuration: caps lock keycode problem
Processing commands for cont...@bugs.debian.org: > forcemerge 594089 593742 Bug#594089: keyboard-configuration: caps lock keycode problem Bug#593742: iceweasel: caps lock toggls bookmarks sidebar Mismatch - only Bugs in the same package can be forcibly merged: Bug 593742 is not in the same package as 594089 > reassign 594089 linux-2.6 Bug #594089 [keyboard-configuration] keyboard-configuration: caps lock keycode problem Bug reassigned from package 'keyboard-configuration' to 'linux-2.6'. Bug No longer marked as found in versions console-setup/1.55. > retitle 594089 caps lock keyboard code problem Bug #594089 [linux-2.6] keyboard-configuration: caps lock keycode problem Changed Bug title to 'caps lock keyboard code problem' from 'keyboard-configuration: caps lock keycode problem' > thanks Stopping processing here. Please contact me if you need assistance. -- 594089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594089 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.128257918812628.transcr...@bugs.debian.org
Processed: reassign 593742 to linux-2.6, forcibly merging 594089 593742
Processing commands for cont...@bugs.debian.org: > reassign 593742 linux-2.6 Bug #593742 {Done: Mike Hommey } [iceweasel] iceweasel: caps lock toggls bookmarks sidebar Bug reassigned from package 'iceweasel' to 'linux-2.6'. Bug No longer marked as found in versions iceweasel/3.5.11-1. > forcemerge 594089 593742 Bug#594089: caps lock keyboard code problem Bug#593742: iceweasel: caps lock toggls bookmarks sidebar Forcibly Merged 593742 594089. > thanks Stopping processing here. Please contact me if you need assistance. -- 594089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594089 593742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593742 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.128257977219030.transcr...@bugs.debian.org
Bug#594092: initramfs-tools: Detection of resume device could terminate prematurely
Package: initramfs-tools Version: 0.98 Severity: normal Hi, My configuration includes (among other things) encrypted swap + uswsusp. Within last month one of the initrams-tools upgrades rendered my setup unusable: resume device (/dev/mapper/swap) was not available during boot. I went and peppered /usr/share/initramfs-tools/hooks/cryptroot with debug output and found out that: 1)I have (orphaned) /etc/suspend.conf lying around since Good Olde Times which lists /dev/sda8 as resume target 2)All other (proper) places list /dev/mapper/swap as resume target 3)"cryptroot" hook terminates prematurely trying to find canonical name for /dev/sda8. Specifically, line 97 of "cryptroot": device=$(canonical_device "$device") || return 0 causes hook to terminate prematurely, broking the resume process. I think that old config files lying around are not the only possible cause for breakage in this place, so other users might be affected as well - for example, if they made errors in their config files. I think that either user should be warned ("Resume device ... is not available, fix manually") or more sensible approach to error handling should be employed. Thank you! -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 8.8M Aug 23 18:59 /boot/initrd.img-2.6.30-1-686 -rw-r--r-- 1 root root 8.6M Aug 10 15:04 /boot/initrd.img-2.6.30-1-686.bak -- /proc/cmdline root=/dev/sda1 ro ramdisk_size=8192 resume=/dev/mapper/swap -- resume RESUME=/dev/mapper/swap -- /proc/filesystems ext2 ext3 fuseblk -- lsmod Module Size Used by iwl394561064 0 omnibook 47824 0 sco 8832 2 rfcomm 30368 14 bnep 10860 4 l2cap 18120 19 rfcomm,bnep vboxnetadp 6428 0 vboxnetflt 12324 0 vboxdrv 155584 2 vboxnetadp,vboxnetflt acpi_cpufreq7640 0 cpufreq_powersave 1292 0 cpufreq_userspace 2768 0 cpufreq_stats 3520 0 cpufreq_conservative 6256 2 autofs420544 1 irda 95720 0 crc_ccitt 1816 1 irda binfmt_misc 7120 1 vmnet 33260 13 parport_pc 22420 0 parport31144 1 parport_pc vmblock11256 1 vmci 42584 0 vmmon 59876 0 kvm_intel 39744 0 kvm 138608 1 kvm_intel fuse 47752 1 nfsd 204900 0 exportfs3792 1 nfsd nfs 221580 0 lockd 57972 2 nfsd,nfs fscache34440 1 nfs nfs_acl 2640 2 nfsd,nfs auth_rpcgss31416 2 nfsd,nfs sunrpc163772 6 nfsd,nfs,lockd,nfs_acl,auth_rpcgss ext3 107172 3 jbd41036 1 ext3 btusb 10276 2 bluetooth 47060 9 sco,rfcomm,bnep,l2cap,btusb visor 13812 0 usbserial 27456 1 visor coretemp5176 0 ip_tables 10188 0 x_tables 14108 1 ip_tables sha256_generic 11216 0 cbc 3012 1 aes_i5868092 4 aes_generic27436 1 aes_i586 dm_crypt 11092 3 dm_mod 49992 7 dm_crypt snd_hda_codec_si3054 4024 1 snd_hda_codec_realtek 178472 1 snd_hda_intel 22192 0 snd_hda_codec 63580 3 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 6120 1 snd_hda_codec arc41560 2 snd_pcm_oss32232 0 snd_mixer_oss 12368 1 snd_pcm_oss ecb 2368 4 snd_pcm62420 4 snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi5688 0 snd_rawmidi18596 1 snd_seq_midi iwlcore92264 1 iwl3945 snd_seq_midi_event 6212 1 snd_seq_midi pcmcia 24280 0 snd_seq42436 2 snd_seq_midi,snd_seq_midi_event snd_timer 17436 2 snd_pcm,snd_seq snd_seq_device 6136 3 snd_seq_midi,snd_rawmidi,snd_seq joydev 8576 0 snd49060 12 snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device mac80211 142848 2 iwl3945,iwlcore yenta_socket 21168 1 tifm_7xx1 4864 0 intel_agp 22900 0 rsrc_nonstatic 9664 1 yenta_socket soundcore 6184 1 snd i2c_i8018564 0 nvidia 8869740 31 pcmcia_core31212 3 pcmcia,yenta_socket,rsrc_nonstatic pcspkr 2104 0 rng_core3672 0 rfkill 9668 2 iwlcore snd_page_all
Bug#594092: initramfs-tools: Detection of resume device could terminate prematurely
reassign 594092 cryptsetup stop On Mon, Aug 23, 2010 at 07:12:59PM +0300, Dmitry Astapov wrote: > Package: initramfs-tools > Version: 0.98 > Severity: normal > > Hi, > > My configuration includes (among other things) encrypted swap + uswsusp. > > Within last month one of the initrams-tools upgrades rendered my setup > unusable: resume device (/dev/mapper/swap) was not available during boot. > > I went and peppered /usr/share/initramfs-tools/hooks/cryptroot with debug > output and found out that: > 1)I have (orphaned) /etc/suspend.conf lying around since Good Olde Times > which lists /dev/sda8 as resume target > 2)All other (proper) places list /dev/mapper/swap as resume target > 3)"cryptroot" hook terminates prematurely trying to find canonical name for > /dev/sda8. > > Specifically, line 97 of "cryptroot": > device=$(canonical_device "$device") || return 0 > > causes hook to terminate prematurely, broking the resume process. I think > that old config files lying around are not the only possible cause for > breakage in this place, so other users might be affected as well - for > example, if they made errors in their config files. > > I think that either user should be warned ("Resume device ... is not > available, fix manually") or more sensible approach to error handling should > be employed. > > Thank you! reassigning to the good folks that do the encryption. happy day. > -- Package-specific info: > -- initramfs sizes > -rw-r--r-- 1 root root 8.8M Aug 23 18:59 /boot/initrd.img-2.6.30-1-686 > -rw-r--r-- 1 root root 8.6M Aug 10 15:04 /boot/initrd.img-2.6.30-1-686.bak > -- /proc/cmdline > root=/dev/sda1 ro ramdisk_size=8192 resume=/dev/mapper/swap > > -- resume > RESUME=/dev/mapper/swap > -- /proc/filesystems > ext2 > ext3 > fuseblk > > -- lsmod > Module Size Used by > iwl394561064 0 > omnibook 47824 0 > sco 8832 2 > rfcomm 30368 14 > bnep 10860 4 > l2cap 18120 19 rfcomm,bnep > vboxnetadp 6428 0 > vboxnetflt 12324 0 > vboxdrv 155584 2 vboxnetadp,vboxnetflt > acpi_cpufreq7640 0 > cpufreq_powersave 1292 0 > cpufreq_userspace 2768 0 > cpufreq_stats 3520 0 > cpufreq_conservative 6256 2 > autofs420544 1 > irda 95720 0 > crc_ccitt 1816 1 irda > binfmt_misc 7120 1 > vmnet 33260 13 > parport_pc 22420 0 > parport31144 1 parport_pc > vmblock11256 1 > vmci 42584 0 > vmmon 59876 0 > kvm_intel 39744 0 > kvm 138608 1 kvm_intel > fuse 47752 1 > nfsd 204900 0 > exportfs3792 1 nfsd > nfs 221580 0 > lockd 57972 2 nfsd,nfs > fscache34440 1 nfs > nfs_acl 2640 2 nfsd,nfs > auth_rpcgss31416 2 nfsd,nfs > sunrpc163772 6 nfsd,nfs,lockd,nfs_acl,auth_rpcgss > ext3 107172 3 > jbd41036 1 ext3 > btusb 10276 2 > bluetooth 47060 9 sco,rfcomm,bnep,l2cap,btusb > visor 13812 0 > usbserial 27456 1 visor > coretemp5176 0 > ip_tables 10188 0 > x_tables 14108 1 ip_tables > sha256_generic 11216 0 > cbc 3012 1 > aes_i5868092 4 > aes_generic27436 1 aes_i586 > dm_crypt 11092 3 > dm_mod 49992 7 dm_crypt > snd_hda_codec_si3054 4024 1 > snd_hda_codec_realtek 178472 1 > snd_hda_intel 22192 0 > snd_hda_codec 63580 3 > snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel > snd_hwdep 6120 1 snd_hda_codec > arc41560 2 > snd_pcm_oss32232 0 > snd_mixer_oss 12368 1 snd_pcm_oss > ecb 2368 4 > snd_pcm62420 4 > snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec,snd_pcm_oss > snd_seq_midi5688 0 > snd_rawmidi18596 1 snd_seq_midi > iwlcore92264 1 iwl3945 > snd_seq_midi_event 6212 1 snd_seq_midi > pcmcia 24280 0 > snd_seq42436 2 snd_seq_midi,snd_seq_midi_event > snd_timer 17436 2 snd_pcm,snd_seq > snd_seq_device 6136 3 snd_seq_midi,snd_rawmidi,snd_seq > joydev 8576 0 > snd49060 12 > snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device > mac80211 142848 2 iwl3945,iwlcore > yenta_socket 2116
Processed: Re: Bug#594092: initramfs-tools: Detection of resume device could terminate prematurely
Processing commands for cont...@bugs.debian.org: > reassign 594092 cryptsetup Bug #594092 [initramfs-tools] initramfs-tools: Detection of resume device could terminate prematurely Bug reassigned from package 'initramfs-tools' to 'cryptsetup'. Bug No longer marked as found in versions initramfs-tools/0.98. > stop Stopping processing here. Please contact me if you need assistance. -- 594092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594092 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.128258053227229.transcr...@bugs.debian.org
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package linux-2.6 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #591073 (http://bugs.debian.org/591073) > # * http://bugzilla.kernel.org/show_bug.cgi?id=16552 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> INVALID > # * closed upstream > tags 591073 + fixed-upstream Bug #591073 [linux-2.6] linux-image-2.6.32-5-amd64: Suspend-to-RAM regression Added tag(s) fixed-upstream. > usertags 591073 - status-NEW Bug#591073: linux-image-2.6.32-5-amd64: Suspend-to-RAM regression Usertags were: status-NEW. Usertags are now: . > usertags 591073 + status-RESOLVED resolution-INVALID Bug#591073: linux-image-2.6.32-5-amd64: Suspend-to-RAM regression There were no usertags set. Usertags are now: status-RESOLVED resolution-INVALID. > thanks Stopping processing here. Please contact me if you need assistance. -- 591073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591073 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.128258655517537.transcr...@bugs.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #591073 (http://bugs.debian.org/591073) # * http://bugzilla.kernel.org/show_bug.cgi?id=16552 # * remote status changed: NEW -> RESOLVED # * remote resolution changed: (?) -> INVALID # * closed upstream tags 591073 + fixed-upstream usertags 591073 - status-NEW usertags 591073 + status-RESOLVED resolution-INVALID thanks -- 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/20100823180233.22407.23209.btsl...@merkel.debian.org
Bug#594118: initramfs-tools: Generating image error. Unexpected operator
Package: initramfs-tools Version: 0.98 Severity: important Hi! I have a problem trying to generate a new initram: debian:~# update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 [: 33: #: unexpected operator /boot/initrd.img-2.6.18-6-686 does not exist. Cannot update. debian:~# If you need more information, please ask me. Thanks a lot. kix. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 9.2M Aug 23 21:45 /boot/initrd.img-2.6.32-5-686 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=5814b385-7c4d-4a8f-bb62-0b4370032c12 ro quiet -- resume # RESUME=/dev/sda3 RESUME='UUID=6242f227-2677-4df5-85d1-c64262909585' -- /proc/filesystems ext3 fuseblk -- lsmod Module Size Used by sco 5857 2 bridge 32987 0 stp 996 1 bridge bnep7444 2 rfcomm 25167 0 l2cap 21705 4 bnep,rfcomm crc16 1027 1 l2cap bluetooth 36327 6 sco,bnep,rfcomm,l2cap vmnet 31752 13 vmblock 8518 1 vsock 29259 0 vmci 41779 1 vsock vmmon 53690 0 fuse 43758 1 dm_snapshot17969 0 dm_mirror 9671 0 dm_region_hash 5644 1 dm_mirror dm_log 6369 2 dm_mirror,dm_region_hash dm_mod 46082 3 dm_snapshot,dm_mirror,dm_log firewire_sbp2 9647 0 loop9757 0 snd_hda_codec_intelhdmi 9027 1 snd_hda_codec_realtek 163226 1 snd_hda_intel 16787 1 snd_hda_codec 46002 3 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 4054 1 snd_hda_codec snd_pcm_oss28671 0 snd_mixer_oss 10461 2 snd_pcm_oss snd_pcm47214 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi3576 0 snd_rawmidi12505 1 snd_seq_midi snd_seq_midi_event 3684 1 snd_seq_midi snd_seq35463 2 snd_seq_midi,snd_seq_midi_event arc4 974 2 snd_timer 12258 2 snd_pcm,snd_seq snd_seq_device 3673 3 snd_seq_midi,snd_rawmidi,snd_seq ecb 1405 2 snd34363 12 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device rt2500pci 11311 0 rt2x00pci 3773 1 rt2500pci rt2x00lib 19029 2 rt2500pci,rt2x00pci i2c_i8016462 0 led_class 1757 1 rt2x00lib mac80211 123302 2 rt2x00pci,rt2x00lib cfg80211 87601 2 rt2x00lib,mac80211 rfkill 10264 3 bluetooth,cfg80211 soundcore 3450 2 snd eeprom_93cx6 963 1 rt2500pci nouveau 314864 2 ttm33378 1 nouveau drm_kms_helper 18305 1 nouveau drm 112020 4 nouveau,ttm,drm_kms_helper i2c_algo_bit3497 1 nouveau i2c_core 12696 5 i2c_i801,nouveau,drm_kms_helper,drm,i2c_algo_bit snd_page_alloc 5045 2 snd_hda_intel,snd_pcm joydev 6771 0 evdev 5609 14 parport_pc 15799 0 button 3598 1 nouveau pcspkr 1207 0 psmouse44657 0 parport22554 1 parport_pc processor 26599 0 serio_raw 2916 0 ext3 94204 2 jbd32169 1 ext3 mbcache 3762 1 ext3 usbhid 27980 0 hid50645 1 usbhid sg 15968 0 fan 2586 0 sd_mod 25869 4 crc_t10dif 1012 1 sd_mod sr_mod 10770 0 cdrom 26487 1 sr_mod firewire_ohci 16509 0 firewire_core 31187 2 firewire_sbp2,firewire_ohci usb_storage30541 0 ata_generic 2019 0 thermal 9206 0 uhci_hcd 16057 0 ata_piix 17640 3 crc_itu_t 1035 1 firewire_core sky2 32829 0 ehci_hcd 27851 0 pata_jmicron1452 0 libata115721 3 ata_generic,ata_piix,pata_jmicron thermal_sys 9378 3 processor,fan,thermal scsi_mod 101401 6 firewire_sbp2,sg,sd_mod,sr_mod,usb_storage,libata usbcore98402 5 usbhid,usb_storage,uhci_hcd,ehci_hcd nls_base4541 1 usbcore -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MO
Bug#594125: [linux-image-2.6.35-trunk-amd64] BSD ring buffer implementation makes suspend to ram unreliable
Package: linux-image-2.6.35-trunk-amd64 Version: 1~experimental.2 Severity: grave Tags: patch --- Please enter the report below this line. --- There is a bug in the linux kernel 2.6.35, that makes suspend to ram unusable (it seems to be fixed in 2.6.36-rc2) [1]. The symptoms are: - Suspend to ram from X hangs the computer, the only option is to press the power button for ~5 sec and thus forcefully turning off the computer (SysRq does not work for me). After a while (when not turning off the computer of cause) the fan goes to full power. - However, suspend to ram from console works. - The hang does happen every time on my laptop. However, on some computers that seems to happen only sporadically. The link [1] contains two possible solutions for this problem. 1. Turn off BSD completely by replacing the corresponding define in i915_drv.h with #define HAS_BSD(dev)(0) 2. 2.6.36-rc2 seems to fix the problem (according to a comment on [1]). [1] https://bugs.freedesktop.org/show_bug.cgi?id=29406 --- System information. --- Architecture: amd64 Kernel: Linux 2.6.32-5-amd64 Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org 101 experimental-snapshots qt-kde.debian.net 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-= module-init-tools | 3.12-1 linux-base (>= 2.6.35-1~experimental.2) | 2.6.35-1~experimental.2 initramfs-tools(>= 0.55) | 0.98 OR linux-initramfs-tool | Recommends(Version) | Installed ===-+- firmware-linux-free (>= 2.6.35) | 2.6.35-1~experimental.2 Suggests (Version) | Installed ===-+-=== linux-doc-2.6.35| 2.6.35-1~experimental.2 grub| OR lilo| -- Florian Kriener August-Bebel-Straße 46 04275 Leipzig Tel: +49 341-3047701 Mobil: +49 176-20070874 -- 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/201008232228.31873.flor...@kriener.org
Bug#570382: after upgrade: "vlogin: openpty(): No such file or directory"
Thanks, I tested that [1], and it does seem to work. Hopefully this bug is being worked on by someone upstream. AFAIK it's not worked on upstream and very probably fixed in newer vserver releases. I asked on vserver's IRC channel and was told in quite clear words something along the lines of "we don't care about ancient kernels that Debian ships". You may want to re-inquiry @vserver. On a different note: the last update to the most recent DSA kernels [2] went completely smoothly - that is all vservers restarted without a hickup. Makes me wonder if that was caused by a change in the 2.6.26-24lenny1 kernel? We'll see at the next upgrade. I'm Cc:ing this to all bug report participants, I hope you all don't mind. *t [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570382#65 [2] http://www.debian.org/security/2010/dsa-2094 -- 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/alpine.deb.2.00.1008232142430.6...@tpo-laptop
Bug#566574: linux-image-2.6.32-trunk-686: ACPI I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299]
Just tested with 2.6.32-5-686 (2.6.32-20). Same message appears. However, now I note that I have in /etc/modules # Generated by sensors-detect on Fri Jun 6 22:03:29 2008 # Chip drivers w83627ehf coretemp Rerunning sensors-detect still detects the same. In System Monitor under Hardware Sensors is shown: atk0110 (loaded by udev? - FT) coretemp (loaded by /etc/modules? -FT) Probably I need to remove w83627ehf from /etc/modules and all should be fine? Ferry
Processed: retitle 594095 to linux-2.6: address space collision on of device [0xfebe0000-0xfebe7fff] ...
Processing commands for cont...@bugs.debian.org: > retitle 594095 linux-2.6: address space collision on of device > [0xfebe-0xfebe7fff] Bug #594095 [snapshot.debian.org] snapshot.debian.org: address space collision on of device [0xfebe-0xfebe7fff] Changed Bug title to 'linux-2.6: address space collision on of device [0xfebe-0xfebe7fff]' from 'snapshot.debian.org: address space collision on of device [0xfebe-0xfebe7fff]' > reassign 594095 linux-2.6 Bug #594095 [snapshot.debian.org] linux-2.6: address space collision on of device [0xfebe-0xfebe7fff] Bug reassigned from package 'snapshot.debian.org' to 'linux-2.6'. > thanks Stopping processing here. Please contact me if you need assistance. -- 594095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594095 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.12825981316950.transcr...@bugs.debian.org
speakup in Debian kernel and installer
[Please include debian-kernel or me in replies; I'm not subscribed to -accessibility.] I haven't seen any bug reports regarding speakup drivers included in the Linux 2.6.32 kernel packages or testing versions of the installer. However I haven't seen any positive reports either. Are they working properly? Also, has anyone tried speakup drivers in Linux 2.6.35 in experimental? 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: speakup in Debian kernel and installer
Hi. On Tue, Aug 24, 2010 at 12:35:03AM +0100, Ben Hutchings wrote: > [Please include debian-kernel or me in replies; I'm not subscribed to > -accessibility.] > > I haven't seen any bug reports regarding speakup drivers included in the > Linux 2.6.32 kernel packages or testing versions of the installer. > However I haven't seen any positive reports either. Are they working > properly? > Yes, speakup works fine using the accent SA or soft synth drivers here. I also haven't seen any problems reported with 2.6.32 > Also, has anyone tried speakup drivers in Linux 2.6.35 in experimental? > I haven't tried 2.6.35, but I have seen mail on the speakup list from people who are having problems with serial ports in 2.6.35. They aren't using Debian, but a kernel built from source. Kenny > Ben. > > -- > Ben Hutchings > Once a job is fouled up, anything done to improve it makes it worse. -- 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/20100824005821.ga6...@hittsjunk.net
Re: speakup in Debian kernel and installer
Hello, Ben Hutchings, le Tue 24 Aug 2010 00:35:03 +0100, a écrit : > [Please include debian-kernel or me in replies; I'm not subscribed to > -accessibility.] > > I haven't seen any bug reports regarding speakup drivers included in the > Linux 2.6.32 kernel packages or testing versions of the installer. > However I haven't seen any positive reports either. Are they working > properly? I've tried the daily build yesterday, and it worked just fine. Samuel -- 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/20100824011105.gv4...@const.famille.thibault.fr
Re: speakup in Debian kernel and installer
Hi Sam, As you know I attend to promote linux as accessibility tool. That's why I try some solutions, even these I don't use myself daily (speech in particular). That's also why I tried gnome-orca 2.30 even if I had to install testing package on my stable (Gnome 2.22) and I suspect it causes issues. I've wanted to test speakup for a long time but never understood how it works. As you tested, can you explain to me what has to be entered. speakup is included, for example, in LFS livecd and Debian, seems the only solution in such contexts. I heard of drivers... but what drivers? How can I know those supported? Is there a relationship with kernel as I see in this treead (LFS livecd has an older kernel (2008))? Actually, do you have a tutorial about this point to know what I've to enter, what are available drivers, what's the role of the kernel's release. Thanks, Regards, Jean-Philippe MENGUAL Le mardi 24 août 2010 à 03:11 +0200, Samuel Thibault a écrit : > Hello, > > Ben Hutchings, le Tue 24 Aug 2010 00:35:03 +0100, a écrit : > > [Please include debian-kernel or me in replies; I'm not subscribed to > > -accessibility.] > > > > I haven't seen any bug reports regarding speakup drivers included in the > > Linux 2.6.32 kernel packages or testing versions of the installer. > > However I haven't seen any positive reports either. Are they working > > properly? > > I've tried the daily build yesterday, and it worked just fine. > > Samuel > > -- 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/1282615704.27264.55.ca...@debian
Bug#594149: linux-image-2.6.32-5-amd64: Lid switch correct every other time; suspend every other lid close; Samsung N150-11 netbook
Package: linux-2.6 Version: 2.6.32-20 Severity: normal Samsung N150-11 netbook. Each lid close&open toggles the lid switch state so when the lid is open, half the time it reports closed: e...@esammy:~$ cat /proc/acpi/button/lid/LID0/state state: open # close & open lid e...@esammy:~$ cat /proc/acpi/button/lid/LID0/state state: closed So, the netbook only suspends every other time the lid is closed. This could be dangerous with the netbook stowed in running mode getting hot. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-20) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Thu Aug 12 13:01:50 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=3cb206a7-b396-4c4f-b462-cd89b27eb3c4 ro quiet ** Not tainted ** Kernel log: [ 1050.208993] pcieport :00:1c.0: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [ 1050.209058] pcieport :00:1c.1: restoring config space at offset 0xf (was 0x200, writing 0x204) [ 1050.209078] pcieport :00:1c.1: restoring config space at offset 0x9 (was 0x10001, writing 0x40514041) [ 1050.209089] pcieport :00:1c.1: restoring config space at offset 0x8 (was 0x0, writing 0x40304020) [ 1050.209100] pcieport :00:1c.1: restoring config space at offset 0x7 (was 0x2000, writing 0x4040) [ 1050.209117] pcieport :00:1c.1: restoring config space at offset 0x3 (was 0x81, writing 0x810008) [ 1050.209129] pcieport :00:1c.1: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [ 1050.209189] pcieport :00:1c.2: restoring config space at offset 0xf (was 0x40300, writing 0x40303) [ 1050.209208] pcieport :00:1c.2: restoring config space at offset 0x9 (was 0x10001, writing 0x40714061) [ 1050.209220] pcieport :00:1c.2: restoring config space at offset 0x8 (was 0x0, writing 0xf020f020) [ 1050.209231] pcieport :00:1c.2: restoring config space at offset 0x7 (was 0x2000, writing 0x2020) [ 1050.209247] pcieport :00:1c.2: restoring config space at offset 0x3 (was 0x81, writing 0x810008) [ 1050.209260] pcieport :00:1c.2: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [ 1050.209319] pcieport :00:1c.3: restoring config space at offset 0xf (was 0x400, writing 0x40a) [ 1050.209339] pcieport :00:1c.3: restoring config space at offset 0x9 (was 0x10001, writing 0x40b140a1) [ 1050.209350] pcieport :00:1c.3: restoring config space at offset 0x8 (was 0x0, writing 0x40904080) [ 1050.209361] pcieport :00:1c.3: restoring config space at offset 0x7 (was 0x2000, writing 0x5050) [ 1050.209377] pcieport :00:1c.3: restoring config space at offset 0x3 (was 0x81, writing 0x810008) [ 1050.209390] pcieport :00:1c.3: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [ 1050.209462] uhci_hcd :00:1d.0: restoring config space at offset 0x1 (was 0x285, writing 0x281) [ 1050.209506] uhci_hcd :00:1d.1: restoring config space at offset 0x1 (was 0x285, writing 0x281) [ 1050.209549] uhci_hcd :00:1d.2: restoring config space at offset 0x1 (was 0x285, writing 0x281) [ 1050.209591] uhci_hcd :00:1d.3: restoring config space at offset 0x1 (was 0x285, writing 0x281) [ 1050.209643] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 0x2900106, writing 0x2900102) [ 1050.209686] pci :00:1e.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1) [ 1050.209697] pci :00:1e.0: restoring config space at offset 0x8 (was 0x0, writing 0xfff0) [ 1050.209783] ahci :00:1f.2: restoring config space at offset 0xf (was 0x200, writing 0x20a) [ 1050.209815] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b7, writing 0x2b00407) [ 1050.209924] ath9k :05:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10b) [ 1050.209959] ath9k :05:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xf014) [ 1050.209971] ath9k :05:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x8) [ 1050.209985] ath9k :05:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100107) [ 1050.210270] sky2 :09:00.0: restoring config space at offset 0xf (was 0x100, writing 0x103) [ 1050.210406] sky2 :09:00.0: restoring config space at offset 0x6 (was 0x1, writing 0x2001) [ 1050.210459] sky2 :09:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xf024) [ 1050.210488] sky2 :09:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x8) [ 1050.210541] sky2 :09:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100507) [ 1050.222997] i915 :00:02.0: setting latency timer to 64 [ 1050.223545] [drm] Big FIFO is enabled [ 1050.292089] [drm] Big FIFO is enabled [ 1050.292109] [drm] Big FIFO is enabled [ 1050.292280] [drm] Big FIFO is enabled [ 1050.316212] HDA Intel :
Processed: tagging 593683
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 593683 + pending Bug #593683 [linux-2.6] linux-2.6 - images does not conflict with pre-policy versions of bootloaders Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 593683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593683 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.128262539924128.transcr...@bugs.debian.org
Processed: tagging 582105
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 582105 + pending Bug #582105 [linux-2.6] 855GM: hard hang when closing lid Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 582105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582105 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.128262672130148.transcr...@bugs.debian.org
Processed: tagging 568207
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 568207 + pending Bug #568207 [linux-2.6] KMS does not work on 82830 CGC Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 568207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568207 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.128262671930128.transcr...@bugs.debian.org
Processed: tagging 593432
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 593432 + pending Bug #593432 [linux-2.6] [i830] Black screen with kms and i915 Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 593432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593432 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.128262682230637.transcr...@bugs.debian.org
Processed: tagging 593507
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 593507 + pending Bug #593507 [linux-2.6] linux-image-2.6.32-5-686: screen blank with KMS on Intel i830 Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 593507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593507 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.128262682330656.transcr...@bugs.debian.org
Bug#588782: same bug as 586369
same bug as 586369
Bug#594156: modules=most does not add virtio_net
Package: initramfs-tools Version: 0.97 Severity: normal Hi, I'm using initramfs-tools in the context of an FAI nfsroot, read, I want to have it booted in a KVM guest with both virtio hard drives and virtio_net. It turns out despite having 'MODULES=most' in /srv/fai/nfsroot/live/filesystem.dir/etc/initramfs-tools/initramfs.conf, the modules 'virtio_pci', 'virtio_blk' and 'virtio_ring' are included, but 'virtio_net' is missing. I'm still looking for a good workaround to get an virtio-net enabled guest installed via an FAI nfsroot. -- 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/20100824064311.16257.51356.report...@localhost.localdomain