Bug#427357: linux-source-2.6.21-4: module psmouse.ko gives segmentation fault
Package: linux-source-2.6.21-4 for amd64 Severity: normal mouse driver selected as a module for kernel build via xconfig|make-kpkg When logged into gdm the cursor is not activated by the mouse. lsmod shows that the module psmouse is not loaded running # insmod ./psmouse.ko gives segmentation fault segmentation fault message ends with error 4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427438: yair-0.0.12-10: Fails to build linux-image-2.6.18-4-k7
Package: yair-0.0.12-10 Severity: serious Justification: no longer builds from source -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-rc3-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Here's the output of error -- dpkg -i /var/cache/apt/archives/linux-image-2.6.18-4-k7_2.6.18.dfsg.1-12_i386.deb (Reading database ... 202587 files and directories currently installed.) Preparing to replace linux-image-2.6.18-4-k7 2.6.18.dfsg.1-12 (using .../linux-image-2.6.18-4-k7_2.6.18.dfsg.1-12_i386.deb) ... The directory /lib/modules/2.6.18-4-k7 still exists. Continuing as directed. Done. Unpacking replacement linux-image-2.6.18-4-k7 ... Running postrm hook script /sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.18-4-k7 Found kernel: /boot/vmlinuz-2.6.17-rc3-k7 Found kernel: /boot/vmlinuz-2.6.16.5-kanotix-2 Found kernel: /boot/vmlinuz-2.6.15-1-k7 Updating /boot/grub/menu.lst ... done Setting up linux-image-2.6.18-4-k7 (2.6.18.dfsg.1-12) ... Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-4-k7/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-4-k7/source Running depmod. Finding valid ramdisk creators. Using /usr/sbin/mkinitrd.yaird to build the ramdisk. yaird error: bad value in /boot/config-2.6.18-4-k7: CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config (fatal) /usr/sbin/mkinitrd.yaird failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.18-4-k7 (--install): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: linux-image-2.6.18-4-k7 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#427381: Random pixels - not chars - in Console display
Processing commands for [EMAIL PROTECTED]: reassign 427357 linux-2.6 Bug#427357: linux-source-2.6.21-4: module psmouse.ko gives segmentation fault Warning: Unknown package 'linux-source-2.6.21-4' Warning: Unknown package 'for' Warning: Unknown package 'amd64' Bug reassigned from package `linux-source-2.6.21-4 for amd64' to `linux-2.6'. reassign 427381 linux-2.6 Bug#427381: Random pixels - not chars - in Console display Warning: Unknown package 'linux-image' Bug reassigned from package `linux-image' to `linux-2.6'. -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-2.6_2.6.18.dfsg.1-13lenny1_alpha.changes ACCEPTED
Accepted: linux-headers-2.6.18-5-all-alpha_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-5-all-alpha_2.6.18.dfsg.1-13lenny1_alpha.deb linux-headers-2.6.18-5-all_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-5-all_2.6.18.dfsg.1-13lenny1_alpha.deb linux-headers-2.6.18-5-alpha-generic_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-5-alpha-generic_2.6.18.dfsg.1-13lenny1_alpha.deb linux-headers-2.6.18-5-alpha-legacy_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-5-alpha-legacy_2.6.18.dfsg.1-13lenny1_alpha.deb linux-headers-2.6.18-5-alpha-smp_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-5-alpha-smp_2.6.18.dfsg.1-13lenny1_alpha.deb linux-headers-2.6.18-5-vserver-alpha_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-5-vserver-alpha_2.6.18.dfsg.1-13lenny1_alpha.deb linux-headers-2.6.18-5-vserver_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-5-vserver_2.6.18.dfsg.1-13lenny1_alpha.deb linux-headers-2.6.18-5_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-5_2.6.18.dfsg.1-13lenny1_alpha.deb linux-image-2.6.18-5-alpha-generic_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-image-2.6.18-5-alpha-generic_2.6.18.dfsg.1-13lenny1_alpha.deb linux-image-2.6.18-5-alpha-legacy_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-image-2.6.18-5-alpha-legacy_2.6.18.dfsg.1-13lenny1_alpha.deb linux-image-2.6.18-5-alpha-smp_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-image-2.6.18-5-alpha-smp_2.6.18.dfsg.1-13lenny1_alpha.deb linux-image-2.6.18-5-vserver-alpha_2.6.18.dfsg.1-13lenny1_alpha.deb to pool/main/l/linux-2.6/linux-image-2.6.18-5-vserver-alpha_2.6.18.dfsg.1-13lenny1_alpha.deb Override entries for your package: linux-headers-2.6.18-5-all-alpha_2.6.18.dfsg.1-13lenny1_alpha.deb - optional devel linux-headers-2.6.18-5-all_2.6.18.dfsg.1-13lenny1_alpha.deb - optional devel linux-headers-2.6.18-5-alpha-generic_2.6.18.dfsg.1-13lenny1_alpha.deb - optional devel linux-headers-2.6.18-5-alpha-legacy_2.6.18.dfsg.1-13lenny1_alpha.deb - optional devel linux-headers-2.6.18-5-alpha-smp_2.6.18.dfsg.1-13lenny1_alpha.deb - optional devel linux-headers-2.6.18-5-vserver-alpha_2.6.18.dfsg.1-13lenny1_alpha.deb - optional devel linux-headers-2.6.18-5-vserver_2.6.18.dfsg.1-13lenny1_alpha.deb - optional devel linux-headers-2.6.18-5_2.6.18.dfsg.1-13lenny1_alpha.deb - optional devel linux-image-2.6.18-5-alpha-generic_2.6.18.dfsg.1-13lenny1_alpha.deb - optional admin linux-image-2.6.18-5-alpha-legacy_2.6.18.dfsg.1-13lenny1_alpha.deb - optional admin linux-image-2.6.18-5-alpha-smp_2.6.18.dfsg.1-13lenny1_alpha.deb - optional admin linux-image-2.6.18-5-vserver-alpha_2.6.18.dfsg.1-13lenny1_alpha.deb - optional admin Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of linux-modules-extra-2.6_2.6.18-7+etch3_sparc.changes
linux-modules-extra-2.6_2.6.18-7+etch3_sparc.changes uploaded successfully to localhost along with the files: linux-modules-extra-2.6_2.6.18-7+etch3.dsc linux-modules-extra-2.6_2.6.18-7+etch3.tar.gz redhat-cluster-modules-2.6.18-5-sparc32_2.6.18+1.03.00-7+etch3_sparc.deb redhat-cluster-modules-2.6-sparc32_2.6.18-7+etch3_sparc.deb squashfs-modules-2.6.18-5-sparc32_2.6.18+3.1r2-7+etch3_sparc.deb squashfs-modules-2.6-sparc32_2.6.18-7+etch3_sparc.deb unionfs-modules-2.6.18-5-sparc32_2.6.18+1.4+debian-7+etch3_sparc.deb unionfs-modules-2.6-sparc32_2.6.18-7+etch3_sparc.deb redhat-cluster-modules-2.6.18-5-sparc64_2.6.18+1.03.00-7+etch3_sparc.deb redhat-cluster-modules-2.6-sparc64_2.6.18-7+etch3_sparc.deb squashfs-modules-2.6.18-5-sparc64_2.6.18+3.1r2-7+etch3_sparc.deb squashfs-modules-2.6-sparc64_2.6.18-7+etch3_sparc.deb unionfs-modules-2.6.18-5-sparc64_2.6.18+1.4+debian-7+etch3_sparc.deb unionfs-modules-2.6-sparc64_2.6.18-7+etch3_sparc.deb redhat-cluster-modules-2.6.18-5-sparc64-smp_2.6.18+1.03.00-7+etch3_sparc.deb redhat-cluster-modules-2.6-sparc64-smp_2.6.18-7+etch3_sparc.deb squashfs-modules-2.6.18-5-sparc64-smp_2.6.18+3.1r2-7+etch3_sparc.deb squashfs-modules-2.6-sparc64-smp_2.6.18-7+etch3_sparc.deb unionfs-modules-2.6.18-5-sparc64-smp_2.6.18+1.4+debian-7+etch3_sparc.deb unionfs-modules-2.6-sparc64-smp_2.6.18-7+etch3_sparc.deb redhat-cluster-modules-2.6.18-5-vserver-sparc64_2.6.18+1.03.00-7+etch3_sparc.deb redhat-cluster-modules-2.6-vserver-sparc64_2.6.18-7+etch3_sparc.deb squashfs-modules-2.6.18-5-vserver-sparc64_2.6.18+3.1r2-7+etch3_sparc.deb squashfs-modules-2.6-vserver-sparc64_2.6.18-7+etch3_sparc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of linux-modules-contrib-2.6_2.6.18-4+etch2_sparc.changes
linux-modules-contrib-2.6_2.6.18-4+etch2_sparc.changes uploaded successfully to localhost along with the files: linux-modules-contrib-2.6_2.6.18-4+etch2.dsc linux-modules-contrib-2.6_2.6.18-4+etch2.tar.gz ivtv-modules-2.6.18-5-sparc32_2.6.18+0.8.2-4+etch2_sparc.deb ivtv-modules-2.6-sparc32_2.6.18-4+etch2_sparc.deb ivtv-modules-2.6.18-5-sparc64_2.6.18+0.8.2-4+etch2_sparc.deb ivtv-modules-2.6-sparc64_2.6.18-4+etch2_sparc.deb ivtv-modules-2.6.18-5-sparc64-smp_2.6.18+0.8.2-4+etch2_sparc.deb ivtv-modules-2.6-sparc64-smp_2.6.18-4+etch2_sparc.deb ivtv-modules-2.6.18-5-vserver-sparc64_2.6.18+0.8.2-4+etch2_sparc.deb ivtv-modules-2.6-vserver-sparc64_2.6.18-4+etch2_sparc.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-modules-extra-2.6_2.6.18-7+etch3_sparc.changes is NEW
linux-modules-extra-2.6_2.6.18-7+etch3.dsc to pool/main/l/linux-modules-extra-2.6/linux-modules-extra-2.6_2.6.18-7+etch3.dsc linux-modules-extra-2.6_2.6.18-7+etch3.tar.gz to pool/main/l/linux-modules-extra-2.6/linux-modules-extra-2.6_2.6.18-7+etch3.tar.gz redhat-cluster-modules-2.6-sparc32_2.6.18-7+etch3_sparc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-sparc32_2.6.18-7+etch3_sparc.deb redhat-cluster-modules-2.6-sparc64-smp_2.6.18-7+etch3_sparc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-sparc64-smp_2.6.18-7+etch3_sparc.deb redhat-cluster-modules-2.6-sparc64_2.6.18-7+etch3_sparc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-sparc64_2.6.18-7+etch3_sparc.deb redhat-cluster-modules-2.6-vserver-sparc64_2.6.18-7+etch3_sparc.deb to pool/main/l/linux-modules-extra-2.6/redhat-cluster-modules-2.6-vserver-sparc64_2.6.18-7+etch3_sparc.deb (new) redhat-cluster-modules-2.6.18-5-sparc32_2.6.18+1.03.00-7+etch3_sparc.deb optional admin Redhat Cluster infrastructure modules for Linux 2.6.18 on uniprocessor sparc32 (sun4m) This package provides the Redhat Cluster infrastructure modules for the Linux kernel version 2.6.18 on uniprocessor sparc32 (sun4m) machines. (new) redhat-cluster-modules-2.6.18-5-sparc64-smp_2.6.18+1.03.00-7+etch3_sparc.deb optional admin Redhat Cluster infrastructure modules for Linux 2.6.18 on multiprocessor 64-bit UltraSPARC This package provides the Redhat Cluster infrastructure modules for the Linux kernel version 2.6.18 on multiprocessor 64-bit UltraSPARC machines. (new) redhat-cluster-modules-2.6.18-5-sparc64_2.6.18+1.03.00-7+etch3_sparc.deb optional admin Redhat Cluster infrastructure modules for Linux 2.6.18 on uniprocessor 64-bit UltraSPARC This package provides the Redhat Cluster infrastructure modules for the Linux kernel version 2.6.18 on uniprocessor 64-bit UltraSPARC machines. (new) redhat-cluster-modules-2.6.18-5-vserver-sparc64_2.6.18+1.03.00-7+etch3_sparc.deb optional admin Redhat Cluster infrastructure modules for Linux 2.6.18 on uniprocessor 64-bit UltraSPARC This package provides the Redhat Cluster infrastructure modules for the Linux kernel version 2.6.18 on uniprocessor 64-bit UltraSPARC machines. squashfs-modules-2.6-sparc32_2.6.18-7+etch3_sparc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6-sparc32_2.6.18-7+etch3_sparc.deb squashfs-modules-2.6-sparc64-smp_2.6.18-7+etch3_sparc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6-sparc64-smp_2.6.18-7+etch3_sparc.deb squashfs-modules-2.6-sparc64_2.6.18-7+etch3_sparc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6-sparc64_2.6.18-7+etch3_sparc.deb squashfs-modules-2.6-vserver-sparc64_2.6.18-7+etch3_sparc.deb to pool/main/l/linux-modules-extra-2.6/squashfs-modules-2.6-vserver-sparc64_2.6.18-7+etch3_sparc.deb (new) squashfs-modules-2.6.18-5-sparc32_2.6.18+3.1r2-7+etch3_sparc.deb optional admin Squash filesystem modules for Linux 2.6.18 on uniprocessor sparc32 (sun4m) This package provides the Squash filesystem modules for the Linux kernel version 2.6.18 on uniprocessor sparc32 (sun4m) machines. . Squashfs is a highly compressed read-only filesystem for Linux. It uses zlib compression to compress both files, inodes and directories. Inodes in the system are very small and all blocks are packed to minimise data overhead. Block sizes greater than 4K are supported up to a maximum of 64K. . Squashfs is intended for general read-only filesystem use, for archival use (i.e. in cases where a .tar.gz file may be used), and in constrained block device/memory systems (e.g. embedded systems) where low overhead is needed. (new) squashfs-modules-2.6.18-5-sparc64-smp_2.6.18+3.1r2-7+etch3_sparc.deb optional admin Squash filesystem modules for Linux 2.6.18 on multiprocessor 64-bit UltraSPARC This package provides the Squash filesystem modules for the Linux kernel version 2.6.18 on multiprocessor 64-bit UltraSPARC machines. . Squashfs is a highly compressed read-only filesystem for Linux. It uses zlib compression to compress both files, inodes and directories. Inodes in the system are very small and all blocks are packed to minimise data overhead. Block sizes greater than 4K are supported up to a maximum of 64K. . Squashfs is intended for general read-only filesystem use, for archival use (i.e. in cases where a .tar.gz file may be used), and in constrained block device/memory systems (e.g. embedded systems) where low overhead is needed. (new) squashfs-modules-2.6.18-5-sparc64_2.6.18+3.1r2-7+etch3_sparc.deb optional admin Squash filesystem modules for Linux 2.6.18 on uniprocessor 64-bit UltraSPARC This package provides the Squash filesystem modules for the Linux kernel version 2.6.18 on uniprocessor 64-bit UltraSPARC machines. . Squashfs is a highly compressed read-only filesystem for Linux. It uses zlib compression to compress both files,
linux-modules-contrib-2.6_2.6.18-4+etch2_sparc.changes is NEW
ivtv-modules-2.6-sparc32_2.6.18-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6-sparc32_2.6.18-4+etch2_sparc.deb ivtv-modules-2.6-sparc64-smp_2.6.18-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6-sparc64-smp_2.6.18-4+etch2_sparc.deb ivtv-modules-2.6-sparc64_2.6.18-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6-sparc64_2.6.18-4+etch2_sparc.deb ivtv-modules-2.6-vserver-sparc64_2.6.18-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6-vserver-sparc64_2.6.18-4+etch2_sparc.deb (new) ivtv-modules-2.6.18-5-sparc32_2.6.18+0.8.2-4+etch2_sparc.deb optional contrib/admin driver for the iTVC15 family of MPEG codecs modules for Linux 2.6.18 on uniprocessor sparc32 (sun4m) This package provides the driver for the iTVC15 family of MPEG codecs modules for the Linux kernel version 2.6.18 on uniprocessor sparc32 (sun4m) machines. (new) ivtv-modules-2.6.18-5-sparc64-smp_2.6.18+0.8.2-4+etch2_sparc.deb optional contrib/admin driver for the iTVC15 family of MPEG codecs modules for Linux 2.6.18 on multiprocessor 64-bit UltraSPARC This package provides the driver for the iTVC15 family of MPEG codecs modules for the Linux kernel version 2.6.18 on multiprocessor 64-bit UltraSPARC machines. (new) ivtv-modules-2.6.18-5-sparc64_2.6.18+0.8.2-4+etch2_sparc.deb optional contrib/admin driver for the iTVC15 family of MPEG codecs modules for Linux 2.6.18 on uniprocessor 64-bit UltraSPARC This package provides the driver for the iTVC15 family of MPEG codecs modules for the Linux kernel version 2.6.18 on uniprocessor 64-bit UltraSPARC machines. (new) ivtv-modules-2.6.18-5-vserver-sparc64_2.6.18+0.8.2-4+etch2_sparc.deb optional contrib/admin driver for the iTVC15 family of MPEG codecs modules for Linux 2.6.18 on uniprocessor 64-bit UltraSPARC This package provides the driver for the iTVC15 family of MPEG codecs modules for the Linux kernel version 2.6.18 on uniprocessor 64-bit UltraSPARC machines. linux-modules-contrib-2.6_2.6.18-4+etch2.dsc to pool/contrib/l/linux-modules-contrib-2.6/linux-modules-contrib-2.6_2.6.18-4+etch2.dsc linux-modules-contrib-2.6_2.6.18-4+etch2.tar.gz to pool/contrib/l/linux-modules-contrib-2.6/linux-modules-contrib-2.6_2.6.18-4+etch2.tar.gz Changes: linux-modules-contrib-2.6 (2.6.18-4+etch2) stable; urgency=high . * Building against 2.6.18-5. Override entries for your package: ivtv-modules-2.6-sparc32_2.6.18-4+etch2_sparc.deb - optional contrib/admin ivtv-modules-2.6-sparc64-smp_2.6.18-4+etch2_sparc.deb - optional contrib/admin ivtv-modules-2.6-sparc64_2.6.18-4+etch2_sparc.deb - optional contrib/admin ivtv-modules-2.6-vserver-sparc64_2.6.18-4+etch2_sparc.deb - optional contrib/admin linux-modules-contrib-2.6_2.6.18-4+etch2.dsc - source contrib/devel Announcing to [EMAIL PROTECTED] Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427514: linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4
Subject: linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4 Package: linux-image-2.6.21-1-amd64 Version: 2.6.21-5~snapshot.8808 Severity: critical Justification: breaks the whole system *** Please type your report below this line *** Hi there, since I have installed 2.6.21-4 from unstable I cannot boot my system anymore. First my configuration: an Asus A8N-E (nforce4) motherboard with two SATA disks. The disks are configured in a software RAID1 using mdadm: /dev/md0 is my / /dev/md1 is my swap /dev/md2 is my /home If I start the system with 2.6.20 it boots fine. Here's a picture of the end of the initramfs and the start of the normal boot: http://www.flickr.com/photos/[EMAIL PROTECTED]/530049031/ The system reaches /sbin/init and it boots just fine. Here is what happens with 2.6.21: http://www.flickr.com/photos/[EMAIL PROTECTED]/530049047/ Something goes wrong in the initramfs, and despite /dev/md0 is started, it can't be mounted. At this point I have tried to toy around in the initramfs, read the /scripts directory but couldn't understand how to make the system move along. (btw, I could really use a pager in there... I hate vi :D) It should be noted that I can start my other two RAID arrays without problems! Please ignore the fact that my 2.6.21 is now a snapshot from the Debian Kernel Team (btw, I have tried also 2.6.22rc3 but the problem is still there) as the problem arised with the upgrade from 2.6.21-3 and -4 from unstable. I don't recall any udev or initramfs-tools upgrade that could have broken the system, especially since 2.6.20 works just fine. Additionally the changelog between -3 and -4 is extremely short so no luck there. Thanks for any help you might give me. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.20-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.21-1-amd64 depends on: ii e2fsprog 1.39+1.40-WIP-2007.04.07+dfsg-2 ext2 file system utilities and lib ii initramf 0.88tools for generating an initramfs ii module-i 3.3-pre11-1 tools for managing Linux kernel mo ii yaird [l 0.0.12-20 Yet Another mkInitRD linux-image-2.6.21-1-amd64 recommends no packages. -- debconf information: linux-image-2.6.21-1-amd64/prerm/removing-running-kernel-2.6.21-1-amd64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.21-1-amd64/postinst/bootloader-error-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/preinst/abort-install-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/prerm/would-invalidate-boot-loader-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/preinst/abort-overwrite-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/preinst/overwriting-modules-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/postinst/create-kimage-link-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/preinst/lilo-initrd-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/postinst/old-initrd-link-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/postinst/old-system-map-link-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/postinst/old-dir-initrd-link-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/preinst/elilo-initrd-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/postinst/depmod-error-2.6.21-1-amd64: false linux-image-2.6.21-1-amd64/preinst/failed-to-move-modules-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.21-1-amd64/preinst/bootloader-initrd-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/preinst/initrd-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/postinst/kimage-is-a-directory: * linux-image-2.6.21-1-amd64/preinst/already-running-this-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/postinst/depmod-error-initrd-2.6.21-1-amd64: false linux-image-2.6.21-1-amd64/postinst/bootloader-test-error-2.6.21-1-amd64: -- BOFH excuse #38: secretary plugged hairdryer into UPS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427514: linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4
On Mon, Jun 04, 2007 at 06:55:14PM +0200, Jack Malmostoso wrote: Hi there, since I have installed 2.6.21-4 from unstable I cannot boot my system anymore. First my configuration: an Asus A8N-E (nforce4) motherboard with two SATA disks. The disks are configured in a software RAID1 using mdadm: /dev/md0 is my / /dev/md1 is my swap /dev/md2 is my /home please post the output for check: cat /etc/fstab cat /proc/mdstat cat /etc/mdadm/mdadm.conf If I start the system with 2.6.20 it boots fine. Here's a picture of the end of the initramfs and the start of the normal boot: http://www.flickr.com/photos/[EMAIL PROTECTED]/530049031/ The system reaches /sbin/init and it boots just fine. Here is what happens with 2.6.21: http://www.flickr.com/photos/[EMAIL PROTECTED]/530049047/ Something goes wrong in the initramfs, and despite /dev/md0 is started, it can't be mounted. At this point I have tried to toy around in the initramfs, read the /scripts directory but couldn't understand how to make the system move along. (btw, I could really use a pager in there... I hate vi :D) It should be noted that I can start my other two RAID arrays without problems! Please ignore the fact that my 2.6.21 is now a snapshot from the Debian Kernel Team (btw, I have tried also 2.6.22rc3 but the problem is still there) as the problem arised with the upgrade from 2.6.21-3 and -4 from unstable. I don't recall any udev or initramfs-tools upgrade that could have broken the system, especially since 2.6.20 works just fine. Additionally the changelog between -3 and -4 is extremely short so no luck there. Thanks for any help you might give me. try to boot with break=mount and please check which devices are up adding rootdelay=9 should shorten the time to land into console also you have more as pager there in busybox ;) check inside too fstype /dev/md0 regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 427514 is normal
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 severity 427514 normal Bug#427514: linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4 Severity set to `normal' from `critical' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#427518: fuse-utils: kernel oops when reinstalling
Processing commands for [EMAIL PROTECTED]: reassign 427518 kernel Bug#427518: fuse-utils: kernel oops when reinstalling Bug reassigned from package `fuse-utils' to `kernel'. tags 427518 patch Bug#427518: fuse-utils: kernel oops when reinstalling There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427514: linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4
hello jack, please keep the bug report on cc for future mails, thanks. On Mon, 04 Jun 2007, Jack Malmostoso wrote: On Mon, 2007-06-04 at 19:12 +0200, maximilian attems wrote: please post the output for check: cat /etc/fstab cat /proc/mdstat cat /etc/mdadm/mdadm.conf Hi Maximilian, thanks for the quick answer! Here's the output you asked for: [EMAIL PROTECTED]:~$ cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/md0/ ext3user_xattr,errors=remount-ro 0 1 /dev/md2/home ext3user_xattr 0 2 /dev/hda/media/cdrom0 udf,iso9660 ro,user,noauto 0 0 /dev/fd0/media/floppy0 vfatrw,user,noauto 0 0 # Swap /dev/md1noneswapsw 0 0 # ia32 chroot /home /var/chroot/sid-ia32/home none bind0 0 /tmp/var/chroot/sid-ia32/tmp none bind0 0 proc/var/chroot/sid-ia32/proc proc defaults0 0 /dev/var/chroot/sid-ia32/dev none bind0 0 [EMAIL PROTECTED]:~$ cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sda2[0] sdb2[1] 497920 blocks [2/2] [UU] md2 : active raid1 sda3[0] sdb3[1] 229046656 blocks [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 14651136 blocks [2/2] [UU] unused devices: none [EMAIL PROTECTED]:~$ cat /etc/mdadm/mdadm.conf DEVICE partitions ARRAY /dev/md2 level=raid1 num-devices=2 UUID=9dae3f6b:a3e79fbb:6044c75b:9f1939bd ARRAY /dev/md1 level=raid1 num-devices=2 UUID=6f583480:58ae2560:eac2cfa7:882022da ARRAY /dev/md0 level=raid1 num-devices=2 UUID=877c34c4:dfed29c7:4338e75f:35082da1 MAILADDR root ok looks sane. try to boot with break=mount and please check which devices are up adding rootdelay=9 should shorten the time to land into console also you have more as pager there in busybox ;) Uhm not really sure what you mean here: I saw /dev/sda and /dev/sdb and all the normal motherboard output. hmm the question is if sda and sdb come up early enough for mdadm, did you try to boot with rootdelay=11 and no break arg? check inside too fstype /dev/md0 There it is: (initramfs) fstype /dev/md0 FSTYPE=ext3 FSSIZE=15002763264 ok this looks sane, but is not what mount is telling us on boot. Hope this helps, just ask for any additional info you might need! yes i'd need more info, first aboves question, then also if you run mdadm by hand from initramfs, please post: mdadm --examine --scan mdadm --assemble --scan --run --auto=yes or directly sh /scripts/local-top/mdadm thanks for feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427514: linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4
On Mon, 2007-06-04 at 19:12 +0200, maximilian attems wrote: please post the output for check: cat /etc/fstab cat /proc/mdstat cat /etc/mdadm/mdadm.conf Hi Maximilian, thanks for the quick answer! Here's the output you asked for: [EMAIL PROTECTED]:~$ cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/md0/ ext3user_xattr,errors=remount-ro 0 1 /dev/md2/home ext3user_xattr 0 2 /dev/hda/media/cdrom0 udf,iso9660 ro,user,noauto 0 0 /dev/fd0/media/floppy0 vfatrw,user,noauto 0 0 # Swap /dev/md1noneswapsw 0 0 # ia32 chroot /home /var/chroot/sid-ia32/home none bind0 0 /tmp/var/chroot/sid-ia32/tmp none bind0 0 proc/var/chroot/sid-ia32/proc proc defaults0 0 /dev/var/chroot/sid-ia32/dev none bind0 0 [EMAIL PROTECTED]:~$ cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sda2[0] sdb2[1] 497920 blocks [2/2] [UU] md2 : active raid1 sda3[0] sdb3[1] 229046656 blocks [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 14651136 blocks [2/2] [UU] unused devices: none [EMAIL PROTECTED]:~$ cat /etc/mdadm/mdadm.conf DEVICE partitions ARRAY /dev/md2 level=raid1 num-devices=2 UUID=9dae3f6b:a3e79fbb:6044c75b:9f1939bd ARRAY /dev/md1 level=raid1 num-devices=2 UUID=6f583480:58ae2560:eac2cfa7:882022da ARRAY /dev/md0 level=raid1 num-devices=2 UUID=877c34c4:dfed29c7:4338e75f:35082da1 MAILADDR root try to boot with break=mount and please check which devices are up adding rootdelay=9 should shorten the time to land into console also you have more as pager there in busybox ;) Uhm not really sure what you mean here: I saw /dev/sda and /dev/sdb and all the normal motherboard output. check inside too fstype /dev/md0 There it is: (initramfs) fstype /dev/md0 FSTYPE=ext3 FSSIZE=15002763264 Hope this helps, just ask for any additional info you might need! -- Have you seen the latest Japanese camera? Apparently it is so fast it can photograph an American with his mouth shut! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
turning on CONFIG_PREEMPT_BKL for 2.6.22
i'm about to shortly enable CONFIG_PREEMPT_BKL on topconfig: * default for smp kernels * not much left that relies on lock_kernel(), unlock_kernel() * good debug infrastructure if that path triggers a bug * no overhead * set in fedora -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
changing maintainer field
heya, can the Maintainer field be changed to the newly added -maint list address so that ususal discussion end in debian-kernel. i just read fedora-kernel and it was nice to follow and easy to read - as not flooded by all bug reports. what where the args against it appart from pure inertia? i'd like to have some nice d-kernel to read again :) regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#426738: linux-image-2.6.21-1-686: soft lockup
On Thu, 31 May 2007 16:59:42 +0200, gregor herrmann wrote: Since the upgrade to 2.6.21 my laptop (Thinkpad R60e) freezes every other minute please checkout trunk builds for 2.6.22-rc3 it has more timer fixes. Nope, I still have freezes of the keyboard/mouse with 2.6.22-rc3-686; and nothing in kern.log/syslog/dmesg. Trial and error lead me to booting with clocksource=acpi_pm - that seems to work around the problem in both 2.6.22-rc3 and 2.6.21-4 (the idea was from http://bugzilla.kernel.org/show_bug.cgi?id=8582) Cheers, gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : debian: the universal operating system - http://www.debian.org/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `-NP: Rolling Stones: Dancing With Mr D signature.asc Description: Digital signature
Bug#426738: linux-image-2.6.21-1-686: soft lockup
On Mon, Jun 04, 2007 at 11:36:11PM +0200, gregor herrmann wrote: Trial and error lead me to booting with clocksource=acpi_pm - that seems to work around the problem in both 2.6.22-rc3 and 2.6.21-4 (the idea was from http://bugzilla.kernel.org/show_bug.cgi?id=8582) ok cool! what's the dmesg diff on your thinkpad with/without that param for 2.6.22-rc3, you might want to attacht that too to the first bug report where you added info :) regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: changing maintainer field
On Mon, Jun 04, 2007 at 11:23:16PM +0200, maximilian attems wrote: heya, can the Maintainer field be changed to the newly added -maint list address so that ususal discussion end in debian-kernel. i just read fedora-kernel and it was nice to follow and easy to read - as not flooded by all bug reports. what where the args against it appart from pure inertia? dannf has that better proposal at hands of automatic bug filtering to -maint list. - http://lists.debian.org/debian-kernel-maint/2007/02/msg3.html i'll second that proposal. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
reenabling sparc32 for 2.6.22
thanks to kylem for fixing the failure upstream. afaik the sparc porter and the release team haven't made any decision concerning sparc32 for lenny. so i think it is only logical to reenable it. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: changing maintainer field
On Monday 04 June 2007 23:42, maximilian attems wrote: what where the args against it appart from pure inertia? Note that you'll probably lose me as someone who occasionally helps reply to bugs as I doubt I'll want to be subscribed to two separate kernel lists. I suspect this will be true for others as well. It will also mean that I will lose some sense of what is happening wrt the kernel. Are there enough people who are planning to subscribe to the bug list anyway or is it just going to further reduce the number of people that see and deal with kernel BRs? Cheers, FJP pgp0mteZFVMVE.pgp Description: PGP signature
Bug#426738: linux-image-2.6.21-1-686: soft lockup
On Mon, 04 Jun 2007 23:41:26 +0200, maximilian attems wrote: Trial and error lead me to booting with clocksource=acpi_pm - that seems to work around the problem in both 2.6.22-rc3 and 2.6.21-4 (the idea was from http://bugzilla.kernel.org/show_bug.cgi?id=8582) ok cool! Yup :) what's the dmesg diff on your thinkpad with/without that param for 2.6.22-rc3, you might want to attacht that too to the first bug report where you added info :) Good idea, will do that tomorrow. Cheers, gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : debian: the universal operating system - http://www.debian.org/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `-NP: Ibrahim Ferrer con Los Bocucos: Ay candela signature.asc Description: Digital signature
Re: changing maintainer field
On Tue, Jun 05, 2007 at 12:13:19AM +0200, Frans Pop wrote: On Monday 04 June 2007 23:42, maximilian attems wrote: what where the args against it appart from pure inertia? Note that you'll probably lose me as someone who occasionally helps reply to bugs as I doubt I'll want to be subscribed to two separate kernel lists. I suspect this will be true for others as well. It will also mean that I will lose some sense of what is happening wrt the kernel. Are there enough people who are planning to subscribe to the bug list anyway or is it just going to further reduce the number of people that see and deal with kernel BRs? Well, I would invert this; I would expect any members of the kernel team to subscribe to the bts for the kernel packages, and currently the easiest way to do that is by subscribing to debian-kernel, so moving the bug traffic to -maint seems like it's just an obstacle for the maintainers to get bug traffic they should (and want to) receive. If nothing else, I think moving the bug traffic to a separate list is going to give us a split-brain effect, since it's not uncommon for bugs to warrant group discussion, and the group it should be discussed with is this one, AFAIK. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
linux-modules-contrib-2.6_2.6.18-4+etch2_sparc.changes ACCEPTED
Accepted: ivtv-modules-2.6-sparc32_2.6.18-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6-sparc32_2.6.18-4+etch2_sparc.deb ivtv-modules-2.6-sparc64-smp_2.6.18-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6-sparc64-smp_2.6.18-4+etch2_sparc.deb ivtv-modules-2.6-sparc64_2.6.18-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6-sparc64_2.6.18-4+etch2_sparc.deb ivtv-modules-2.6-vserver-sparc64_2.6.18-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6-vserver-sparc64_2.6.18-4+etch2_sparc.deb ivtv-modules-2.6.18-5-sparc32_2.6.18+0.8.2-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6.18-5-sparc32_2.6.18+0.8.2-4+etch2_sparc.deb ivtv-modules-2.6.18-5-sparc64-smp_2.6.18+0.8.2-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6.18-5-sparc64-smp_2.6.18+0.8.2-4+etch2_sparc.deb ivtv-modules-2.6.18-5-sparc64_2.6.18+0.8.2-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6.18-5-sparc64_2.6.18+0.8.2-4+etch2_sparc.deb ivtv-modules-2.6.18-5-vserver-sparc64_2.6.18+0.8.2-4+etch2_sparc.deb to pool/contrib/l/linux-modules-contrib-2.6/ivtv-modules-2.6.18-5-vserver-sparc64_2.6.18+0.8.2-4+etch2_sparc.deb linux-modules-contrib-2.6_2.6.18-4+etch2.dsc to pool/contrib/l/linux-modules-contrib-2.6/linux-modules-contrib-2.6_2.6.18-4+etch2.dsc linux-modules-contrib-2.6_2.6.18-4+etch2.tar.gz to pool/contrib/l/linux-modules-contrib-2.6/linux-modules-contrib-2.6_2.6.18-4+etch2.tar.gz Override entries for your package: ivtv-modules-2.6-sparc32_2.6.18-4+etch2_sparc.deb - optional contrib/admin ivtv-modules-2.6-sparc64-smp_2.6.18-4+etch2_sparc.deb - optional contrib/admin ivtv-modules-2.6-sparc64_2.6.18-4+etch2_sparc.deb - optional contrib/admin ivtv-modules-2.6-vserver-sparc64_2.6.18-4+etch2_sparc.deb - optional contrib/admin ivtv-modules-2.6.18-5-sparc32_2.6.18+0.8.2-4+etch2_sparc.deb - optional contrib/admin ivtv-modules-2.6.18-5-sparc64-smp_2.6.18+0.8.2-4+etch2_sparc.deb - optional contrib/admin ivtv-modules-2.6.18-5-sparc64_2.6.18+0.8.2-4+etch2_sparc.deb - optional contrib/admin ivtv-modules-2.6.18-5-vserver-sparc64_2.6.18+0.8.2-4+etch2_sparc.deb - optional contrib/admin linux-modules-contrib-2.6_2.6.18-4+etch2.dsc - optional contrib/devel Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
FIREWIRE on 2.6.22
the new stack is waiting to get enabled on topconfig: CONFIG_FIREWIRE=m # CONFIG_IEEE1394 is not set downside no ETH1394 support yet. but i guess more user are confused by it than anyone actually using it. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427574: linux-image-2.6.21-1-686: quickcam_messenger driver does not work
Package: linux-image-2.6.21-1-686 Version: 2.6.21-4 Severity: normal when I plug my webcam quickcam messenger and try to use it (with xawtv for example), all I get is a blank screen. The cam works perfectly with the previous version of the kernel (2.6.18-4) -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.21-1-686 depends on: ii initramfs-tools [linux-initra 0.88 tools for generating an initramfs ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-20 Yet Another mkInitRD Versions of packages linux-image-2.6.21-1-686 recommends: ii libc6-i6862.5-9+b1 GNU C Library: Shared libraries [i -- debconf information excluded ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: changing maintainer field
On Tue, Jun 05, 2007 at 12:13:19AM +0200, Frans Pop wrote: On Monday 04 June 2007 23:42, maximilian attems wrote: what where the args against it appart from pure inertia? Note that you'll probably lose me as someone who occasionally helps reply to bugs as I doubt I'll want to be subscribed to two separate kernel lists. I suspect this will be true for others as well. It will also mean that I will lose some sense of what is happening wrt the kernel. Are there enough people who are planning to subscribe to the bug list anyway or is it just going to further reduce the number of people that see and deal with kernel BRs? Cheers, FJP the purpose is to build a sane discussion list to build up again the kernel team. if you look up fedora-kernel you get usefull info. concerning the kernel bts 50% of the reports lack info, 30% is against outdated kernels. the rest needs to get to upstream attention. yes i agree that the bts needs sorting i've done it in the past and is not fun, but that is a different issue. the svn commits should also go to -maint. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: changing maintainer field
On Tue, Jun 05, 2007 at 12:13:19AM +0200, Frans Pop wrote: On Monday 04 June 2007 23:42, maximilian attems wrote: what where the args against it appart from pure inertia? Note that you'll probably lose me as someone who occasionally helps reply to bugs as I doubt I'll want to be subscribed to two separate kernel lists. I suspect this will be true for others as well. why? I mean, what's the overhead of subscribing to two separate lists? Just curious.. It will also mean that I will lose some sense of what is happening wrt the kernel. Are there enough people who are planning to subscribe to the bug list anyway or is it just going to further reduce the number of people that see and deal with kernel BRs? I for one would certainly subscribe to both. However, I've heard complaints from people that they are interested in higher level/lower traffic discussions (new upstream to be uploaded to experimental, kernel update in a stable release, should we drop kernel-package, etc), but they are not interested in individual bugs. The current model is suboptimal for them. Perhaps we can force these people to watch bug traffic go by so that they can't help but participate in triage at some level, but I suspect its more likely that these people will just unsubscribe altogether (or implement their own filter). imo, people should be able to select their level of involvement. However, since I personally want to see all of this mail, I'm not really going to push the issue. If there's no outcry from people who want to see only bugs or only non-bugs, then we're probably trying to solve a non-existant problem. In fact, of the people I remember complaning about this, I don't think either are active on the current list (and I don't know whether they would subscribe to either filtered one). I do however think that getting more people involved with triage is critical. I think the best way to do that would be for the kernel team to create some sort of work flow that establishes the rules for dealing with bugs, things like: * When and how to forward bugs upstream * How long to leave a bug open w/o a response from the submitter * Procedures for narrowing down a fix/breakage - e.g., determining if its debian-specific, using git-bisect, etc * Useful usertag procedures for reducing the problem into smaller sets - e.g., hardware, subsystem, etc. In short, get it down to where 80% of the work can be handled by monkeys, then start baiting traps with bananas and building automated poop-slingers where feasible. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
