Bug#563136: linux-image-2.6.32-trunk-amd64: module ath5k not working (Invalid EEPROM checksum)
Confirmed here with AR2413 (AR5005G). The relevant upstream bug is http://bugzilla.kernel.org/show_bug.cgi?id=14874 . I confirm http://git.kernel.org/?p=linux/kernel/git/linville/wireless-2.6.git;a=commit;h=359207c687cc8f4f9845c8dadd0d6dabad44e584 solves the issue for me. Other wifi issues mentioned here seem to be unrelated, please report them separately. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551286: marked as done (linux-image-2.6.30-2-amd64 doesn't start software raid on boot)
Your message dated Thu, 7 Jan 2010 13:46:19 +0100 with message-id 20100107124619.gd30...@stro.at and subject line Re: Bug#551286: Solution - probed has caused the Debian Bug report #551286, regarding linux-image-2.6.30-2-amd64 doesn't start software raid on boot 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.) -- 551286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.30-2-amd64 Version: 2.6.30-8 Severity: normal This does not happen on 2.6.30-1-amd64, so I simply use the older kernel for now; when the older kernel boots, I do see the software raid being detected and configured. My system uses software RAID on all of its drives, including the boot device. linux-image-2.6.30-2-amd64 refuses to boot for me; it cannot find the root filesystem, and it appears the reason is because it can't find any of the software raids. The uuid's for the software raid devices are not present, nor are the normal /dev/md? entries. /proc/mdstat doesn't exist either. I've taken a full log of the boot (via serial console), and dumped it to a file, which I'll include as an attachment. -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-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.30-2-amd64 depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.10-3 tools for managing Linux kernel mo linux-image-2.6.30-2-amd64 recommends no packages. Versions of packages linux-image-2.6.30-2-amd64 suggests: pn grub | lilo none (no description available) pn linux-doc-2.6.30 none (no description available) -- debconf information: linux-image-2.6.30-2-amd64/preinst/bootloader-initrd-2.6.30-2-amd64: true linux-image-2.6.30-2-amd64/preinst/initrd-2.6.30-2-amd64: linux-image-2.6.30-2-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.30-2-amd64/postinst/kimage-is-a-directory: linux-image-2.6.30-2-amd64/preinst/abort-install-2.6.30-2-amd64: linux-image-2.6.30-2-amd64/postinst/depmod-error-initrd-2.6.30-2-amd64: false linux-image-2.6.30-2-amd64/preinst/overwriting-modules-2.6.30-2-amd64: true linux-image-2.6.30-2-amd64/postinst/old-dir-initrd-link-2.6.30-2-amd64: true linux-image-2.6.30-2-amd64/postinst/old-system-map-link-2.6.30-2-amd64: true linux-image-2.6.30-2-amd64/preinst/elilo-initrd-2.6.30-2-amd64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.30-2-amd64/preinst/failed-to-move-modules-2.6.30-2-amd64: linux-image-2.6.30-2-amd64/prerm/would-invalidate-boot-loader-2.6.30-2-amd64: true linux-image-2.6.30-2-amd64/postinst/old-initrd-link-2.6.30-2-amd64: true linux-image-2.6.30-2-amd64/postinst/bootloader-error-2.6.30-2-amd64: linux-image-2.6.30-2-amd64/prerm/removing-running-kernel-2.6.30-2-amd64: true linux-image-2.6.30-2-amd64/postinst/depmod-error-2.6.30-2-amd64: false linux-image-2.6.30-2-amd64/preinst/lilo-initrd-2.6.30-2-amd64: true linux-image-2.6.30-2-amd64/preinst/abort-overwrite-2.6.30-2-amd64: linux-image-2.6.30-2-amd64/postinst/create-kimage-link-2.6.30-2-amd64: true linux-image-2.6.30-2-amd64/postinst/bootloader-test-error-2.6.30-2-amd64: [Linux-bzImage, setup=0x3000, size=0x21bba0] [Initrd, addr=0x37873000, size=0x77c9c5] [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.30-2-amd64 (Debian 2.6.30-8) (wa...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-3) ) #1 SMP Fri Sep 25 22:16:56 UTC 2009 [0.00] Command line: BOOT_IMAGE=/vmlinuz-2.6.30-2-amd64 root=UUID=e5c87f98-51b3-4073-a043-3fdc532dc611 ro console=ttyS0,115200 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009ac00 (usable) [0.00] BIOS-e820: 0009f800 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - 7fee (usable) [0.00] BIOS-e820: 7fee -
Bug#563947: linux-image-2.6.30-2-686 doesn't start software raid on boot
On Wed, 06 Jan 2010, trophime wrote: Package: linux-image-2.6.30-2-686 Version: 2.6.30-8squeeze1 Severity: critical Justification: breaks the whole system no, wrong, only valid if it would break several boxes. The problem appeared after an upgrade from lenny to squeeze. This does not happen on 2.6.26-2-686. The problem is similar to #551286 for amd64 but the proposed fixed do not work for me. you provide zero information, how about if you start to A) try out 2.6.32 from unstable woow yes there is a newer linux image out there, shouldn't that be tried out? B) start giving infos on where your bug lies: dpkg -l mdadm udev util-linux-ng lvm2 bootlog or at least picture of wrong boot. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Xen support on Squeeze
On Sun, 03 Jan 2010, William Pitcock wrote: That was opposed quite strongly by the kernel folks last time it was attempted. Were there any fundamental changes in the Xen dom0 patches since then? Only by the kernel folks which believe all of the crap that the KVM guys say about Xen. There are plenty of kernel developers willing to see the patches merged. Hmm, you have a problem there. Linus is very likely going to cheerfully tell the Xen and KVM developers to duke it out in a bloodbath, and to not forget to bring AlacrityVM into the fray either. He could care less for virtualization, and he is likely to refuse to merge anything non-trivial until the virtualization crazy people manage to reach a consensus on a sane API. Look for the AlacrityVM threads in LKML if you doubt me. Note: I am not defending KVM. I don't agree with their main ideology (that their hardware-emulating approach is the One True Way). But I can well see why Linus decided to take that instance. Xen's track record from hell on getting their act cleaned up for upstream merging is also going to get in the way. Some people have long memories. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 554158
Processing commands for cont...@bugs.debian.org: # submitter acknowledged as not a kernel bug close 554158 Bug#554158: linux-image-2.6-amd64: USB Dell optical whell mouse unrecognised 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Thomas Douillard thomas.douill...@gmail.com 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 debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Xen support on Squeeze
On Thu, Jan 07, 2010 at 11:06:56AM -0200, Henrique de Moraes Holschuh wrote: On Sun, 03 Jan 2010, William Pitcock wrote: That was opposed quite strongly by the kernel folks last time it was attempted. Were there any fundamental changes in the Xen dom0 patches since then? Only by the kernel folks which believe all of the crap that the KVM guys say about Xen. There are plenty of kernel developers willing to see the patches merged. Hmm, you have a problem there. Linus is very likely going to cheerfully tell the Xen and KVM developers to duke it out in a bloodbath, and to not forget to bring AlacrityVM into the fray either. He could care less for virtualization, and he is likely to refuse to merge anything non-trivial until the virtualization crazy people manage to reach a consensus on a sane API. Look for the AlacrityVM threads in LKML if you doubt me. Then again the KVM vs. AlacrityVM discussion is a bit different. AlacrityVM is a fork of KVM.. Note: I am not defending KVM. I don't agree with their main ideology (that their hardware-emulating approach is the One True Way). But I can well see why Linus decided to take that instance. Xen's track record from hell on getting their act cleaned up for upstream merging is also going to get in the way. Some people have long memories. Linus has been happily accepting a lot of Xen pv_ops (domU) patches from Jeremy lately.. So it seems to be mostly about the 'quality' of the code. -- Pasi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#554158: linux-image-2.6-amd64: USB Dell optical whell mouse unrecognised
Update : the mouse works after an update, it was probably not a kernel bug since it works whichever is the version of the kernel. The bug can be closed. Thomas
Bug#563947: linux-image-2.6.30-2-686 doesn't start software raid on boot
On Thu, 2010-01-07 at 13:43 +0100, maximilian attems wrote: On Wed, 06 Jan 2010, trophime wrote: Package: linux-image-2.6.30-2-686 Version: 2.6.30-8squeeze1 Severity: critical Justification: breaks the whole system no, wrong, only valid if it would break several boxes. The problem appeared after an upgrade from lenny to squeeze. This does not happen on 2.6.26-2-686. The problem is similar to #551286 for amd64 but the proposed fixed do not work for me. you provide zero information, how about if you start to A) try out 2.6.32 from unstable woow yes there is a newer linux image out there, shouldn't that be tried out? B) start giving infos on where your bug lies: dpkg -l mdadm udev util-linux-ng lvm2 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===-===-== ii lvm22.02.54-1 The Linux Logical Volume Manager ii mdadm 3.0.3-2 tool to administer Linux MD arrays (software RAID) ii udev149-2 /dev/ and hotplug management daemon ii util-linux 2.16.2-0 Miscellaneous system utilities bootlog or at least picture of wrong boot. On boot the error message is the following: mdadm: No devices listed in conf file were not found Volume group System not found Skipping volume group unable to find LVM volume System/debian I have no other trace... thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Incomplete upload found in Debian upload queue
Probably you are the uploader of the following file(s) in the Debian upload queue directory: linux-2.6_2.6.32-4.diff.gz linux-2.6_2.6.32-4.dsc This looks like an upload, but a .changes file is missing, so the job cannot be processed. If no .changes file arrives within 23:29:40, the files will be deleted. If you didn't upload those files, please just ignore this message. Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of linux-2.6_2.6.32-4_multi.changes
linux-2.6_2.6.32-4_multi.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.32-4.dsc linux-2.6_2.6.32-4.diff.gz linux-support-2.6.32-trunk_2.6.32-4_all.deb linux-patch-debian-2.6.32_2.6.32-4_all.deb firmware-linux-free_2.6.32-4_all.deb linux-source-2.6.32_2.6.32-4_all.deb linux-doc-2.6.32_2.6.32-4_all.deb linux-manual-2.6.32_2.6.32-4_all.deb linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb linux-image-2.6.32-trunk-686_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb linux-image-2.6.32-trunk-amd64_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb linux-libc-dev_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb linux-image-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-2.6_2.6.32-4_multi.changes ACCEPTED
Accepted: firmware-linux-free_2.6.32-4_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-4_all.deb linux-2.6_2.6.32-4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-4.diff.gz linux-2.6_2.6.32-4.dsc to main/l/linux-2.6/linux-2.6_2.6.32-4.dsc linux-doc-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-4_all.deb linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-image-2.6.32-trunk-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-686_2.6.32-4_i386.deb linux-image-2.6.32-trunk-amd64_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-amd64_2.6.32-4_i386.deb linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb linux-image-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb linux-libc-dev_2.6.32-4_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-4_i386.deb linux-manual-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-4_all.deb linux-patch-debian-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-4_all.deb linux-source-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-4_all.deb linux-support-2.6.32-trunk_2.6.32-4_all.deb to main/l/linux-2.6/linux-support-2.6.32-trunk_2.6.32-4_all.deb Override entries for your package: firmware-linux-free_2.6.32-4_all.deb - optional kernel linux-2.6_2.6.32-4.dsc - source devel linux-doc-2.6.32_2.6.32-4_all.deb - optional doc linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb - optional kernel linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb - optional kernel linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb - optional kernel linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb - optional kernel linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb - optional kernel linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb - optional kernel linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb - optional kernel linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb - optional kernel linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb - optional kernel linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb - optional kernel linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb - optional kernel linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb - optional kernel linux-image-2.6.32-trunk-686_2.6.32-4_i386.deb - optional kernel linux-image-2.6.32-trunk-amd64_2.6.32-4_i386.deb - optional kernel linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb - optional kernel linux-image-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb - optional kernel linux-libc-dev_2.6.32-4_i386.deb - optional devel linux-manual-2.6.32_2.6.32-4_all.deb - optional doc linux-patch-debian-2.6.32_2.6.32-4_all.deb - optional kernel linux-source-2.6.32_2.6.32-4_all.deb - optional kernel linux-support-2.6.32-trunk_2.6.32-4_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 508527 515533 522920 558077 563036 563355 563356 563693 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
Bug#508923: marked as done ([via-velocity] ifconfig eth0 up crash kernel hard)
Your message dated Thu, 07 Jan 2010 16:41:49 + with message-id e1nsvqj-0007j1...@ries.debian.org and subject line Bug#508527: fixed in linux-2.6 2.6.32-4 has caused the Debian Bug report #508527, regarding [via-velocity] ifconfig eth0 up crash kernel hard 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.) -- 508527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-11 Severity: important The box is VIA Epia SN board with a VIA C7 processor. This chipset has two network cards, eth0 and eth1 eth0: VIA Networking Velocity Family Gigabit Ethernet Adapter eth1: VIA Rhine II at 0x1c800, 00:40:63:f7:b6:8b, IRQ 23. (lspci output is at the end) Doing 'ifconfig eth0 up' crashes the kernel hard (kernel oops + box frozen). eth1 is working fine. eth0 was working fine with Etch 2.6.18-6 kernel. This is 100% reproducible. (The box also crashes at boot-time if eth0 is configured at boot-time via /etc/network/interfaces) The oops message is not logged, but is the same as in bug #508527 '2.6.26-11 oops on initial NIC (via-velocity) setup' and also in kernel Bugzilla #11121 http://bugzilla.kernel.org/show_bug.cgi?id=11121 (also under Debian). Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. $ lspci 00:00.0 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:00.5 PIC: VIA Technologies, Inc. CN896/VN896/P4M900 I/O APIC Interrupt Controller 00:00.6 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Security Device 00:00.7 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge 00:02.0 PCI bridge: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller (rev 80) 00:03.0 PCI bridge: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller (rev 80) 00:0f.0 RAID bus controller: VIA Technologies, Inc. VT8251 AHCI/SATA 4-Port Controller (rev 20) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07) 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 91) 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 91) 00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 91) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8251 PCI to ISA Bridge 00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c) 00:13.0 Host bridge: VIA Technologies, Inc. VT8251 Host Bridge 01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01) 03:00.0 Ethernet controller: VIA Technologies, Inc. VT6120/VT6121/VT6122 Gigabit Ethernet Adapter (rev 82) 80:00.0 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port 80:00.1 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port 80:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-4_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-4_all.deb linux-2.6_2.6.32-4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-4.diff.gz linux-2.6_2.6.32-4.dsc to main/l/linux-2.6/linux-2.6_2.6.32-4.dsc linux-doc-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-4_all.deb linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb
Bug#563355: marked as done (linux-2.6: FTBFS in s390: source_s390_vserver/kernel/vserver/proc.c:70: error: '__NR_vserver' undeclared)
Your message dated Thu, 07 Jan 2010 16:41:49 + with message-id e1nsvqj-0007jr...@ries.debian.org and subject line Bug#563355: fixed in linux-2.6 2.6.32-4 has caused the Debian Bug report #563355, regarding linux-2.6: FTBFS in s390: source_s390_vserver/kernel/vserver/proc.c:70: error: '__NR_vserver' undeclared 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.) -- 563355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux-2.6 Version: 2.6.32-3 Severity: grave Hi, Your package failed to build in s390 with the following error: CC kernel/vserver/proc.o /build/buildd-linux-2.6_2.6.32-3-s390-7O5pHW/linux-2.6-2.6.32/debian/build/ source_s390_vserver/kernel/vserver/proc.c: In function 'proc_vci': /build/buildd-linux-2.6_2.6.32-3-s390-7O5pHW/linux-2.6-2.6.32/debian/build/ source_s390_vserver/kernel/vserver/proc.c:70: error: '__NR_vserver' undeclared (first use in this function) /build/buildd-linux-2.6_2.6.32-3-s390-7O5pHW/linux-2.6-2.6.32/debian/build/ source_s390_vserver/kernel/vserver/proc.c:70: error: (Each undeclared identifier is reported only once /build/buildd-linux-2.6_2.6.32-3-s390-7O5pHW/linux-2.6-2.6.32/debian/build/ source_s390_vserver/kernel/vserver/proc.c:70: error: for each function it appears in.) make[7]: *** [kernel/vserver/proc.o] Error 1 Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-4_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-4_all.deb linux-2.6_2.6.32-4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-4.diff.gz linux-2.6_2.6.32-4.dsc to main/l/linux-2.6/linux-2.6_2.6.32-4.dsc linux-doc-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-4_all.deb linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-image-2.6.32-trunk-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-686_2.6.32-4_i386.deb linux-image-2.6.32-trunk-amd64_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-amd64_2.6.32-4_i386.deb linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb linux-image-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb linux-libc-dev_2.6.32-4_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-4_i386.deb linux-manual-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-4_all.deb linux-patch-debian-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-4_all.deb linux-source-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-4_all.deb linux-support-2.6.32-trunk_2.6.32-4_all.deb to main/l/linux-2.6/linux-support-2.6.32-trunk_2.6.32-4_all.deb A summary of the
Bug#558077: marked as done (dpkg --print-installation-architecture is deprecated)
Your message dated Thu, 07 Jan 2010 16:41:49 + with message-id e1nsvqj-0007jg...@ries.debian.org and subject line Bug#558077: fixed in linux-2.6 2.6.32-4 has caused the Debian Bug report #558077, regarding dpkg --print-installation-architecture is deprecated 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.) -- 558077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32~rc8-1~experimental.1 Severity: minor Tags: patch Hello, dpkg --print-installation-architecture is deprecated[1]. It's not used but refered to in some comments. Best regards Uwe [1] http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=a7a2de0 ---8- dpkg --print-installation-architecture is deprecated since 2005. Don't refer to it. Index: linux-2.6-debian/debian/templates/temp.image.plain/postinst === --- linux-2.6-debian.orig/debian/templates/temp.image.plain/postinst 2009-11-26 09:26:18.0 +0100 +++ linux-2.6-debian/debian/templates/temp.image.plain/postinst 2009-11-26 09:27:23.0 +0100 @@ -28,7 +28,7 @@ my $relink_src_link = 'YES'; # There is no harm in checking the link my $relink_build_link = 'YES'; # There is no harm in checking the link my $force_build_link = '';# There is no harm in checking the link -my $arch = =A; # should be same as dpkg --print-installation-architecture +my $arch = =A; # should be same as dpkg --print-architecture my $kernel_arch = =B; my $ramdisk = =MK; # List of tools to create initial ram fs. my $package_name = =ST-image-$version; Index: linux-2.6-debian/debian/templates/temp.image.plain/postrm === --- linux-2.6-debian.orig/debian/templates/temp.image.plain/postrm 2009-11-26 09:26:18.0 +0100 +++ linux-2.6-debian/debian/templates/temp.image.plain/postrm 2009-11-26 09:27:23.0 +0100 @@ -34,7 +34,7 @@ my $ignore_depmod_err = '';# normally we do not my $relink_build_link = 'YES'; # There is no harm in checking the link my $force_build_link = '';# we shall not create a dangling link -my $arch = =A; # should be same as dpkg --print-installation-architecture +my $arch = =A; # should be same as dpkg --print-architecture my $kernel_arch = =B; my $ramdisk = =MK; # List of tools to create initial ram fs. my $package_name= =ST-image-$version; Index: linux-2.6-debian/debian/templates/temp.image.plain/preinst === --- linux-2.6-debian.orig/debian/templates/temp.image.plain/preinst 2009-11-26 09:26:18.0 +0100 +++ linux-2.6-debian/debian/templates/temp.image.plain/preinst 2009-11-26 09:27:23.0 +0100 @@ -22,7 +22,7 @@ my $relink_src_link = 'YES'; # There is no harm in checking the link my $relink_build_link = 'YES'; # There is no harm in checking the link my $force_build_link = ''; # There is no harm in checking the link -my $arch = =A; # should be same as dpkg --print-installation-architecture +my $arch = =A; # should be same as dpkg --print-architecture my $kernel_arch = =B; my $ramdisk = =MK; # List of tools to create initial ram fs. my $package_name= =ST-image-$version; Index: linux-2.6-debian/debian/templates/temp.image.plain/prerm === --- linux-2.6-debian.orig/debian/templates/temp.image.plain/prerm 2009-11-26 09:26:18.0 +0100 +++ linux-2.6-debian/debian/templates/temp.image.plain/prerm2009-11-26 09:27:23.0 +0100 @@ -22,7 +22,7 @@ my $ignore_depmod_err = '';# normally we do not my $relink_build_link = 'YES'; # There is no harm in checking the link my $force_build_link = ''; # There is no harm in checking the link -my $arch = =A; # should be same as dpkg --print-installation-architecture +my $arch = =A; # should be same as dpkg --print-architecture my $kernel_arch = =B; my $package_name= =ST-image-$version; -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions| http://www.pengutronix.de/ | ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-4 We believe that the bug you reported is fixed in
Bug#522920: marked as done (linux-2.6: please set CONFIG_MOUSE_PS2_ELANTECH=y (for various EeePC models))
Your message dated Thu, 07 Jan 2010 16:41:49 + with message-id e1nsvqj-0007jc...@ries.debian.org and subject line Bug#522920: fixed in linux-2.6 2.6.32-4 has caused the Debian Bug report #522920, regarding linux-2.6: please set CONFIG_MOUSE_PS2_ELANTECH=y (for various EeePC models) 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.) -- 522920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.29-1-686 Version: 2.6.29-1 Severity: normal To get features like 2-finger scrolling with the Xorg Synaptics driver on the eee pc 1000 and other devices with an elantech touchpad, the config option CONFIG_MOUSE_PS2_ELANTECH is needed. -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.28 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.29-1-686 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.2 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.29-1-686 recommends: ii libc6-i6862.9-6 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.29-1-686 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.29 none(no description available) -- debconf information excluded ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-4_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-4_all.deb linux-2.6_2.6.32-4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-4.diff.gz linux-2.6_2.6.32-4.dsc to main/l/linux-2.6/linux-2.6_2.6.32-4.dsc linux-doc-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-4_all.deb linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-image-2.6.32-trunk-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-686_2.6.32-4_i386.deb linux-image-2.6.32-trunk-amd64_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-amd64_2.6.32-4_i386.deb linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb linux-image-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb linux-libc-dev_2.6.32-4_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-4_i386.deb linux-manual-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-4_all.deb
Bug#563036: marked as done (fails to boot on thecus n2100)
Your message dated Thu, 07 Jan 2010 16:41:49 + with message-id e1nsvqj-0007jm...@ries.debian.org and subject line Bug#563036: fixed in linux-2.6 2.6.32-4 has caused the Debian Bug report #563036, regarding fails to boot on thecus n2100 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.) -- 563036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-3 Severity: normal Without a serial console, all I can tell is that the root disk is accessed briefly and then the boot must fail as there is no further disk activity. I wonder if bug #561309 is really fixed. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:01.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] 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: 64 (1000ns min, 250ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 27 Region 0: I/O ports at 9000 [size=256] Region 1: Memory at 800a0200 (32-bit, non-prefetchable) [size=256] Expansion ROM at 8008 [disabled] [size=64K] Capabilities: access denied Kernel driver in use: r8169 00:02.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet [10ec:8169] 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: 64 (1000ns min, 250ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 30 Region 0: I/O ports at 9400 [size=256] Region 1: Memory at 800a0300 (32-bit, non-prefetchable) [size=256] Expansion ROM at 8009 [disabled] [size=64K] Capabilities: access denied Kernel driver in use: r8169 00:03.0 Mass storage controller [0180]: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller [1095:3512] (rev 01) Subsystem: Silicon Image, Inc. SiI 3512 SATALink Controller [1095:3512] 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, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 29 Region 0: I/O ports at 9850 [size=8] Region 1: I/O ports at 9860 [size=4] Region 2: I/O ports at 9858 [size=8] Region 3: I/O ports at 9864 [size=4] Region 4: I/O ports at 9840 [size=16] Region 5: Memory at 800a (32-bit, non-prefetchable) [size=512] [virtual] Expansion ROM at 8000 [disabled] [size=512K] Capabilities: access denied Kernel driver in use: sata_sil 00:04.0 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 62) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] 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: 22, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 28 Region 4: I/O ports at 9800 [size=32] Capabilities: access denied Kernel driver in use: uhci_hcd 00:04.1 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 62) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] 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: 22, Cache Line Size: 32 bytes Interrupt: pin B routed to IRQ 27 Region 4: I/O ports at 9820 [size=32]
Bug#563356: marked as done (linux-2.6: FTBFS in ia64: source_ia64_vserver/mm/memory.c:2995: error: implicit declaration of function 'vx_page_fault')
Your message dated Thu, 07 Jan 2010 16:41:50 + with message-id e1nsvqk-0007jf...@ries.debian.org and subject line Bug#563356: fixed in linux-2.6 2.6.32-4 has caused the Debian Bug report #563356, regarding linux-2.6: FTBFS in ia64: source_ia64_vserver/mm/memory.c:2995: error: implicit declaration of function 'vx_page_fault' 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.) -- 563356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux-2.6 Version: 2.6.32-3 Severity: grave Hi, Your package failed to build in ia64 with the following error: /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c : In function 'copy_pte_range': /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c :651: error: implicit declaration of function 'vx_rss_avail' /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c : In function 'insert_page': /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c :1519: error: implicit declaration of function 'vx_file_rsspages_inc' /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c : In function 'do_wp_page': /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c :2155: error: implicit declaration of function 'vx_file_rsspages_dec' /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c :2156: error: implicit declaration of function 'vx_anon_rsspages_inc' /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c : In function 'handle_pte_fault': /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c :2945: error: 'VXPT_UNKNOWN' undeclared (first use in this function) /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c :2945: error: (Each undeclared identifier is reported only once /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c :2945: error: for each function it appears in.) /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c :2973: error: 'VXPT_WRITE' undeclared (first use in this function) /build/buildd/linux-2.6-2.6.32/debian/build/source_ia64_vserver/mm/memory.c :2995: error: implicit declaration of function 'vx_page_fault' make[6]: *** [mm/memory.o] Error 1 -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-4_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-4_all.deb linux-2.6_2.6.32-4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-4.diff.gz linux-2.6_2.6.32-4.dsc to main/l/linux-2.6/linux-2.6_2.6.32-4.dsc linux-doc-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-4_all.deb linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb
Bug#515533: marked as done (linux-2.6.26: tulip module handles dmfe cards (again))
Your message dated Thu, 07 Jan 2010 16:41:49 + with message-id e1nsvqj-0007j6...@ries.debian.org and subject line Bug#515533: fixed in linux-2.6 2.6.32-4 has caused the Debian Bug report #515533, regarding linux-2.6.26: tulip module handles dmfe cards (again) 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.) -- 515533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6-486 Version: 2.6.26+17 Severity: important After upgrading to linux-2.6.26 from 2.6.18, one of my two network cards stopped working. Closer examination showed lots of tulip_stop_rxtx() failed (CSR5 0xfc74 CSR6 0x2042202) messages. It seems that bug #405203 resurfaced again, but I was unable to add a reply there since it's archived already. The workaround described there (rmmod tulip; rmmod dmfe; modprobe dmfe) works for me. A quick diff of the two kernel versions' modules.pcimap files shows that both dmfe and tulip claim responsibility for the same devices (again): $ diff -y 2.6.18-6-486/modules.pcimap 2.6.26-1-486/modules.pcimap | grep 1282 dmfe 0x1282 0x9132 0x 0xf dmfe 0x1282 0x9132 0x 0xf dmfe 0x1282 0x9102 0x 0xf dmfe 0x1282 0x9102 0x 0xf dmfe 0x1282 0x9100 0x 0xf dmfe 0x1282 0x9100 0x 0xf dmfe 0x1282 0x9009 0x 0xf dmfe 0x1282 0x9009 0x 0xf tulip 0x1282 0x9100 0x 0xf tulip 0x1282 0x9102 0x 0xf -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-486 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6-486 depends on: ii linux-image-2.6.26-1-486 2.6.26-13 Linux 2.6.26 image on x86 linux-image-2.6-486 recommends no packages. linux-image-2.6-486 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-4_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-4_all.deb linux-2.6_2.6.32-4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-4.diff.gz linux-2.6_2.6.32-4.dsc to main/l/linux-2.6/linux-2.6_2.6.32-4.dsc linux-doc-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-4_all.deb linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686_2.6.32-4_i386.deb linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-486_2.6.32-4_i386.deb linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-image-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-image-2.6.32-trunk-686_2.6.32-4_i386.deb to
Bug#508527: marked as done (2.6.26-11 oops on initial NIC (via-velocity) setup)
Your message dated Thu, 07 Jan 2010 16:41:49 + with message-id e1nsvqj-0007j1...@ries.debian.org and subject line Bug#508527: fixed in linux-2.6 2.6.32-4 has caused the Debian Bug report #508527, regarding 2.6.26-11 oops on initial NIC (via-velocity) setup 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.) -- 508527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kernel Version: 2.6.26-11 Tags: lenny I get an kernel oops while booting lenny after dist-upgrading from etch. The oops occurs when usually the VT6120/VT6121/VT6122 Gigabit Ethernet Adapter (via-velocity) is getting configured. Its 100% reproducible, booting a fresh weekly build lenny installer result in the same crashes. ---8--- [ 60.663481] BUG: unable to handle kernel NULL pointer dereference at [ 60.664009] IP: [] [ 60.664009] *pde = [ 60.664009] Oops: [#1] SMP [ 60.664009] Modules linked in: dm_crypt crypto_blkcipher dm_snapshot dm_mirror dm_log dm_mod via_rng rng_core loop evdev tpm_infineon tpm tpm_bios serio_raw snd_pcm sns [ 60.664009] [ 60.664009] Pid: 2062, comm: ifconfig Not tainted (2.6.26-1-686 #1) [ 60.664009] EIP: 0060:[] EFLAGS: 00010046 CPU: 0 [ 60.664009] EIP is at 0x0 [ 60.664009] EAX: 00a3 EBX: 3d20 ECX: 01bd7000 EDX: c0372940 [ 60.664009] ESI: c0372940 EDI: EBP: 00a3 ESP: f7b1fe50 [ 60.664009] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 60.664009] Process ifconfig (pid: 2062, ti=f7b1e000 task=f744f940 task.ti=f7b1e000) [ 60.664009] Stack: c0105f3a f7847000 f74019c0 f7847c10 80d0 c01042a7 f7847000 00fc [ 60.664009]1000 f74019c0 f7847c10 80d0 007b 007b 00d8 [ 60.664009]ff5c c0171d01 0060 00010216 f77963e0 f7b38100 f7afc000 [ 60.664009] Call Trace: [ 60.664009] [c0105f3a] do_IRQ+0x4d/0x63 [ 60.664009] [c01042a7] common_interrupt+0x23/0x28 [ 60.664009] [c0171d01] __kmalloc+0x9c/0xb2 [ 60.664009] [f88426b0] velocity_init_td_ring+0x32/0xe1 [via_velocity] [ 60.664009] [f8843848] velocity_open+0x16d/0x20f [via_velocity] [ 60.664009] [c0259d26] dev_open+0x64/0x95 [ 60.664009] [c0258c14] dev_change_flags+0x92/0x13b [ 60.664009] [c0292a1e] devinet_ioctl+0x232/0x52c [ 60.664009] [c024e71b] sock_ioctl+0x19f/0x1c1 [ 60.664009] [c024e57c] sock_ioctl+0x0/0x1c1 [ 60.664009] [c017e3f0] vfs_ioctl+0x1c/0x5d [ 60.664009] [c017e67b] do_vfs_ioctl+0x24a/0x261 [ 60.664009] [c017e6d3] sys_ioctl+0x41/0x5a [ 60.664009] [c0103853] sysenter_past_esp+0x78/0xb1 [ 60.664009] === [ 60.664009] Code: Bad EIP value. [ 60.664009] EIP: [] 0x0 SS:ESP 0068:f7b1fe50 [ 60.664009] Kernel panic - not syncing: Fatal exception in interrupt ---8--- ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-4_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-4_all.deb linux-2.6_2.6.32-4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-4.diff.gz linux-2.6_2.6.32-4.dsc to main/l/linux-2.6/linux-2.6_2.6.32-4.dsc linux-doc-2.6.32_2.6.32-4_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-4_all.deb linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-486_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686-bigmem_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-686_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all-i386_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-all_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-amd64_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common-vserver_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-common_2.6.32-4_i386.deb linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-trunk-vserver-686-bigmem_2.6.32-4_i386.deb
Re: Kernel audit code bugs in Debian stable
On Fri, Dec 25, 2009 at 04:55:59PM +0300, Sergey Sireskin wrote: Hi All, I would like to report, that current Debian 2.6.26-2 kernel packages are unstable (soft and hard locks occur) when intensively using audit features. There are already fixes by Eric Paris and Al Viro for these bugs in mainline kernel. These patches should be included in Debian kernels as well. Otherwise Debian kernels are competely useless in cases when audit system is enabled and audit.rules are configured. The following patch commits have to be included: def57543418a5f47debae28a0a9dea2effc11692 8f7b0ba1c853919b85b54774775f567f30006107 As well as these two patches on top of them: http://www.gossamer-threads.com/lists/linux/kernel/1169784 http://www.gossamer-threads.com/lists/linux/kernel/1169785 Thanks Sergey. Would you mind filing a bug for these so it can be tracked? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563947: linux-image-2.6.30-2-686 doesn't start software raid on boot
On Thu, Jan 07, 2010 at 02:39:17PM +0100, trophime wrote: ii lvm22.02.54-1 The Linux Logical Volume Manager ii mdadm 3.0.3-2 tool to administer Linux MD arrays (software RAID) ii udev149-2 /dev/ and hotplug management daemon ii util-linux 2.16.2-0 Miscellaneous system utilities this looks fine. bootlog or at least picture of wrong boot. On boot the error message is the following: mdadm: No devices listed in conf file were not found Volume group System not found Skipping volume group unable to find LVM volume System/debian I have no other trace... did you get thrown to a console? add bootparam rootdelay=12 to grub and wait for 12 seconds, then check which devices exists: ls -l/dev/[hs]da* see more info on http://wiki.debian.org/InitramfsDebug -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564114: e1000: Potential packet filtering bypass
Package: linux-2.6 Version: 2.6.32-4 Severity: normal Tags: patch security Fabian Yamaguchi made a presentation at 26C3 http://events.ccc.de/congress/2009/Fahrplan/events/3596.en.html which included a bug in e1000 related to this fix for CVE-2009-1385: commit ea30e11970a96cfe5e32c03a29332554573b4a10 Author: Neil Horman nhor...@tuxdriver.com Date: Tue Jun 2 01:29:58 2009 -0700 e1000: add missing length check to e1000 receive routine The bug is that the last part of a scattered frame will be accepted so long as it is longer than 4 bytes. This can be used to evade packet filtering in front of the host with the e1000 hardware, since the packet filter will look at the real frame headers but Linux will see the 'headers' in this last part. Personally I doubt that many packet filters are configured to allow jumbo frames through, hence severity is only 'normal'. A proposed fix was posted in: http://article.gmane.org/gmane.linux.network/148454 We should get a separate CVE number for this bug. Ben. -- System Information: Debian Release: squeeze/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Ben Hutchings To err is human; to really foul things up requires a computer. signature.asc Description: This is a digitally signed message part
Bug#564110: r8169: Fix for CVE-2009-1389 introduces denial of service issue
Package: linux-2.6 Version: 2.6.32-4 Severity: serious Tags: security Fabian Yamaguchi made a presentation at 26C3 http://events.ccc.de/congress/2009/Fahrplan/events/3596.en.html which included a bug in r8169 reintroduced by: commit fdd7b4c3302c93f6833e338903ea77245eb510b4 Author: Eric Dumazet eric.duma...@gmail.com Date: Tue Jun 9 04:01:02 2009 -0700 r8169: fix crash when large packets are received On some older r8169 controllers this will enable scattering on receive, and the first word of the second and subsequent RX buffers for a frame will wrongly be treated as a status word. This can be used for denial of service at the very least. There is ongoing discussion on netdev about how to fix this. In the mean time we should get a CVE number for this. Ben. -- System Information: Debian Release: squeeze/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Ben Hutchings To err is human; to really foul things up requires a computer. signature.asc Description: This is a digitally signed message part
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org:
# Thu Jan 7 19:03:16 UTC 2010
# Tagging as pending bugs that are closed by packages in NEW
# http://ftp-master.debian.org/new.html
#
# Source package in NEW: snmp-mibs-downloader
tags 559039 + pending
Bug #559039 [wnpp] ITP: snmp-mibs-downloader -- Downloads RFCs and IANA Docs
containing MIBs and extracts them
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 558077 + pending
Bug #558077 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] dpkg
--print-installation-architecture is deprecated
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 563693 + pending
Bug #563693 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.32-trunk-amd64: iwl3945 chokes at currently packaged firmware.
Makes adapter keep restarting
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 563356 + pending
Bug #563356 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux-2.6]
linux-2.6: FTBFS in ia64: source_ia64_vserver/mm/memory.c:2995: error: implicit
declaration of function 'vx_page_fault'
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 563355 + pending
Bug #563355 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux-2.6]
linux-2.6: FTBFS in s390: source_s390_vserver/kernel/vserver/proc.c:70: error:
'__NR_vserver' undeclared
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 563036 + pending
Bug #563036 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] fails to
boot on thecus n2100
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 515533 + pending
Bug #515533 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-2.6.26: tulip module handles dmfe cards (again)
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 508527 + pending
Bug #508527 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] 2.6.26-11
oops on initial NIC (via-velocity) setup
Bug #508923 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
[via-velocity] ifconfig eth0 up crash kernel hard
Added tag(s) pending.
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 522920 + pending
Bug #522920 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] linux-2.6:
please set CONFIG_MOUSE_PS2_ELANTECH=y (for various EeePC models)
Added tag(s) pending.
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 debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564110: r8169: Fix for CVE-2009-1389 introduces denial of service issue
Julien Cristau pointed out the thread http://thread.gmane.org/gmane.comp.security.oss.general/2457 where it appears that Red Hat has allocated CVE-2009-4537 for this. Ben. -- Ben Hutchings To err is human; to really foul things up requires a computer. signature.asc Description: This is a digitally signed message part
Bug#564114: e1000: Potential packet filtering bypass
Julien Cristau pointed out the thread http://thread.gmane.org/gmane.comp.security.oss.general/2457. It appears that Red Hat allocated CVE-2009-4536 for this and CVE-2009-4538 for a similar bug in e1000e. Ben. -- Ben Hutchings To err is human; to really foul things up requires a computer. signature.asc Description: This is a digitally signed message part
Processed: bug 563136 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=14874
Processing commands for cont...@bugs.debian.org: forwarded 563136 http://bugzilla.kernel.org/show_bug.cgi?id=14874 Bug #563136 [linux-2.6] linux-image-2.6.32-trunk-amd64: module ath5k not working Set Bug forwarded-to-address to 'http://bugzilla.kernel.org/show_bug.cgi?id=14874'. 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 debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 564110 in 2.6.26-19, found 564110 in 2.6.26-21, found 564114 in 2.6.26-19 ...
Processing commands for cont...@bugs.debian.org: found 564110 2.6.26-19 Bug #564110 [linux-2.6] r8169: Fix for CVE-2009-1389 introduces denial of service issue There is no source info for the package 'linux-2.6' at version '2.6.26-19' with architecture '' Unable to make a source version for version '2.6.26-19' Bug Marked as found in versions 2.6.26-19. found 564110 2.6.26-21 Bug #564110 [linux-2.6] r8169: Fix for CVE-2009-1389 introduces denial of service issue There is no source info for the package 'linux-2.6' at version '2.6.26-21' with architecture '' Unable to make a source version for version '2.6.26-21' Bug Marked as found in versions 2.6.26-21. found 564114 2.6.26-19 Bug #564114 [linux-2.6] e1000: Potential packet filtering bypass There is no source info for the package 'linux-2.6' at version '2.6.26-19' with architecture '' Unable to make a source version for version '2.6.26-19' Bug Marked as found in versions 2.6.26-19. found 564114 2.6.26-21 Bug #564114 [linux-2.6] e1000: Potential packet filtering bypass There is no source info for the package 'linux-2.6' at version '2.6.26-21' with architecture '' Unable to make a source version for version '2.6.26-21' Bug Marked as found in versions 2.6.26-21. 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 debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 563136
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 563136 + pending Bug #563136 [linux-2.6] linux-image-2.6.32-trunk-amd64: module ath5k not working Added tag(s) pending. 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 debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade script for libata transition
On Tue, 2009-12-29 at 14:54 +0100, Marco d'Itri wrote: On Dec 29, Ben Hutchings b...@decadent.org.uk wrote: Is it not possible to add corresponding rules, e.g.: Two issues: I am not sure that it is possible to determine the new $ID_PATH value and I fear that multiple rules for the same link name may confuse the scripts. Please can you test whether this is the case. Although CD device names are not as critical as disks, I do want to make this upgrade as smooth as possible. Ben. -- Ben Hutchings To err is human; to really foul things up requires a computer. signature.asc Description: This is a digitally signed message part
Re: Upgrade script for libata transition
On Tue, 2009-12-29 at 12:06 +, Ben Hutchings wrote: Linux kernel packages for squeeze will use libata-based drivers in preference to old-style IDE drivers. On some systems this will change the names of PATA devices and will also change the names of SCSI devices already present in those systems if they are enumerated after the PATA devices. On upgrade, we will recommend that users identify hard disk volumes in configuration files by label or UUID (unique identifier) rather than by device name, which will work with both old and new kernel versions. I think that in most cases it should be possible to update the system configuration automatically, if the user agrees to this. The following script implements this. Please review and verify that it does the right thing for your package's configuration file(s). (I would also welcome a more general review of the code.) [...] I have not yet seen any comments from maintainers of the various boot loaders. It is vital that this upgrade process is reliable and does not prevent systems from booting, so please do review the code for your boot loader. If you prefer, I can prepare packages that include this script on postinst and upload them to people.debian.org for you or others to test. Ben. -- Ben Hutchings To err is human; to really foul things up requires a computer. signature.asc Description: This is a digitally signed message part
Bug#564156: FTBFS on armel: isp1362-hcd was written for some other kernel version
Package: linux-2.6 Version: 2.6.32-4 Justification: fails to build from source Severity: important Tags: patch It seems the submitter of this driver was only pretending to work with mainline, because this code won't compile on anything after 2.6.26: #ifdef CONFIG_ARM if (isp1362_hcd-board) set_irq_type(irq, isp1362_hcd-board-int_act_high ? IRQT_RISING : IRQT_FALLING); #endif It looks like this can easily be fixed, but as this is a platform device driver and none of our kernel flavours appears to use it I see no reason to build it at all. Ben. -- System Information: Debian Release: squeeze/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Ben Hutchings To err is human; to really foul things up requires a computer. signature.asc Description: This is a digitally signed message part
Bug#564114: [Secure-testing-team] e1000: Potential packet filtering bypass
On Thu, 07 Jan 2010 19:27:02 + Ben Hutchings wrote: Julien Cristau pointed out the thread http://thread.gmane.org/gmane.comp.security.oss.general/2457. It appears that Red Hat allocated CVE-2009-4536 for this and CVE-2009-4538 for a similar bug in e1000e. do you follow kernel-sec [0]? i entered these CVEs when they were first disclosed over a week ago. mike [0] http://svn.debian.org/wsvn/kernel-sec -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Upgrade script for libata transition
On Thu, Jan 07, 2010 at 10:49:56PM +, Ben Hutchings wrote: On Tue, 2009-12-29 at 12:06 +, Ben Hutchings wrote: Linux kernel packages for squeeze will use libata-based drivers in preference to old-style IDE drivers. On some systems this will change the names of PATA devices and will also change the names of SCSI devices already present in those systems if they are enumerated after the PATA devices. On upgrade, we will recommend that users identify hard disk volumes in configuration files by label or UUID (unique identifier) rather than by device name, which will work with both old and new kernel versions. I think that in most cases it should be possible to update the system configuration automatically, if the user agrees to this. The following script implements this. Please review and verify that it does the right thing for your package's configuration file(s). (I would also welcome a more general review of the code.) I have not yet seen any comments from maintainers of the various boot loaders. It is vital that this upgrade process is reliable and does not prevent systems from booting, so please do review the code for your boot loader. Well, aboot is effectively unmaintained, along with the port as a whole, since I no longer have an alpha that boots (and I don't think doing test builds on a buildd is adequate for uploading a bootloader with a different toolchain, so I haven't officially orphaned the package). If you care about getting feedback for alpha, I'd suggest mailing debian-al...@lists.debian.org. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Re: Upgrade script for libata transition
Ben Hutchings wrote: I have not yet seen any comments from maintainers of the various boot loaders. did you see http://lists.debian.org/debian-kernel/2009/12/msg00596.html -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
