Processed: fixed 573231 in 2.6.33-1~experimental.2
Processing commands for cont...@bugs.debian.org:
fixed 573231 2.6.33-1~experimental.2
Bug #573231 {Done: Stephen Kitt st...@sk2.org} [linux-2.6]
xserver-xorg-video-radeon: Font and bitmap corruption with full EXA (HD 4650
AGP)
There is no source info for the package 'linux-2.6' at version
'2.6.33-1~experimental.2' with architecture ''
Unable to make a source version for version '2.6.33-1~experimental.2'
Bug Marked as fixed in versions 2.6.33-1~experimental.2.
thanks
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
Archive:
http://lists.debian.org/handler.s.c.12682947335646.transcr...@bugs.debian.org
Bug#573406: src:linux-2.6: please use CONFIG_IP_FIB_TRIE
Package: src:linux-2.6 Severity: wishlist please use CONFIG_IP_FIB_TRIE in the future. This improves lookup performance if you have a large number of routes. LC-trie is a longest matching prefix lookup algorithm which performs better than FIB_HASH for large routing tables. But, it consumes more memory and is more complex. LC-trie is described in: IP-address lookup using LC-tries. Stefan Nilsson and Gunnar Karlsson IEEE Journal on Selected Areas in Communications, 17(6):1083-1092, June 1999 An experimental study of compression methods for dynamic tries Stefan Nilsson and Matti Tikkanen. Algorithmica, 33(1):19-33, 2002. http://www.nada.kth.se/~snilsson/public/papers/dyntrie2/ it has been in the kernel since 2.6.13, is actively maintained and mature. while it does not hurt the run-of-the-mill desktop or server setup in any way it will drasticly improve performance for routers. -- System Information: Debian Release: 5.0.4 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311080727.7136.58188.report...@jesaja.schuldei.org
Re: openvz kernel for debian squeeze
maximilian attems wrote: On Wed, 10 Mar 2010, Pavel Emelyanov wrote: Kir Kolyshkin wrote: Yup, we gonna rebase today, will let you know when done. Done. I've merged the 2.6.32.9. Please pull and check. thanks, cool! allmost good just had to fix up small things that seems debian specific: 1 out of 21 hunks FAILED -- saving rejects to file fs/namespace.c.rej # aufs patch already exports vfsmount_lock (no further comment) 1 out of 1 hunk FAILED -- saving rejects to file init/version.c.rej # debian specific hackery to /proc/version, easy fixup 1 out of 7 hunks FAILED -- saving rejects to file security/device_cgroup.c.rej # devcgroup_inode_permission export, see aboves aufs patch you don't have to deal with that happily. however on testbuild I get this build failure: CC [M] kernel/cpt/cpt_process.o /home/mattems/src/linux-2.6-2.6.32/debian/build/source_amd64_openvz/kernel/cpt/cpt_process.c: In function ‘dump_one_process’: /home/mattems/src/linux-2.6-2.6.32/debian/build/source_amd64_openvz/kernel/cpt/cpt_process.c:957: error: ‘_TIF_ABI_PENDING’ undeclared (first use in this function) /home/mattems/src/linux-2.6-2.6.32/debian/build/source_amd64_openvz/kernel/cpt/cpt_process.c:957: error: (Each undeclared identifier is reported only once /home/mattems/src/linux-2.6-2.6.32/debian/build/source_amd64_openvz/kernel/cpt/cpt_process.c:957: error: for each function it appears in.) make[7]: *** [kernel/cpt/cpt_process.o] Error 1 This was fixed this morning :) As long as two beancounters leaks. Please update. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b98cb03.6030...@parallels.com
Bug#573460: BUG: recent printk recursion!
Package: linux-image-2.6.26-2-openvz-amd64 Version: 2.6.26-2 I've got a VPS node running 2.6.26-2-openvz-amd64 and several guest machines. My kernel keeps reporting a printk bug in syslog: VPS-NODE:~# cat /var/log/syslog | grep recursion Mar 5 10:15:30 VPS-NODE kernel: BUG: recent printk recursion! Mar 5 10:15:35 VPS-NODE kernel: BUG: recent printk recursion! Mar 5 10:15:37 VPS-NODE kernel: BUG: recent printk recursion! Mar 5 10:15:43 VPS-NODE kernel: [896780.607831] BUG: recent printk recursion! Mar 5 10:15:47 VPS-NODE kernel: BUG: recent printk recursion! Mar 5 10:15:52 VPS-NODE kernel: BUG: recent printk recursion! I have found similar reports here: http://forum.openvz.org/index.php?t=msggoto=36696 http://bugzilla.openvz.org/show_bug.cgi?id=1284 I followed the guide to reproduce the problem on fresh install and I managed to do so: 1. Installed fresh Debian with 2.6.26-2-amd64 kernel 2. Installed linux-image-2.6.26-2-openvz-amd64 3. Edited /etc/sysctl.conf to forward traffic and allow proxy_arp 4. Reboot 5. Downloaded template form http://download.openvz.org/template/precreated/debian-5.0-x86.tar.gz to /vz/templates/cache 6. Created container with IP 192.168.1.3 7. Installed syslog inside the container and applied followin firewall rules: :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -i lo -j ACCEPT -A INPUT -d 192.168.1.3 -p tcp --dport 22 -j ACCEPT -A INPUT -d 192.168.1.3 -j LOG -A INPUT -d 192.168.1.3 -j DROP COMMIT 8. Allowed all traffic through venet0 on HN and :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -i lo -j ACCEPT -A INPUT -d 192.168.1.2 -p tcp --dport 22 -j ACCEPT -A INPUT -d 192.168.1.2 -j LOG -A INPUT -d 192.168.1.2 -j DROP COMMIT If I start hitting the HN IP address from other machine on any other port than 22 I get nice logging in /var/log/syslog until any attempt to connect to 192.168.1.3 on any blocked port. Once this is done I get: BUG: recent printk recursion! in HN and VPS logs. to the container, at which point all logging to both stops. _ Got a cool Hotmail story? Tell us now http://clk.atdmt.com/UKM/go/195013117/direct/01/
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #572339 (http://bugs.debian.org/572339) # * http://bugzilla.kernel.org/show_bug.cgi?id=15218 # * remote status changed: (?) - NEW usertags 572339 + status-NEW thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311170909.13491.49271.btsl...@merkel.debian.org
Processing of linux-2.6_2.6.26-21lenny4_i386.changes
linux-2.6_2.6.26-21lenny4_i386.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.26-21lenny4.dsc linux-2.6_2.6.26-21lenny4.diff.gz linux-doc-2.6.26_2.6.26-21lenny4_all.deb linux-manual-2.6.26_2.6.26-21lenny4_all.deb linux-patch-debian-2.6.26_2.6.26-21lenny4_all.deb linux-source-2.6.26_2.6.26-21lenny4_all.deb linux-support-2.6.26-2_2.6.26-21lenny4_all.deb linux-tree-2.6.26_2.6.26-21lenny4_all.deb linux-image-2.6.26-2-486_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-486_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-686_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-686-bigmem_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-686-bigmem_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-amd64_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-amd64_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-openvz-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-openvz-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common-openvz_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-all_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-all-i386_2.6.26-21lenny4_i386.deb linux-libc-dev_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-vserver-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-vserver-686_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-vserver-686-bigmem_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common-vserver_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-xen-686_2.6.26-21lenny4_i386.deb linux-modules-2.6.26-2-xen-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-xen-686_2.6.26-21lenny4_i386.deb xen-linux-system-2.6.26-2-xen-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common-xen_2.6.26-21lenny4_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 Archive: http://lists.debian.org/e1npn6m-0005qa...@ries.debian.org
Bug#573460: BUG: recent printk recursion!
On Thu, Mar 11, 2010 at 04:50:56PM +, Ralph Turexy wrote: Package: linux-image-2.6.26-2-openvz-amd64 Version: 2.6.26-2 [...] Please specify the package version number, not what 'uname -r' says. Ben. -- Ben Hutchings Humour is the best antidote to reality. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311184618.gm2...@decadent.org.uk
linux-2.6_2.6.26-22_amd64.changes ACCEPTED
Notes: Mapping stable to proposed-updates. Accepted: linux-2.6_2.6.26-22.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz linux-2.6_2.6.26-22.dsc to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc linux-doc-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-libc-dev_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.26-22_amd64.deb linux-manual-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-22_all.deb linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-patch-debian-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-22_all.deb linux-source-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-source-2.6.26_2.6.26-22_all.deb linux-support-2.6.26-2_2.6.26-22_all.deb to main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-22_all.deb linux-tree-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-tree-2.6.26_2.6.26-22_all.deb xen-linux-system-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/xen-linux-system-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb Override entries for your package: linux-2.6_2.6.26-22.dsc - source devel linux-doc-2.6.26_2.6.26-22_all.deb - optional doc linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb - optional devel linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb - optional devel linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb - optional devel linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb - optional devel linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb - optional devel linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb - optional devel linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb - optional devel linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb - optional devel linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb - optional devel linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb - optional devel linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb - optional admin linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb - optional admin linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb - optional admin linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb - optional admin linux-libc-dev_2.6.26-22_amd64.deb - optional devel linux-manual-2.6.26_2.6.26-22_all.deb - optional doc linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb - optional admin linux-patch-debian-2.6.26_2.6.26-22_all.deb - optional devel linux-source-2.6.26_2.6.26-22_all.deb - optional devel linux-support-2.6.26-2_2.6.26-22_all.deb - optional devel linux-tree-2.6.26_2.6.26-22_all.deb - optional devel xen-linux-system-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb - extra admin Announcing to debian-chan...@lists.debian.org Closing bugs: 479652 499671 508460 508527 513537 515533 524521 524542 529697 542633 547183 5571533 559035 562694 562815 562891 562892 565353 565960 568317 568345 570428 570532 571603 572322 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:
Bug#568561: marked as done (linux-image-2.6.26-2-xen-amd64: klogd doesn't receive kernel messages)
Your message dated Thu, 11 Mar 2010 19:53:48 + with message-id e1npos4-0007bx...@ries.debian.org and subject line Bug#568561: fixed in linux-2.6 2.6.26-21lenny4 has caused the Debian Bug report #568561, regarding linux-image-2.6.26-2-xen-amd64: klogd doesn't receive kernel messages 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.) -- 568561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-xen-amd64 Version: 2.6.26-21 Severity: important Hello, Since upgrade to the new point release 5.0.4 of lenny, kernel logging doesn't work anymore. With the former kernel 2.6.26-19lenny2, it works. It must be related to either amd64 and/or xen kernels beside maybe others. On a i686 based server, the problem does not exist. I tried to start klogd with option -s without success. So neither reading from /proc/kmsg nor the system call interface to the kernel message buffers enabled klogd to print the kernel messages through syslogd. Funnly, with dmesg, all kernel messages were displayed. Cheers, Phibo -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-xen-amd64 depends on: ii initramfs-tools 0.92o tools for generating an initramfs ii linux-modules-2.6.26-2-xen-am 2.6.26-21 Linux 2.6.26 modules on AMD64 linux-image-2.6.26-2-xen-amd64 recommends no packages. Versions of packages linux-image-2.6.26-2-xen-amd64 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none(no description available) -- no debconf information ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-21lenny4 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: linux-2.6_2.6.26-21lenny4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-21lenny4.diff.gz linux-2.6_2.6.26-21lenny4.dsc to main/l/linux-2.6/linux-2.6_2.6.26-21lenny4.dsc linux-doc-2.6.26_2.6.26-21lenny4_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-21lenny4_all.deb linux-headers-2.6.26-2-486_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-486_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-686-bigmem_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-686-bigmem_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-all-i386_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-i386_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-all_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-amd64_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common-openvz_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common-vserver_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common-xen_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-openvz-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-vserver-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-xen-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-686_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-486_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-image-2.6.26-2-486_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-686-bigmem_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-image-2.6.26-2-686-bigmem_2.6.26-21lenny4_i386.deb
Bug#569683: marked as done (linux-image-2.6.26-2-686: /proc/pid/maps is empty for all processes)
Your message dated Thu, 11 Mar 2010 19:53:48 + with message-id e1npos4-0007c3...@ries.debian.org and subject line Bug#570554: fixed in linux-2.6 2.6.26-21lenny4 has caused the Debian Bug report #570554, regarding linux-image-2.6.26-2-686: /proc/pid/maps is empty for all processes 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.) -- 570554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.26-21 Severity: normal Tags: patch /proc/pid/maps is empty for all processes, only /proc/self/maps works. The following patch helped me to fix the problem: --- linux-2.6-2.6.26/fs/proc/base.c 2008-07-13 16:51:29.0 -0500 +++ linux/fs/proc/base.c2009-12-26 02:14:58.0 -0600 @@ -251,7 +251,8 @@ task_lock(task); if (task-mm != mm) goto out; - if (task-mm != current-mm __ptrace_may_attach(task) 0) + if (task-mm != current-mm ((mm-flags MMF_IN_EXEC) || + __ptrace_may_attach(task) 0)) goto out; task_unlock(task); return mm; I'm writing this report from modified kernel, which contains this patch, and I test like 'cat /proc/1/maps' works now. -- Package-specific info: ** Kernel log: boot messages should be attached -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26cust1 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-686 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-2-686 recommends: ii libc6-i686 2.7-18lenny2 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-2-686 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none(no description available) Versions of packages linux-image-2.6.26-2-686 is related to: pn firmware-bnx2 none (no description available) pn firmware-bnx2xnone (no description available) pn firmware-ipw2x00 none (no description available) pn firmware-ivtv none (no description available) pn firmware-iwlwifi none (no description available) pn firmware-linuxnone (no description available) pn firmware-linux-nonfreenone (no description available) pn firmware-qlogic none (no description available) pn firmware-ralink none (no description available) -- debconf information: linux-image-2.6.26-2-686/postinst/bootloader-error-2.6.26-2-686: shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-2-686/postinst/old-dir-initrd-link-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/initrd-2.6.26-2-686: linux-image-2.6.26-2-686/preinst/overwriting-modules-2.6.26-2-686: true linux-image-2.6.26-2-686/postinst/bootloader-test-error-2.6.26-2-686: linux-image-2.6.26-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.26-2-686/postinst/depmod-error-2.6.26-2-686: false linux-image-2.6.26-2-686/prerm/would-invalidate-boot-loader-2.6.26-2-686: true linux-image-2.6.26-2-686/postinst/kimage-is-a-directory: linux-image-2.6.26-2-686/postinst/old-initrd-link-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/bootloader-initrd-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/abort-overwrite-2.6.26-2-686: linux-image-2.6.26-2-686/preinst/abort-install-2.6.26-2-686: linux-image-2.6.26-2-686/preinst/elilo-initrd-2.6.26-2-686: true linux-image-2.6.26-2-686/postinst/depmod-error-initrd-2.6.26-2-686: false linux-image-2.6.26-2-686/postinst/create-kimage-link-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/lilo-initrd-2.6.26-2-686: true linux-image-2.6.26-2-686/prerm/removing-running-kernel-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/failed-to-move-modules-2.6.26-2-686: linux-image-2.6.26-2-686/postinst/old-system-map-link-2.6.26-2-686: true ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-21lenny4 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due
Bug#570554: marked as done (linux: /proc/pid/maps empty)
Your message dated Thu, 11 Mar 2010 19:53:48 + with message-id e1npos4-0007c3...@ries.debian.org and subject line Bug#570554: fixed in linux-2.6 2.6.26-21lenny4 has caused the Debian Bug report #570554, regarding linux: /proc/pid/maps empty 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.) -- 570554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux-2.6 Version: 2.6.26-21lenny3 Hi, I'm seeing a regression test failure in elfutils because on some of the buildds /proc/pid/maps is empty. I have succesful logs and failed logs with 2.6.26-2-amd64, as reported by uname. But they're obviously not running the same version anymore. As far as I can see all the buildds I have a problem with run 2.6.26-21lenny3. Kurt ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-21lenny4 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: linux-2.6_2.6.26-21lenny4.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-21lenny4.diff.gz linux-2.6_2.6.26-21lenny4.dsc to main/l/linux-2.6/linux-2.6_2.6.26-21lenny4.dsc linux-doc-2.6.26_2.6.26-21lenny4_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-21lenny4_all.deb linux-headers-2.6.26-2-486_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-486_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-686-bigmem_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-686-bigmem_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-all-i386_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-i386_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-all_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-amd64_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common-openvz_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common-vserver_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common-xen_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-common_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-openvz-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-vserver-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-686_2.6.26-21lenny4_i386.deb linux-headers-2.6.26-2-xen-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-686_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-486_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-image-2.6.26-2-486_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-686-bigmem_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-image-2.6.26-2-686-bigmem_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-image-2.6.26-2-686_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-amd64_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-openvz-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-686_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-vserver-686-bigmem_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-686-bigmem_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-vserver-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-686_2.6.26-21lenny4_i386.deb linux-image-2.6.26-2-xen-686_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-image-2.6.26-2-xen-686_2.6.26-21lenny4_i386.deb linux-libc-dev_2.6.26-21lenny4_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.26-21lenny4_i386.deb linux-manual-2.6.26_2.6.26-21lenny4_all.deb to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-21lenny4_all.deb linux-modules-2.6.26-2-xen-686_2.6.26-21lenny4_i386.deb to
Bug#571603: marked as done (linux-image-2.6.26-2-xen-686: Dom0 crashes on newer hypervisors if msi interrupts are available)
Your message dated Thu, 11 Mar 2010 19:57:16 +
with message-id e1npovq-00086h...@ries.debian.org
and subject line Bug#571603: fixed in linux-2.6 2.6.26-22
has caused the Debian Bug report #571603,
regarding linux-image-2.6.26-2-xen-686: Dom0 crashes on newer hypervisors if
msi interrupts are available
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.)
--
571603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.26-2-xen-686
Version: 2.6.26-21lenny3
Severity: normal
Tags: patch
The default Debian kernel dom0 will not boot on
hypervisors = Xen 3.3 if MSI interrupts are available.
The reason for this is that one of the patches included
in the build (suse-200808...) has an incorrect structure
definition. (It was a structure used at some point during
development, but changed before the 3.3 release. The patch
was a snapshot of development after the initial change but
before the final version.)
The attached patch updates the msi code to the appropriate
(released, stable, forwards-compatible) structure definition,
so that the 2.6.26-xen kernel can boot on future hypervisors
(including the upcoming 4.0 release). I've already tested it
within the debian source build system.
A work-around is to add pci=nosmi on the kernel command line.
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-2-xen-686 depends on:
ii initramfs-tools0.92o tools for generating an initramfs
ii linux-modules-2.6. 2.6.26-21lenny3 Linux 2.6.26 modules on i686
Versions of packages linux-image-2.6.26-2-xen-686 recommends:
ii libc6-xen 2.7-18lenny2 GNU C Library: Shared libraries [X
Versions of packages linux-image-2.6.26-2-xen-686 suggests:
ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn linux-doc-2.6.26 none(no description available)
-- no debconf information
diff -u -r build_i386_xen_686/drivers/pci/msi-xen.c build_i386_xen_686-fix/drivers/pci/msi-xen.c
--- build_i386_xen_686/drivers/pci/msi-xen.c 2010-02-25 12:23:43.0 +
+++ build_i386_xen_686-fix/drivers/pci/msi-xen.c 2010-02-25 13:08:16.0 +
@@ -238,11 +238,27 @@
return 0;
}
+static u64 find_table_base(struct pci_dev *dev, int pos)
+{
+ u8 bar;
+ u32 reg;
+ unsigned long flags;
+
+ pci_read_config_dword(dev, msix_table_offset_reg(pos), reg);
+ bar = reg PCI_MSIX_FLAGS_BIRMASK;
+
+ flags = pci_resource_flags(dev, bar);
+ if (flags (IORESOURCE_DISABLED | IORESOURCE_UNSET | IORESOURCE_BUSY))
+ return 0;
+
+ return pci_resource_start(dev, bar);
+}
+
/*
* Protected by msi_lock
*/
static int msi_map_pirq_to_vector(struct pci_dev *dev, int pirq,
- int entry_nr, int msi)
+ int entry_nr, u64 table_base)
{
struct physdev_map_pirq map_irq;
int rc;
@@ -254,10 +270,10 @@
map_irq.type = MAP_PIRQ_TYPE_MSI;
map_irq.index = -1;
map_irq.pirq = pirq;
-map_irq.msi_info.bus = dev-bus-number;
-map_irq.msi_info.devfn = dev-devfn;
- map_irq.msi_info.entry_nr = entry_nr;
-map_irq.msi_info.msi = msi;
+ map_irq.bus = dev-bus-number;
+ map_irq.devfn = dev-devfn;
+ map_irq.entry_nr = entry_nr;
+ map_irq.table_base = table_base;
if ((rc = HYPERVISOR_physdev_op(PHYSDEVOP_map_pirq, map_irq)))
printk(KERN_WARNING map irq failed\n);
@@ -268,9 +284,9 @@
return map_irq.pirq;
}
-static int msi_map_vector(struct pci_dev *dev, int entry_nr, int msi)
+static int msi_map_vector(struct pci_dev *dev, int entry_nr, u64 table_base)
{
- return msi_map_pirq_to_vector(dev, -1, entry_nr, msi);
+ return msi_map_pirq_to_vector(dev, -1, entry_nr, table_base);
}
static void pci_intx_for_msi(struct pci_dev *dev, int enable)
@@ -286,7 +302,7 @@
if (!dev-msi_enabled)
return;
- pirq = msi_map_pirq_to_vector(dev, dev-irq, 0, 1);
+ pirq = msi_map_pirq_to_vector(dev, dev-irq, 0, 0);
if (pirq 0)
return;
@@ -296,19 +312,29 @@
static void __pci_restore_msix_state(struct pci_dev *dev)
{
+int pos;
unsigned long flags;
+ u64 table_base;
struct msi_dev_list *msi_dev_entry;
struct msi_pirq_entry *pirq_entry, *tmp;
+ pos = pci_find_capability(dev, PCI_CAP_ID_MSIX);
+ if (pos = 0)
+ return;
+
if (!dev-msix_enabled)
return;
msi_dev_entry =
Bug#572322: marked as done (qla2xxx: Loading Module results in DMA error on Calgary PHB)
Your message dated Thu, 11 Mar 2010 19:57:16 + with message-id e1npovq-00086m...@ries.debian.org and subject line Bug#572322: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #572322, regarding qla2xxx: Loading Module results in DMA error on Calgary PHB 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.) -- 572322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Severity: important Currently all Debian Kernels 2.6.18 (including 2.6.32 from unstable) are unusable on larger IBM xSeries machines with QLogic cards as loading the kernel modules results in a crash and reboot of the whole machine: Feb 24 10:34:12 dbsrv01 kernel: [ 95.516679] qla2xxx :02:01.0: Cable is unplugged... Feb 24 10:34:12 dbsrv01 kernel: [ 95.516679] scsi(1): fw_state=4 curr time=208e. Feb 24 10:34:12 dbsrv01 kernel: [ 95.516679] scsi(1): Firmware ready FAILED . Feb 24 10:34:12 dbsrv01 kernel: [ 95.516679] qla2x00_restart_isp(): Configure loop done, status = 0x0 Feb 24 10:34:13 dbsrv01 kernel: [ 95.516679] qla2xxx :02:01.0: ISP System Error - mbx1=65h mbx2=2h mbx3=8080h. Feb 24 10:34:13 dbsrv01 kernel: [ 95.516679] qla2xxx :02:01.0: Firmware dump saved to temp buffer (1/c20007f84000). Feb 24 10:34:13 dbsrv01 kernel: [ 95.516679] qla2x00_abort_isp(1): exiting. Feb 24 10:34:13 dbsrv01 kernel: [ 95.516679] qla2x00_mailbox_command(1): finished abort_isp Feb 24 10:34:13 dbsrv01 kernel: [ 95.516679] qla2x00_mailbox_command(1): finished abort_isp Feb 24 10:34:13 dbsrv01 kernel: [ 95.545239] qla2x00_mailbox_command(1): FAILED. mbx0=69, mbx1=8023, mbx2=, cmd=69 Feb 24 10:34:13 dbsrv01 kernel: [ 95.613508] qla2x00_get_firmware_state(1): failed=100. Feb 24 10:34:13 dbsrv01 kernel: [ 95.620441] scsi(1): fw_state=8023 curr time=2118. Feb 24 10:34:13 dbsrv01 kernel: [ 95.625500] scsi(1): Firmware ready FAILED . Feb 24 10:34:13 dbsrv01 kernel: [ 95.687879] scsi(1): qla2x00_loop_resync - end Feb 24 10:34:13 dbsrv01 kernel: [ 96.232463] scsi(1): dpc: sched qla2x00_abort_isp ha = 81086b4e85f8 Feb 24 10:34:13 dbsrv01 kernel: [ 96.232463] qla2xxx :02:01.0: Performing ISP error recovery - ha= 81086b4e85f8. Feb 24 10:34:13 dbsrv01 kernel: [ 96.236463] Calgary: DMA error on Calgary PHB 0x2, 0x02010...@csr 0x8...@plssr The only kernel which works fine - as far as I know - is the RHEL Kernel as they ship a patch which disables msi-x [1]. The issue is also known on several other bugtrackers, including bugzilla.kernel.org ([2], [3]). Unfortunately there doesn't seem to be a proper fix from upstream, so it would be nice to have the RHEL workaround in Debian, too, as using Lenny is a PITA thanks to this bug - currently we're using the Etch Kernel as this is the last one which works well. According to the bugzilla.kernel.org bug the issue was introduced with 2.6.20. Machine and the Qlogic cards are both running the latest BIOS and Firmware versions, so there is nothing to upgrade there unfortunately. [1] http://launchpadlibrarian.net/17517188/linux-2.6-scsi-qla2xxx-disable-msi-x-by-default.patch [2] http://bugzilla.kernel.org/show_bug.cgi?id=11646 [3] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268242 Best regards, Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-22 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: linux-2.6_2.6.26-22.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz linux-2.6_2.6.26-22.dsc to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc linux-doc-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb
Bug#568317: marked as done (linux-image-* postinst did not correctly run lilo)
Your message dated Thu, 11 Mar 2010 19:57:16 + with message-id e1npovq-00086n...@ries.debian.org and subject line Bug#568317: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #568317, regarding linux-image-* postinst did not correctly run lilo 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.) -- 568317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: perl Version: 5.10.0-19lenny2 Severity: important I noticed that /var/lib/dpkg/info/linux-image-*.postinst did not correctly run lilo. Seems that the bug can be reproduced with script: #! /usr/bin/perl $_ = 'do_bootloader = yes'; #print ctrl1\n; print test1\n if /do_bootloader\s*=\s*(yes|true|1)\s*/ig; #print ctrl2\n; print test2\n if /do_bootloader\s*=\s*(yes|true|1)\s*/ig; #print ctrl3\n; print test3\n if /do_bootloader\s*=\s*(yes|true|1)\s*/ig; #print ctrl4\n; print test4\n if /do_bootloader\s*=\s*(yes|true|1)\s*/ig; #print ctrl5\n; print test5\n if /do_bootloader\s*=\s*(yes|true|1)\s*/ig; #print ctrl6\n; print test6\n if /do_bootloader\s*=\s*(yes|true|1)\s*/ig; exit; which should print 6 tests, but it prints 1,3,5 only. Uncommenting the control lines, those are printed correctly, but still only tests 1,3,5 are printed. Am I going mad ??!! Thanks, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-pk03.15-svr (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages perl depends on: ii libc62.7-18lenny2GNU C Library: Shared libraries ii libdb4.6 4.6.21-11 Berkeley v4.6 Database Libraries [ ii libgdbm3 1.8.3-3 GNU dbm database routines (runtime ii perl-base5.10.0-19lenny2 minimal Perl system ii perl-modules 5.10.0-19lenny2 Core Perl modules Versions of packages perl recommends: ii netbase 4.34 Basic TCP/IP networking system Versions of packages perl suggests: pn libterm-readline-gnu-per none (no description available) ii perl-doc 5.10.0-19lenny2 Perl documentation -- no debconf information ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-22 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: linux-2.6_2.6.26-22.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz linux-2.6_2.6.26-22.dsc to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc linux-doc-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb
Bug#562891: marked as done (openvz: checkpointing shared memory fails)
Your message dated Thu, 11 Mar 2010 19:57:15 +
with message-id e1npovp-000863...@ries.debian.org
and subject line Bug#562891: fixed in linux-2.6 2.6.26-22
has caused the Debian Bug report #562891,
regarding openvz: checkpointing shared memory fails
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.)
--
562891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.26-21
Severity: important
Tags: patch
fixes panic on psql use:
http://archives.postgresql.org/pgsql-general/2009-10/msg00125.php
will add patch to lenny openvz featureset
(checking ABI build atm
--
maks
From 1f7db8ea4a3e4be07047223a0c53fb501346aea7 Mon Sep 17 00:00:00 2001
From: Vitaily Gusev vgu...@openvz.org
Date: Mon, 12 Oct 2009 18:53:30 +0400
Subject: [PATCH 87/90] cpt: dump inode content for shm_file_operations
If file-f_op == shm_file_operations then cpt code doesn't
dump inode content, and dump only for f_op == shmem_file_operations.
Bug http://bugzilla.openvz.org/show_bug.cgi?id=1342
Signed-off-by: Vitaliy Gusev vgu...@openvz.org
Signed-off-by: Pavel Emelyanov xe...@openvz.org
---
kernel/cpt/cpt_files.c | 22 +-
1 files changed, 13 insertions(+), 9 deletions(-)
diff --git a/kernel/cpt/cpt_files.c b/kernel/cpt/cpt_files.c
index dd05814..866ca53 100644
--- a/kernel/cpt/cpt_files.c
+++ b/kernel/cpt/cpt_files.c
@@ -620,19 +620,23 @@ static int dump_content_regular(struct file *file, struct
cpt_context *ctx)
return -EINVAL;
do_read = file-f_op-read;
- if (file-f_op == shm_file_operations) {
- struct shm_file_data *sfd = file-private_data;
- cpt_dump_content_sysvshm(sfd-file, ctx);
+ if (file-f_op == shm_file_operations ||
+ file-f_op == shmem_file_operations) {
+ struct file *shm_file = file;
- return 0;
- }
- if (file-f_op == shmem_file_operations) {
- do_read = file-f_dentry-d_inode-i_fop-read;
- cpt_dump_content_sysvshm(file, ctx);
+ /* shmget uses shm ops */
+ if (file-f_op == shm_file_operations) {
+ struct shm_file_data *sfd = file-private_data;
+ shm_file = sfd-file;
+ }
+
+ cpt_dump_content_sysvshm(shm_file, ctx);
+
+ do_read = shm_file-f_dentry-d_inode-i_fop-read;
if (!do_read) {
wprintk_ctx(TMPFS is not configured?\n);
- return dump_content_shm(file, ctx);
+ return dump_content_shm(shm_file, ctx);
}
}
--
1.6.5.7
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-2-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/bash
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.26-22
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:
linux-2.6_2.6.26-22.diff.gz
to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz
linux-2.6_2.6.26-22.dsc
to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc
linux-doc-2.6.26_2.6.26-22_all.deb
to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb
linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb
Bug#565960: marked as done (bnx2 can crash in various cases)
Your message dated Thu, 11 Mar 2010 19:57:16 + with message-id e1npovq-00086j...@ries.debian.org and subject line Bug#565960: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #565960, regarding bnx2 can crash in various cases 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.) -- 565960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.26-21 Severity: important Tags: patch fixed-upstream Netconsole would panic when resetting bnx2 devices. This was fixed in v2.6.27 (commit id 9a120bc570627342c17befaa6af9b0a556dfda48). bnx2 can crash if 'ethtool -s' is run on a device is down. This was fixed in v2.6.27 (commit id d6b14486953d0e8d1c57db29bf6104cea198b884). bnx2_poll_work() has race conditions that can lead to a panic. This was fixed in v2.6.27.25 (commit id 44c94aa0806d36ee902350027c20c63283923112). I believe these fixes are suitable for a stable release, but am not able to test them myself. 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 ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-22 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: linux-2.6_2.6.26-22.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz linux-2.6_2.6.26-22.dsc to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc linux-doc-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-libc-dev_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.26-22_amd64.deb linux-manual-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-22_all.deb linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-patch-debian-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-22_all.deb linux-source-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-source-2.6.26_2.6.26-22_all.deb linux-support-2.6.26-2_2.6.26-22_all.deb to main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-22_all.deb linux-tree-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-tree-2.6.26_2.6.26-22_all.deb xen-linux-system-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/xen-linux-system-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb A summary of the changes between this version and the previous one is attached.
Bug#550740: marked as done (linux-image-2.6.26-2-openvz-amd64: checkpointing openvz resets shared memory to zero)
Your message dated Thu, 11 Mar 2010 19:57:15 + with message-id e1npovp-000863...@ries.debian.org and subject line Bug#562891: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #562891, regarding linux-image-2.6.26-2-openvz-amd64: checkpointing openvz resets shared memory to zero 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.) -- 562891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-openvz-amd64 Version: 2.6.26-19 Severity: critical Justification: causes serious data loss The checkpoint/restore of vzctl resets shared memory in an openvz container to zero if a programm access this shared memory. More information in the upstream bugreport: http://bugzilla.openvz.org/show_bug.cgi?id=1342 -- Package-specific info: ** Version: Linux version 2.6.26-2-openvz-amd64 (Debian 2.6.26-19) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Aug 19 23:15:49 UTC 2009 ** Command line: root=/dev/mapper/service-system ro quiet ** Not tainted ** Kernel log: [3.172062] ide0: BM-DMA at 0xfc00-0xfc07 [3.172076] ide1: BM-DMA at 0xfc08-0xfc0f [3.172086] Probing IDE interface ide0... [3.551179] hiddev96hidraw0: USB HID v1.10 Device [American Power Conversion Back-UPS BR 800 FW:9.o2 .I USB FW:o2 ] on usb-:00:1d.1-1 [3.551179] usbcore: registered new interface driver usbhid [3.551179] usbhid: v2.6:USB HID core driver [4.191959] hda: HL-DT-STDVD-ROM GDR8163B, ATAPI CD/DVD-ROM drive [4.835552] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [4.859479] hda: UDMA/33 mode selected [4.859479] Probing IDE interface ide1... [5.470719] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [5.475160] ide1 at 0x170-0x177,0x376 on irq 15 [6.007116] Driver 'sd' needs updating - please use bus_type methods [6.007116] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) [6.007116] sd 0:0:0:0: [sda] Write Protect is off [6.007116] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [6.007116] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6.007116] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) [6.007116] sd 0:0:0:0: [sda] Write Protect is off [6.007116] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [6.007116] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6.007116] sda:6hda: ATAPI 52X DVD-ROM drive, 256kB Cache [6.015160] Uniform CD-ROM driver Revision: 3.20 [6.021160] sda1 sda2 [6.021361] sd 0:0:0:0: [sda] Attached SCSI disk [6.218508] md: raid0 personality registered for level 0 [6.229939] md: md0 stopped. [6.234816] md: bindsda1 [6.246839] md0: setting max_sectors to 128, segment boundary to 32767 [6.246839] raid0: looking at sda1 [6.246839] raid0: comparing sda1(240832) with sda1(240832) [6.246839] raid0: END [6.246839] raid0: == UNIQUE [6.246839] raid0: 1 zones [6.246839] raid0: FINAL 1 zones [6.246839] raid0: done. [6.246839] raid0 : md_size is 240832 blocks. [6.246839] raid0 : conf-hash_spacing is 240832 blocks. [6.246839] raid0 : nb_zone is 1. [6.246839] raid0 : Allocating 8 bytes for hash. [6.247034] md: md1 stopped. [6.273707] md: bindsda2 [6.286009] md1: setting max_sectors to 128, segment boundary to 32767 [6.286009] raid0: looking at sda2 [6.286009] raid0: comparing sda2(488142976) with sda2(488142976) [6.286009] raid0: END [6.286009] raid0: == UNIQUE [6.286009] raid0: 1 zones [6.286009] raid0: FINAL 1 zones [6.286009] raid0: done. [6.286009] raid0 : md_size is 488142976 blocks. [6.286009] raid0 : conf-hash_spacing is 488142976 blocks. [6.286009] raid0 : nb_zone is 1. [6.286009] raid0 : Allocating 8 bytes for hash. [6.357615] device-mapper: uevent: version 1.0.3 [6.358163] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-de...@redhat.com [6.550451] PM: Starting manual resume from disk [6.607194] kjournald starting. Commit interval 5 seconds [6.607194] EXT3-fs: mounted filesystem with ordered data mode. [7.381760] udevd version 125 started [8.058604] EDAC MC: Ver: 2.1.0 Aug 19 2009 [8.061974] EDAC e752x: tolm = 4, remapbase = ffc000, remaplimit = 0 [8.062011] EDAC MC0: Giving out device to 'e752x_edac' 'E7525': DEV :00:00.0 [8.062083] EDAC PCI0: Giving out device to module
Bug#524521: marked as done (Fix time warps with VMI clocksource)
Your message dated Thu, 11 Mar 2010 19:57:15 + with message-id e1npovp-00085k...@ries.debian.org and subject line Bug#524521: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #524521, regarding Fix time warps with VMI clocksource 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.) -- 524521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.26-13 This is a bug in the VMI_timer clocksource implementation and affects only when running with VMI enabled on VMware platform. There can be situations when the VMI_CYCLES_COUNTER can go back between subsequent reads of that counter. This could result in kernels hangs due to the unsigned calculation that are done in the clocksource code. This situation is only seen when the guest is running boot-halt tests (as the VMI timer could mostly be skewed only during the boot process) in a highly over-committed situation. So though the bug is not very severe it has negligible impact as it affects code which will be run only when running under VMware and that too in 32bit configuration. Please include it for the next update of the kernel for lenny. Commit details are commit 48ffc70b675aa7798a52a2e92e20f6cce9140b3d Author: Alok N Kataria akata...@vmware.com Date: Wed Feb 18 12:33:55 2009 -0800 x86, vmi: TSC going backwards check in vmi clocksource Thanks, Alok ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-22 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: linux-2.6_2.6.26-22.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz linux-2.6_2.6.26-22.dsc to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc linux-doc-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-libc-dev_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.26-22_amd64.deb linux-manual-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-22_all.deb linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-patch-debian-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-22_all.deb linux-source-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-source-2.6.26_2.6.26-22_all.deb linux-support-2.6.26-2_2.6.26-22_all.deb to main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-22_all.deb linux-tree-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-tree-2.6.26_2.6.26-22_all.deb xen-linux-system-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/xen-linux-system-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb A summary of the changes between
Bug#508460: marked as done (ipv6: add/up results in permanent 'tentative' flag, up/add works)
Your message dated Thu, 11 Mar 2010 19:57:15 + with message-id e1npovp-000850...@ries.debian.org and subject line Bug#508460: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #508460, regarding ipv6: add/up results in permanent 'tentative' flag, up/add works 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.) -- 508460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-11 Severity: normal Tags: ipv6 X-Debbugs-Cc: 507...@bugs.debian.org Over at #507646, we stumbled over something that seems like a bug in the duplicate address detection mechanism of the kernel: If I add an address to an interface (bridge or physical interface, does not matter), and then up the iface, then the tentative flag on the address never gets cleared (look for SEE HERE markers): khyber:/# ip addr add 2001:41e0:ff38:fffd::5 dev br1 ip addr show dev br1 sleep 10 ip addr show dev br1 ip link set br1 up ip addr show dev br1 sleep 10 ip addr show dev br1 9: br1: BROADCAST,MULTICAST mtu 1500 qdisc noqueue state DOWN link/ether 3e:2b:4a:f3:6a:e1 brd ff:ff:ff:ff:ff:ff inet6 2001:41e0:ff38:fffd::5/128 scope global tentative valid_lft forever preferred_lft forever 9: br1: BROADCAST,MULTICAST mtu 1500 qdisc noqueue state DOWN link/ether 3e:2b:4a:f3:6a:e1 brd ff:ff:ff:ff:ff:ff inet6 2001:41e0:ff38:fffd::5/128 scope global tentative valid_lft forever preferred_lft forever 9: br1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether 3e:2b:4a:f3:6a:e1 brd ff:ff:ff:ff:ff:ff inet6 2001:41e0:ff38:fffd::5/128 scope global tentative valid_lft forever preferred_lft forever^ SEE HERE inet6 fe80::3c2b:4aff:fef3:6ae1/64 scope link tentative valid_lft forever preferred_lft forever 9: br1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether 3e:2b:4a:f3:6a:e1 brd ff:ff:ff:ff:ff:ff inet6 2001:41e0:ff38:fffd::5/128 scope global tentative valid_lft forever preferred_lft forever^ SEE HERE inet6 fe80::3c2b:4aff:fef3:6ae1/64 scope link valid_lft forever preferred_lft forever If I first up the interface, then add the address, it works as expected (look for SEE HERE markers) khyber:/# ip addr show dev br1 ip link set br1 up ip addr show dev br1 ip addr add 2001:41e0:ff38:fffd::5 dev br1 ip addr show dev br1 sleep 10 ip addr show dev br1 9: br1: BROADCAST,MULTICAST mtu 1500 qdisc noqueue state DOWN link/ether 3e:2b:4a:f3:6a:e1 brd ff:ff:ff:ff:ff:ff 9: br1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether 3e:2b:4a:f3:6a:e1 brd ff:ff:ff:ff:ff:ff inet6 fe80::3c2b:4aff:fef3:6ae1/64 scope link tentative valid_lft forever preferred_lft forever 9: br1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether 3e:2b:4a:f3:6a:e1 brd ff:ff:ff:ff:ff:ff inet6 2001:41e0:ff38:fffd::5/128 scope global tentative valid_lft forever preferred_lft forever^ SEE HERE inet6 fe80::3c2b:4aff:fef3:6ae1/64 scope link tentative valid_lft forever preferred_lft forever 9: br1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether 3e:2b:4a:f3:6a:e1 brd ff:ff:ff:ff:ff:ff inet6 2001:41e0:ff38:fffd::5/128 scope global valid_lft forever preferred_lft forever^ SEE HERE inet6 fe80::3c2b:4aff:fef3:6ae1/64 scope link valid_lft forever preferred_lft forever I cannot reproduce this with a sit tunnel device, which seems logical as DAD/tentative states are not used in a point-to-point context, I think. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems ah, but a man's reach should exceed his grasp, or what's a heaven for? -- robert browning -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.26-1-amd64 depends on: ii debconf [debconf-2.0]
Bug#529697: marked as done (linux-image-2.6.26-2-686: Crystal 4237b audio card not working and causing kernel freeze during boot)
Your message dated Thu, 11 Mar 2010 19:57:15 + with message-id e1npovp-00085u...@ries.debian.org and subject line Bug#529697: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #529697, regarding linux-image-2.6.26-2-686: Crystal 4237b audio card not working and causing kernel freeze during 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.) -- 529697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Version: 2.6.26-15lenny2 Severity: normal After a fresh Lenny install on a Dell CPi D266XT with a builtin Crystal 4237b sound card the system freezes during boot for several minutes before continuing to boot correctly. After booting correctly sound does not work. The relevant part of the dmesg is included below. [ 43.816923] found SMC SuperIO Chip (devid=0x09 rev=01 base=0x03f0): FDC37N958FR [ 43.817079] Revision higher than expected [ 44.171969] BUG: unable to handle kernel NULL pointer dereference at 0170 [ 44.172203] IP: [c021be05] pnp_activate_dev+0x3/0x3a [ 44.172370] *pde = [ 44.172510] Oops: [#1] SMP [ 44.172687] Modules linked in: snd_cs4232(+) snd_wavefront snd_opl3_lib snd_cs4231_lib irda snd_hwdep snd_mpu401_uart snd_rawmidi crc_ccitt snd_seq_device pcmcia firm ware_class serio_raw snd_pcm psmouse snd_timer i2c_piix4 snd i2c_core yenta_socket rsrc_nonstatic soundcore pcmcia_core snd_page_alloc pcspkr evdev dcdbas ext3 jbd mbcac he sha256_generic aes_i586 aes_generic cbc dm_crypt crypto_blkcipher dm_mirror dm_log dm_snapshot dm_mod ide_cd_mod cdrom ide_disk ata_generic libata scsi_mod dock piix ide_pci_generic uhci_hcd floppy ide_core usbcore thermal_sys [ 44.173664] [ 44.173664] Pid: 1182, comm: modprobe Not tainted (2.6.26-2-686 #1) [ 44.173664] EIP: 0060:[c021be05] EFLAGS: 00010246 CPU: 0 [ 44.173664] EIP is at pnp_activate_dev+0x3/0x3a [ 44.173664] EAX: EBX: ECX: 0014 EDX: [ 44.173664] ESI: EDI: cb45e200 EBP: c023ab31 ESP: ca1e7dd8 [ 44.173664] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 44.173664] Process modprobe (pid: 1182, ti=ca1e6000 task=ca5cae00 task.ti=ca1e6000) [ 44.173664] Stack: cc97d3a3 cb7fac00 cc97d77d cb45e200 cc97f680 [ 44.173664]c021ac73 cb45e200 cc97f69c c023aaba cb45e200 cb45e2b8 cc97f69c [ 44.173664]c023ab68 c035bc40 cc97f69c c023a403 cb444d7c cb444d80 cb45e254 [ 44.173664] Call Trace: [ 44.173664] [cc97d3a3] snd_cs423x_pnp_init_wss+0xd/0xe1 [snd_cs4232] [ 44.173664] [cc97d77d] snd_cs4232_pnpbios_detect+0x88/0xe8 [snd_cs4232] [ 44.173664] [c021ac73] pnp_device_probe+0x63/0x80 [ 44.173664] [c023aaba] driver_probe_device+0xb5/0x12c [ 44.173664] [c023ab68] __driver_attach+0x37/0x55 [ 44.173664] [c023a403] bus_for_each_dev+0x37/0x59 [ 44.173664] [c023a955] driver_attach+0x11/0x13 [ 44.173664] [c023ab31] __driver_attach+0x0/0x55 [ 44.173664] [c023a757] bus_add_driver+0x8a/0x1a7 [ 44.173664] [c01ddd50] kset_find_obj+0x20/0x4b [ 44.173664] [c023ad49] driver_register+0x6d/0xc1 [ 44.173664] [cc936027] alsa_card_cs423x_init+0x27/0x68 [snd_cs4232] [ 44.173664] [c013f66e] sys_init_module+0x187a/0x19ea [ 44.173664] [c018a629] seq_open+0x4d/0x6a [ 44.173664] [c0115b67] do_page_fault+0x29b/0x5b8 [ 44.173664] [c0166435] vma_link+0xa3/0xbd [ 44.173664] [c0127067] __request_region+0x0/0x80 [ 44.173664] [c0103853] sysenter_past_esp+0x78/0xb1 [ 44.173664] === [ 44.173664] Code: 93 9c 00 00 00 52 50 68 c9 90 32 c0 e8 0b 71 f0 ff b8 f0 ff ff ff 83 c4 0c eb 09 b8 ed ff ff ff eb 02 31 c0 5b 5e 5f c3 53 31 d2 83 b8 70 01 00 00 00 89 c3 75 25 e8 73 ff ff ff ba f0 ff ff ff [ 44.173664] EIP: [c021be05] pnp_activate_dev+0x3/0x3a SS:ESP 0068:ca1e7dd8 [ 44.184830] ---[ end trace 9e9e1834427073d5 ]--- [ 45.578284] orinoco 0.15 (David Gibson her...@gibson.dropbear.id.au, Pavel Roskin pro...@gnu.org, et al) [ 45.630165] orinoco_cs 0.15 (David Gibson her...@gibson.dropbear.id.au, Pavel Roskin pro...@gnu.org, et al) [ 45.712423] eth0: Hardware identity CUT [ 45.712634] eth0: Station identity CUT [ 45.712742] eth0: Firmware determined as Lucent/Agere 8.72 [ 45.712839] eth0: Ad-hoc demo mode supported [ 45.712930] eth0: IEEE standard IBSS ad-hoc mode supported [ 45.713026] eth0: WEP supported, 104-bit key [ 45.713249] eth0: MAC address CUT [ 45.713436] eth0: Station name HERMES I [ 45.714126] eth0:
Bug#542633: marked as done (openvz: [UBC]: Endless loop in __sk_stream_wait_memory.)
Your message dated Thu, 11 Mar 2010 19:57:15 + with message-id e1npovp-00085a...@ries.debian.org and subject line Bug#542633: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #542633, regarding openvz: [UBC]: Endless loop in __sk_stream_wait_memory. 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.) -- 542633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.26-18 Severity: important Tags: patch The loop in __sk_stream_wait_memory when tcp_sendmsg asks to wait for TCPSNDBUF space is endless when the timeout is not specified. The only way out is to queue a signal for that process. Lets return a status flag from ub_sock_snd_queue_add that UB space is available. This is enough to make a correct decision to leave the cycle. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-rc6-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 ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-22 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: linux-2.6_2.6.26-22.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz linux-2.6_2.6.26-22.dsc to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc linux-doc-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-libc-dev_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.26-22_amd64.deb linux-manual-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-22_all.deb linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-patch-debian-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-22_all.deb linux-source-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-source-2.6.26_2.6.26-22_all.deb linux-support-2.6.26-2_2.6.26-22_all.deb to main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-22_all.deb linux-tree-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-tree-2.6.26_2.6.26-22_all.deb xen-linux-system-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/xen-linux-system-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 542...@bugs.debian.org, and the maintainer will reopen the bug report if
Bug#570532: marked as done (linux-source-2.6.26: patch required for yealink.c)
Your message dated Thu, 11 Mar 2010 19:57:16 +
with message-id e1npovq-00086c...@ries.debian.org
and subject line Bug#570532: fixed in linux-2.6 2.6.26-22
has caused the Debian Bug report #570532,
regarding linux-source-2.6.26: patch required for yealink.c
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.)
--
570532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-source-2.6.26
Version: 2.6.26-21lenny3
Severity: normal
Tags: patch
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (800, 'stable'), (500, 'unstable'), (400, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Hi,
I'm requesting a patch to the yealink module to fix an error
like usb_submit_urb failed -2 when used with a K2B box.
More info: http://marc.info/?l=linux-usbm=121482783614488w=2
Many thanks
Marcel
/
diff --git a/drivers/input/misc/yealink.c b/drivers/input/misc/yealink.c
index 46279ef..facefd3 100644
--- a/drivers/input/misc/yealink.c
+++ b/drivers/input/misc/yealink.c
@@ -119,6 +119,8 @@ struct yealink_dev {
u8 lcdMap[ARRAY_SIZE(lcdMap)]; /* state of LCD, LED ... */
int key_code; /* last reported key*/
+ unsigned int shutdown:1;
+
int stat_ix;
union {
struct yld_status s;
@@ -424,10 +426,10 @@ send_update:
static void urb_irq_callback(struct urb *urb)
{
struct yealink_dev *yld = urb-context;
- int ret;
+ int ret, status = urb-status;
- if (urb-status)
- err(%s - urb status %d, __FUNCTION__, urb-status);
+ if (status)
+ err(%s - urb status %d, __func__, status);
switch (yld-irq_data-cmd) {
case CMD_KEYPRESS:
@@ -447,33 +449,38 @@ static void urb_irq_callback(struct urb *urb)
yealink_do_idle_tasks(yld);
- ret = usb_submit_urb(yld-urb_ctl, GFP_ATOMIC);
- if (ret)
- err(%s - usb_submit_urb failed %d, __FUNCTION__, ret);
+ if (!yld-shutdown) {
+ ret = usb_submit_urb(yld-urb_ctl, GFP_ATOMIC);
+ if (ret ret != -EPERM)
+ err(%s - usb_submit_urb failed %d, __func__, ret);
+ }
}
static void urb_ctl_callback(struct urb *urb)
{
struct yealink_dev *yld = urb-context;
- int ret;
+ int ret = 0, status = urb-status;
- if (urb-status)
- err(%s - urb status %d, __FUNCTION__, urb-status);
+ if (status)
+ err(%s - urb status %d, __func__, status);
switch (yld-ctl_data-cmd) {
case CMD_KEYPRESS:
case CMD_SCANCODE:
/* ask for a response */
- ret = usb_submit_urb(yld-urb_irq, GFP_ATOMIC);
+ if (!yld-shutdown)
+ ret = usb_submit_urb(yld-urb_irq, GFP_ATOMIC);
break;
default:
/* send new command */
yealink_do_idle_tasks(yld);
- ret = usb_submit_urb(yld-urb_ctl, GFP_ATOMIC);
+ if (!yld-shutdown)
+ ret = usb_submit_urb(yld-urb_ctl, GFP_ATOMIC);
+ break;
}
- if (ret)
- err(%s - usb_submit_urb failed %d, __FUNCTION__, ret);
+ if (ret ret != -EPERM)
+ err(%s - usb_submit_urb failed %d, __func__, ret);
}
/***
@@ -505,7 +512,7 @@ static int input_open(struct input_dev *dev)
struct yealink_dev *yld = input_get_drvdata(dev);
int i, ret;
- dbg(%s, __FUNCTION__);
+ dbg(%s, __func__);
/* force updates to device */
for (i = 0; isizeof(yld-master); i++)
@@ -521,7 +528,7 @@ static int input_open(struct input_dev *dev)
yld-ctl_data-sum = 0x100-CMD_INIT-10;
if ((ret = usb_submit_urb(yld-urb_ctl, GFP_KERNEL)) != 0) {
dbg(%s - usb_submit_urb failed with result %d,
- __FUNCTION__, ret);
+ __func__, ret);
return ret;
}
return 0;
@@ -531,8 +538,18 @@ static void input_close(struct input_dev *dev)
{
struct yealink_dev *yld = input_get_drvdata(dev);
+ yld-shutdown = 1;
+ /*
+* Make sure the flag is seen by other CPUs before we start
+* killing URBs so new URBs won't be submitted
+*/
+ smp_wmb();
+
usb_kill_urb(yld-urb_ctl);
usb_kill_urb(yld-urb_irq);
+
+ yld-shutdown = 0;
+ smp_wmb();
}
/***
@@ -809,9 +826,6 @@ static int usb_cleanup(struct yealink_dev *yld, int err)
if (yld == NULL)
return err;
- usb_kill_urb(yld-urb_irq); /* parameter validation in core/urb
Bug#559035: marked as done (linux-image-2.6.26-2-xen-amd64: Random segfaults with lenny amd64 kernel)
Your message dated Thu, 11 Mar 2010 19:57:15 + with message-id e1npovp-00085o...@ries.debian.org and subject line Bug#559035: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #559035, regarding linux-image-2.6.26-2-xen-amd64: Random segfaults with lenny amd64 kernel 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.) -- 559035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-xen-amd64 Version: 2.6.26-19lenny2 Severity: normal After upgrading machines to a lenny kernel (2.6.26-2-amd64 and 2.6.26-2-xen-amd64 variants) exim4 and python2.5 (while runing xm list) started segfaulting randomly every few days. Switching to an older (2.6.18) or newer kernel (2.6.30) seems to stop the segfaults. Could this be a bug in 2.6.26 kernel? [1795253.833144] python[21737] general protection ip:7fff71e45ef0 sp:7fff7212a2a0 error:0 in libc-2.7.so[7fff71dd5000+14a000] [1795253.849015] python/21737: potentially unexpected fatal signal 11. [1795253.857992] [1795253.859855] CPU 2: [1795253.862371] Modules linked in: xt_physdev ipmi_devintf sha1_generic drbd cn ipt_REJECT xt_tcpudp xt_multiport nf_conntrack_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables ipv6 bridge bonding 8021q loop ipmi_si psmouse ipmi_msghandler hpilo pcspkr serio_raw rng_core container button shpchp i5000_edac pci_hotplug edac_core evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod ide_cd_mod cdrom ata_generic libata dock piix usbhid hid ff_memless ide_pci_generic bnx2 uhci_hcd ide_core ehci_hcd firmware_class cciss scsi_mod thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] [1795253.927555] Pid: 21737, comm: python Not tainted 2.6.26-2-xen-amd64 #1 [1795253.936845] RIP: e033:[7fff71e45ef0] [7fff71e45ef0] [1795253.943918] RSP: e02b:7fff7212a2a0 EFLAGS: 00010282 [1795253.952055] RAX: ff04f4004b832140 RBX: 018b0520 RCX: 7fff721241b0 [1795253.960764] RDX: RSI: 7fff71e45c60 RDI: 7fff7212a2a0 [1795253.969370] RBP: 6e726574 R08: 018b49d0 R09: 7fff72cbec18 [1795253.977782] R10: 09070935092b0933 R11: 0044c3f0 R12: 7fff72c0dc60 [1795253.987324] R13: 7fff7212a320 R14: 7fff7212b390 R15: 496144d9 [1795253.997788] FS: 7fff72ccb6e0() GS:8053a100() knlGS: [1795254.007295] CS: e033 DS: ES: [1795254.011771] DR0: DR1: DR2: [1795254.020183] DR3: DR6: 0ff0 DR7: 0400 [1795254.028675] [1795254.028676] Call Trace: [1795254.033439] [1806430.409988] python[21591]: segfault at 7fff1891feb8 ip 4ae07b sp 7fff1891fec0 error 6 in python2.5[40+125000] [1806430.423289] python/21591: potentially unexpected fatal signal 11. [1806430.432669] [1806430.434555] CPU 6: [1806430.437108] Modules linked in: xt_physdev ipmi_devintf sha1_generic drbd cn ipt_REJECT xt_tcpudp xt_multiport nf_conntrack_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables ipv6 bridge bonding 8021q loop ipmi_si psmouse ipmi_msghandler hpilo pcspkr serio_raw rng_core container button shpchp i5000_edac pci_hotplug edac_core evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod ide_cd_mod cdrom ata_generic libata dock piix usbhid hid ff_memless ide_pci_generic bnx2 uhci_hcd ide_core ehci_hcd firmware_class cciss scsi_mod thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] [1806430.501555] Pid: 21591, comm: python Not tainted 2.6.26-2-xen-amd64 #1 [1806430.507219] RIP: e033:[004ae07b] [004ae07b] [1806430.518525] RSP: e02b:7fff1891fec0 EFLAGS: 00010206 [1806430.525038] RAX: 496144d9 RBX: 0023 RCX: 0061 [1806430.534938] RDX: 496144d9 RSI: 0049 RDI: 00e76230 [1806430.543730] RBP: 00e76230 R08: R09: 00e76310 [1806430.551969] R10: 7fff18faa6e0 R11: R12: 00e76230 [1806430.560422] R13: 7fff18923fa0 R14: 7fff18923ec0 R15: 496144d9 [1806430.568935] FS: 7fff18faa6e0() GS:8053a300() knlGS: [1806430.578950] CS: e033 DS: ES: [1806430.584247] DR0: DR1: DR2: [1806430.595820] DR3: DR6: 0ff0 DR7: 0400 [1806430.604144] [1806430.604145] Call Trace: [1806430.608612] [1816999.691072] python[17816]
Bug#565353: marked as done (linux-2.6: Update bnx2 PCI IDs)
Your message dated Thu, 11 Mar 2010 19:57:16 +
with message-id e1npovq-00086d...@ries.debian.org
and subject line Bug#565353: fixed in linux-2.6 2.6.26-22
has caused the Debian Bug report #565353,
regarding linux-2.6: Update bnx2 PCI IDs
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.)
--
565353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6.26-2-amd64
Severity: important
Tags: patch, lenny
Version: 2.6.26-2
Hi,
The BCM5716 network chipset from Broadcom works perfectly well with the bnx2
driver in 2.6.26 (including the existing firmware), but it has an
unrecognised PCI ID, so the kernel doesn't detect it.
The attached patch adds the relevant PCI ID. We've built patched kernels
locally and verified that it works OK on a Dell PowerEdge R410.
Thanks,
- Matt
diff -urpN linux-source-2.6.26.orig/drivers/net/bnx2.c linux-source-2.6.26/drivers/net/bnx2.c
--- linux-source-2.6.26.orig/drivers/net/bnx2.c 2008-07-13 21:51:29.0 +
+++ linux-source-2.6.26/drivers/net/bnx2.c 2010-01-14 01:54:09.0 +
@@ -56,7 +56,7 @@
#define DRV_MODULE_NAME bnx2
#define PFX DRV_MODULE_NAME :
-#define DRV_MODULE_VERSION 1.7.5
+#define DRV_MODULE_VERSION 1.7.5-1
#define DRV_MODULE_RELDATE April 29, 2008
#define FW_FILE_06 bnx2-06-4.0.5.fw
#define FW_FILE_09 bnx2-09-4.0.5.fw
@@ -87,6 +87,7 @@ typedef enum {
BCM5708S,
BCM5709,
BCM5709S,
+ BCM5716,
} board_t;
/* indexed by board_t, above */
@@ -102,6 +103,7 @@ static struct {
{ Broadcom NetXtreme II BCM5708 1000Base-SX },
{ Broadcom NetXtreme II BCM5709 1000Base-T },
{ Broadcom NetXtreme II BCM5709 1000Base-SX },
+ { Broadcom NetXtreme II BCM5716 1000Base-T },
};
static struct pci_device_id bnx2_pci_tbl[] = {
@@ -123,6 +125,8 @@ static struct pci_device_id bnx2_pci_tbl
PCI_ANY_ID, PCI_ANY_ID, 0, 0, BCM5709 },
{ PCI_VENDOR_ID_BROADCOM, PCI_DEVICE_ID_NX2_5709S,
PCI_ANY_ID, PCI_ANY_ID, 0, 0, BCM5709S },
+ { PCI_VENDOR_ID_BROADCOM, PCI_DEVICE_ID_NX2_5716,
+ PCI_ANY_ID, PCI_ANY_ID, 0, 0, BCM5716 },
{ 0, }
};
diff -urpN linux-source-2.6.26.orig/include/linux/pci_ids.h linux-source-2.6.26/include/linux/pci_ids.h
--- linux-source-2.6.26.orig/include/linux/pci_ids.h 2008-07-13 21:51:29.0 +
+++ linux-source-2.6.26/include/linux/pci_ids.h 2010-01-14 01:55:44.0 +
@@ -1940,6 +1940,7 @@
#define PCI_DEVICE_ID_TIGON3_5752M 0x1601
#define PCI_DEVICE_ID_NX2_5709 0x1639
#define PCI_DEVICE_ID_NX2_5709S 0x163a
+#define PCI_DEVICE_ID_NX2_5716 0x163b
#define PCI_DEVICE_ID_TIGON3_5700 0x1644
#define PCI_DEVICE_ID_TIGON3_5701 0x1645
#define PCI_DEVICE_ID_TIGON3_5702 0x1646
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.26-22
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:
linux-2.6_2.6.26-22.diff.gz
to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz
linux-2.6_2.6.26-22.dsc
to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc
linux-doc-2.6.26_2.6.26-22_all.deb
to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb
linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb
linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb
Bug#547183: marked as done (Please upgrade the 'megaraid_sas' module to version 00.00.03.21)
Your message dated Thu, 11 Mar 2010 19:57:15 + with message-id e1npovp-00085g...@ries.debian.org and subject line Bug#547183: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #547183, regarding Please upgrade the 'megaraid_sas' module to version 00.00.03.21 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.) -- 547183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26.2-amd64 Version: 2.6.26-19 Severity: minor I use Debian Lenny amd64 on Dell PowerEdge R610 servers. When I use Dell's OpenManage tool to query the storage subsystem's status, I get the following output : my-server:~# omreport storage controller Controller PERC 6/i Integrated (Embedded) Controllers ID: 0 Status: Non-Critical Name : PERC 6/i Integrated Slot ID : Embedded State : Degraded Firmware Version : 6.2.0-0013 Minimum Required Firmware Version : Not Applicable Driver Version: 00.00.03.20-rc1 Minimum Required Driver Version : 00.00.03.21 Number of Connectors : 2 Rebuild Rate : 30% BGI Rate : 30% Check Consistency Rate: 30% Reconstruct Rate : 30% Alarm State : Not Applicable Cluster Mode : Not Applicable SCSI Initiator ID : Not Applicable Cache Memory Size : 256 MB Patrol Read Mode : Auto Patrol Read State : Stopped Patrol Read Rate : 30% Patrol Read Iterations: 6 Abort check consistency on error : Disabled Allow Revertible Hot Spare and Replace Member : Enabled Auto replace member on predictive failure : Disabled Load balance : Auto Note : the omreport program is found in the contributed Debian package built for Dell's OpenManage tools ; these packages can be found at this Deb repository : http://ftp.sara.nl/pub/sara-omsa/ (in my situation, I use OMSA v6 for amd64). As you can see above, the tool reports my RAID SAS controller runs in degraded mode, while the same controller, when queried in the Dell R610 BIOS interface, says everything is OK. And, as you can also see above, the reason for this false alarm is probably the version of the driver (megaraid_sas) which is 00.00.03.20-rc1, whereas the OpenManage tool expects at least version 00.00.03.21. So, it would be nice to upgrade the version of the 'megaraid_sas' module embedded in Lenny's kernel image, as it would probably correct this (benign) bug, and thus allow Dell PE R610 users to get the correct status for their PERC 6/i controller without having to shutdown their system and consult the BIOS interface. Note : I have filed this bug for package 'linux-image-2.6.26.2-amd64' as I use my servers in 64-bit mode, but the same version upgrade would certainly benefit other Linux image packages as well (especially the i386/i686 kernel images, for people using the same R610 servers in 32-bit mode)... Thanks in advance. ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-22 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: linux-2.6_2.6.26-22.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz linux-2.6_2.6.26-22.dsc to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc linux-doc-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb to
Bug#479652: marked as done (linux-image-2.6.24-1-686: xorg problem with 2.6.24/25)
Your message dated Thu, 11 Mar 2010 19:57:15 +
with message-id e1npovp-00084p...@ries.debian.org
and subject line Bug#479652: fixed in linux-2.6 2.6.26-22
has caused the Debian Bug report #479652,
regarding linux-image-2.6.24-1-686: xorg problem with 2.6.24/25
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.)
--
479652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.24-1-686
Version: 2.6.24-6
Severity: important
Hi
I have Athlon XP on Gigabyte GA-7ZX MB and Matrox MGA450.
I have no problems running linux-image-2.6.22-3-k7
With newest 2.6.2{4,5}-1-686 can't start xserver in proper
frequency range.
I've tested with:
- fresh xorg.conf - CRT monitor switches off
- my old xorg.conf - 48 Hz vertical (where 2.6.22 gives 75 Hz)
diff of Xorg.0.logs 2.6.22 v 2.6.24 gives only (with my conf):
313c313
(II) MGA(0): I2C Monitor info: 0x8214a78
---
(II) MGA(0): I2C Monitor info: 0x8214a70
690,691c690,691
(II) MGA(0): [drm] added 8192 byte SAREA at 0xfac4a000
(II) MGA(0): [drm] mapped SAREA 0xfac4a000 to 0xb7cc4000
---
(II) MGA(0): [drm] added 8192 byte SAREA at 0xf8bef000
(II) MGA(0): [drm] mapped SAREA 0xf8bef000 to 0xb7bee000
Mirek
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (991, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-1-686 (SMP w/1 CPU core)
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) (ignored: LC_ALL set to
pl_PL)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.24-1-686 depends on:
ii debconf [debconf-2.0] 1.5.21 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92a tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.24-1-686 recommends:
ii libc6-i6862.7-10 GNU C Library: Shared libraries [i
-- debconf information:
linux-image-2.6.24-1-686/preinst/overwriting-modules-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/bootloader-error-2.6.24-1-686:
linux-image-2.6.24-1-686/postinst/create-kimage-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/prerm/would-invalidate-boot-loader-2.6.24-1-686: true
linux-image-2.6.24-1-686/preinst/initrd-2.6.24-1-686:
linux-image-2.6.24-1-686/preinst/lilo-has-ramdisk:
linux-image-2.6.24-1-686/preinst/abort-install-2.6.24-1-686:
linux-image-2.6.24-1-686/prerm/removing-running-kernel-2.6.24-1-686: true
linux-image-2.6.24-1-686/preinst/abort-overwrite-2.6.24-1-686:
linux-image-2.6.24-1-686/postinst/bootloader-test-error-2.6.24-1-686:
linux-image-2.6.24-1-686/preinst/lilo-initrd-2.6.24-1-686: true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.24-1-686/postinst/old-system-map-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/preinst/failed-to-move-modules-2.6.24-1-686:
linux-image-2.6.24-1-686/postinst/depmod-error-initrd-2.6.24-1-686: false
linux-image-2.6.24-1-686/preinst/bootloader-initrd-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/old-initrd-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/old-dir-initrd-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/depmod-error-2.6.24-1-686: false
linux-image-2.6.24-1-686/preinst/elilo-initrd-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/kimage-is-a-directory:
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.26-22
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:
linux-2.6_2.6.26-22.diff.gz
to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz
linux-2.6_2.6.26-22.dsc
to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc
linux-doc-2.6.26_2.6.26-22_all.deb
to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb
linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb
to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb
linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb
to
Bug#524542: marked as done (Patches to fix bugs related to TSC clocksource on VMware)
Your message dated Thu, 11 Mar 2010 19:57:15 + with message-id e1npovp-00085p...@ries.debian.org and subject line Bug#524542: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #524542, regarding Patches to fix bugs related to TSC clocksource on VMware 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.) -- 524542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.26-13 This is regarding some patches which improve timekeeping for Linux when running under VMware. Without these patches we may see incorrect timekeeping with Debian's lenny kernel when running as guest under VMware. VMware hypervisor exports a consistent TSC to the guest for timekeeping purposes, but still due to some kernel assumptions which don't hold true in virtualization environments, the kernel can mark the TSC unstable and hence unusable for timekeeping purposes. Without these patches TSC cannot be used as a reliable clocksource under VMware. The problems with TSC assumptions in the kernel are as follows. 1) TSC calibration : TSC calibration maybe error prone in virtualized environment, and since an error in TSC frequency may accumulate during the kernels runtime, its important to keep the error to the minimum. The best way to get the TSC frequency is to ask the hypervisor for that. 2) With the NO-HZ kernel, there is no guarantee that the acpi_pm timer will be sampled at least every 4.68 seconds (the wrap interval), because the vcpu, in extreme circumstances, may not have a chance to run in that time. Thus, the acpi_pm timer is not suitable to be used as a clocksource watchdog when running on a hypervisor. 3) Virtual TSCs can be kept nearly in sync, but because the virtual TSC offset is set by software, it's not perfect. So, the TSC synchronization test at bootup can fail. (Really, it can fail on native as well, and that's why the tests for backwards TSC were added to read_tsc()/vread_tsc()). We need a way to skip this check when on VMware. These patches add some VMware detection code which we use to get around these TSC assumptions which fail under VMware's hypervisor. Please note that these patches are not VMI ( paravirt) specific, and change the default kernel for 32 and 64bit, but the modifications come into affect only when we are running under VMware. Just the init and detection code is run for native case. This will also change the kABI, as it adds a field to the cpuinfo_x86 structure. The mainline commit id's are commit b2bcc7b299f37037b4a78dc1538e5d6508ae8110 x86: add a synthetic TSC_RELIABLE feature bit commit 49ab56ac6e1b907b7dadb72a4012460359feaf0e x86: add X86_FEATURE_HYPERVISOR feature bit commit 88b094fb8d4fe43b7025ea8d487059e8813e02cd x86: Hypervisor detection and get tsc_freq from hypervisor commit eca0cd028bdf0f6aaceb0d023e9c7501079a7dda x86: Add a synthetic TSC_RELIABLE feature bit. commit 395628ef4ea12ff0748099f145363b5e33c69acb x86: Skip verification by the watchdog for TSC clocksource. commit 6bdbfe99916398dbb28d83833cc04757110f2738 x86: VMware: Fix vmware_get_tsc code commit fd8cd7e1919fc1c27fe2fdccd2a1cd32f791ef0f x86: vmware: look for DMI string in the product serial key These patches have been included in the Ubuntu intrepid kernel as well which is 2.6.27, so if its easier you may cherry pick those patches from that tree. The only reason it might be easier is because IMO it would require less or no effort to backport it to Lenny from Intrepid rather than from mainline where these patches were applied in the 2.6.29 cycle. Thanks, Alok ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-22 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: linux-2.6_2.6.26-22.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz linux-2.6_2.6.26-22.dsc to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc linux-doc-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb to
Bug#562892: marked as done (linux-2.6: cfq-related oops)
Your message dated Thu, 11 Mar 2010 19:57:16 +
with message-id e1npovq-000868...@ries.debian.org
and subject line Bug#562892: fixed in linux-2.6 2.6.26-22
has caused the Debian Bug report #562892,
regarding linux-2.6: cfq-related oops
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.)
--
562892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.26-21
Severity: important
Tags: patch
Oops happens while doing preparation for vzt-ss test
(just creating/starting
VEs, with continuous ps axf running in background if it matters):
http://bugzilla.openvz.org/show_bug.cgi?id=1240
From 1a6d795abc130bd356b10abbd91ef63ef23f01c4 Mon Sep 17 00:00:00 2001
From: Konstantin Khlebnikov khlebni...@openvz.org
Date: Thu, 24 Dec 2009 20:58:15 +0300
Subject: [PATCH 88/90] cfq: unlink queues at bc destroy
Unlink cfq-queues from cfq-io-contexts at cfq-bc-data destroy and
always revalidate cached cfq-queues from cfq-io-context.
Should fix pdflush oops in cfq_set_request after container stop.
http://bugzilla.openvz.org/show_bug.cgi?id=1240
Signed-off-by: Konstantin Khlebnikov khlebni...@openvz.org
Signed-off-by: Pavel Emelyanov xe...@openvz.org
---
block/cfq-iosched.c | 20 +---
kernel/bc/io_prio.c | 11 +++
2 files changed, 16 insertions(+), 15 deletions(-)
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
index b25b442..3a9992a 100644
--- a/block/cfq-iosched.c
+++ b/block/cfq-iosched.c
@@ -2014,32 +2014,22 @@ cfq_set_request(struct request_queue *q, struct request
*rq, gfp_t gfp_mask)
struct cfq_queue *cfqq;
unsigned long flags;
struct ub_iopriv *iopriv;
- struct cfq_bc_data *cfq_bc = NULL;
might_sleep_if(gfp_mask __GFP_WAIT);
cic = cfq_get_io_context(cfqd, gfp_mask);
iopriv = cfqq_ub_iopriv(cfqd, is_sync);
- if (!is_sync)
- cfq_bc = bc_findcreate_cfq_bc(iopriv, cfqd, gfp_mask);
spin_lock_irqsave(q-queue_lock, flags);
- if (!cic || (!is_sync cfq_bc == NULL))
+ if (!cic)
goto queue_fail;
cfqq = cic_to_cfqq(cic, is_sync);
- if (!cfqq) {
- cfqq = cfq_get_queue(cfqd, is_sync, cic-ioc, gfp_mask);
-
- if (!cfqq)
- goto queue_fail;
-
- cic_set_cfqq(cic, cfqq, is_sync);
- }
-
- if (!is_sync cfqq-cfq_bc != cfq_bc) {
- cfq_put_queue(cfqq);
+ if (!cfqq || cfqq-cfq_bc-ub_iopriv != iopriv) {
+ if (cfqq)
+ cfq_put_queue(cfqq);
+ cic_set_cfqq(cic, NULL, is_sync);
cfqq = cfq_get_queue(cfqd, is_sync, cic-ioc, gfp_mask);
cic_set_cfqq(cic, cfqq, is_sync);
if (!cfqq)
diff --git a/kernel/bc/io_prio.c b/kernel/bc/io_prio.c
index 5bb22e5..4a1ee2e 100644
--- a/kernel/bc/io_prio.c
+++ b/kernel/bc/io_prio.c
@@ -88,6 +88,7 @@ static void inline bc_cfq_bc_check_empty(struct cfq_bc_data
*cfq_bc)
static void bc_release_cfq_bc(struct cfq_bc_data *cfq_bc)
{
+ struct cfq_io_context *cic;
struct cfq_data *cfqd;
elevator_t *eq;
int i;
@@ -109,6 +110,16 @@ static void bc_release_cfq_bc(struct cfq_bc_data *cfq_bc)
eq-ops-put_queue(cfq_bc-async_idle_cfqq);
cfq_bc-async_idle_cfqq = NULL;
}
+ list_for_each_entry(cic, cfqd-cic_list, queue_list) {
+ if (cic-cfqq[0] cic-cfqq[0]-cfq_bc == cfq_bc) {
+ eq-ops-put_queue(cic-cfqq[0]);
+ cic-cfqq[0] = NULL;
+ }
+ if (cic-cfqq[1] cic-cfqq[1]-cfq_bc == cfq_bc) {
+ eq-ops-put_queue(cic-cfqq[1]);
+ cic-cfqq[1] = NULL;
+ }
+ }
/*
* Note: this cfq_bc is already not in active list,
* but can be still pointed from cfqd as active.
--
1.6.5.7
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-2-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/bash
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.26-22
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:
linux-2.6_2.6.26-22.diff.gz
to
Bug#562694: marked as done (Does not have atl1c driver needed by many netbooks)
Your message dated Thu, 11 Mar 2010 19:57:15 + with message-id e1npovp-00085t...@ries.debian.org and subject line Bug#562694: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #562694, regarding Does not have atl1c driver needed by many netbooks 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.) -- 562694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.26-21 Severity: important The atl1c driver was introduced in Linux 2.6.29. It supports the Atheros AR8131 and AR8132 Ethernet controllers used in many netbooks. I will investigate whether it can be backported. Ben. -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable'), (100, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-22 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: linux-2.6_2.6.26-22.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz linux-2.6_2.6.26-22.dsc to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc linux-doc-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-libc-dev_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.26-22_amd64.deb linux-manual-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-22_all.deb linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-patch-debian-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-22_all.deb linux-source-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-source-2.6.26_2.6.26-22_all.deb linux-support-2.6.26-2_2.6.26-22_all.deb to main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-22_all.deb linux-tree-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-tree-2.6.26_2.6.26-22_all.deb xen-linux-system-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/xen-linux-system-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 562...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with
Bug#568345: marked as done (Potential stability issues in megaraid_sas)
Your message dated Thu, 11 Mar 2010 19:57:16 + with message-id e1npovq-00086s...@ries.debian.org and subject line Bug#568345: fixed in linux-2.6 2.6.26-22 has caused the Debian Bug report #568345, regarding Potential stability issues in megaraid_sas 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.) -- 568345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.26-21 Severity: important Tags: patch fixed-upstream The following bug fixes were made upstream in 2.6.27 but have not been applied in lenny: commit 06f579dee5dd75c2aaf8fe83d034b54702f4 Author: Yang, Bo bo.y...@lsi.com Date: Sun Aug 10 12:42:37 2008 -0700 [SCSI] megaraid_sas: add readl to force PCI posting flush MegaRAID SAS Driver get unexpected Interrupt. Add the dummy readl to force PCI flush will fix this issue. commit 530e6fc1e05f14762aea954ca8d6422c5a7077c1 Author: Yang, Bo bo.y...@lsi.com Date: Sun Aug 10 12:42:37 2008 -0700 [SCSI] megaraid_sas: add the shutdown DCMD cmd to driver shutdown routine Add the shutdown DCMD cmd to driver shutdown routine to make megaraid sas FW shutdown proper. I believe these are suitable for a stable update. 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-1-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 ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-22 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: linux-2.6_2.6.26-22.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-22.diff.gz linux-2.6_2.6.26-22.dsc to main/l/linux-2.6/linux-2.6_2.6.26-22.dsc linux-doc-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-22_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-22_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-22_amd64.deb linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-22_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-amd64_2.6.26-22_amd64.deb linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-libc-dev_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.26-22_amd64.deb linux-manual-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-22_all.deb linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb to main/l/linux-2.6/linux-modules-2.6.26-2-xen-amd64_2.6.26-22_amd64.deb linux-patch-debian-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-22_all.deb linux-source-2.6.26_2.6.26-22_all.deb to main/l/linux-2.6/linux-source-2.6.26_2.6.26-22_all.deb linux-support-2.6.26-2_2.6.26-22_all.deb to main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-22_all.deb linux-tree-2.6.26_2.6.26-22_all.deb to
Bug#573483: linux-kbuild-2.6: please upload 2.6.33 to experimental
Package: linux-kbuild-2.6 Severity: normal Hi, please build a new version of linux-kbuild-2.6 for 2.6.33 and upload it to experimental to accompany the 2.6.33 kernel there. That way we can build kernel modules for 2.6.33 and give the new kernel more testing. Thanks. Andreas -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (800, 'stable'), (700, 'testing'), (600, 'unstable'), (130, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311194734.20522.96242.report...@chili.ae.cs.uni-frankfurt.de
Re: openvz kernel for debian squeeze
On Thu, 11 Mar 2010, Pavel Emelyanov wrote:
This was fixed this morning :) As long as two beancounters leaks.
Please update.
cool, indeed fixed, but needed belows fix too:
From 318d047e844100dff4f7525d6090cbd81b54aa90 Mon Sep 17 00:00:00 2001
From: maximilian attems m...@stro.at
Date: Thu, 11 Mar 2010 20:44:18 +0100
Subject: [PATCH] memory failure: fix up openvz compilation
due to 801183f17814b0f99fa907ca73c7908d623e3beb
s/for_each_process/for_each_process_all/
Signed-off-by: maximilian attems m...@stro.at
---
mm/memory-failure.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/memory-failure.c b/mm/memory-failure.c
index dacc641..9d28f5c 100644
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
@@ -226,7 +226,7 @@ static void collect_procs_anon(struct page *page, struct
list_head *to_kill,
av = page_lock_anon_vma(page);
if (av == NULL) /* Not actually mapped anymore */
goto out;
- for_each_process (tsk) {
+ for_each_process_all (tsk) {
if (!task_early_kill(tsk))
continue;
list_for_each_entry (vma, av-head, anon_vma_node) {
@@ -263,7 +263,7 @@ static void collect_procs_file(struct page *page, struct
list_head *to_kill,
read_lock(tasklist_lock);
spin_lock(mapping-i_mmap_lock);
- for_each_process(tsk) {
+ for_each_process_all(tsk) {
pgoff_t pgoff = page-index (PAGE_CACHE_SHIFT - PAGE_SHIFT);
if (!task_early_kill(tsk))
--
1.7.0
also there seem to be an interference with CGROUP_FREEZER,
getting this:
kernel/built-in.o: In function `update_freezer_state':
cgroup_freezer.c:(.text+0x521f3): undefined reference to `cgroup_iter_start'
cgroup_freezer.c:(.text+0x5222e): undefined reference to `cgroup_iter_next'
cgroup_freezer.c:(.text+0x5225b): undefined reference to `cgroup_iter_end'
kernel/built-in.o: In function `freezer_write':
cgroup_freezer.c:(.text+0x52300): undefined reference to `cgroup_iter_start'
cgroup_freezer.c:(.text+0x52312): undefined reference to `cgroup_iter_next'
cgroup_freezer.c:(.text+0x52325): undefined reference to `cgroup_iter_end'
cgroup_freezer.c:(.text+0x52345): undefined reference to `cgroup_iter_start'
cgroup_freezer.c:(.text+0x523a9): undefined reference to `cgroup_iter_next'
cgroup_freezer.c:(.text+0x523c1): undefined reference to `cgroup_iter_end'
make[5]: *** [.tmp_vmlinux1] Error 1
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100311200406.ga21...@baikonur.stro.at
Bug#573490: drbd fails to load: drbd: disagrees about version of symbol cn_add_callback
Package: linux-2.6 Version: 2.6.26-21lenny4 Severity: critical drbd fails to load and there goes my failover high available cluster... *t -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-21lenny4) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Tue Mar 9 17:35:51 UTC 2010 ** Command line: root=/dev/sda6 ro console=tty0 console=ttyS0,115200n8 ** Not tainted ** Kernel log: [3.637885] hub 4-0:1.0: USB hub found [3.637895] hub 4-0:1.0: 6 ports detected [3.693311] megaraid: fw version:[516A] bios version:[H418] [3.710308] hub 2-0:1.0: unable to enumerate USB device on port 1 [3.714272] scsi0 : LSI Logic MegaRAID driver [3.721905] scsi[0]: scanning scsi channel 0 [Phy 0] for non-raid devices [3.761772] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002 [3.765777] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [3.774055] usb usb4: Product: EHCI Host Controller [3.781775] usb usb4: Manufacturer: Linux 2.6.26-2-686 ehci_hcd [3.787796] usb usb4: SerialNumber: :00:1d.7 [3.798388] ICH5: IDE controller (0x8086:0x24db rev 0x02) at PCI slot :00:1f.1 [3.805361] PIIX_IDE :00:1f.1: enabling device (0005 - 0007) [3.813349] ACPI: Unable to derive IRQ for device :00:1f.1 [3.819257] ICH5: not 100% native mode: will probe irqs later [3.825442] ide0: BM-DMA at 0xfc00-0xfc07 [3.827731] ide1: BM-DMA at 0xfc08-0xfc0f [3.832153] Probing IDE interface ide0... [4.002933] usb 4-3: new high speed USB device using ehci_hcd and address 2 [4.157565] usb 4-3: configuration #1 chosen from 1 choice [4.166602] hub 4-3:1.0: USB hub found [4.173569] hub 4-3:1.0: 2 ports detected [4.257100] hda: SAMSUNG CD-ROM SN-124, ATAPI CD/DVD-ROM drive [4.279943] usb 4-3: New USB device found, idVendor=413c, idProduct=a001 [4.285574] usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [4.811642] scsi 0:0:6:0: Processor PE/PV1x2 SCSI BP 1.0 PQ: 0 ANSI: 2 [5.129518] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [5.129665] hda: UDMA/33 mode selected [5.137469] Probing IDE interface ide1... [5.770029] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [5.778425] ide1 at 0x170-0x177,0x376 on irq 15 [6.042916] No dock devices found. [6.061215] libata version 3.00 loaded. [6.083004] hda: ATAPI 24X CD-ROM drive, 128kB Cache [6.088253] Uniform CD-ROM driver Revision: 3.20 [6.155945] scsi: waiting for bus probes to complete ... [7.460859] scsi[0]: scanning scsi channel 1 [virtual] for logical drives [7.464859] scsi 0:1:0:0: Direct-Access MegaRAID LD 0 RAID1 69G 516A PQ: 0 ANSI: 2 [7.500860] scsi 0:0:6:0: Attached scsi generic sg0 type 3 [7.504688] scsi 0:1:0:0: Attached scsi generic sg1 type 0 [7.521520] Driver 'sd' needs updating - please use bus_type methods [7.525518] sd 0:1:0:0: [sda] 143114240 512-byte hardware sectors (73274 MB) [7.533568] sd 0:1:0:0: [sda] Write Protect is off [7.540143] sd 0:1:0:0: [sda] Mode Sense: 00 00 00 00 [7.540180] sd 0:1:0:0: [sda] Asking for cache data failed [7.545523] sd 0:1:0:0: [sda] Assuming drive cache: write through [7.549519] sd 0:1:0:0: [sda] 143114240 512-byte hardware sectors (73274 MB) [7.557566] sd 0:1:0:0: [sda] Write Protect is off [7.562414] sd 0:1:0:0: [sda] Mode Sense: 00 00 00 00 [7.562441] sd 0:1:0:0: [sda] Asking for cache data failed [7.569398] sd 0:1:0:0: [sda] Assuming drive cache: write through [7.574970] sda: sda1 sda2 sda5 sda6 sda7 sda8 sda9 sda10 [7.618048] sd 0:1:0:0: [sda] Attached SCSI disk [7.873149] PM: Starting manual resume from disk [7.898278] kjournald starting. Commit interval 5 seconds [7.901106] EXT3-fs: mounted filesystem with ordered data mode. [9.041328] udevd version 125 started [9.416597] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [9.776070] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [9.784247] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [9.880420] input: Power Button (FF) as /class/input/input0 [9.896414] ACPI: Power Button (FF) [PWRF] [9.940220] EDAC MC: Ver: 2.1.0 Mar 9 2010 [ 10.000495] Contact your BIOS vendor to see if the E752x error registers can be safely un-hidden [ 10.638351] ACPI Exception (video-1631): AE_NOT_FOUND, Evaluating _DOD [20080321] [ 10.647586] input: Video Bus as /class/input/input1 [ 10.699347] ACPI: Video Device [EVGA] (multi-head: no rom: yes post: no) [ 10.840751] input: PC Speaker as /class/input/input2 [ 11.058215] Error: Driver 'pcspkr' is already registered, aborting... [ 11.149292] intel_rng: FWH not detected [ 11.847190] Adding 1951856k swap on /dev/sda5. Priority:-1 extents:1 across:1951856k [ 12.002662] EXT3 FS on sda6, internal journal [ 13.476334]
Processed: severity of 573490 is important
Processing commands for cont...@bugs.debian.org: severity 573490 important Bug #573490 [linux-2.6] drbd fails to load: drbd: disagrees about version of symbol cn_add_callback Severity set to 'important' from 'critical' thanks 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 Archive: http://lists.debian.org/handler.s.c.126834295117917.transcr...@bugs.debian.org
Bug#570382: more datapoints on vserver start failure
So once again I had to upgrade kernels and I noticed: * that only my -686 kernel based machines failed to start the vservers (guests) correctly. The amd64 machine started them without problems. I see that florian.duf...@inria.fr also has an 686 machine. I'm Cc:ing Dan to see whether that's also the case for him. * on one of the machines the *first* of the vserver actually did start all others not and on the other machine all vservers did not start correctly. So it's not either all vservers fail to start or none. Might a ressource pressure problem? * stopping and starting the vservers one after the other fixed the problem, the vservers started correctly *t -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.00.1003112212200.2...@tpo-laptop
Bug#573490: Link to same bug in Launchpad
See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/494658 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.00.1003112202040.2...@tpo-laptop
Bug#573490: drbd fails to load: drbd: disagrees about version of symbol cn_add_callback
On Thu, Mar 11, 2010 at 09:43:45PM +0100, Tomas Pospisek wrote: Package: linux-2.6 Version: 2.6.26-21lenny4 Severity: critical drbd fails to load and there goes my failover high available cluster... *t well, crap - we ignored that ABI change because google showed only an old/deprecated module as an out-of-tree user, but we obviously missed drbd. We'll work on an update to the drbd modules. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311213823.ga22...@lackof.org
Bug#524542: closed by dann frazier da...@debian.org (Bug#524542: fixed in linux-2.6 2.6.26-22)
Hi Dann, Thanks for including this fix. Can you please let me know when will this kernel update be released ? I see this on the queue for proposed-updates, but no information about the release schedule is forthcoming from this link below. http://release.debian.org/proposed-updates/stable.html Some of our customers are hit by these TSC issues and will like to get a kernel build with the proper fixes for this issue. Thanks, Alok -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1268343721.967.11.ca...@ank32
Re: openvz kernel for debian squeeze
On 03/11/2010 11:04 PM, maximilian attems wrote: On Thu, 11 Mar 2010, Pavel Emelyanov wrote: This was fixed this morning :) As long as two beancounters leaks. Please update. cool, indeed fixed, but needed belows fix too: Appled, thanks! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9967bf.9040...@parallels.com
Re: openvz kernel for debian squeeze
On Fri, 12 Mar 2010, Pavel Emelyanov wrote: On 03/11/2010 11:04 PM, maximilian attems wrote: On Thu, 11 Mar 2010, Pavel Emelyanov wrote: This was fixed this morning :) As long as two beancounters leaks. Please update. cool, indeed fixed, but needed belows fix too: Appled, thanks! thanks, cool. any word on these two issues: a) compile failure due to CGROUP_FREEZER on (it's on in debian topconfig) kernel/built-in.o: In function `update_freezer_state': cgroup_freezer.c:(.text+0x521f3): undefined reference to `cgroup_iter_start' cgroup_freezer.c:(.text+0x5222e): undefined reference to `cgroup_iter_next' cgroup_freezer.c:(.text+0x5225b): undefined reference to `cgroup_iter_end' kernel/built-in.o: In function `freezer_write': cgroup_freezer.c:(.text+0x52300): undefined reference to `cgroup_iter_start' cgroup_freezer.c:(.text+0x52312): undefined reference to `cgroup_iter_next' cgroup_freezer.c:(.text+0x52325): undefined reference to `cgroup_iter_end' cgroup_freezer.c:(.text+0x52345): undefined reference to `cgroup_iter_start' cgroup_freezer.c:(.text+0x523a9): undefined reference to `cgroup_iter_next' cgroup_freezer.c:(.text+0x523c1): undefined reference to `cgroup_iter_end' make[5]: *** [.tmp_vmlinux1] Error 1 b) 2.6.26 legacy setting, is that still relevant? # CONFIG_NF_CONNTRACK_IPV6 is not set -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311222634.ga30...@stro.at
Bug#524542: closed by dann frazier da...@debian.org (Bug#524542: fixed in linux-2.6 2.6.26-22)
On Thu, Mar 11, 2010 at 01:42:01PM -0800, Alok Kataria wrote: Hi Dann, Thanks for including this fix. Can you please let me know when will this kernel update be released ? I see this on the queue for proposed-updates, but no information about the release schedule is forthcoming from this link below. http://release.debian.org/proposed-updates/stable.html Some of our customers are hit by these TSC issues and will like to get a kernel build with the proper fixes for this issue. The 5.0.5 release has not been scheduled, though we aim for a stable point release about every two months. Until then, your customers are welcome to add proposed-updates to their sources.list. Builds for all other architectures should appear over the next several days. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311222103.gb22...@lackof.org
Bug#524542: closed by dann frazier da...@debian.org (Bug#524542: fixed in linux-2.6 2.6.26-22)
hello, On Thu, 11 Mar 2010, Alok Kataria wrote: Thanks for including this fix. Can you please let me know when will this kernel update be released ? I see this on the queue for proposed-updates, but no information about the release schedule is forthcoming from this link below. http://release.debian.org/proposed-updates/stable.html afaik this depends on the stable release managers. Some of our customers are hit by these TSC issues and will like to get a kernel build with the proper fixes for this issue. as quick and easy workaround you can install them or let them install form proposed-updates, see instructions: http://www.es.debian.org/releases/proposed-updates best regards -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311223610.gb30...@stro.at
Processed: Re: Bug#573490: drbd fails to load: drbd: disagrees about version of symbol cn_add_callback
Processing commands for cont...@bugs.debian.org: tags 573490 + patch Bug #573490 [linux-2.6] drbd fails to load: drbd: disagrees about version of symbol cn_add_callback Added tag(s) patch. affects 573490 drbd8-source Bug #573490 [linux-2.6] drbd fails to load: drbd: disagrees about version of symbol cn_add_callback Added indication that 573490 affects drbd8-source thanks 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 Archive: http://lists.debian.org/handler.s.c.126834855112184.transcr...@bugs.debian.org
Bug#542633: Bug#571457: OpenVZ TCP/IP socket write hangs - is this Debian bug 542633 ?
hello, On Wed, 03 Mar 2010, Dr. Andreas =?UTF-8?Q?Kr=C3=BCger ?= wrote: I would like to ask you whether you think the following bug is the same as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542633 openvz: [UBC]: Endless loop in __sk_stream_wait_memory. yes it looks like. I had a reproducible stops working with a Subversion server running on an OpenVZ guest. After some investigation, this turned out to be nothing Subversion-specific. I was able to reproduce with a minimal client / server pair. I have also filed the Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571457 on the same issue, originally against Subversion, now I have reassigned it to the OpenVZ image I have been using. Would you kindly tell me whether this bug is the same as Debian bug 542633 ? Do you think this is Debian specific, or does it also concern OpenVZ upstream? please test the 2.6.26-22 upload to stable proposed uploads, see instructions on how to install http://www.de.debian.org/releases/proposed-updates thanks for feedback on it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311224710.gc30...@stro.at
Processed: severity of 573176 is wishlist
Processing commands for cont...@bugs.debian.org: severity 573176 wishlist Bug #573176 [linux-headers-2.6.33-2-686] linux-headers-2.6.33-2-686: cannot be installed Severity set to 'wishlist' from 'grave' thanks 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 Archive: http://lists.debian.org/handler.s.c.126834825710271.transcr...@bugs.debian.org
Bug#501789: marked as done (linux-image-2.6.26-1-amd64: ACPI Error for AC adapter)
Your message dated Fri, 12 Mar 2010 00:01:32 +0100 with message-id 20100311230132.gd30...@stro.at and subject line Re: linux-image-2.6.26-1-amd64: ACPI Error for AC adapter has caused the Debian Bug report #501789, regarding linux-image-2.6.26-1-amd64: ACPI Error for AC adapter 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.) -- 501789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-5 Severity: important The system do not detect AC on and AC off ACPI events. For a laptop this is really annoying. In the kernel log there is an AC off and AC on in sequence. I remember that in the etch kernel (2.6.18 one) it worked. Moreover I experience ACPI slowness (with the events that work) -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-5) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Sep 10 15:31:12 UTC 2008 ** Command line: root=/dev/hda6 ro vga=791 ** Tainted: P (1) ** Kernel log: [17727.084207] ACPI Error (psargs-0358): [\_SB_.PCI0.P0P1.VGA_.ODSF] Namespace lookup failure, AE_NOT_FOUND [17727.084218] ACPI Error (psparse-0530): Method parse/execution failed [\ACEV] (Node 81007fb45c30), AE_NOT_FOUND [17727.084262] ACPI Error (psparse-0530): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_._Q34] (Node 81007fb46fd0), AE_NOT_FOUND [17752.184318] ACPI Error (psargs-0358): [\_SB_.PCI0.P0P1.VGA_.ODSF] Namespace lookup failure, AE_NOT_FOUND [17752.184329] ACPI Error (psparse-0530): Method parse/execution failed [\ACEV] (Node 81007fb45c30), AE_NOT_FOUND [17752.184372] ACPI Error (psparse-0530): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_._Q34] (Node 81007fb46fd0), AE_NOT_FOUND ** Loaded modules: Module Size Used by snd_usb_audio 91296 1 snd_usb_lib20224 1 snd_usb_audio snd_hwdep 12040 1 snd_usb_audio snd_intel8x0 36008 4 snd_ac97_codec115416 1 snd_intel8x0 ac97_bus6272 1 snd_ac97_codec snd_pcm_oss41760 0 snd_mixer_oss 18816 1 snd_pcm_oss snd_pcm81800 5 snd_usb_audio,snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_seq_dummy 7428 0 snd_seq_oss33152 0 snd_seq_midi 11072 0 snd_rawmidi26784 2 snd_usb_lib,snd_seq_midi snd_seq_midi_event 11904 2 snd_seq_oss,snd_seq_midi snd_seq54304 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 25744 3 snd_pcm,snd_seq snd_seq_device 11668 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd63688 20 snd_usb_audio,snd_hwdep,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 12064 1 snd snd_page_alloc 13072 2 snd_intel8x0,snd_pcm tun14084 1 nvidia 8105072 26 i2c_core 27936 1 nvidia powernow_k817156 0 cpufreq_conservative11784 0 cpufreq_stats 9120 0 cpufreq_userspace 8452 0 cpufreq_powersave 6400 0 cpufreq_ondemand 11792 1 freq_table 9344 3 powernow_k8,cpufreq_stats,cpufreq_ondemand ipv6 288328 14 fuse 53184 3 reiserfs 211072 4 sbp2 25356 0 loop 19468 0 joydev 14848 0 pcmcia 38680 0 firmware_class 12544 1 pcmcia parport_pc 31016 0 parport41776 1 parport_pc irtty_sir 9728 0 sir_dev16904 1 irtty_sir serio_raw 9860 0 irda 117732 1 sir_dev crc_ccitt 6528 1 irda pcspkr 7040 0 psmouse42268 0 k8temp 9216 0 hci_usb18460 0 bluetooth 57124 1 hci_usb yenta_socket 27916 1 rsrc_nonstatic 14080 1 yenta_socket pcmcia_core41508 3 pcmcia,yenta_socket,rsrc_nonstatic video 24084 5 output 7808 1 video battery16904 0 ac 9352 0 asus_laptop21852 0 led_class 8968 1 asus_laptop button 11680 0 evdev 14208 8 ext3 124688 1 jbd51240 1 ext3
Bug#500992: marked as done (Communication with USB-Modem (cdc-acm) hangs the modem (Kernel 2.2.26))
Your message dated Fri, 12 Mar 2010 00:02:55 +0100 with message-id 20100311230255.ge30...@stro.at and subject line Re: linux-image-2.6-686: problem still exists (Communication with B-Modem hangs the modem) has caused the Debian Bug report #500992, regarding Communication with USB-Modem (cdc-acm) hangs the modem (Kernel 2.2.26) 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.) -- 500992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: hylafax-server Version: 2:4.4.4-10 Severity: important Since I switched from Etch to Lenny I cannot send faxes anymore using hylafax: The modem hangs: it remains on-hook but does not send any data. Stopping hylafax does not make the modem to go on-hook. Faxes are not transmitted. I use a ELSA USB 56k Modem http://www.plastic-spoon.de/hardware/Elsa-USB-Microlink-56k.html which appears as /dev/ttyACM0. It is configured as a Fax class 1.0 modem. To make shure this is not a syndrome of my modems hardware failing i plugged in a spare modem of the same type. The same fault happens :-( At least for me, hylafax is unusable. I do not know how to debug further, it /might/ be a problem of the kernel (e.g. module cdc-acm) as well. Thanks for your efforts ... Sebastian -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages hylafax-server depends on: ii adduser3.110 add and remove users and groups ii bsd-mailx [mailx] 8.1.2-0.20071201cvs-3 A simple mail user agent ii debconf [debconf-2 1.5.22Debian configuration management sy ii ghostscript8.62.dfsg.1-3.1 The GPL Ghostscript PostScript/PDF ii ghostscript-x [gs] 8.62.dfsg.1-3.1 The GPL Ghostscript PostScript/PDF ii hylafax-client 2:4.4.4-10Flexible client/server fax softwar ii libc6 2.7-13GNU C Library: Shared libraries ii libgcc11:4.3.1-9 GCC support library ii libpam0g 1.0.1-4 Pluggable Authentication Modules l ii libstdc++6 4.3.1-9 The GNU Standard C++ Library v3 ii libtiff-tools 3.8.2-11 TIFF manipulation and conversion t ii libtiff4 3.8.2-11 Tag Image File Format (TIFF) libra ii lsb-base 3.2-20Linux Standard Base 3.2 init scrip ii mailx 1:20071201-3 Transitional package for mailx ren ii psmisc 22.6-1Utilities that use the proc filesy ii sed4.1.5-6 The GNU sed stream editor ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime hylafax-server recommends no packages. Versions of packages hylafax-server suggests: pn mgettynone (no description available) pn psrip none (no description available) -- debconf-show failed ---End Message--- ---BeginMessage--- closing as no update since a while. if you can reproduce with 2.6.32 linux images, please inform upstrean on bugzilla.kernel.org and let us know the bug nr. thanks for the feedback. ---End Message---
Bug#498328: marked as done (linux-image-2.6.26-1-amd64: nice is not fair: mouse jumps and chars repeated in terminal)
Your message dated Fri, 12 Mar 2010 00:05:14 +0100 with message-id 20100311230514.gf30...@stro.at and subject line Re: linux-image-2.6.26-1-amd64: nice is not fair: mouse jumps and chars repeated in terminal has caused the Debian Bug report #498328, regarding linux-image-2.6.26-1-amd64: nice is not fair: mouse jumps and chars repeated in terminal 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.) -- 498328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-4 Severity: normal Hello, I updated 2 days ago to this kernel, and I start notice pretty soon this problem: when I execute a program of mine (even with nice -n 19), with 4 parallel thread (it's cpu bound), the system completely slow down, the mouse starts jumping (not a smooth movement), switching to other application is really slow and the programs starts repeating input chars randomly (verified with amsn and gnome-terminal): this is what I came out trying a ls /proc...: $ s /pro/2808 The funny thing is that this machine has boinc always running (on 4 cores) and I cannot experience any of the above problem. I used the default configuration shipped along with this kernel. Please let me know anything I can do to help you fix is. Thanks, Sandro -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-4) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 11:13:42 UTC 2008 ** Command line: BOOT_IMAGE=Linux-2.6.26-1 ro root=fe00 root=/dev/mapper/system-root ** Not tainted ** Kernel log: [ 16.927913] XFS mounting filesystem dm-5 [ 16.996832] Ending clean XFS mount for filesystem: dm-5 [ 17.023057] Filesystem dm-6: Disabling barriers, not supported by the underlying device [ 17.029946] XFS mounting filesystem dm-6 [ 17.104940] Ending clean XFS mount for filesystem: dm-6 [ 17.156946] Filesystem dm-4: Disabling barriers, not supported by the underlying device [ 17.270190] XFS mounting filesystem dm-4 [ 17.394182] Ending clean XFS mount for filesystem: dm-4 [ 17.394182] Filesystem dm-3: Disabling barriers, not supported by the underlying device [ 17.451200] XFS mounting filesystem dm-3 [ 17.488301] Ending clean XFS mount for filesystem: dm-3 [ 17.847446] usb-storage: device scan complete [ 17.847993] scsi 6:0:0:0: Direct-Access TOSHIBA MK2546GSX PQ: 0 ANSI: 2 CCS [ 17.860391] sd 6:0:0:0: [sdc] 488397168 512-byte hardware sectors (250059 MB) [ 17.868879] sd 6:0:0:0: [sdc] Write Protect is off [ 17.874246] sd 6:0:0:0: [sdc] Mode Sense: 00 38 00 00 [ 17.874248] sd 6:0:0:0: [sdc] Assuming drive cache: write through [ 17.880878] sd 6:0:0:0: [sdc] 488397168 512-byte hardware sectors (250059 MB) [ 17.887943] sd 6:0:0:0: [sdc] Write Protect is off [ 17.891962] sd 6:0:0:0: [sdc] Mode Sense: 00 38 00 00 [ 17.891963] sd 6:0:0:0: [sdc] Assuming drive cache: write through [ 17.898839] sdc: sdc1 [ 17.971295] sd 6:0:0:0: [sdc] Attached SCSI disk [ 17.976547] sd 6:0:0:0: Attached scsi generic sg3 type 0 [ 43.751324] r8169: eth1: link up [ 43.756467] r8169: eth1: link up [ 44.180058] NET: Registered protocol family 10 [ 44.185662] lo: Disabled Privacy Extensions [ 44.203348] r8169: eth0: link down [ 44.208203] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 56.445781] eth1: no IPv6 routers present [ 65.608352] lp0: using parport0 (interrupt-driven). [ 65.641647] ppdev: user-space parallel port driver [ 67.220265] RPC: Registered udp transport module. [ 67.224270] RPC: Registered tcp transport module. [ 67.286716] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 67.350703] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 67.355545] NFSD: starting 90-second grace period [ 68.267317] device eth0 entered promiscuous mode [ 72.760695] mtrr: type mismatch for e000,1000 old: write-back new: write-combining [ 107.795864] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 216.943229] r8169: eth1: link down [ 218.535229] r8169: eth1: link up [17932.161204] usb 8-2: new high speed USB device using ehci_hcd and address 3 [17932.297175] usb 8-2: configuration #2 chosen from 1 choice [17932.301175] usb 8-2: New USB device found, idVendor=047e, idProduct=2892 [17932.301175] usb 8-2: New USB device strings: Mfr=1,
Bug#573490: drbd fails to load: drbd: disagrees about version of symbol cn_add_callback
tags 573490 + patch
affects 573490 drbd8-source
thanks
On Thu, Mar 11, 2010 at 02:38:23PM -0700, dann frazier wrote:
On Thu, Mar 11, 2010 at 09:43:45PM +0100, Tomas Pospisek wrote:
Package: linux-2.6
Version: 2.6.26-21lenny4
Severity: critical
drbd fails to load and there goes my failover high available cluster...
*t
well, crap - we ignored that ABI change because google showed only an
old/deprecated module as an out-of-tree user, but we obviously missed
drbd. We'll work on an update to the drbd modules.
This patch builds for me, but I don't have a drbd setup. I'd
appreciate it if someone could test it :)
diff -u drbd8-8.0.14/debian/changelog drbd8-8.0.14/debian/changelog
--- drbd8-8.0.14/debian/changelog
+++ drbd8-8.0.14/debian/changelog
@@ -1,3 +1,10 @@
+drbd8 (2:8.0.14-2+lenny1) UNRELEASED; urgency=high
+
+ * Update for connector API change in linux-2.6_2.6.26-21lenny4
+ * Restrict netlink calls to users with CAP_SYS_ADMIN (CVE Requested)
+
+ -- dann frazier da...@debian.org Thu, 11 Mar 2010 15:47:53 -0700
+
drbd8 (2:8.0.14-2) unstable; urgency=low
* Drop dpatch build-dependency.
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/user/drbdsetup.c
+++ drbd8-8.0.14/user/drbdsetup.c
@@ -408,6 +408,7 @@
EM(ProtocolCRequired) = Protocol C required,
EM(VMallocFailed) = vmalloc() failed. Out of memory?,
EM(DataOfWrongCurrent) = Can only attach to the data we lost last (see kernel log).,
+ EM(ERR_PERM) = Permission denied. CAP_SYS_ADMIN necessary,
};
#define MAX_ERROR (sizeof(error_messages)/sizeof(*error_messages))
const char * error_to_string(int err_no)
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/drbd/drbd_nl.c
+++ drbd8-8.0.14/drbd/drbd_nl.c
@@ -1764,9 +1764,14 @@
};
+#ifdef KERNEL_HAS_CN_SKB_PARMS
+STATIC void drbd_connector_callback(struct cn_msg *req, struct netlink_skb_parms *nsp)
+{
+#else
STATIC void drbd_connector_callback(void *data)
{
struct cn_msg *req = data;
+#endif
struct drbd_nl_cfg_req *nlp = (struct drbd_nl_cfg_req *)req-data;
struct cn_handler_struct *cm;
struct cn_msg *cn_reply;
@@ -1782,13 +1787,20 @@
return;
}
+#ifdef KERNEL_HAS_CN_SKB_PARMS
+ if (!cap_raised(nsp-eff_cap, CAP_SYS_ADMIN)) {
+ retcode = ERR_PERM;
+ goto fail;
+ }
+#endif
+
mdev = ensure_mdev(nlp);
if (!mdev) {
retcode = MinorNotKnown;
goto fail;
}
- TRACE(TraceTypeNl, TraceLvlSummary, nl_trace_packet(data););
+ TRACE(TraceTypeNl, TraceLvlSummary, nl_trace_packet(req););
if (nlp-packet_type = P_nl_after_last_packet) {
retcode = UnknownNetLinkPacket;
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/drbd/linux/drbd_config.h
+++ drbd8-8.0.14/drbd/linux/drbd_config.h
@@ -85,4 +85,8 @@
//#define NEED_SG_SET_BUF
#define HAVE_LINUX_SCATTERLIST_H
+/* In 2.6.32 we finally fixed connector to pass netlink_skb_parms to the callback
+ */
+#define KERNEL_HAS_CN_SKB_PARMS
+
#endif
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/drbd/linux/drbd.h
+++ drbd8-8.0.14/drbd/linux/drbd.h
@@ -140,6 +140,7 @@
CSUMSResyncRunning, /* DRBD 8.2 only */
VERIFYIsRunning, /* DRBD 8.2 only */
DataOfWrongCurrent,
+ ERR_PERM,
/* insert new ones above this line */
AfterLastRetCode
only in patch2:
unchanged:
--- drbd8-8.0.14.orig/scripts/adjust_drbd_config_h.sh
+++ drbd8-8.0.14/scripts/adjust_drbd_config_h.sh
@@ -104,6 +104,11 @@
have_linux_scatterlist_h=0
need_sg_set_buf=1
fi
+ if grep_q netlink_skb_parms $KDIR/include/linux/connector.h ; then
+have_netlink_skb_parms=1
+ else
+have_netlink_skb_parms=0
+ fi
else
# not a 2.6. kernel. just leave it alone...
exit 0
@@ -131,6 +136,8 @@
{ ( $need_sg_set_buf ? '' : '//' ) . \$1}e;
s{.*(#define HAVE_LINUX_SCATTERLIST_H.*)}
{ ( $have_linux_scatterlist_h ? '' : '//' ) . \$1}e;
+ s{.*(#define KERNEL_HAS_CN_SKB_PARMS.*)}
+ { ( $have_netlink_skb_parms ? '' : '//' ) . \$1}e;
\
./linux/drbd_config.h \
./linux/drbd_config.h.new
Bug#465752: ntp: Default distribution does not form peer relationships
tags 465752 moreinfo stop can you still reprduce this error with newer linux images? Squeeze will shipp with 2.6.32 and Lenny received several fixes since. thanks for the feedback. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311230652.gg30...@stro.at
Bug#514260: marked as done (linux-image-2.6.26-1-amd64: kernel does not support multiple, not similarm soundcards)
Your message dated Fri, 12 Mar 2010 00:21:34 +0100 with message-id 20100311232134.gj30...@stro.at and subject line Re: linux-image-2.6.26-1-amd64: kernel does not support multiple, not similarm soundcards) has caused the Debian Bug report #514260, regarding linux-image-2.6.26-1-amd64: kernel does not support multiple, not similarm soundcards 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.) -- 514260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: important It is no longer possible (earlier releases of 2.6.26 allowed for this as it should) to have 2 (different) soundcards active. After booting alsaconf must be run to reconfigure a soundcard to enable and unmute it. Tested with 2 different Soundblaster Cards drivers besides the onboard ac97 soundcard. -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 2009 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.26-1-amd64 root=/dev/mapper/nexus-root ro splash GRUB_CMDLINE_LINUX= ** Tainted: P (1) ** Kernel log: [ 11.738950] input: PC Speaker as /class/input/input5 [ 11.901096] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16 [ 11.901145] ACPI: PCI Interrupt :05:06.0[A] - Link [APC1] - GSI 16 (level, low) - IRQ 16 [ 11.943312] cannot find the slot for index 0 (range 0-0), error: -16 [ 11.943360] Intel ICH: probe of :00:04.0 failed with error -12 [ 12.174616] pnp: the driver 'parport_pc' has been registered [ 12.174636] parport_pc 00:09: reported by Plug and Play ACPI [ 12.174724] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 12.179289] pnp: the driver 'ns558' has been registered [ 12.272105] parport_pc 00:09: driver attached [ 12.272364] ns558 00:0c: driver attached [ 12.294997] gameport: NS558 PnP Gameport is pnp00:0c/gameport0, io 0x201, speed 912kHz [ 12.333721] pnp: the driver 'mpu401' has been registered [ 12.333997] mpu401 00:0b: driver attached [ 14.960870] EXT3 FS on dm-0, internal journal [ 15.056003] loop: module loaded [ 15.150009] kobject_add_internal failed for audio with -EEXIST, don't try to register things with the same name in the same directory. [ 15.150070] Pid: 2122, comm: modprobe Not tainted 2.6.26-1-amd64 #1 [ 15.150109] [ 15.150110] Call Trace: [ 15.150190] [8031b305] kobject_add_internal+0x13f/0x17e [ 15.150234] [8031b742] kobject_add+0x74/0x7c [ 15.150288] [8031b15c] kobject_get+0x12/0x17 [ 15.150329] [80382b41] get_device+0x17/0x20 [ 15.150368] [80383151] device_add+0x9b/0x53f [ 15.150408] [8031afc6] kobject_init+0x41/0x69 [ 15.150451] [803836a1] device_create_vargs+0x9a/0xc6 [ 15.150496] [80383711] device_create+0x44/0x4c [ 15.150541] [a023621d] :soundcore:sound_insert_unit+0x13b/0x14d [ 15.150591] [a0236424] :soundcore:register_sound_special_device+0x144/0x153 [ 15.150658] [a00250af] :sound:oss_init+0xaf/0x13b [ 15.150704] [80255067] sys_init_module+0x190e/0x1aa4 [ 15.150758] [a023626b] :soundcore:register_sound_midi+0x0/0x3c [ 15.150816] [8020beca] system_call_after_swapgs+0x8a/0x8f [ 15.150863] [ 15.310729] PPP generic driver version 2.4.2 [ 15.546009] PPP MPPE Compression module registered [ 15.693722] PPP Deflate Compression module registered [ 15.706060] PPP BSD Compression module registered [ 21.445401] kjournald starting. Commit interval 5 seconds [ 21.446236] EXT3 FS on dm-5, internal journal [ 21.446295] EXT3-fs: mounted filesystem with ordered data mode. [ 21.446908] kjournald starting. Commit interval 5 seconds [ 21.447003] EXT3 FS on dm-4, internal journal [ 21.447061] EXT3-fs: mounted filesystem with ordered data mode. [ 21.447803] kjournald starting. Commit interval 5 seconds [ 21.447943] EXT3 FS on dm-1, internal journal [ 21.448024] EXT3-fs: mounted filesystem with ordered data mode. [ 21.448644] kjournald starting. Commit interval 5 seconds [ 21.448763] EXT3 FS on dm-2, internal journal [ 21.448821] EXT3-fs: mounted filesystem with ordered data mode. [ 21.564349] Adding 6041592k swap on /dev/mapper/nexus-swap_1. Priority:-1 extents:1 across:6041592k [ 22.864128] fuse init (API version 7.9) [ 23.922684] NET: Registered protocol family 10 [ 23.923357] lo: Disabled
Bug#503766: intelfb.ko: loading framebuffer module kills machine
On Mon, 11 May 2009, Michal Suchanek wrote: Package: linux-image-2.6.29-1-amd64 Version: 2.6.29-3 Followup-For: Bug #503766 With 2.6.29 the display is turned off when the intelfb module is loaded. Unable to frob numlock led on keyboard, no ping. can you still reproduce that with 2.6.32 linux images from unstable? if yes please file bug upstream on bugzilla.kernel.org and let us know the bug nr. thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311230955.gh30...@stro.at
Bug#517449: marked as done (linux-image-2.6.26-1-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds))
Your message dated Fri, 12 Mar 2010 00:25:21 +0100 with message-id 20100311232521.ga3...@baikonur.stro.at and subject line Re: linux-image-2.6.26-1-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds) has caused the Debian Bug report #517449, regarding linux-image-2.6.26-1-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds) 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.) -- 517449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: important Tags: patch * ISSUE Lenny's kernel is subject to the bug described here: http://lkml.org/lkml/2009/1/11/70 * ANALYSIS FIX and fixed with this thread: http://lkml.org/lkml/2009/1/15/107 (in particular with http://lkml.org/lkml/2009/1/15/231 and http://lkml.org/lkml/2009/1/15/240, AFAIU) FWIW, this seems to have made it to 2.6.28.y at least, with: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.28.y.git;a=commit;h=046e7f77d734778a3b2e7d51ce63da3dbe7a8168 http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.28.y.git;a=commit;h=df94b12439ca449a852e579fc2952dac80f70c90 * TYPICAL SYMPTOMS Basically, running tasks at SCHED_IDLEPRIO (such as BOINC) renders the system sluggish and randomly unresponsive. Messages such as this one appear in dmesg: [1830473.188790] INFO: task pdflush:3945 blocked for more than 120 seconds. [1830473.269257] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [1830473.365255] pdflush D 81003c595800 0 3945 2 [1830473.365274] 81002f055d60 0046 81002f055d70 804289af [1830473.365278] 8100258eaee0 81003e966f60 8100258eb168 00028031dc67 [1830473.365281] 0008 a03445b4 81000a2e8340 000b [1830473.365283] Call Trace: [1830473.365380] [804289af] thread_return+0x6b/0xac [1830473.365448] [a03445b4] :xfs:xfs_log_move_tail+0x46/0x12c [1830473.365472] [a035b055] :xfs:xfs_buf_wait_unpin+0x86/0xa8 [1830473.365479] [8022c202] default_wake_function+0x0/0xe [1830473.365503] [a035b49b] :xfs:xfs_buf_iorequest+0x20/0x61 [1830473.365538] [a035ec2e] :xfs:xfs_bdstrat_cb+0x36/0x3a [1830473.365559] [a0357d59] :xfs:xfs_bwrite+0x5e/0xbb [1830473.365580] [a0352209] :xfs:xfs_syncsub+0x119/0x226 [1830473.365602] [a03600d4] :xfs:xfs_fs_write_super+0x1b/0x21 [1830473.365608] [8029cd90] sync_supers+0x60/0xa4 [1830473.365615] [802783f2] pdflush+0x0/0x211 [1830473.365619] [80277fb9] wb_kupdate+0x2d/0x10d [1830473.369036] [802783f2] pdflush+0x0/0x211 [1830473.369036] [80278556] pdflush+0x164/0x211 [1830473.369036] [80277f8c] wb_kupdate+0x0/0x10d [1830473.369036] [80246083] kthread+0x47/0x74 [1830473.369036] [80230196] schedule_tail+0x27/0x5c [1830473.369036] [8020cf28] child_rip+0xa/0x12 [1830473.369036] [80213299] restore_i387_ia32+0xb0/0xd4 [1830473.369036] [8024603c] kthread+0x0/0x74 [1830473.369036] [8020cf1e] child_rip+0x0/0x12 Sometimes keyboard input will yield repeated keystrokes. SSH session will stop echoing. And basically hell freezes over for 2 minutes. I believe this bug relates to #498328, #499046 and possibly #499198 This is an extremely nasty bug. I've seen it very frequently while running BOINC on Xen dom0 on a 16-core box (using debian xen kernel). A temporary workaround has been to cap BOINC to 90% CPU usage: freezes still happen but last less. HTH -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 2009 -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.26-1-amd64 recommends no packages. Versions of packages linux-image-2.6.26-1-amd64 suggests: ii grub 0.97-47lenny2
Bug#517586: marked as done (Soft lockup in kjournald)
Your message dated Fri, 12 Mar 2010 00:25:21 +0100 with message-id 20100311232521.ga3...@baikonur.stro.at and subject line Re: linux-image-2.6.26-1-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds) has caused the Debian Bug report #517586, regarding Soft lockup in kjournald 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.) -- 517586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: important Once in a while the whole system start crawling with the following messages printed in kernel log. Simple saving file in xemacs can completely freeze the whole system for 30 seconds. There is a similar bug reported in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/276476 The bug is happening several times a week. This bug is probably the same as bug #516374, but I'm not running any VMs - pure native fully updated Debian Lenny on AMD64, CPU - Intel QX9770. I have other machine with alike config, but Dual Core CPU and this bug never happens. -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 2009 ** Command line: root=/dev/mapper/vg0-root_crypt ro quiet ** Not tainted ** Kernel log: [1304639.266960] INFO: task kjournald:5479 blocked for more than 120 seconds. [1304639.266964] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [1304639.266965] kjournald D 810001002350 0 5479 2 [1304639.266968] 81022c4bbd30 0046 81022ae82758 81022f0c72f0 [1304639.266972] 81022cd10040 81022f13ae60 81022cd102c8 80248d42 [1304639.266975] 802125e7 000ccafa8cc8c6f0 8024ac3e [1304639.266978] Call Trace: [1304639.267003] [802125e7] read_tsc+0x9/0x20 [1304639.267006] [8024ac3e] getnstimeofday+0x39/0x98 [1304639.267013] [802bacd1] sync_buffer+0x0/0x3f [1304639.267016] [80428b97] io_schedule+0x5c/0x9e [1304639.267021] [802bad0c] sync_buffer+0x3b/0x3f [1304639.267023] [80428df2] __wait_on_bit+0x40/0x6e [1304639.267029] [802bacd1] sync_buffer+0x0/0x3f [1304639.267032] [80428e8c] out_of_line_wait_on_bit+0x6c/0x78 [1304639.267037] [802461d7] wake_bit_function+0x0/0x23 [1304639.267050] [a01fcdde] :jbd:journal_commit_transaction+0x3e0/0xbf2 [1304639.267057] [8023cf29] lock_timer_base+0x26/0x4b [1304639.267063] [8023cf9f] try_to_del_timer_sync+0x51/0x5a [1304639.267075] [a01ffd0c] :jbd:kjournald+0xc1/0x1fb [1304639.267079] [802461a9] autoremove_wake_function+0x0/0x2e [1304639.267088] [a01ffc4b] :jbd:kjournald+0x0/0x1fb [1304639.267093] [80246083] kthread+0x47/0x74 [1304639.267095] [80230196] schedule_tail+0x27/0x5c [1304639.267099] [8020cf28] child_rip+0xa/0x12 [1304639.267109] [8021a826] lapic_next_event+0xf/0x13 [1304639.267115] [8024603c] kthread+0x0/0x74 [1304639.267117] [8020cf1e] child_rip+0x0/0x12 [1304639.267121] [1307798.216952] INFO: task kjournald:5479 blocked for more than 120 seconds. [1307798.216956] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [1307798.216958] kjournald D 0 5479 2 [1307798.216961] 81022c4bbd30 0046 81022f0c72f0 [1307798.216964] 81022cd10040 81022f0b1470 81022cd102c8 00018031dc67 [1307798.216968] [1307798.216970] Call Trace: [1307798.217004] [802bacd1] sync_buffer+0x0/0x3f [1307798.217007] [80428b97] io_schedule+0x5c/0x9e [1307798.217012] [802bad0c] sync_buffer+0x3b/0x3f [1307798.217014] [80428df2] __wait_on_bit+0x40/0x6e [1307798.217021] [802bacd1] sync_buffer+0x0/0x3f [1307798.217023] [80428e8c] out_of_line_wait_on_bit+0x6c/0x78 [1307798.217029] [802461d7] wake_bit_function+0x0/0x23 [1307798.217042] [a01fcdde] :jbd:journal_commit_transaction+0x3e0/0xbf2 [1307798.217049] [8023cf29] lock_timer_base+0x26/0x4b [1307798.217055] [8023cf9f] try_to_del_timer_sync+0x51/0x5a [1307798.217066] [a01ffd0c] :jbd:kjournald+0xc1/0x1fb [1307798.217070] [802461a9] autoremove_wake_function+0x0/0x2e [1307798.217079]
Bug#405223: marked as done (linux-image-2.6.18-3-xen-vserver-686: 4gb seg fixup messages)
Your message dated Mon, 15 Feb 2010 20:18:14 +0100 with message-id 20100215191814.gn9...@baikonur.stro.at and subject line Re: Xen || vserver troubles has caused the Debian Bug report #405223, regarding linux-image-2.6.18-3-xen-vserver-686: 4gb seg fixup messages 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.) -- 405223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.18-3-xen-vserver-686 Version: 2.6.18-8 Severity: normal my syslog is getting flooded with messages like this: 4gb seg fixup, process bash (pid 4760), cs:ip 73:b7e062a5 printk: 2830 messages suppressed. this doesn't happen when running non-xen kernels. live well, vagrant -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-xen-vserver-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.18-3-xen-vserver-686 depends on: ii initramfs-tools 0.85e tools for generating an initramfs ii linux-modules-2.6.18-3-xen-vs 2.6.18-8 Linux 2.6.18 modules on PPro/Celer Versions of packages linux-image-2.6.18-3-xen-vserver-686 recommends: ii libc6-xen2.3.6.ds1-8 GNU C Library: Shared libraries [X -- no debconf information ---End Message--- ---BeginMessage--- the 2.6.18 linux images from Etch are no longer supported, thus closing this bug report. As both Xen or vserver stayed out of tree it is very unlikely that they improved a lot since. With modern hardware kvm or lxc (linux containers) are recommended. if you still haven't upgraded to Lenny please notice that Etch has no security support any more as of today: http://www.debian.org/News/2010/20100121 if you can reproduce said bugs with 2.6.32 linux images from unstable please shout on said box and bug can be reopened: reportbug -N bugnr thank you for your report. ---End Message---
Bug#570382: more datapoints on vserver start failure
On Thu, Mar 11, 2010 at 10:17:40PM +0100, Tomas Pospisek wrote: So once again I had to upgrade kernels and I noticed: * that only my -686 kernel based machines failed to start the vservers (guests) correctly. The amd64 machine started them without problems. I see that florian.duf...@inria.fr also has an 686 machine. I'm Cc:ing Dan to see whether that's also the case for him. Yes, also the case for me. I haven't tried an amd64 vserver kernel. * on one of the machines the *first* of the vserver actually did start all others not and on the other machine all vservers did not start correctly. So it's not either all vservers fail to start or none. Might a ressource pressure problem? I found the same thing - it wasn't reproducible 100% of the time. * stopping and starting the vservers one after the other fixed the problem, the vservers started correctly Again, my findings were similar. The problem only seemed to exhibit itself using /etc/init.d/vserver start - starting vservers with vserver foo start would always work. -dan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311233100.gb28...@hercules.pureserver.info
Processed: tagging 507785
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 507785 + pending Bug #507785 [linux-2.6] xen-linux-system: Xen domU clock frozen on dom0 boot 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 Archive: http://lists.debian.org/handler.s.c.12683515031022.transcr...@bugs.debian.org
Processed: tagging 504805
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 504805 + pending Bug #504805 [linux-2.6] linux-image-2.6.26-1-xen-686: panic: iret exception 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 Archive: http://lists.debian.org/handler.s.c.1268351492923.transcr...@bugs.debian.org
Processed: tagging 506118
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 506118 + pending Bug #506118 [linux-2.6] xen-linux-system-2.6.26-1-xen-amd64: Dom0 reboots after loading xend when atl1 network is present 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 Archive: http://lists.debian.org/handler.s.c.126835149.transcr...@bugs.debian.org
Processed: tagging 509085
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 509085 + pending Bug #509085 [linux-2.6] linux-image-2.6.26-1-xen-amd64: lsusb, rmmod usb-ehci-hcd, etc, hang and generate traces in dmesg 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 Archive: http://lists.debian.org/handler.s.c.12683515061068.transcr...@bugs.debian.org
Processed: tagging 499745
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 499745 + pending Bug #499745 [linux-2.6] linux-image-2.6.26-1-xen-686: freezes under Xen 3.2.0 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 Archive: http://lists.debian.org/handler.s.c.1268351481840.transcr...@bugs.debian.org
Processed: tagging 503857
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 503857 + pending Bug #503857 [linux-2.6] xen-linux-system-2.6.26-1-xen-686: serial oops under load 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 Archive: http://lists.debian.org/handler.s.c.1268351484870.transcr...@bugs.debian.org
Processed: tagging 505545
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 505545 + pending Bug #505545 [linux-2.6] [linux-image-2.6.26-1-xen-amd64] linux-image-2.6.26-1-xen-amd64 floppy mount problem 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 Archive: http://lists.debian.org/handler.s.c.1268351496948.transcr...@bugs.debian.org
Re: openvz kernel for debian squeeze
On Thu, Mar 11, 2010 at 11:26:34PM +0100, maximilian attems wrote: any word on these two issues: a) compile failure due to CGROUP_FREEZER on (it's on in debian topconfig) kernel/built-in.o: In function `update_freezer_state': cgroup_freezer.c:(.text+0x521f3): undefined reference to `cgroup_iter_start' cgroup_freezer.c:(.text+0x5222e): undefined reference to `cgroup_iter_next' cgroup_freezer.c:(.text+0x5225b): undefined reference to `cgroup_iter_end' kernel/built-in.o: In function `freezer_write': cgroup_freezer.c:(.text+0x52300): undefined reference to `cgroup_iter_start' cgroup_freezer.c:(.text+0x52312): undefined reference to `cgroup_iter_next' cgroup_freezer.c:(.text+0x52325): undefined reference to `cgroup_iter_end' cgroup_freezer.c:(.text+0x52345): undefined reference to `cgroup_iter_start' cgroup_freezer.c:(.text+0x523a9): undefined reference to `cgroup_iter_next' cgroup_freezer.c:(.text+0x523c1): undefined reference to `cgroup_iter_end' make[5]: *** [.tmp_vmlinux1] Error 1 tested that current git tree compiles with CONFIG_CGROUP_FREEZER not set. b) 2.6.26 legacy setting, is that still relevant? # CONFIG_NF_CONNTRACK_IPV6 is not set -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100311234726.ga26...@baikonur.stro.at
Re: openvz kernel for debian squeeze
On Tue, 09 Mar 2010, Ola Lundqvist wrote: * Testing kernel when built please go ahaed: http://charm.itp.tuwien.ac.at/~mattems/linux-image-2.6.32-4-openvz-amd64_2.6.32-10_amd64.deb checksum signed: http://charm.itp.tuwien.ac.at/~mattems/linux-image-2.6.32-4-openvz-amd64_2.6.32-10_amd64.deb.sha256.asc once I've a response to my two outstanding questions and you tell me that aboves boots and can create guests I'm happy to add the image to squeeze. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100312001107.gk30...@stro.at
Processed: reopening 517449
Processing commands for cont...@bugs.debian.org:
reopen 517449
Bug #517449 {Done: maximilian attems m...@stro.at}
[linux-image-2.6.26-2-vserver-amd64] linux-image-2.6.26-1-amd64: SCHED_IDLE
issues (tasks blocked for more than 120 seconds)
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
thanks
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
Archive:
http://lists.debian.org/handler.s.c.126835564815270.transcr...@bugs.debian.org
Bug#517449: closed by maximilian attems m...@stro.at (Re: linux-image-2.6.26-1-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds))
On Fri, Mar 12, 2010 at 12:33 AM, Debian Bug Tracking System ow...@bugs.debian.org wrote: Version: 2.6.26-21 this should have been fixed on stable update, thus closing. Which stable update? It happened to me no later than this morning, and I'm running: ii linux-image-2.6.26-2-amd64 2.6.26-21lenny3 Linux 2.6.26 image on AMD64 Thanks, T-Bone -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7d01f9f01003111648i749b6321s9010bf4bbaee7...@mail.gmail.com
Bug#507728: marked as done (linux-image-2.6.26-1-686: USB mass storage devices unreliable when connected through USB hubs)
Your message dated Fri, 12 Mar 2010 00:11:37 +0100 with message-id 20100311231137.gi30...@stro.at and subject line Re: Bug#507728: linux-image-2.6.26-1-686: USB mass storage devices unreliable when connected through USB hubs has caused the Debian Bug report #507728, regarding linux-image-2.6.26-1-686: USB mass storage devices unreliable when connected through USB hubs 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.) -- 507728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-10 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 USB mass storage devices always seem to fail after a few moments of reading or writing when they are connected via a USB hub. This is accompanied by messages such as the following: Dec 3 22:56:32 xerces kernel: [ 3975.148272] sd 6:0:0:0: [sda] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK Dec 3 22:56:32 xerces kernel: [ 3975.148286] end_request: I/O error, dev sda, sector 8065 Dec 3 22:56:32 xerces kernel: [ 3975.148303] Buffer I/O error on device sda1, logical block 1 Dec 3 22:56:32 xerces kernel: [ 3975.148307] lost page write due to I/O error on sda1 Dec 3 22:56:32 xerces kernel: [ 3975.148625] usb 4-3.1: USB disconnect, address 10 Dec 3 22:56:32 xerces kernel: [ 3975.151790] Buffer I/O error on device sda1, logical block 8192 Dec 3 22:56:32 xerces kernel: [ 3975.151800] lost page write due to I/O error on sda1 Dec 3 22:56:32 xerces hald[3015]: forcibly attempting to lazy unmount /dev/sda1 as enclosing drive was disconnected Dec 3 22:56:32 xerces hald: unmounted /dev/sda1 from '/media/UDISK 2.0' on behalf of uid 0 This happens with two computers (a Samsung Q45 and a PC with an Asus A7V8X-X motherboard); two mass storage devices (an Xclef HD-500 40 GB MP3 player, and a play.com 16 GB flash device) and two hubs (a Belin F5U234 and a Trust HU-5870V). In all cases, connecting the device directly to the computer without going through a hub eliminates the problem. If the device disconnects while I am copying files to it then this causes DATA LOSS as the original files are removed (this is probably a separate bug that I should file against nautilus though). - -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-10) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Sat Nov 8 19:00:26 UTC 2008 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.26-1-686 root=/dev/md0 ro noresume vga=0x305 quiet ** Tainted: P (1) ** Kernel log: [ 3850.488294] usb-storage: device scan complete [ 3850.534969] scsi 3:0:0:0: Direct-Access USB DISK 2.0 PMAP PQ: 0 ANSI: 0 CCS [ 3852.308778] sd 3:0:0:0: [sda] READ CAPACITY failed [ 3852.308788] sd 3:0:0:0: [sda] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK [ 3852.308802] sd 3:0:0:0: [sda] Sense not available. [ 3852.308855] sd 3:0:0:0: [sda] Write Protect is off [ 3852.308859] sd 3:0:0:0: [sda] Mode Sense: 00 00 00 00 [ 3852.308863] sd 3:0:0:0: [sda] Assuming drive cache: write through [ 3852.309028] sd 3:0:0:0: [sda] Attached SCSI removable disk [ 3852.312940] usb 4-3.3: USB disconnect, address 7 [ 3857.916177] usb 4-3.4: new high speed USB device using ehci_hcd and address 8 [ 3858.010800] usb 4-3.4: configuration #1 chosen from 1 choice [ 3858.011161] scsi4 : SCSI emulation for USB Mass Storage devices [ 3858.011439] usb 4-3.4: New USB device found, idVendor=13fe, idProduct=3100 [ 3858.011443] usb 4-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3858.011446] usb 4-3.4: Product: USB DISK 2.0 [ 3858.011448] usb 4-3.4: Manufacturer: [ 3858.011450] usb 4-3.4: SerialNumber: 078A15502BA2 [ 3858.011459] usb-storage: device found at 8 [ 3858.011462] usb-storage: waiting for device to settle before scanning [ 3863.008256] usb-storage: device scan complete [ 3863.055296] scsi 4:0:0:0: Direct-Access USB DISK 2.0 PMAP PQ: 0 ANSI: 0 CCS [ 3864.968454] sd 4:0:0:0: [sda] 31764480 512-byte hardware sectors (16263 MB) [ 3864.968454] sd 4:0:0:0: [sda] Write Protect is off [ 3864.968454] sd 4:0:0:0: [sda] Mode Sense: 23 00 00 00 [ 3864.968454] sd 4:0:0:0: [sda] Assuming drive cache: write through [ 3864.975464] sd 4:0:0:0: [sda] 31764480 512-byte hardware sectors (16263 MB) [ 3864.976069] sd 4:0:0:0: [sda] Write Protect is off [ 3864.976069] sd 4:0:0:0: [sda] Mode Sense: 23 00 00 00 [ 3864.976069] sd 4:0:0:0: [sda] Assuming drive cache: write through [ 3864.976069]
Bug#517449: closed by maximilian attems m...@stro.at (Re: linux-image-2.6.26-1-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds))
On Fri, Mar 12, 2010 at 01:48:20AM +0100, Thibaut VARENE wrote: On Fri, Mar 12, 2010 at 12:33 AM, Debian Bug Tracking System ow...@bugs.debian.org wrote: Version: 2.6.26-21 this should have been fixed on stable update, thus closing. Which stable update? It happened to me no later than this morning, and I'm running: ii linux-image-2.6.26-2-amd64 2.6.26-21lenny3 Linux 2.6.26 image on AMD64 2.6.26-21 has idle fixes, uff, will see if i can see more relevant fixes in 2.6.27 stable, thanks for quick feedback, reopened -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100312005216.gb26...@baikonur.stro.at
Bug#517449: closed by maximilian attems m...@stro.at (Re: linux-image-2.6.26-1-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds))
On Fri, Mar 12, 2010 at 01:48:20AM +0100, Thibaut VARENE wrote: On Fri, Mar 12, 2010 at 12:33 AM, Debian Bug Tracking System ow...@bugs.debian.org wrote: Version: 2.6.26-21 this should have been fixed on stable update, thus closing. Which stable update? It happened to me no later than this morning, and I'm running: ii linux-image-2.6.26-2-amd64 2.6.26-21lenny3 Linux 2.6.26 image on AMD64 please post aboves, thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100312021634.gc26...@baikonur.stro.at
Processed: severity of 573460 is important
Processing commands for cont...@bugs.debian.org: severity 573460 important Bug #573460 [linux-image-2.6.26-2-openvz-amd64] BUG: recent printk recursion! Severity set to 'important' from 'normal' thanks 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 Archive: http://lists.debian.org/handler.s.c.126836562213998.transcr...@bugs.debian.org
Processed: tagging 573460
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 573460 + pending Bug #573460 [linux-image-2.6.26-2-openvz-amd64] BUG: recent printk recursion! 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 Archive: http://lists.debian.org/handler.s.c.12683667660.transcr...@bugs.debian.org
Processed: tagging 571457
Processing commands for cont...@bugs.debian.org: tags 571457 moreinfo Bug #571457 [linux-image-2.6.26-2-openvz-686] OpenVZ write system call to TCP/IP connection hangs, burning CPU cycles endlessly. Added tag(s) moreinfo. thanks 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 Archive: http://lists.debian.org/handler.s.c.126836983224590.transcr...@bugs.debian.org
Bug#573490: Check kernel config during drbd8 builds
This patch adds the config script to the package (as done in unstable) and ensures that it runs at build time. Given this, you can adjust the config script or the code to report a fatal error if it detects the insecure connector API. Ben. diff -u drbd8-8.0.14/debian/drbd8-source.drbd-Makefile drbd8-8.0.14/debian/drbd8-source.drbd-Makefile --- drbd8-8.0.14/debian/drbd8-source.drbd-Makefile +++ drbd8-8.0.14/debian/drbd8-source.drbd-Makefile @@ -12,0 +12,9 @@ drbd-objs += connector.o cn_queue.o endif +# Automatically update config +$(addprefix $(obj)/,$(drbd-objs)): $(obj)/linux/drbd_config.h +$(obj)/linux/drbd_config.h: FORCE + $(Q)if [ $(obj) != $(src) ]; then \ + mkdir -p $(@D)\ + cp $(src)/linux/drbd_config.h $@; \ + fi + cd $(obj) KDIR=$(objtree) $(src)/../scripts/adjust_drbd_config_h.sh +.PHONY: FORCE diff -u drbd8-8.0.14/debian/rules drbd8-8.0.14/debian/rules --- drbd8-8.0.14/debian/rules +++ drbd8-8.0.14/debian/rules @@ -113,7 +113,8 @@ cp debian/drbd8-source.Makefile debian/$(PACKAGE)-source/usr/src/modules/drbd8/Makefile cp debian/drbd8-source.drbd-Makefile debian/$(PACKAGE)-source/usr/src/modules/drbd8/drbd/Makefile cp drbd/linux/drbd_config.h debian/$(PACKAGE)-source/usr/src/modules/drbd8 -# cp -a scripts/adjust_drbd_config_h.sh debian/$(PACKAGE)-source/usr/src/modules/drbd/scripts/ + mkdir debian/$(PACKAGE)-source/usr/src/modules/drbd8/scripts + cp scripts/adjust_drbd_config_h.sh debian/$(PACKAGE)-source/usr/src/modules/drbd8/scripts/ # install debian/ files mkdir -p debian/$(PACKAGE)-source/usr/src/modules/drbd8/debian/ --- END --- -- Ben Hutchings Humour is the best antidote to reality. signature.asc Description: This is a digitally signed message part
Processed: tagging 500145
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 500145 + pending Bug #500145 [linux-2.6] Subject: linux-image-2.6.26-1-openvz-686: more warnings in logs 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 Archive: http://lists.debian.org/handler.s.c.1268370853685.transcr...@bugs.debian.org
Re: openvz kernel for debian squeeze
Hi Unfortunatly I do not have any amd64 machine to test on. Do you have a kernel (or source so I can compile myself) for i386 (i686 actually)? I have an AMD machine, but no 64 bit variant unfortunatly. Best regards, // Ola On Fri, Mar 12, 2010 at 01:11:07AM +0100, maximilian attems wrote: On Tue, 09 Mar 2010, Ola Lundqvist wrote: * Testing kernel when built please go ahaed: http://charm.itp.tuwien.ac.at/~mattems/linux-image-2.6.32-4-openvz-amd64_2.6.32-10_amd64.deb checksum signed: http://charm.itp.tuwien.ac.at/~mattems/linux-image-2.6.32-4-openvz-amd64_2.6.32-10_amd64.deb.sha256.asc once I've a response to my two outstanding questions and you tell me that aboves boots and can create guests I'm happy to add the image to squeeze. -- --- Inguza Technology AB --- MSc in Information Technology / o...@inguza.comAnnebergsslingan 37\ | o...@debian.org 654 65 KARLSTAD| | http://inguza.com/Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100312053142.ga3...@inguza.net
Bug#573071: linux-image-2.6.32-2-amd64: KVM linux guests oops in kvm_leave_lazy_mmu on boot
tags 573071 + patch thanks The patch posted at http://marc.info/?l=kvmm=126834221504655w=2 should fix this. It's cc'd to stable so we may just pick it up that way. Ben. -- Ben Hutchings If God had intended Man to program, we'd have been born with serial I/O ports. signature.asc Description: This is a digitally signed message part
Processed: Re: linux-image-2.6.32-2-amd64: KVM linux guests oops in kvm_leave_lazy_mmu on boot
Processing commands for cont...@bugs.debian.org: tags 573071 + patch Bug #573071 [linux-2.6] linux-image-2.6.32-2-amd64: KVM linux guests oops in kvm_leave_lazy_mmu on boot Added tag(s) 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 debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.126837286321019.transcr...@bugs.debian.org
Bug#573490: Patch works for me
Applying drbd-connector.patch got my DRBD setup working again. Thanx! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4791a538-5f91-4292-857f-31135eb3f...@peytz.dk
Re: openvz kernel for debian squeeze
On 03/12/2010 02:47 AM, maximilian attems wrote: On Thu, Mar 11, 2010 at 11:26:34PM +0100, maximilian attems wrote: any word on these two issues: a) compile failure due to CGROUP_FREEZER on (it's on in debian topconfig) kernel/built-in.o: In function `update_freezer_state': cgroup_freezer.c:(.text+0x521f3): undefined reference to `cgroup_iter_start' cgroup_freezer.c:(.text+0x5222e): undefined reference to `cgroup_iter_next' cgroup_freezer.c:(.text+0x5225b): undefined reference to `cgroup_iter_end' kernel/built-in.o: In function `freezer_write': cgroup_freezer.c:(.text+0x52300): undefined reference to `cgroup_iter_start' cgroup_freezer.c:(.text+0x52312): undefined reference to `cgroup_iter_next' cgroup_freezer.c:(.text+0x52325): undefined reference to `cgroup_iter_end' cgroup_freezer.c:(.text+0x52345): undefined reference to `cgroup_iter_start' cgroup_freezer.c:(.text+0x523a9): undefined reference to `cgroup_iter_next' cgroup_freezer.c:(.text+0x523c1): undefined reference to `cgroup_iter_end' make[5]: *** [.tmp_vmlinux1] Error 1 tested that current git tree compiles with CONFIG_CGROUP_FREEZER not set. Yes. Turn it off for openvz, please, I will fix the Kconfigs accordingly. I'll make the defconfig .config compilable, but we'll ship our own one anyway. Can you tell me the deadline by what we should resolve all the issues with .config? b) 2.6.26 legacy setting, is that still relevant? # CONFIG_NF_CONNTRACK_IPV6 is not set The config used will be taken from FC12 (like we did for 2.6.27). This particular option will be turned on after I receive fixes for per-ve iptables from one of my kernel developers ;) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b99e97a.7030...@parallels.com
Bug#573531: drbd8-modules-2.6.26-2-amd64: Can not load drbd module
Package: drbd8-modules-2.6.26-2-amd64 Version: 2.6.26+8.0.14-6+lenny1 Severity: important *** Please type your report below this line *** Hello, after installing the security update for linux-image-2.6.26-2-amd (2.6.26-21lenny4) my hole cluster was going down, because the drbd module could not be loaded. hot...@beta:~$ lsmod | grep drbd hot...@beta:~$ sudo modprobe drbd FATAL: Error inserting drbd (/lib/modules/2.6.26-2-xen-amd64/extra/drbd8/drbd/drbd.ko): Unknown symbol in module, or unknown parameter (see dmesg) hot...@beta:~$ sudo tail /var/log/syslog ... Mar 12 07:59:15 beta kernel: [ 148.854821] drbd: disagrees about version of symbol cn_add_callback Mar 12 07:59:15 beta kernel: [ 148.854824] drbd: Unknown symbol cn_add_callback I decided to purge drbd8-modules-2.6.26-2-amd64 and installed drbd8-source. After that i was able to load the drbd module. Regards, Dennis -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages drbd8-modules-2.6.26-2-amd64 depends on: ii linux-image-2.6.26-2-amd 2.6.26-21lenny4 Linux 2.6.26 image on AMD64 drbd8-modules-2.6.26-2-amd64 recommends no packages. drbd8-modules-2.6.26-2-amd64 suggests no packages. -- no debconf information signature.asc Description: OpenPGP digital signature
