Processed (with 5 errors): RE: Closing
Processing commands for cont...@bugs.debian.org:
> reopen 610507
Bug #610507 {Done: Moritz Mühlenhoff } [linux-2.6]
squeeze/amd64 kernel: 180 seconds timeout when booting
Bug reopened
Ignoring request to alter fixed versions of bug #610507 to the same values
previously set
> Hi, I can reproduce #610507 with Wheezy and kernel 3.2.0-4-amd64
Unknown command or malformed arguments to command.
> The following command fixes the problem:
Unknown command or malformed arguments to command.
> # echo 'blacklist ipmi_si' > /etc/modprobe.d/ipmi.conf
> With kind regards,
Unknown command or malformed arguments to command.
> Fabrice Aeschbacher
Unknown command or malformed arguments to command.
> > -Original Message-
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.
Please contact me if you need assistance.
--
610507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137327445527547.transcr...@bugs.debian.org
Bug#713943: linux-image-3.9-1-powerpc64: windfarm module is not working any more
I confirm. Fans are crazy with Debian's 3.9-1 kernel.
Processed: reopen 610507
Processing commands for cont...@bugs.debian.org: > reopen 610507 Bug #610507 [linux-2.6] squeeze/amd64 kernel: 180 seconds timeout when booting Bug 610507 is not marked as done; doing nothing. > reassign 610507 src:linux Bug #610507 [linux-2.6] squeeze/amd64 kernel: 180 seconds timeout when booting Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions linux-2.6/2.6.32-30. Ignoring request to alter fixed versions of bug #610507 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 610507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13732760307611.transcr...@bugs.debian.org
Bug#610507: reproduce #610507 with Wheezy + fix with blacklist
Hi, I can reproduce #610507 with Wheezy and kernel 3.2.0-4-amd64 on the same hardware (Intel Xeon W3530 4 cores) The following command eliminates the timeout: # echo 'blacklist ipmi_si' > /etc/modprobe.d/ipmi.conf With kind regards, Fabrice Aeschbacher -- 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/09d9be2ac4aa764dabaa8c91e48d819e033b37e...@demchp99e35msx.ww902.siemens.net
Processed: Re: Bug#666386: closed by Moritz Mühlenhoff (Closing)
Processing commands for cont...@bugs.debian.org: > reassign 666386 src:linux Bug #666386 [src:linux-2.6] vlan over bridge largely broken but NETIF_F_VLAN_CHALLENGED not set Warning: Unknown package 'src:linux-2.6' Bug reassigned from package 'src:linux-2.6' to 'src:linux'. No longer marked as found in versions linux-2.6/2.6.32-41. Ignoring request to alter fixed versions of bug #666386 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 666386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137327733315697.transcr...@bugs.debian.org
Bug#701744: Xen netback regression
Ian Campbell wrote: > I've put my test builds for both squeeze- and wheezy-security up at > http://xenbits.xen.org/people/ianc/debian/701774/ Short answer: linux-image-2.6.32-5-xen-amd64_2.6.32-48squeeze4~ijc0_amd64.deb solves my problem (bonding packet loss). Tests: - 2 nodes with base install of squeeze - apt-get install xen-linux-system ifenslave-2.6 - each node has one single head and one dual head NIC: root@xen02:/# dmesg | grep eth [0.795296] e1000e :05:00.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:19:d1:a3:e9:0d [0.795299] e1000e :05:00.0: eth0: Intel(R) PRO/1000 Network Connection [0.795368] e1000e :05:00.0: eth0: MAC: 2, PHY: 2, PBA No: FF-0FF [0.869452] igb :02:00.0: eth1: (PCIe:2.5Gb/s:Width x4) 00:1b: 21:aa:07:10 [0.869743] igb :02:00.0: eth1: PBA No: G18758-001 [1.079555] igb :02:00.1: eth2: (PCIe:2.5Gb/s:Width x4) 00:1b: 21:aa:07:11 [1.079846] igb :02:00.1: eth2: PBA No: G18758-001 02:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) - the dual head NICs are configured as bond1 pointopoint: iface bond1 inet static bond-slaves eth1 eth2 bond-mode 0 bond-miimon 100 bond-primary eth1 eth2 address 10.10.10.12 netmask 255.255.255.0 network 10.10.10.255 pointopoint 10.10.10.10 Test1: node xen01 runs linux-image-2.6.32-5-xen-amd64_2.6.32-45_amd64 node xen02 runs linux-image-2.6.32-5-xen-amd64_2.6.32-48squeeze3_amd64 root@xen02:/home/helmutw# ping 10.10.10.10 [...] ^C --- 10.10.10.10 ping statistics --- 10 packets transmitted, 7 received, 30% packet loss, time 9022ms rtt min/avg/max/mdev = 0.026/0.027/0.029/0.003 ms Test2: both nodes run linux-image-2.6.32-5-xen-amd64_2.6.32-48squeeze3_amd64 packet loss: 100% Test3: node xen01 runs linux-image-2.6.32-5-xen-amd64_2.6.32-45_amd64 node xen02 runs linux-image-2.6.32-5-xen- amd64_2.6.32-48squeeze4~ijc0_amd64 packet loss: 0% Test4: both nodes run linux-image-2.6.32-5-xen- amd64_2.6.32-48squeeze4~ijc0_amd64 packet loss: 0% Obviously these tests say nothing about the other reported problems. Helmut Wollmersdorfer
Bug#709632: Acknowledgement (gssd: Ignore a preferred_realm specified via the -R option)
Hi, the attached patch has been accept in upstream GIT (see [42]). Will someone apply it for Wheezy (and maybe Squeeze?). Thanks and best regards Max [42] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=a402f768db1dc6497cf7f592b33e142936897de2 -- The real problem with C++ for kernel modules is: the language just sucks. -- Linus Torvalds -- 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/20130708093654.gb3...@principal.rfc2324.org
Bug#715364: linux: severe virtualisation regression: cannot boot CentOS 5 guests
Package: src:linux Version: 3.9.8-1 Severity: important Also listed at https://bugzilla.redhat.com/show_bug.cgi?id=965711 I wanted to keep track of this problem in Debian: There is a difference between qemu-system-x86_64 -cdrom CentOS-5.9-x86_64-netinstall.iso and qemu-system-x86_64 -cdrom CentOS-5.9-x86_64-netinstall.iso -enable-kvm meaning that the latter exhibits the problem. Setup is Debian sid or testing: ii qemu-system-x86 1.5.0+dfsg-4i386QEMU full system emulation binaries (x86) Linux tglase.lan.tarent.de 3.9-1-amd64 #1 SMP Debian 3.9.6-1 i686 GNU/Linux Linux ldegen-wirt.lan.tarent.de 3.9-1-amd64 #1 SMP Debian 3.9.6-1 x86_64 GNU/Linux A “ceteris paribus” reboot into the stable Debian kernel makes things work with -enable-kvm (and blazingly fast compared to without it): Linux ldegen-wirt.lan.tarent.de 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux (That ISO image above can be found by duckduckgoïng around easily.) -- Package-specific info: ** Version: Linux version 3.9-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-4) ) #1 SMP Debian 3.9.6-1 ** Command line: BOOT_IMAGE=/vmlinuz-3.9-1-amd64 root=/dev/mapper/vg--tglase-lv--tglase--root ro ** Not tainted ** Kernel log: [571156.094736] scsi6 : usb-storage 10-1:1.0 [571156.094875] usbcore: registered new interface driver usb-storage [571156.094879] USB Mass Storage support registered. [571157.097284] scsi scan: INQUIRY result too short (5), using 36 [571157.097297] scsi 6:0:0:0: Direct-Access PQ: 0 ANSI: 0 [571157.099205] sd 6:0:0:0: Attached scsi generic sg6 type 0 [571157.102534] sd 6:0:0:0: [sdf] 15523840 512-byte logical blocks: (7.94 GB/7.40 GiB) [571157.105538] sd 6:0:0:0: [sdf] Write Protect is off [571157.105546] sd 6:0:0:0: [sdf] Mode Sense: 00 06 00 00 [571157.108525] sd 6:0:0:0: [sdf] Asking for cache data failed [571157.108532] sd 6:0:0:0: [sdf] Assuming drive cache: write through [571157.123522] sd 6:0:0:0: [sdf] Asking for cache data failed [571157.123529] sd 6:0:0:0: [sdf] Assuming drive cache: write through [571157.127783] sdf: sdf1 [571157.151881] sd 6:0:0:0: [sdf] Asking for cache data failed [571157.151889] sd 6:0:0:0: [sdf] Assuming drive cache: write through [571157.151896] sd 6:0:0:0: [sdf] Attached SCSI removable disk [571158.353358] usb 10-1: USB disconnect, device number 3 [622548.181531] ICMPv6 checksum failed [2a01:0198:0200:00ee::::0001 > 2a01:0238:4200:4342:321e:80ff:fe12:4223] [666059.421169] do_general_protection: 66 callbacks suppressed [666059.421176] traps: ld-linux-x32.so[11153] general protection ip:f7792e9d sp:ffa18948 error:0 in ld-2.17.so[f777c000+21000] [666059.438679] traps: ld-linux-x32.so[11167] general protection ip:f77d3e9d sp:ffb0f638 error:0 in ld-2.17.so[f77bd000+21000] [667233.354940] traps: ld-linux-x32.so[23354] general protection ip:f7734e9d sp:ffc90d38 error:0 in ld-2.17.so[f771e000+21000] [667233.423954] traps: ld-linux-x32.so[23398] general protection ip:f774ae9d sp:ffaa5738 error:0 in ld-2.17.so[f7734000+21000] [667233.456890] traps: ld-linux-x32.so[23418] general protection ip:f771ae9d sp:ffd2acb8 error:0 in ld-2.17.so[f7704000+21000] [667233.465266] traps: ld-linux-x32.so[23426] general protection ip:f77d6e9d sp:ff8aacb8 error:0 in ld-2.17.so[f77c+21000] [667233.476270] traps: ld-linux-x32.so[23434] general protection ip:f7719e9d sp:ffd2a508 error:0 in ld-2.17.so[f7703000+21000] [667233.569668] traps: ld-linux-x32.so[23460] general protection ip:f77cae9d sp:ffe85568 error:0 in ld-2.17.so[f77b4000+21000] [667233.592012] traps: ld-linux-x32.so[23480] general protection ip:f7795e9d sp:ffbd7b58 error:0 in ld-2.17.so[f777f000+21000] [667233.601626] traps: ld-linux-x32.so[23488] general protection ip:f77d7e9d sp:ffbc4558 error:0 in ld-2.17.so[f77c1000+21000] [667233.612896] traps: ld-linux-x32.so[23496] general protection ip:f7743e9d sp:fff89b98 error:0 in ld-2.17.so[f772d000+21000] [667233.670763] traps: ld-linux-x32.so[23528] general protection ip:f7715e9d sp:ffbaa0a8 error:0 in ld-2.17.so[f76ff000+21000] [766561.488166] do_general_protection: 12 callbacks suppressed [766561.488174] traps: ld-linux-x32.so[17684] general protection ip:f7796e9d sp:ff95a668 error:0 in ld-2.17.so[f778+21000] [766561.498032] traps: ld-linux-x32.so[17692] general protection ip:f77ebe9d sp:ffb990b8 error:0 in ld-2.17.so[f77d5000+21000] [766561.503681] traps: ld-linux-x32.so[17700] general protection ip:f7785e9d sp:fffba718 error:0 in ld-2.17.so[f776f000+21000] [766561.513520] traps: ld-linux-x32.so[17708] general protection ip:f7767e9d sp:ffe21368 error:0 in ld-2.17.so[f7751000+21000] [766561.622705] traps: ld-linux-x32.so[17722] general protection ip:f7726e9d sp:ff87f228 error:0 in ld-2.17.so[f771+21000] [766561.633846] traps: ld-linux-x32.so[17730] general protection ip:f773ee9d sp:ffdc59a8 error:0 in ld-2.17.so[f7728000+21000] [766561.642499] traps: ld-linux-x32.so[177
Bug#715370: linux-image-3.9-1-486: CONFIG_GPIO_CS5535 has been set to 'y' when it should be 'M'
Package: linux-image-3.9-1-486 Severity: important # # PCI GPIO expanders: # CONFIG_GPIO_CS5535=y # CONFIG_GPIO_AMD8111 is not set # CONFIG_GPIO_LANGWELL is not set CONFIG_GPIO_PCH=m CONFIG_GPIO_ML_IOH=m that should be "M". linux 3.2.0 and above moved over to scx200_acb and linux 3.9.0 and above moved over to scx200_gpio, which are incompatible with gpio_cs5535. by compiling in GPIO_CS5535 as a forced install it could potentially be interfering with scx200, which can no longer reserve access to the chip base. as it's compiled in, it's also impossible to pass in the mask parameter except as a boot-time kernel command-line option. -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.9.0 (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 -- 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/20130708130100.5730.32042.report...@zoo.pathintelligence.com
Bug#714974: NFS 'readdir loop' error on JFS
Hi Ben, I remember hitting this problem as I was working on the new-ish readdir code. The problem has to do with the readdir cookies generated by JFS. In a large directory the same cookie might be reused to refer to different files, and this can confuse the client (it entered an infinite loop before Trond came up with the loop detection). I ended up switching to ext4 to finish the project. - Bryan On Sun, Jul 7, 2013 at 9:13 PM, Ben Hutchings wrote: > Jonathan McDowell and Karl Schmidt reported that when sharing a JFS > filesystem through NFS and Samba, NFS clients can report 'readdir loop' > and the directories in question then appear to have duplicate entries on > the client system. > > This was seen with Linux 3.2 on the server and client. The JFS > directory code is basically unchanged since then, but NFS has changed > somewhat. > > The original bug reports were: > http://bugs.debian.org/685407#85 > http://bugs.debian.org/714974 > > The log messages are: > [593351.877678] NFS: directory fs/nfsd contains a readdir loop.Please contact > your server vendor. The file: .nfs3proc.o.cmda.com has duplicate cookie 73 > [593351.904689] NFS: directory fs/nfsd contains a readdir loop.Please contact > your server vendor. The file: .nfs3proc.o.cmda.com has duplicate cookie 73 > [280774.570555] NFS: directory //accounting contains a readdir loop.Please > contact your server vendor. The file: .~lock.credit.rtf1.rtf# has duplicate > cookie 199 > > Is this likely to be a problem with JFS, the NFS client or server? Can > anyone suggest how to investigate this further? > > Ben. > > -- > Ben Hutchings > It is easier to write an incorrect program than to understand a correct one. -- 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/camfxnowpmubjlbcntcm5-fb9ssmaeuxs1hsjvb7x70fonvy...@mail.gmail.com
Bug#648155: nfs-common: nfs mount hangs when kerberos ticket expires.
The bug is still present on latest "stable" wheezy. This is quite annoying since this make NFS4+Kerberos almost unusable where users have the opportunity to put their computer to sleep -- and the Kerberos ticket expires during the sleep period. If I understand it well, this is a "kernel bug". Is there any hope the proposed patch made its way in Wheezy's kernel? As a side node, is this a duplicate of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446238 ? -- 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/51dad062.7010...@chicoree.fr
Bug#715370: Acknowledgement (linux-image-3.9-1-486: CONFIG_GPIO_CS5535 has been set to 'y' when it should be 'M')
right. having enormous difficulty tracking this down, but there appears to be some kernel config dependencies of CONFIG_GPIO_CS5535 which are set to "Y" which are forcing CONFIG_GPIO_CS5535 to "y". ... but that actually turns out not to be the main problem: the main problem is that although GPIO_CS5535 has been converted (since 3.2.0) to the standard GPIO format, CONFIG_GPIO_SYSFS isn't set, making it impossible to gain access to it! as this is for an AMD Geode LX (PC-Engines alix6f2), gaining access to the GPIO in order to pull relays, change the LED status and so on, is somewhat essential. could i therefore request that CONFIG_GPIO_SYSFS be set to Y so that GPIO - which is protected by having to explicitly take action in userspace in order to gain access to it anyway - is accessible? l. -- 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/capweedwgenjyjxww6fxg3npx+bd_bessb8mpgffmxnc9fas...@mail.gmail.com
Bug#714974: NFS 'readdir loop' error on JFS
On 07/07/2013 08:13 PM, Ben Hutchings wrote: Jonathan McDowell and Karl Schmidt reported that when sharing a JFS filesystem through NFS and Samba, NFS clients can report 'readdir loop' and the directories in question then appear to have duplicate entries on the client system. This was seen with Linux 3.2 on the server and client. The JFS directory code is basically unchanged since then, but NFS has changed somewhat. The original bug reports were: http://bugs.debian.org/685407#85 http://bugs.debian.org/714974 The log messages are: [593351.877678] NFS: directory fs/nfsd contains a readdir loop.Please contact your server vendor. The file: .nfs3proc.o.cmda.com has duplicate cookie 73 [593351.904689] NFS: directory fs/nfsd contains a readdir loop.Please contact your server vendor. The file: .nfs3proc.o.cmda.com has duplicate cookie 73 [280774.570555] NFS: directory //accounting contains a readdir loop.Please contact your server vendor. The file: .~lock.credit.rtf1.rtf# has duplicate cookie 199 Is this likely to be a problem with JFS, the NFS client or server? Can anyone suggest how to investigate this further? Ben. The experiment with NFS client on Windozs XP was bad - very poor performance. I'm told that it might work better in Windoze 7 - removed and back to samba. For now, I am not having problems after commenting out this line in smb.conf #strict locking = yes Previously, I had already commented out : #oplocks = no #level2oplocks = no But could still reproduce the problem. I'm not sure it is fixed as there were time before when all worked well for some weeks before the errors turned. Question: Is samba still using NLM protocol to lock files? ( I think NFS no longer uses that? ) ,.,.,. I've did find a different error during all this testing -included here as it might be related - perhaps due to the last nfs update. in /etc/exports the server called malaysia we have: /home/accounting 192.168.1.0/24(rw,sync,no_root_squash,no_all_squash) fstab on a Debian wheezy client: malaysia:/home/accounting/mnt/accounting nfs defaults,rsize=8192,wsize=8192,intr 0 0 /mnt# ll total 112 drwxrwsrwx 16 nobody nogroup 4096 2013-07-08 08:00 accounting/ This is wrong.. I think this may have to do with a bug workaround where the installer added 27.0.1.1 to the /etc/hosts file ? Then there is /etc/idmapd and /etc/defaults/nfs-common on the client that I didn't used to have to mess with? It is also important to have the fqdn as the first name in /etc/hosts hostname --fqdn is correct on both machines I think this might have to do with a fix for CVE-2013-1923 The changes I made included adding NEED_IDMAPD=yes to /etc/defaults/nfs-common And removing no_all_squash which is now the default. Is NEED_IDMAPD=yes now needed as reverse lookups have been turned off? The debian wiki needs updating to let people know they need to if this is really the case? It has been a long night.. Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://secure.transtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Wrapping people up in the symbols of success when they are unearned, is very destructive. kps -- 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/51dade1a.9040...@xtronics.com
Processed: reassign 566356 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 566356 src:linux Bug #566356 [linux-2.6] ntfs write support is useless Bug #581695 [linux-2.6] Disable vestigal NTFS write mode and print to STDERR when attempted Bug reassigned from package 'linux-2.6' to 'src:linux'. Bug reassigned from package 'linux-2.6' to 'src:linux'. Ignoring request to alter found versions of bug #566356 to the same values previously set Ignoring request to alter found versions of bug #581695 to the same values previously set Ignoring request to alter fixed versions of bug #566356 to the same values previously set Ignoring request to alter fixed versions of bug #581695 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 566356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566356 581695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137329964425632.transcr...@bugs.debian.org
Processed: reassign 666556 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 666556 src:linux Bug #666556 [src:linux-2.6] Please enable Intel Sandy-Bridge Integrated MC CONFIG_EDAC_SBRIDGE Warning: Unknown package 'src:linux-2.6' Bug reassigned from package 'src:linux-2.6' to 'src:linux'. No longer marked as found in versions linux-2.6/3.2.12-1. Ignoring request to alter fixed versions of bug #666556 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 666556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137329963625575.transcr...@bugs.debian.org
Processed: reassign 671874 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 671874 src:linux Bug #671874 [linux-2.6] linux-2.6: build nfs-modules udeb for amd64 Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 3.2.15-1. Ignoring request to alter fixed versions of bug #671874 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 671874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137329963525558.transcr...@bugs.debian.org
Processed: reassign 603957 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 603957 src:linux Bug #603957 [linux-2.6] linux-2.6: consider raising CONFIG_HZ to 1000 Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 2.6.32-27. Ignoring request to alter fixed versions of bug #603957 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 603957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137329967725823.transcr...@bugs.debian.org
Processed: reassign 640953 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 640953 src:linux Bug #640953 [linux-2.6] linux-image-3.0.0-1-amd64: CONFIG_KPROBE_EVENT is not set Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 3.0.0-3. Ignoring request to alter fixed versions of bug #640953 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 640953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137329965025668.transcr...@bugs.debian.org
Processed: reassign 635899 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 635899 src:linux Bug #635899 [linux-2.6] Please disable CC_OPTIMIZE_FOR_SIZE Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 3.0.0-1. Ignoring request to alter fixed versions of bug #635899 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 635899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137329966325739.transcr...@bugs.debian.org
Processed: reassign 577736 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 577736 src:linux Bug #577736 [linux-2.6] linux-2.6: [gencontrol.py] Allow additional "Provides" for headers and source the same way as for image in featuresets Bug reassigned from package 'linux-2.6' to 'src:linux'. Ignoring request to alter found versions of bug #577736 to the same values previously set Ignoring request to alter fixed versions of bug #577736 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 577736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137329968425903.transcr...@bugs.debian.org
Processed: reassign 660288 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 660288 src:linux Bug #660288 [linux-2.6] Please enable CONFIG_KALLSYMS_ALL Bug reassigned from package 'linux-2.6' to 'src:linux'. Ignoring request to alter found versions of bug #660288 to the same values previously set Ignoring request to alter fixed versions of bug #660288 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 660288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137329965625705.transcr...@bugs.debian.org
Processed: reassign 616401 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 616401 src:linux Bug #616401 [linux-2.6] linux-image-2.6.38-rc6-amd64: Please enable FTRACE_SYSCALLS Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 2.6.38~rc6-1~experimental.1. Ignoring request to alter fixed versions of bug #616401 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 616401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137329966925787.transcr...@bugs.debian.org
Processed: reassign 676779 to src:linug
Processing commands for cont...@bugs.debian.org: > reassign 676779 src:linug Bug #676779 [linux-2.6] linux-image-3.2.0-2-kirkwood: Please enable CONFIG_ZRAM=m Bug reassigned from package 'linux-2.6' to 'src:linug'. Warning: Unknown package 'src:linug' Warning: Unknown package 'src:linug' No longer marked as found in versions 3.2.18-1. Warning: Unknown package 'src:linug' Warning: Unknown package 'src:linug' Ignoring request to alter fixed versions of bug #676779 to the same values previously set Warning: Unknown package 'src:linug' > thanks Stopping processing here. Please contact me if you need assistance. -- 676779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137330045430392.transcr...@bugs.debian.org
Processed: reassign 678731 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 678731 src:linux Bug #678731 [linux-2.6] linux-2.6: Please build dummy_hcd and g_mass_storage modules Bug reassigned from package 'linux-2.6' to 'src:linux'. Ignoring request to alter found versions of bug #678731 to the same values previously set Ignoring request to alter fixed versions of bug #678731 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 678731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137330049530624.transcr...@bugs.debian.org
Processed: reassign 676779 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 676779 src:linux Bug #676779 [src:linug] linux-image-3.2.0-2-kirkwood: Please enable CONFIG_ZRAM=m Warning: Unknown package 'src:linug' Bug reassigned from package 'src:linug' to 'src:linux'. Ignoring request to alter found versions of bug #676779 to the same values previously set Ignoring request to alter fixed versions of bug #676779 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 676779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137330045630408.transcr...@bugs.debian.org
Processed: retitle 676779 to Please enable CONFIG_ZRAM=m for archs other than x86
Processing commands for cont...@bugs.debian.org: > retitle 676779 Please enable CONFIG_ZRAM=m for archs other than x86 Bug #676779 [src:linux] linux-image-3.2.0-2-kirkwood: Please enable CONFIG_ZRAM=m Changed Bug title to 'Please enable CONFIG_ZRAM=m for archs other than x86' from 'linux-image-3.2.0-2-kirkwood: Please enable CONFIG_ZRAM=m' > thanks Stopping processing here. Please contact me if you need assistance. -- 676779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137330048530576.transcr...@bugs.debian.org
Bug#678731: linux-2.6: Please build dummy_hcd and g_mass_storage modules
On Thu, Jun 28, 2012 at 09:48:19PM +0200, intrigeri wrote: > Hi, > > berta...@ptitcanardnoir.org wrote (27 Jun 2012 11:00:22 GMT) : > > On Wed, Jun 27, 2012 at 04:32:31AM +0100, Ben Hutchings wrote: > > >> Yes, but I think it would make more sense to emulate a USB storage > >> device in qemu rather than the host kernel. > > I do agree. > > bertagaz and I have spent a bit more time testing and comparing the > available options. Our results are summed up there: > https://tails.boum.org/todo/automated_builds_and_tests/USB/ > > tl;dr --> as far as Wheezy is concerned: > * qemu-kvm emulates just fine a USB 2.0 mass storage device, and > knows how to boot from it; personally, I'd rather use that than > a dedicated kernel module. > * with qemu-kvm on the command-line: no need for an additional > kernel module > * with a libvirt stack: a missing interface in some abstraction > layer makes it a pain to use the qemu-kvm USB emulation of > removable mass storage devices. How's the state of affairs with libvirt 1.1 from unstable? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130708162252.GA6647@pisco.westfalen.local
Processed: reassign 678731 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 678731 src:linux Bug #678731 [src:linux] linux-2.6: Please build dummy_hcd and g_mass_storage modules Ignoring request to reassign bug #678731 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 678731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137330066931861.transcr...@bugs.debian.org
Bug#666556: marked as done (Please enable Intel Sandy-Bridge Integrated MC CONFIG_EDAC_SBRIDGE)
Your message dated Mon, 8 Jul 2013 18:32:37 +0200 with message-id <20130708163237.ga22...@inutil.org> and subject line Re: Bug#666556: Please enable Intel Sandy-Bridge Integrated MC CONFIG_EDAC_SBRIDGE has caused the Debian Bug report #666556, regarding Please enable Intel Sandy-Bridge Integrated MC CONFIG_EDAC_SBRIDGE 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.) -- 666556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux-2.6 Version: 3.2.12-1 Severity: normal Hello, Please enable the support for the Intel Sandy-Bridge memory controller for EDAC so we can take advantage of ECC ram modules on this platform. Just set CONFIG_EDAC_SBRIDGE=m in the .config Thanks! -- ~~~ Carlos Alberto Lopez Perez http://neutrino.es Igalia - Free Software Engineeringhttp://www.igalia.com ~~~ signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 3.2.39-1 On Sun, Apr 01, 2012 at 07:20:11AM +0100, Ben Hutchings wrote: > On Sat, 2012-03-31 at 19:30 +0200, Carlos Alberto Lopez Perez wrote: > > Source: linux-2.6 > > Version: 3.2.12-1 > > Severity: normal > > > > > > Hello, > > > > > > Please enable the support for the Intel Sandy-Bridge memory controller > > for EDAC so we can take advantage of ECC ram modules on this platform. > > As you may know, EDAC is not required for ECC. It does improve error > reporting and helps you to identify faulty modules. > > > Just set CONFIG_EDAC_SBRIDGE=m in the .config > > The driver is marked as experimental and there are several important bug > fixes post-3.2. If we enable it, we also need to apply those bug fixes > and possibly others. This was enabled in 3.2.39. Cheers, Moritz--- End Message ---
Bug#679094: marked as done (linux-image-3.4-trunk-amd64: 3.2, 3.3 and 3.4 debian kernels lack latencytop support)
Your message dated Mon, 8 Jul 2013 18:44:20 +0200 with message-id <20130708164420.ga23...@inutil.org> and subject line Re: Bug#679094: linux-image-3.4-trunk-amd64: 3.2, 3.3 and 3.4 debian kernels lack latencytop support has caused the Debian Bug report #679094, regarding linux-image-3.4-trunk-amd64: 3.2, 3.3 and 3.4 debian kernels lack latencytop support 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.) -- 679094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 3.4.1-1~experimental.1 Severity: normal Dear Maintainer, On reporting latencytop: fails with error "no protocol specified" I found: http://bugs.debian.org/679091 I found: ms@mango:~> sux Passwort: xauth: file /root/.Xauthority does not exist bash: Kann die Prozessgruppe des Terminals nicht setzen (-1).: Unpassender IOCTL (I/O-Control) für das Gerät bash: Keine Job Steuerung in dieser Shell. mango:/home/ms# latencytop mount: none already mounted or /sys/kernel/debug/ busy mount: according to mtab, none is already mounted on /sys/kernel/debug Please enable the CONFIG_LATENCYTOP configuration in your kernel. Exiting... The current Debian kernels all lack latencytop support: mango:~# grep LATENCY /boot/config-* /boot/config-3.2.0-2-amd64:CONFIG_HAVE_LATENCYTOP_SUPPORT=y /boot/config-3.2.0-2-amd64:# CONFIG_LATENCYTOP is not set /boot/config-3.3.0-trunk-amd64:CONFIG_HAVE_LATENCYTOP_SUPPORT=y /boot/config-3.3.0-trunk-amd64:# CONFIG_LATENCYTOP is not set /boot/config-3.4-trunk-amd64:CONFIG_HAVE_LATENCYTOP_SUPPORT=y /boot/config-3.4-trunk-amd64:# CONFIG_LATENCYTOP is not set Please consider activating this support again. Otherwise someone who wants to use latencytop needs to recompile the kernel which greatly reduces the usefulness of the latencytop package. Thanks, Martin -- Package-specific info: ** Version: Linux version 3.4-trunk-amd64 (Debian 3.4.1-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Wed Jun 6 10:34:53 CEST 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.4-trunk-amd64 root=UUID=459c3940-f915-460f-a673-386121d7a8c6 ro resume=/dev/sda7 no_console_suspend ** Tainted: WO (4608) * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [ 8225.257334] e1000e :00:19.0: irq 40 for MSI/MSI-X [ 8225.257337] snd_hda_intel :00:1b.0: irq 43 for MSI/MSI-X [ 8225.257376] ehci_hcd :00:1d.0: setting latency timer to 64 [ 8225.257389] usb usb2: root hub lost power or was reset [ 8225.257396] pci :00:1e.0: setting latency timer to 64 [ 8225.257413] ahci :00:1f.2: setting latency timer to 64 [ 8225.261287] ehci_hcd :00:1d.0: cache line size of 32 is not supported [ 8225.306523] parport_pc 00:0a: activated [ 8225.306774] serial 00:0b: activated [ 8225.577530] ata8: SATA link down (SStatus 0 SControl 300) [ 8225.577561] ata7: SATA link down (SStatus 0 SControl 300) [ 8225.577591] ata5: SATA link down (SStatus 0 SControl 300) [ 8225.613435] usb 1-1: reset high-speed USB device number 2 using ehci_hcd [ 8225.749017] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8225.749107] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8225.749137] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 8225.752692] ata4.00: configured for UDMA/100 [ 8225.755299] ata3.00: configured for UDMA/133 [ 8225.755417] sd 2:0:0:0: [sda] Starting disk [ 8225.757292] ata6.00: configured for UDMA/133 [ 8225.757367] sd 5:0:0:0: [sdb] Starting disk [ 8225.856806] usb 2-1: reset high-speed USB device number 2 using ehci_hcd [ 8226.060330] usb 1-1.4: reset high-speed USB device number 3 using ehci_hcd [ 8227.038062] usb 2-1.8: reset low-speed USB device number 4 using ehci_hcd [ 8227.576710] usb 2-1.7: reset low-speed USB device number 3 using ehci_hcd [ 8227.870701] PM: restore of devices complete after 2624.032 msecs [ 8227.870807] PM: Image restored successfully. [ 8227.870809] Restarting tasks ... done. [ 8227.873014] PM: Basic memory bitmaps freed [ 8228.008570] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx [ 8903.147658] scsi_verify_blk_ioctl: 444 callbacks suppressed [ 8903.147664] mdadm: sending ioctl 1261 to a partition! [ 8903.147668] mdadm: sending ioctl 1261 to a partition! [ 8903.294210] mdadm: sending ioctl 1261 to a partition! [ 8903.294217] mdadm: sending ioctl 1261 to a partition! [ 8903.385724] mdadm: sending ioctl 1261 to a partition! [ 8903.385728] mdadm: sending ioctl 1261 to a partition! [ 8903.489773] mdadm: sending ioctl
Bug#645869: marked as done (linux-2.6: keep kernel.sched_autogroup_enabled setting default (to 1))
Your message dated Mon, 8 Jul 2013 18:43:21 +0200 with message-id <20130708164321.ga22...@inutil.org> and subject line Re: Bug#645869: linux-2.6: keep kernel.sched_autogroup_enabled setting default (to 1) has caused the Debian Bug report #645869, regarding linux-2.6: keep kernel.sched_autogroup_enabled setting default (to 1) 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.) -- 645869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 3.0.0-6 Severity: wishlist Hey, since few versions, linux-2.6 uses an “autogroup" scheduling setting, which is supposed to improve the responsiveness, especially for desktop session. Upstream enables it by default, and there's a sysctl (kernel.sched_autogroup_enabled) to disable it in case it causes issues. Debian ships a patch (debian/patches/debian/sched-autogroup-disabled.patch) which changes the default to disabled. I'm not too sure what is the rationale for changing the default, but I think it'd be nice to revert that and keep upstream default, unless there are good reasons to divert from them. Regards, -- Yves-Alexis -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On Wed, Oct 19, 2011 at 01:55:32PM +0100, Ben Hutchings wrote: > On Wed, 2011-10-19 at 10:10 +0200, Yves-Alexis Perez wrote: > > Package: linux-2.6 > > Version: 3.0.0-6 > > Not yet released, so you can't tell whether this will be changed! > > > Severity: wishlist > > > > Hey, > > > > since few versions, linux-2.6 uses an “autogroup" scheduling setting, which > > is supposed to improve the responsiveness, especially for desktop session. > > > > Upstream enables it by default, and there's a sysctl > > (kernel.sched_autogroup_enabled) to disable it in case it causes issues. > > > > Debian ships a patch (debian/patches/debian/sched-autogroup-disabled.patch) > > which changes the default to disabled. > > > > I'm not too sure what is the rationale for changing the default, but I think > > it'd be nice to revert that and keep upstream default, unless there are good > > reasons to divert from them. > > The upstream default is that it is disabled at compile-time, since > SCHED_AUTOGROUP is not 'default y' or selected by any other option. > > Our default matches this but adds the option to enable it at run-time. Closing the bug, since we're following the upstream default here. Yves-Alexis, maybe the desktop meta packages (XFCE, Gnome, KDE) could set the sysctl setting? Cheers, Moritz--- End Message ---
Bug#598535: marked as done (error messages on resume)
Your message dated Mon, 8 Jul 2013 19:40:05 +0200 with message-id <20130708174005.GA7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #598535, regarding error messages on resume 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.) -- 598535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-23 Severity: minor File: /boot/vmlinuz-2.6.32-5-686 suspend to ram works pretty reliably for me. That said, on resume I get a bunch of error messages on vt63 [...] btusb_intr_complete: hci0 urb eeaef280 failed to resubmit (1) [...] btusb_intr_complete: hci0 urb eeaefb80 failed to resubmit (1) [...] btusb_intr_complete: hci0 urb eeaef100 failed to resubmit (1) [...] codec_write 0: semaphore is not ready for register 0x26 [...] pm_op(): pci_pm_resume+0x0/0x60 returns -16 [...] PM: Device :00:00.0 failed to resume async: error -16 Thanks for your work, Michael -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 03) Subsystem: Compaq Computer Corporation Device [0e11:0860] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: agpgart-intel 00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP Controller [8086:3341] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01) (prog-if 00 [UHCI]) Subsystem: Compaq Computer Corporation Device [0e11:0860] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 81) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge [8086:24cc] (rev 01) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: Intel ICH 00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller [8086:24c6] (rev 01) (prog-if 00 [Generic]) Subsystem: Compaq Computer Corporation Device [0e11:0860] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: Intel ICH Modem 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] [1002:4c66] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Compaq Computer Corporation Device [0e11:0860] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: radeon 02:00.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev 80) (prog-if 10 [OHCI]) Subsystem: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel d
Bug#603767: marked as done (gdm: starts on v8 instead of vt7)
Your message dated Mon, 8 Jul 2013 19:40:05 +0200 with message-id <20130708174005.GA7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #596700, regarding gdm: starts on v8 instead of vt7 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.) -- 596700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdm Severity: normal After upgrading from lenny to squeeze, gdm starts on vt8 always (even after restarting it). It should start on vt7 as this is the expected behaviour. -- System Information: Debian Release: 5.0.6 APT prefers stable APT policy: (900, 'stable'), (650, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#614667: marked as done (pm-utils: Annoying sound in internal speakers when pm-hibernate is true)
Your message dated Mon, 8 Jul 2013 19:40:37 +0200 with message-id <20130708174037.GB7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #614667, regarding pm-utils: Annoying sound in internal speakers when pm-hibernate is true 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.) -- 614667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pm-utils Version: 1.4.1-6 Severity: important Hi When the pm-hibernate is true starts a crunch in the internal speakers every second. The culprit is the script "intel-audio-powersave" in /usr/lib/pm-utils/power.d. If sound is active (using mumble o listening music) the sound disappears. lspci -v: 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02) Subsystem: Sony Corporation Device 81e6 Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at de40 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: HDA Intel Thanks. Sorry for my english. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (800, 'experimental'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pm-utils depends on: ii kbd 1.15.2-2 Linux console font and keytable ut ii powermgmt-base1.31 Common utils and configs for power Versions of packages pm-utils recommends: ii hdparm9.32-1 tune hard disk parameters for high ii procps1:3.2.8-10 /proc file system utilities ii vbetool 1.1-2 run real-mode video BIOS code to a Versions of packages pm-utils suggests: ii cpufrequtils 007-1 utilities to deal with the cpufreq ii ethtool 1:2.6.34-3 display or change Ethernet device ii radeontool1.6.1-1utility to control ATI Radeon back ii wireless-tools30~pre9-5 Tools for manipulating Linux Wirel -- no debconf information --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#610245: marked as done (shorewall: speed problem when using simple traffic control and a value for OUT-BANDWIDTH)
Your message dated Mon, 8 Jul 2013 19:40:37 +0200
with message-id <20130708174037.GB7214@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #610245,
regarding shorewall: speed problem when using simple traffic control and a
value for OUT-BANDWIDTH
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.)
--
610245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shorewall
Version: 4.4.16-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When using a tcinterfaces file that look like this
#INTERFACE TYPEIN-BANDWIDTHOUT-BANDWIDTH
eth0external9300kbit:100kb 9300kbit:100kb
does the limit work for in-bandwith, it becomes around 9Mb/s.
But it does not work for out-bandwidth, the out-bandwidth is limited to 0.2Mb/s,
not close to 9.3.
If the out-bandwith setting is removed does is work as normal, and the speed is
adount 9Mb/s.
- -- System Information:
Debian Release: 6.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages shorewall depends on:
ii bc1.06.95-2 The GNU bc arbitrary precision cal
ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy
ii iproute 20100519-3 networking and traffic control too
ii iptables 1.4.10-1 administration tools for packet fi
ii perl-modules 5.10.1-17 Core Perl modules
shorewall recommends no packages.
Versions of packages shorewall suggests:
ii linux-image-2.6.26-2-amd 2.6.26-26lenny1 Linux 2.6.26 image on AMD64
ii linux-image-2.6.32-5-amd 2.6.32-30 Linux 2.6.32 for 64-bit PCs
ii make 3.81-8 An utility for Directing compilati
pn shorewall-doc (no description available)
- -- Configuration Files:
/etc/default/shorewall changed:
startup=1
OPTIONS=""
/etc/shorewall/shorewall.conf changed:
STARTUP_ENABLED=Yes
VERBOSITY=1
LOGFILE=/var/log/firewall
STARTUP_LOG=/var/log/shorewall-init.log
LOG_VERBOSITY=2
LOGFORMAT="firewall: %s:%s:"
LOGTAGONLY=No
LOGLIMIT=60/min:20
LOGALLNEW=
BLACKLIST_LOGLEVEL=
MACLIST_LOG_LEVEL=info
TCP_FLAGS_LOG_LEVEL=info
SMURF_LOG_LEVEL=info
LOG_MARTIANS=Yes
IPTABLES=
IP=
TC=
IPSET=
PERL=/usr/bin/perl
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin
SHOREWALL_SHELL=/bin/sh
SUBSYSLOCK=""
MODULESDIR=
CONFIG_PATH=/etc/shorewall:/usr/share/shorewall
RESTOREFILE=
IPSECFILE=zones
LOCKFILE=
DROP_DEFAULT="Drop"
REJECT_DEFAULT="Reject"
ACCEPT_DEFAULT="none"
QUEUE_DEFAULT="none"
NFQUEUE_DEFAULT="none"
RSH_COMMAND='ssh ${root}@${system} ${command}'
RCP_COMMAND='scp ${files} ${root}@${system}:${destination}'
IP_FORWARDING=Off
ADD_IP_ALIASES=No
ADD_SNAT_ALIASES=No
RETAIN_ALIASES=No
TC_ENABLED=Simple
TC_EXPERT=No
TC_PRIOMAP="2 3 3 3 2 3 1 1 2 2 2 2 2 2 2 2"
CLEAR_TC=Yes
MARK_IN_FORWARD_CHAIN=No
CLAMPMSS=No
ROUTE_FILTER=Yes
DETECT_DNAT_IPADDRS=No
MUTEX_TIMEOUT=60
ADMINISABSENTMINDED=Yes
BLACKLISTNEWONLY=Yes
MODULE_SUFFIX=ko
DISABLE_IPV6=Yes
DYNAMIC_ZONES=No
PKTTYPE=Yes
NULL_ROUTE_RFC1918=No
MACLIST_TABLE=filter
MACLIST_TTL=
SAVE_IPSETS=No
MAPOLDACTIONS=No
FASTACCEPT=Yes
IMPLICIT_CONTINUE=No
HIGH_ROUTE_MARKS=No
OPTIMIZE=15
EXPORTPARAMS=Yes
EXPAND_POLICIES=Yes
KEEP_RT_TABLES=No
DELETE_THEN_ADD=Yes
MULTICAST=No
DONT_LOAD=
AUTO_COMMENT=Yes
MANGLE_ENABLED=Yes
USE_DEFAULT_RT=No
RESTORE_DEFAULT_ROUTE=Yes
AUTOMAKE=No
WIDE_TC_MARKS=No
TRACK_PROVIDERS=No
ZONE2ZONE=2
ACCOUNTING=No
DYNAMIC_BLACKLIST=Yes
OPTIMIZE_ACCOUNTING=Yes
LOAD_HELPERS_ONLY=No
REQUIRE_INTERFACE=No
FORWARD_CLEAR_MARK=
COMPLETE=No
BLACKLIST_DISPOSITION=DROP
MACLIST_DISPOSITION=REJECT
TCP_FLAGS_DISPOSITION=DROP
- -- debconf information:
shorewall/invalid_config:
shorewall/dont_restart:
shorewall/major_release:
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAk0zGxkACgkQw5UvgfnzqGowFgCgtEGvkovHkhwcaX2v0sWXXYxE
GJcAoL1g31XYkNtc0zPurRkQikbynINc
=k9MZ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.
We don't have the ressources to reproduce
Bug#607428: marked as done (linux-image-2.6.32-5-686: sound problem)
Your message dated Mon, 8 Jul 2013 19:40:05 +0200 with message-id <20130708174005.GA7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #607428, regarding linux-image-2.6.32-5-686: sound problem 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.) -- 607428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-29 Severity: minor I upgraded from lenny (xfce4) to squeeze on my laptop (acer aspire 5102 wlmi) I installed linux-image-2.6.32-5-686. All works fine except the sound : "alsamixer" doesn't give the option CD and "cdcd" works but no sound. (however sound-juicer works fine) lspci: 00:14.2 Audio device: ATI Technologies Inc IXP SB4x0 High Definition Audio Controller (rev 01) When I boot on the kernel 2.6.30 instead of the kernel 2.6.32-5-686, I get the option CD with "alsamixer" and "cdcd" works fine (with sound) And on the other hand I did the same upgrade (lenny -> squeeze with kernel 2.6.32-5-686) on a desktop and I didn't encounter this problem. I would like the sound on my laptop to work fine with the kernel 2.6.32-5-686. How can I do that ? Thanks in advance. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-29) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Dec 10 16:12:40 UTC 2010 ** Command line: root=UUID=1505c8bd-c890-4c4c-93e0-3fe16b2e6df0 ro quiet ** Not tainted ** Kernel log: [9.735593] [drm] radeon kernel modesetting enabled. [9.735691] radeon :01:05.0: power state changed by ACPI to D0 [9.735700] radeon :01:05.0: power state changed by ACPI to D0 [9.735717] radeon :01:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [9.737899] [drm] radeon: Initializing kernel modesetting. [9.738021] [drm] register mmio base: 0xC010 [9.738024] [drm] register mmio size: 65536 [9.738399] [drm] GPU reset succeed (RBBM_STATUS=0x0140) [9.738424] [drm:rs400_gart_adjust_size] *ERROR* Forcing to 32M GART size (because of ASIC bug ?) [9.738480] [drm] Generation 2 PCI interface, using max accessible memory [9.738484] [drm] radeon: VRAM 128M [9.738486] [drm] radeon: VRAM from 0x7800 to 0x7FFF [9.738489] [drm] radeon: GTT 32M [9.738491] [drm] radeon: GTT from 0x8000 to 0x81FF [9.738524] [drm] radeon: irq initialized. [9.738664] [drm] Detected VRAM RAM=128M, BAR=128M [9.738670] [drm] RAM width 128bits DDR [9.738766] [TTM] Zone kernel: Available graphics memory: 441954 kiB. [9.738770] [TTM] Zone highmem: Available graphics memory: 971654 kiB. [9.738794] [drm] radeon: 128M of VRAM memory ready [9.738796] [drm] radeon: 32M of GTT memory ready. [9.738819] [drm] GART: num cpu pages 8192, num gpu pages 8192 [9.739482] [drm] radeon: 4 quad pipes, 1 z pipes initialized. [9.739498] [drm] radeon: cp idle (0x1C03) [9.739544] [drm] Loading R300 Microcode [9.739547] platform radeon_cp.0: firmware: requesting radeon/R300_cp.bin [9.777003] phy0: Selected rate control algorithm 'minstrel' [9.777900] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) [9.830823] radeon_cp: Failed to load firmware "radeon/R300_cp.bin" [9.830874] [drm:r100_cp_init] *ERROR* Failed to load firmware! [9.830920] radeon :01:05.0: failled initializing CP (-2). [9.830964] radeon :01:05.0: Disabling GPU acceleration [9.831011] [drm] radeon: cp finalized [9.831148] [drm] Default TV standard: NTSC [9.831150] [drm] 14.31818 MHz TV ref clk [9.831232] [drm] Panel ID String: QDS [9.831236] [drm] Panel Size 1280x800 [9.831288] [drm] Radeon Display Connectors [9.831291] [drm] Connector 0: [9.831293] [drm] VGA [9.831296] [drm] DDC: 0x68 0x68 0x68 0x68 0x68 0x68 0x68 0x68 [9.831299] [drm] Encoders: [9.831301] [drm] CRT1: INTERNAL_DAC2 [9.831303] [drm] Connector 1: [9.831305] [drm] LVDS [9.831309] [drm] DDC: 0x198 0x198 0x19c 0x19c 0x1a0 0x1a0 0x1a4 0x1a4 [9.831311] [drm] Encoders: [9.831313] [drm] LCD1: INTERNAL_LVDS [9.920684] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean. [9.923094] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean. [9.924101] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [9.924921] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. [9.925884] pcmcia_socket pcmci
Bug#592487: marked as done (linux-image-2.6.32-5-xen-686: dom0 under virtualbox: APIC write causes WARNING)
Your message dated Mon, 8 Jul 2013 19:40:05 +0200 with message-id <20130708174005.GA7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #592487, regarding linux-image-2.6.32-5-xen-686: dom0 under virtualbox: APIC write causes WARNING 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.) -- 592487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-18 Severity: normal [0.004000] [ cut here ] [0.004000] WARNING: at /build/buildd-linux-2.6_2.6.32-18-i386-HNrmOz/linux-2.6-2.6.32/debian/build/source_i386_xen/arch/x86/xen/enlighten.c:731 perf_events_lapic_init+0x28/0x29() [0.004000] Hardware name: VirtualBox [0.004000] Modules linked in: [0.004000] Pid: 0, comm: swapper Not tainted 2.6.32-5-xen-686 #1 [0.004000] Call Trace: [0.004000] [] ? warn_slowpath_common+0x5e/0x8a [0.004000] [] ? warn_slowpath_null+0xa/0xc [0.004000] [] ? perf_events_lapic_init+0x28/0x29 [0.004000] [] ? init_hw_perf_events+0x2dd/0x376 [0.004000] [] ? check_bugs+0x8/0xd8 [0.004000] [] ? start_kernel+0x309/0x31d [0.004000] [] ? xen_start_kernel+0x615/0x61c [0.004000] [] ? print_local_APIC+0x61/0x380 [0.004000] ---[ end trace a7919e7f17c0a725 ]--- -- Package-specific info: ** Version: Linux version 2.6.32-5-xen-686 (Debian 2.6.32-18) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Sat Jul 24 07:00:17 UTC 2010 ** Command line: root=UUID=e4c2a533-6ef3-44dc-a990-7008664951a3 ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [3.318557] scsi 2:0:0:0: CD-ROMVBOX CD-ROM 1.0 PQ: 0 ANSI: 5 [3.384604] usb 2-1: new full speed USB device using ohci_hcd and address 2 [3.408181] sd 0:0:0:0: [sda] 41943040 512-byte logical blocks: (21.4 GB/20.0 GiB) [3.408335] sd 0:0:0:0: [sda] Write Protect is off [3.408341] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [3.408406] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.408750] sda: sda1 sda2 [3.450546] sd 0:0:0:0: [sda] Attached SCSI disk [3.587924] sd 0:0:0:0: Attached scsi generic sg0 type 0 [3.593307] sr 2:0:0:0: Attached scsi generic sg1 type 5 [3.669180] usb 2-1: New USB device found, idVendor=80ee, idProduct=0021 [3.669198] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 [3.669207] usb 2-1: Product: USB Tablet [3.669215] usb 2-1: Manufacturer: VirtualBox [3.669449] usb 2-1: configuration #1 chosen from 1 choice [3.749855] usbcore: registered new interface driver hiddev [3.766284] input: VirtualBox USB Tablet as /devices/pci:00/:00:06.0/usb2/2-1/2-1:1.0/input/input1 [3.766426] generic-usb 0003:80EE:0021.0001: input,hidraw0: USB HID v1.10 Mouse [VirtualBox USB Tablet] on usb-:00:06.0-1/input0 [3.766510] usbcore: registered new interface driver usbhid [3.766517] usbhid: v2.6:USB HID core driver [4.345200] PM: Starting manual resume from disk [4.345226] PM: Resume from partition 8:5 [4.345248] PM: Checking hibernation image. [4.349417] PM: Error -22 checking image file [4.349424] PM: Resume from disk failed. [4.478484] EXT4-fs (sda1): mounted filesystem with ordered data mode [6.237035] udev: starting version 158 [7.824810] input: PC Speaker as /devices/platform/pcspkr/input/input2 [8.103234] piix4_smbus :00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr [8.162426] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [8.162533] ACPI: Power Button [PWRF] [8.162681] input: Sleep Button as /devices/LNXSYSTM:00/LNXSLPBN:00/input/input4 [8.162723] ACPI: Sleep Button [SLPF] [8.194624] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input5 [8.378664] ACPI: AC Adapter [AC] (on-line) [8.638724] Error: Driver 'pcspkr' is already registered, aborting... [9.267065] xen: registering gsi 21 triggering 0 polarity 1 [9.267124] xen_allocate_pirq: returning irq 21 for gsi 21 [9.267169] xen: --> irq=21 [9.267228] Already setup the GSI :21 [9.267268] Intel ICH :00:05.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [9.267513] Intel ICH :00:05.0: setting latency timer to 64 [9.309777] parport_pc 00:04: reported by Plug and Play ACPI [ 10.169086] intel8x0_measure_ac97_clock: measured 180996 usecs (15636
Bug#627645: marked as done (linux-image-2.6.32-5-kirkwood: 'Out of memory and no killable processes...' when trying to run ld.bfd under gdb)
Your message dated Mon, 8 Jul 2013 19:40:37 +0200
with message-id <20130708174037.GB7214@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #627645,
regarding linux-image-2.6.32-5-kirkwood: 'Out of memory and no killable
processes...' when trying to run ld.bfd under gdb
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.)
--
627645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-30
Severity: minor
While trying to debug chromium-browser build failures on my sheevaplug I
attached gdb to a running "ld.bfd" process. After some time I got a
kernel panic and had to use JTAG to read the dmesg from memory.
The dmesg is attached. I don't expect that you can do much about this
but I thought it might help to let people know about the problem (it is
in fact a local DoS since no root privileges were used). I was building
chromium-browser in an unstable chroot that was mounted via NFS from
another machine.
ommit interval 5 seconds
<6>[ 12.563032] EXT3-fs: recovery complete.
<6>[ 12.984956] EXT3-fs: mounted filesystem with ordered data mode.
<6>[ 13.566602] udev[154]: starting version 164
<6>[ 14.249662] Adding 714744k swap on /dev/mmcblk0p5. Priority:-1 extents:1
across:714744k SS
<6>[ 14.415425] EXT3 FS on mmcblk0p2, internal journal
<6>[ 14.597380] loop: module loaded
<6>[ 22.119125] eth0: link up, 1000 Mb/s, full duplex, flow control disabled
<6>[ 23.130689] IPv6: Loaded, but administratively disabled, reboot required
to enable
<3>[ 128.455065] ata2: exception Emask 0x10 SAct 0x0 SErr 0x401 action 0xe
frozen
<3>[ 128.462527] ata2: edma_err_cause=0010 pp_flags=, dev connect
<3>[ 128.469278] ata2: SError: { PHYRdyChg DevExch }
<6>[ 128.473849] ata2: hard resetting link
<4>[ 134.426520] ata2: link is slow to respond, please be patient (ready=0)
<3>[ 138.506523] ata2: SRST failed (errno=-16)
<6>[ 138.510553] ata2: hard resetting link
<6>[ 139.836530] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
<6>[ 139.856772] ata2.00: ATA-7: SAMSUNG HD103UJ, 1AA01113, max UDMA7
<6>[ 139.862823] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
<6>[ 139.886813] ata2.00: configured for UDMA/133
<6>[ 139.891122] ata2: EH complete
<5>[ 139.894364] scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD103UJ
1AA0 PQ: 0 ANSI: 5
<5>[ 139.939151] sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00
TB/931 GiB)
<5>[ 139.947565] sd 1:0:0:0: [sda] Write Protect is off
<7>[ 139.952387] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
<5>[ 139.952486] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
<6>[ 139.962876] sda: unknown partition table
<5>[ 139.978879] sd 1:0:0:0: [sda] Attached SCSI disk
<6>[72415.918527] RPC: Registered udp transport module.
<6>[72415.923258] RPC: Registered tcp transport module.
<6>[72415.928017] RPC: Registered tcp NFSv4.1 backchannel transport module.
<5>[72415.992176] Slow work thread pool: Starting up
<5>[72415.997173] Slow work thread pool: Ready
<5>[72416.002038] FS-Cache: Loaded
<5>[72416.114290] FS-Cache: Netfs 'nfs' registered for caching
<3>[421978.774045] ata2: exception Emask 0x10 SAct 0x0 SErr 0x10 action 0x6
frozen
<3>[421978.781508] ata2: edma_err_cause=0220 pp_flags=0003,
SError=0010
<3>[421978.788690] ata2: SError: { Dispar }
<6>[421978.792386] ata2: hard resetting link
<6>[421979.296531] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
<6>[421979.336800] ata2.00: configured for UDMA/133
<6>[421979.341189] ata2: EH complete
<3>[520311.272438] ata2: exception Emask 0x10 SAct 0x0 SErr 0x18 action 0x6
frozen
<3>[520311.279905] ata2: edma_err_cause=0020 pp_flags=,
SError=0018
<3>[520311.287093] ata2: SError: { 10B8B Dispar }
<6>[520311.291313] ata2: hard resetting link
<6>[520311.796532] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
<6>[520311.836800] ata2.00: configured for UDMA/133
<6>[520311.841189] ata2: EH complete
<3>[1130600.900737] ata2: exception Emask 0x10 SAct 0x0 SErr 0x18 action
0x6 frozen
<3>[1130600.908287] ata2: edma_err_cause=0020 pp_flags=,
SError=0018
<3>[1130600.915549] ata2: SError: { 10B8B Dispar }
<6>[1130600.919860] ata2: hard resetting link
<6>[1130601.266528] ata2: SATA link down (SStatus 0 SControl F300)
<6>[1130606.266530] ata2: hard resetting link
<6>[1130606.616525] ata2: SATA link down (SStatus 0 SControl F300)
<4>[1130606.60] ata2: limiting
Bug#596700: marked as done (The X server does not deallocate its vt upon shutdown. Restarting the X server results in the use of a higher-numbered vt.)
Your message dated Mon, 8 Jul 2013 19:40:05 +0200 with message-id <20130708174005.GA7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #596700, regarding The X server does not deallocate its vt upon shutdown. Restarting the X server results in the use of a higher-numbered vt. 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.) -- 596700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xorg Version: 1:7.5+6 I am running Debian Squeeze on the i386 architecture. The video card has an Nvidia RIVA TNT2 chipset. The nv driver (xserver-xorg-video-nv) is being used. The monitor is a CRT multi-sync monitor with DDC2/EDID support. My Desktop Environment is GNOME. Here's the scenario: (1) I boot the system. The X server starts on vt 7, running the gdm login interface daemon. I login on the X console using my non-superuser userid and password. This works fine. (2) I then logout of the desktop environment using System -> Logout from the GNOME action bar. Logout proceeds without incident, the X server shuts down, then restarts automatically. But when it restarts, it restarts on vt 8 instead of vt 7. This is not immediately apparent, but if I switch to vt 1 via Ctrl+Alt+F1, then attempt to switch back to the X server via Alt+F7, I see a black screen. If I use Alt+F8 instead, I see the gdm login screen. With the help of someone on the debian-user mailing list, plus some trial-and-error experimentation, I have come up with the following procedure which I use to get the X server back on vt 7 again, without a reboot: (a) When you see the gdm login screen again after logging out, switch to text console number 1 via Ctrl+Alt+F1. (b) login as root on vt 1. Attempt to deallocate vt 7 with deallocvt 7 This results in an error message: VT_DISALLOCATE: Device or resource busy (c) Issue the command killall console-kit-daemon (d) Once again issue the command deallocvt 7 This time it succeeds. (e) Restart gdm with /etc/init.d/gdm restart The X server shuts down and restarts, this time on vt 7. Note: for some installations, "/etc/init.d/gdm3 restart" is needed instead. Do not login yet! (f) Switch back to vt 1 via Ctrl+Alt+F1. (g) Issue the command deallocvt 8 to deallocate vt 8, which was used by the previous instance of the X server. This time it works. It is not necessary to kill the console-kit-daemon process this time. (i) Logout of the root session on vt 1. (j) Switch back to the X server via Alt+F7. (k) Login to the X server's desktop environment as usual. This is a cumbersome and convoluted work-around, but it works. The problem does not appear to be GNOME-related. Someone else on the debian-user mailing list requested help with these symptoms. He also was using the nv driver, but he was not using GNOME. He started the X server directly with "startx". I don't remember what window manager he was using, but he was not using a desktop environment. All he has to do is stop the X server, manually deallocate vt 7, and issue startx again. console-kit-daemon is apparently not used in his environment. It is apparently not specific to the nv driver either. I have seen these symptoms in the GNOME environment using the intel driver as well. -- .''`. Stephen Powell : :' : `. `'` `- --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#639462: marked as done (linux-image: unable to access (some) USB disks)
Your message dated Mon, 8 Jul 2013 19:40:37 +0200 with message-id <20130708174037.GB7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #639462, regarding linux-image: unable to access (some) USB disks 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.) -- 639462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Severity: minor Hi I had a USB disk that used to work (I think back in Squeeze); "suddenly" it no longer got a device and I could not use it. It was not super important, so I did not file the report back then. On my laptop I see the following in my dmesg log: """ (3.0.0-1-686-pae) [ 3865.900092] usb 1-1: new high speed USB device number 8 using ehci_hcd [ 3866.033178] usb 1-1: config 1 has an invalid interface number: 2 but max is 1 [ 3866.033187] usb 1-1: config 1 has no interface number 1 [ 3866.034295] usb 1-1: New USB device found, idVendor=04b4, idProduct=6830 [ 3866.034302] usb 1-1: New USB device strings: Mfr=0, Product=83, SerialNumber=70 [ 3866.034307] usb 1-1: Product: Cypress AT2LP RC58 [ 3866.034312] usb 1-1: SerialNumber: M000 [ 3866.035199] scsi9 : usb-storage 1-1:1.0 [ 3866.037076] generic-usb 0003:04B4:6830.0006: hiddev0,hidraw2: USB HID v1.10 Device [Cypress AT2LP RC58] on usb-:00:1d.7-1/input2 [ 3888.144064] usb 1-1: reset high speed USB device number 8 using ehci_hcd [ 3909.136069] usb 1-1: reset high speed USB device number 8 using ehci_hcd """ The "reset high speed USB device" keeps repeating until I unplug (or unpower) the USB device. On my newer home PC I see a slightly different message: """ (3.0.0-1-amd64) [ 51.874852] usb 1-1: new high speed USB device number 3 using ehci_hcd [ 52.007827] usb 1-1: config 1 has an invalid interface number: 2 but max is 1 [ 52.008210] usb 1-1: config 1 has no interface number 1 [ 52.009948] usb 1-1: New USB device found, idVendor=04b4, idProduct=6830 [ 52.010335] usb 1-1: New USB device strings: Mfr=0, Product=83, SerialNumber=70 [ 52.010919] usb 1-1: Product: Cypress AT2LP RC58 [ 52.011596] usb 1-1: SerialNumber: M000 [ 52.012790] scsi16 : usb-storage 1-1:1.0 [ 52.013838] ums-cypress: probe of 1-1:1.2 failed with error -5 [ 52.015651] generic-usb 0003:04B4:6830.0002: hiddev0,hidraw0: USB HID v1.10 Device [Cypress AT2LP RC58] on usb-:00:1a.7-1/input2 [ 74.071858] usb 1-1: reset high speed USB device number 3 using ehci_hcd [ 76.599841] usb 1-1: USB disconnect, device number 3 """ Last I checked I could mount USBpens and another USB disk (from a different vendor). ~Niels -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#627618: marked as done (/lib/modules/2.6.38-2-686/kernel/sound/pci/hda/snd-hda-intel.ko: snd_pcm_avail() returned a value that is exceptionally large: 356416 bytes (2020 ms))
Your message dated Mon, 8 Jul 2013 19:40:37 +0200 with message-id <20130708174037.GB7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #627618, regarding /lib/modules/2.6.38-2-686/kernel/sound/pci/hda/snd-hda-intel.ko: snd_pcm_avail() returned a value that is exceptionally large: 356416 bytes (2020 ms) 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.) -- 627618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.38-5 Severity: minor File: /lib/modules/2.6.38-2-686/kernel/sound/pci/hda/snd-hda-intel.ko Tags: upstream Got the following lines in my syslog. Can't say I have heard any clicks, and I don't know how to repro, but the text says I should report it so I am: May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 356416 bytes (2020 ms). May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: snd_pcm_dump(): May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: Soft volume PCM May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: Control: PCM Playback Volume May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: min_dB: -51 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: max_dB: 0 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: resolution: 256 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: Its setup is: May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: stream : PLAYBACK May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: access : MMAP_INTERLEAVED May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: format : S16_LE May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: subformat: STD May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: channels : 2 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: rate : 44100 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: exact rate : 44100 (44100/1) May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: msbits : 16 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: buffer_size : 16384 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: period_size : 8192 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: period_time : 185759 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: tstamp_mode : ENABLE May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: period_step : 1 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: avail_min: 15802 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: period_event : 0 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: start_threshold : -1 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: stop_threshold : 1073741824 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: silence_threshold: 0 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: silence_size : 0 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: boundary : 1073741824 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: Slave: Hardware PCM card 0 'HDA Intel' device 0 subdevice 0 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: Its setup is: May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: stream : PLAYBACK May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: access : MMAP_INTERLEAVED May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: format : S16_LE May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: subformat: STD May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: channels : 2 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: rate : 44100 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: exact rate : 44100 (44100/1) May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: msbits : 16 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: buffer_size : 16384 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: period_size : 8192 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: period_time : 185759 May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c: tstamp_mode : ENABLE May 22 09:45:15 johansdator pulseaudio[2452]: alsa-util.c:
Bug#630404: marked as done (linux-image-3.0.0-rc2-amd64: uses a literal "%d" in "wlan%d")
Your message dated Mon, 8 Jul 2013 19:40:37 +0200 with message-id <20130708174037.GB7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #630404, regarding linux-image-3.0.0-rc2-amd64: uses a literal "%d" in "wlan%d" 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.) -- 630404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 3.0.0~rc2-1~experimental.1 Severity: minor Note that below the text "wlan%d" contains literally a "%d". This could be problematic since the machine in question can usefully use more than one wireless card (one built-in, plus a Cardbus or ExpressCard one). lakeview ok % dmesg | grep wlan [ 32.533716] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 71.775836] wlan%d: direct probe to 00:26:f2:fa:e9:92 (try 1/3) [ 71.776634] wlan%d: direct probe responded [ 71.776693] wlan%d: authenticate with 00:26:f2:fa:e9:92 (try 1) [ 71.777112] wlan%d: authenticated [ 71.780121] wlan%d: associate with 00:26:f2:fa:e9:92 (try 1) [ 71.780754] wlan%d: RX AssocResp from 00:26:f2:fa:e9:92 (capab=0x411 status=0 aid=1) [ 71.780759] wlan%d: associated [ 71.783031] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 81.784185] wlan%d: disassociating from 00:26:f2:fa:e9:92 by local choice (reason=3) [ 81.801303] wlan%d: deauthenticating from 00:26:f2:fa:e9:92 by local choice (reason=3) [ 84.258256] wlan%d: authenticate with 00:26:f2:fa:e9:92 (try 1) [ 84.258703] wlan%d: authenticated [ 84.258926] wlan%d: associate with 00:26:f2:fa:e9:92 (try 1) [ 84.259577] wlan%d: RX ReassocResp from 00:26:f2:fa:e9:92 (capab=0x411 status=0 aid=1) [ 84.259584] wlan%d: associated [ 572.442569] ADDRCONF(NETDEV_UP): wlan1: link is not ready -- Package-specific info: ** Version: Linux version 3.0.0-rc2-amd64 (Debian 3.0.0~rc2-1~experimental.1) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-2) ) #1 SMP Thu Jun 9 19:02:26 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-3.0.0-rc2-amd64 root=/dev/mapper/lakeview-root ro quiet usbcore.autosuspend=1 ** Not tainted ** Kernel log: [ 14.159587] audit: name_count maxed, losing inode data: dev=00:06, inode=6506 [ 14.159593] audit: name_count maxed, losing inode data: dev=00:06, inode=6794 [ 14.159597] audit: name_count maxed, losing inode data: dev=00:06, inode=6794 [ 14.159603] audit: name_count maxed, losing inode data: dev=00:06, inode=6794 [ 14.159606] audit: name_count maxed, losing inode data: dev=00:06, inode=6794 [ 14.159611] audit: name_count maxed, losing inode data: dev=00:06, inode=6506 [ 14.159615] audit: name_count maxed, losing inode data: dev=00:06, inode=6799 [ 14.159620] audit: name_count maxed, losing inode data: dev=00:06, inode=6799 [ 14.159626] audit: name_count maxed, losing inode data: dev=00:06, inode=6799 [ 14.159630] audit: name_count maxed, losing inode data: dev=00:06, inode=6799 [ 14.159634] audit: name_count maxed, losing inode data: dev=00:06, inode=6506 [ 14.159637] audit: name_count maxed, losing inode data: dev=00:06, inode=6804 [ 14.159641] audit: name_count maxed, losing inode data: dev=00:06, inode=6804 [ 14.159651] audit: name_count maxed, losing inode data: dev=00:06, inode=6804 [ 14.159654] audit: name_count maxed, losing inode data: dev=00:06, inode=6804 [ 14.446464] EXT4-fs (dm-3): barriers disabled [ 14.455178] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: data=ordered,barrier=0 [ 14.522477] systemd-fsck[707]: /dev/sda1: clean, 266/62248 files, 108632/248976 blocks [ 14.640779] EXT4-fs (dm-2): barriers disabled [ 14.756160] EXT3-fs: barriers not enabled [ 14.756348] kjournald starting. Commit interval 5 seconds [ 14.756562] EXT3-fs (sda1): using internal journal [ 14.756566] EXT3-fs (sda1): mounted filesystem with ordered data mode [ 14.856665] EXT4-fs (dm-4): barriers disabled [ 14.866941] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: data=ordered,barrier=0,journal_async_commit,user_xattr [ 14.867698] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: data=ordered,barrier=0 [ 16.282130] fuse init (API version 7.16) [ 17.850528] IBM TrackPoint firmware: 0x0e, buttons: 3/3 [ 18.090132] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input11 [ 18.256310] NET: Registered protocol family 15 [ 18.284615] alg: No test for cipher_null (cipher_null-generic) [ 18.284656] alg: No test for ecb(cipher_null) (ecb-cipher_null) [ 18
Bug#677237: marked as done (linux-image-2.6.32-5-amd64: btrfs kernel oops)
Your message dated Mon, 8 Jul 2013 19:41:03 +0200 with message-id <20130708174102.GC7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #677237, regarding linux-image-2.6.32-5-amd64: btrfs kernel 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.) -- 677237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-45 Severity: minor I have just installed this machine and testing btrfs for 2 drives (each 2TB, configured with raid1 metadata, raid0 data) I noticed these kernel oops in dmes -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-45) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May 6 04:00:17 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=/dev/md0 ro quiet ** Not tainted ** Kernel log: [836882.704176] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [836882.704296] btrfs-transac D 0002 0 7573 2 0x [836882.704301] 88003fdcb880 0046 a038a43f [836882.704306] a038c469 a038921c f9e0 88007e565fd8 [836882.704310] 00015780 00015780 88007e9d9530 88007e9d9828 [836882.704315] Call Trace: [836882.704346] [] ? btree_submit_bio_hook+0x94/0x9f [btrfs] [836882.704361] [] ? __btree_submit_bio_start+0x0/0x173 [btrfs] [836882.704374] [] ? __btree_submit_bio_done+0x0/0x12 [btrfs] [836882.704382] [] ? ktime_get_ts+0x68/0xb2 [836882.704389] [] ? sync_page+0x0/0x46 [836882.704395] [] ? io_schedule+0x73/0xb7 [836882.704399] [] ? sync_page+0x41/0x46 [836882.704403] [] ? __wait_on_bit+0x41/0x70 [836882.704407] [] ? wait_on_page_bit+0x6b/0x71 [836882.704411] [] ? wake_bit_function+0x0/0x23 [836882.704426] [] ? btrfs_wait_marked_extents+0xe0/0x11a [btrfs] [836882.704440] [] ? btrfs_write_and_wait_marked_extents+0x28/0x3b [btrfs] [836882.704454] [] ? btrfs_commit_transaction+0x4fe/0x605 [btrfs] [836882.704460] [] ? del_timer_sync+0xc/0x16 [836882.704464] [] ? autoremove_wake_function+0x0/0x2e [836882.704477] [] ? transaction_kthread+0x16b/0x1ea [btrfs] [836882.704483] [] ? __wake_up_common+0x44/0x72 [836882.704496] [] ? transaction_kthread+0x0/0x1ea [btrfs] [836882.704501] [] ? kthread+0x79/0x81 [836882.704507] [] ? child_rip+0xa/0x20 [836882.704510] [] ? kthread+0x0/0x81 [836882.704513] [] ? child_rip+0x0/0x20 [837002.708061] INFO: task btrfs-transacti:7573 blocked for more than 120 seconds. [837002.708172] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [837002.708293] btrfs-transac D 0002 0 7573 2 0x [837002.708299] 88003fdcb880 0046 a038a43f [837002.708303] a038c469 a038921c f9e0 88007e565fd8 [837002.708308] 00015780 00015780 88007e9d9530 88007e9d9828 [837002.708312] Call Trace: [837002.708346] [] ? btree_submit_bio_hook+0x94/0x9f [btrfs] [837002.708361] [] ? __btree_submit_bio_start+0x0/0x173 [btrfs] [837002.708374] [] ? __btree_submit_bio_done+0x0/0x12 [btrfs] [837002.708382] [] ? ktime_get_ts+0x68/0xb2 [837002.708390] [] ? sync_page+0x0/0x46 [837002.708396] [] ? io_schedule+0x73/0xb7 [837002.708400] [] ? sync_page+0x41/0x46 [837002.708404] [] ? __wait_on_bit+0x41/0x70 [837002.708408] [] ? wait_on_page_bit+0x6b/0x71 [837002.708412] [] ? wake_bit_function+0x0/0x23 [837002.708427] [] ? btrfs_wait_marked_extents+0xe0/0x11a [btrfs] [837002.708441] [] ? btrfs_write_and_wait_marked_extents+0x28/0x3b [btrfs] [837002.708455] [] ? btrfs_commit_transaction+0x4fe/0x605 [btrfs] [837002.708462] [] ? del_timer_sync+0xc/0x16 [837002.708466] [] ? autoremove_wake_function+0x0/0x2e [837002.708479] [] ? transaction_kthread+0x16b/0x1ea [btrfs] [837002.708485] [] ? __wake_up_common+0x44/0x72 [837002.708498] [] ? transaction_kthread+0x0/0x1ea [btrfs] [837002.708502] [] ? kthread+0x79/0x81 [837002.708507] [] ? child_rip+0xa/0x20 [837002.708511] [] ? kthread+0x0/0x81 [837002.708514] [] ? child_rip+0x0/0x20 [837242.716064] INFO: task btrfs-transacti:7573 blocked for more than 120 seconds. [837242.716185] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [837242.716305] btrfs-transac D 0002 0 7573 2 0x [837242.716311] 814891f0 0046 a038a43f [837242.716316] fff
Bug#672101: marked as done (WARNINGs from lookup_one_len while booting from reiserfs)
Your message dated Mon, 8 Jul 2013 19:41:03 +0200 with message-id <20130708174102.GC7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #672101, regarding WARNINGs from lookup_one_len while booting from reiserfs 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.) -- 672101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-41squeeze2 Severity: minor After upgrading the kernel to squeeze/stable I've noticed this kernel oops in the startup. It may be related to using reiserfs/lvm/raid1: [ 33.260871] REISERFS (device dm-0): found reiserfs format "3.6" with standard journal [ 33.269764] REISERFS (device dm-0): using ordered data mode [ 33.284952] REISERFS (device dm-0): journal params: device dm-0, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [ 33.302567] REISERFS (device dm-0): checking transaction log (dm-0) [ 33.434979] REISERFS (device dm-0): Using r5 hash to sort names [ 33.441709] [ cut here ] [ 33.446969] WARNING: at /build/buildd-linux-2.6_2.6.32-41squeeze2-amd64-NDo8b7/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/namei.c:1285 lookup_one _len+0x3a/0x8e() [ 33.464066] Hardware name: ProLiant DL160 G5 [ 33.468932] Modules linked in: ext3 jbd mbcache coretemp ipmi_si ipmi_msghandler ide_generic ide_cd_mod ide_core snd_pcm snd_timer snd soundcore snd_page _alloc shpchp i5400_edac edac_core pcspkr pci_hotplug i5k_amb rng_core evdev button processor reiserfs dm_mirror dm_region_hash dm_log dm_snapshot dm_mod us bhid hid raid1 md_mod sg sr_mod cdrom sd_mod crc_t10dif ata_generic uhci_hcd ata_piix libata ehci_hcd scsi_mod usbcore nls_base tg3 libphy thermal thermal_s ys [last unloaded: scsi_wait_scan] [ 33.521927] Pid: 2098, comm: mount Not tainted 2.6.32-5-amd64 #1 [ 33.528739] Call Trace: [ 33.531560] [] ? lookup_one_len+0x3a/0x8e [ 33.537985] [] ? lookup_one_len+0x3a/0x8e [ 33.544408] [] ? warn_slowpath_common+0x77/0xa3 [ 33.551416] [] ? lookup_one_len+0x3a/0x8e [ 33.557843] [] ? vfs_quota_on_mount+0x35/0x85 [ 33.564662] [] ? finish_unfinished+0x108/0x545 [reiserfs] [ 33.572647] [] ? reiserfs_fill_super+0x8f6/0xa41 [reiserfs] [ 33.580849] [] ? sget+0x39d/0x3af [ 33.586492] [] ? get_sb_bdev+0x135/0x192 [ 33.592822] [] ? reiserfs_fill_super+0x0/0xa41 [reiserfs] [ 33.600803] [] ? vfs_kern_mount+0x99/0x14b [ 33.607322] [] ? do_kern_mount+0x43/0xe2 [ 33.613649] [] ? do_mount+0x72a/0x792 [ 33.619682] [] ? sys_mount+0x80/0xbd [ 33.625619] [] ? system_call_fastpath+0x16/0x1b [ 33.640395] ---[ end trace e314ea9c2b078cfd ]--- The machine has been running fine for 4 days now but still looks a bit worrying. Apologies if this has already been reported. Regards and thanks for your great work, Michael -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-41squeeze2) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Mar 22 17:26:33 UTC 2012 ** Command line: root=/dev/md2 ro console=tty0 console=ttyS0,115200n8 vga=normal com1=115200,8n1 ** Tainted: W (512) * Taint on warning. ** Kernel log: [114876.220343] [] ? ip_rcv_finish+0x373/0x38d [114876.226903] [] ? ip_rcv+0x2a0/0x2ed [114876.232781] [] ? napi_skb_finish+0x1c/0x31 [114876.239345] [] ? tg3_poll_work+0x708/0xb49 [tg3] [114876.246482] [] ? select_task_rq_fair+0x1fa/0x843 [114876.253619] [] ? tg3_poll+0x8f/0x1a8 [tg3] [114876.260181] [] ? __wake_up+0x30/0x44 [114876.266159] [] ? net_rx_action+0xae/0x1c9 [114876.272622] [] ? __do_softirq+0xdd/0x1a6 [114876.278989] [] ? call_softirq+0x1c/0x30 [114876.285258] [] ? do_softirq+0x3f/0x7c [114876.291332] [] ? irq_exit+0x36/0x76 [114876.297211] [] ? do_IRQ+0xa0/0xb6 [114876.302896] [] ? ret_from_intr+0x0/0x11 [114876.309161][] ? mwait_idle+0x72/0x7d [114876.315928] [] ? mwait_idle+0x22/0x7d [114876.322002] [] ? cpu_idle+0xa2/0xda [114876.327882] [] ? early_idt_handler+0x0/0x71 [114876.334539] [] ? start_kernel+0x3dc/0x3e8 [114876.341001] [] ? x86_64_start_kernel+0xf9/0x106 [114876.348047] Mem-Info: [114876.350713] Node 0 DMA per-cpu: [114876.354364] CPU0: hi:0, btch: 1 usd: 0 [114876.359855] CPU1: hi:0, btch: 1 usd: 0 [114876.365344] CPU2: hi:0, btch: 1 usd: 0 [114876.370835] CPU3: hi:0, btch: 1 usd: 0 [114876.376323] CPU4: hi:0, btch: 1 usd: 0 [114876.381814] CPU5: hi:0, btch:
Bug#671803: marked as done (linux-image-3.2.0-2-amd64: brcmsmac/80211 wireless, kernel prints some errors)
Your message dated Mon, 8 Jul 2013 19:41:03 +0200 with message-id <20130708174102.GC7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #671803, regarding linux-image-3.2.0-2-amd64: brcmsmac/80211 wireless, kernel prints some errors 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.) -- 671803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 3.2.16-1 Severity: normal Thanks for "brcmsmac: "INTERMEDIATE but not AMPDU" only when tracing" fix in 3.2.16-1. Kernel still prints some wlan errors, but they don't cause major trouble in my light use. Still, maybe this can be fixed. -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.16-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Apr 30 05:20:23 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/LISKO_VG-rootlv ro quiet ** Not tainted ** Kernel log: [8.729883] [drm] Encoders: [8.729886] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [8.729973] [drm] Internal thermal controller without fan control [8.730114] [drm] radeon: power management initialized [8.731062] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [8.759879] cfg80211: World regulatory domain updated: [8.759888] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [8.759894] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.759899] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [8.759905] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [8.759910] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.759914] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.760407] cfg80211: Calling CRDA for country: US [8.772343] cfg80211: Regulatory domain changed to country: US [8.772351] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [8.772358] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2700 mBm) [8.772363] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 1700 mBm) [8.772368] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.772373] cfg80211: (549 KHz - 560 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.772378] cfg80211: (565 KHz - 571 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.772382] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 3000 mBm) [9.197344] [drm] fb mappable at 0xC0142000 [9.197350] [drm] vram apper at 0xC000 [9.197353] [drm] size 4325376 [9.197356] [drm] fb depth is 24 [9.197359] [drm]pitch is 5632 [9.197735] fbcon: radeondrmfb (fb0) is primary device [9.610259] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.4, id: 0x1c0b1, caps: 0xd04733/0xa4/0xa0400 [9.682588] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input9 [9.719153] Console: switching to colour frame buffer device 170x48 [9.725856] fb0: radeondrmfb frame buffer device [9.725859] drm: registered panic notifier [9.725889] [drm] Initialized radeon 2.12.0 20080528 for :00:01.0 on minor 0 [9.726105] snd_hda_intel :00:01.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [9.726245] snd_hda_intel :00:01.1: irq 44 for MSI/MSI-X [9.726285] snd_hda_intel :00:01.1: setting latency timer to 64 [9.747210] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0 [9.747433] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input10 [9.747897] snd_hda_intel :00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [9.803112] input: HDA ATI SB Mic as /devices/pci:00/:00:14.2/sound/card1/input11 [9.803293] input: HDA ATI SB Headphone as /devices/pci:00/:00:14.2/sound/card1/input12 [ 10.282109] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 10.354361] EXT4-fs (dm-1): re-mounted. Opts: commit=60,errors=remount-ro [ 10.435938] loop: module loaded [ 11.308327] Adding 974844k swap on /dev/mapper/LISKO_VG-swap--1. Priority:-1 extents:1 across:974844k SS [ 11.385273] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [ 11.396651] EXT4-fs (dm-3): mounted filesystem without journal. Opts: commit=60 [ 11.808047] RPC: Registered named UNIX sock
Bug#656668: marked as done (ACPI battery device may disappear on failure to read battery status)
Your message dated Mon, 8 Jul 2013 19:41:03 +0200 with message-id <20130708174102.GC7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #656668, regarding ACPI battery device may disappear on failure to read battery status 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.) -- 656668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: linux-image-3.2.0-1-amd64 version: 3.2.1-1 severity: major linux 3.2 changed what is available in /sys/class/power_supply. wmbattery worked fine with 3.1, but the new 3.2 upgrade broke it. This is a kernel problem, please change this back. You can add the new ADP1, but don't remove the BAT0. It's a userspace/kernel breakage, the kernel shouldn't be doing that. From 3.2: == root@urk:~# tree /sys/class/power_supply/ADP1/ /sys/class/power_supply/ADP1/ ├── device -> ../../../ACPI0003:00 ├── online ├── power │ ├── async │ ├── autosuspend_delay_ms │ ├── control │ ├── runtime_active_kids │ ├── runtime_active_time │ ├── runtime_enabled │ ├── runtime_status │ ├── runtime_suspended_time │ └── runtime_usage ├── subsystem -> ../../../../../../class/power_supply ├── type └── uevent == From 3.1: == root@urk:~# tree /sys/class/power_supply/BAT0/ /sys/class/power_supply/BAT0/ ├── alarm ├── cycle_count ├── device -> ../../../PNP0C0A:00 ├── energy_full ├── energy_full_design ├── energy_now ├── manufacturer ├── model_name ├── power │ ├── async │ ├── autosuspend_delay_ms │ ├── control │ ├── runtime_active_kids │ ├── runtime_active_time │ ├── runtime_enabled │ ├── runtime_status │ ├── runtime_suspended_time │ └── runtime_usage ├── power_now ├── present ├── serial_number ├── status ├── subsystem -> ../../../../../../class/power_supply ├── technology ├── type ├── uevent ├── voltage_min_design └── voltage_now == --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#513808: marked as done (linux-image-2.6.26-1-amd64: ACPI Error Method parse/execution failed after suspend)
Your message dated Mon, 8 Jul 2013 19:41:26 +0200 with message-id <20130708174126.GD7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #513808, regarding linux-image-2.6.26-1-amd64: ACPI Error Method parse/execution failed after suspend 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.) -- 513808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: important After testing the suspend to RAM options in KDE3.5.9 i noticed the next output after resume : [ 1033.998126] ACPI Exception (exoparg2-0444): AE_AML_PACKAGE_LIMIT, Index (7) is beyond end of object [20080321] [ 1033.998136] ACPI Error (psparse-0530): Method parse/execution failed [\_SB_.WMID.WMBA] (Node 8100371da2d0), AE_AML_PACKAGE_LIMIT higher in dmesg there was : PM: Writing back config space on device :06:04.1 at offset 4 (was 0, writing c0210400) [ 1033.207361] PM: Writing back config space on device :06:04.1 at offset 3 (was 80, writing 804008) [ 1033.207370] PM: Writing back config space on device :06:04.1 at offset 1 (was 210, writing 216) [ 1033.223348] PM: Writing back config space on device :06:04.2 at offset f (was 482002ff, writing 4820020b) [ 1033.223377] PM: Writing back config space on device :06:04.2 at offset 4 (was 0, writing c0210800) [ 1033.223384] PM: Writing back config space on device :06:04.2 at offset 3 (was 80, writing 804008) [ 1033.223394] PM: Writing back config space on device :06:04.2 at offset 1 (was 210, writing 216) -- 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/sda5 ro quiet ** Tainted: P (1) ** Kernel log: [ 1033.051086] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 [ 1033.067105] PM: Writing back config space on device :06:02.0 at offset f (was 1c0a0100, writing 1c0a010b) [ 1033.067133] PM: Writing back config space on device :06:02.0 at offset 4 (was 0, writing c020) [ 1033.067140] PM: Writing back config space on device :06:02.0 at offset 3 (was 0, writing 6008) [ 1033.067149] PM: Writing back config space on device :06:02.0 at offset 1 (was 290, writing 2900016) [ 1033.067175] ACPI: PCI Interrupt :06:02.0[A] -> GSI 22 (level, low) -> IRQ 22 [ 1033.069256] PM: Writing back config space on device :06:04.0 at offset f (was 744010b, writing 5c0010b) [ 1033.069264] PM: Writing back config space on device :06:04.0 at offset e (was 0, writing a8fc) [ 1033.069271] PM: Writing back config space on device :06:04.0 at offset d (was 0, writing a800) [ 1033.069278] PM: Writing back config space on device :06:04.0 at offset c (was 0, writing a4fc) [ 1033.069285] PM: Writing back config space on device :06:04.0 at offset b (was 0, writing a400) [ 1033.069292] PM: Writing back config space on device :06:04.0 at offset a (was 0, writing 57fff000) [ 1033.069299] PM: Writing back config space on device :06:04.0 at offset 9 (was 0, writing 5400) [ 1033.069306] PM: Writing back config space on device :06:04.0 at offset 8 (was 0, writing 507ff000) [ 1033.069313] PM: Writing back config space on device :06:04.0 at offset 7 (was 0, writing 5040) [ 1033.069321] PM: Writing back config space on device :06:04.0 at offset 6 (was 20070706, writing b0070706) [ 1033.069332] PM: Writing back config space on device :06:04.0 at offset 3 (was 824008, writing 82a820) [ 1033.179293] ata2: SATA link down (SStatus 0 SControl 310) [ 1033.207325] PM: Writing back config space on device :06:04.1 at offset f (was 40102ff, writing 401020b) [ 1033.207353] PM: Writing back config space on device :06:04.1 at offset 4 (was 0, writing c0210400) [ 1033.207361] PM: Writing back config space on device :06:04.1 at offset 3 (was 80, writing 804008) [ 1033.207370] PM: Writing back config space on device :06:04.1 at offset 1 (was 210, writing 216) [ 1033.223348] PM: Writing back config space on device :06:04.2 at offset f (was 482002ff, writing 4820020b) [ 1033.223377] PM: Writing back config space on device :06:04.2 at offset 4 (was 0, writing c0210800) [ 1033.223384] PM: Writing back config space on device :06:04.2 at offset 3 (was 80, writing 804008) [ 1033.223394] PM: Writing back config
Bug#644265: marked as done (linux-image-2.6.32-5-amd64: ksm does not work)
Your message dated Mon, 8 Jul 2013 19:40:05 +0200
with message-id <20130708174005.GA7214@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #644265,
regarding linux-image-2.6.32-5-amd64: ksm does not work
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.)
--
644265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-35squeeze2
Severity: normal
enabling ksm by echo 1 > /sys/kernel/mm/ksm/run has no effect
full_scans are always 0, no increment in any of the other variables
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-35squeeze2) (da...@debian.org) (gcc
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Sep 9 20:23:16 UTC 2011
** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64
root=UUID=49a2baa4-c4fb-4b25-a847-da38aabf6eb4 ro quiet
** Tainted: P (1)
* Proprietary module has been loaded.
** Kernel log:
[1888762.816160] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 7e 61 43 00 00 01 00
[1888762.816185] ata1.00: cmd a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma
2048 in
[1888762.816188] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4
(timeout)
[1888762.816195] ata1.00: status: { DRDY }
[1888762.816207] ata1: hard resetting link
[1888763.136059] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[1888763.160243] ata1.00: configured for UDMA/100
[1888763.165702] ata1: EH complete
[1888793.816223] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[1888793.816236] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 7e 61 43 00 00 01 00
[1888793.816260] ata1.00: cmd a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma
2048 in
[1888793.816264] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4
(timeout)
[1888793.816270] ata1.00: status: { DRDY }
[1888793.816284] ata1: hard resetting link
[1888794.136058] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[1888794.160243] ata1.00: configured for UDMA/100
[1888794.160859] ata1: EH complete
[124.816182] ata1.00: limiting speed to UDMA/66:PIO4
[124.816192] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[124.816202] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 7e 61 43 00 00 01 00
[124.816226] ata1.00: cmd a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma
2048 in
[124.816230] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4
(timeout)
[124.816236] ata1.00: status: { DRDY }
[124.816249] ata1: hard resetting link
[125.136058] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[125.160243] ata1.00: configured for UDMA/66
[125.160812] sr 0:0:0:0: [sr0] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[125.160820] sr 0:0:0:0: [sr0] Sense Key : Aborted Command [current]
[descriptor]
[125.160827] Descriptor sense data with sense descriptors (in hex):
[125.160831] 72 0b 00 00 00 00 00 0e 09 0c 00 00 00 02 00 00
[125.160845] 00 08 00 00 a0 40
[125.160853] sr 0:0:0:0: [sr0] Add. Sense: No additional sense information
[125.160860] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 7e 61 43 00 00 01 00
[125.160874] end_request: I/O error, dev sr0, sector 33129740
[125.160907] ata1: EH complete
[155.816222] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[155.816235] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 05 2c 00 00 01 00
[155.816259] ata1.00: cmd a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma
2048 in
[155.816263] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4
(timeout)
[155.816269] ata1.00: status: { DRDY }
[155.816283] ata1: hard resetting link
[156.136058] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[156.160244] ata1.00: configured for UDMA/66
[156.160811] ata1: EH complete
[1898559.432027] usb 1-6: new high speed USB device using ehci_hcd and address 4
[1898560.344047] hub 1-0:1.0: unable to enumerate USB device on port 6
[1898560.716021] usb 4-2: new full speed USB device using ohci_hcd and address 2
[1898560.918991] usb 4-2: not running at top speed; connect to a high speed hub
[1898560.942991] usb 4-2: New USB device found, idVendor=1949, idProduct=0004
[1898560.942998] usb 4-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[1898560.943004] usb 4-2: Product: Amazon Kindle
[1898560.943008] usb 4-2: Manufacturer: Amazon
[1898560.943012] usb 4-2: SerialNumber: B008D0A112830JDV
[1898560.944961] usb 4-2: configuration #1 chosen from 1 choice
[1898561.378518] Initializing USB Mass
Bug#514298: marked as done (linux-image-2.6.26-1-amd64: If i connect my dvb-t usb sick terratec xxs he makes some entries in the /var/log/syslog)
Your message dated Mon, 8 Jul 2013 19:41:26 +0200 with message-id <20130708174126.GD7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #514298, regarding linux-image-2.6.26-1-amd64: If i connect my dvb-t usb sick terratec xxs he makes some entries in the /var/log/syslog 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.) -- 514298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: minor -- 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/sda1 ro quiet vga=795 ** Tainted: P (1) ** Kernel log: [30932.445624] dib0700: Unknown remote controller key: 13 36 1 0 [30932.605581] dib0700: Unknown remote controller key: 13 36 1 0 [30932.789008] dib0700: Unknown remote controller key: 13 36 1 0 [30932.972792] dib0700: Unknown remote controller key: 13 36 1 0 [30933.132293] dib0700: Unknown remote controller key: 13 36 1 0 [30933.296651] dib0700: Unknown remote controller key: 13 36 1 0 [30933.444874] dib0700: Unknown remote controller key: 13 36 1 0 [30933.628643] dib0700: Unknown remote controller key: 13 36 1 0 [30933.785726] dib0700: Unknown remote controller key: 13 36 1 0 [30933.949291] dib0700: Unknown remote controller key: 13 36 1 0 [30934.149291] dib0700: Unknown remote controller key: 13 36 1 0 [30934.308814] dib0700: Unknown remote controller key: 13 36 1 0 [30934.468818] dib0700: Unknown remote controller key: 13 36 1 0 [30934.699814] dib0700: Unknown remote controller key: 13 36 1 0 [30934.896405] dib0700: Unknown remote controller key: 13 36 1 0 [30935.059937] dib0700: Unknown remote controller key: 13 36 1 0 [30935.308203] dib0700: Unknown remote controller key: 13 36 1 0 [30935.524322] dib0700: Unknown remote controller key: 13 36 1 0 [30935.744034] dib0700: Unknown remote controller key: 13 36 1 0 [30935.896191] dib0700: Unknown remote controller key: 13 36 1 0 [30936.121374] dib0700: Unknown remote controller key: 13 36 1 0 [30936.291369] dib0700: Unknown remote controller key: 13 36 1 0 [30936.479064] dib0700: Unknown remote controller key: 13 36 1 0 [30936.655770] dib0700: Unknown remote controller key: 13 36 1 0 [30936.874306] dib0700: Unknown remote controller key: 13 36 1 0 [30937.030130] dib0700: Unknown remote controller key: 13 36 1 0 [30937.200502] dib0700: Unknown remote controller key: 13 36 1 0 [30937.376651] dib0700: Unknown remote controller key: 13 36 1 0 [30937.584613] dib0700: Unknown remote controller key: 13 36 1 0 [30937.738102] dib0700: Unknown remote controller key: 13 36 1 0 [30937.926887] dib0700: Unknown remote controller key: 13 36 1 0 [30938.081590] dib0700: Unknown remote controller key: 13 36 1 0 [30938.243238] dib0700: Unknown remote controller key: 13 36 1 0 [30938.433996] dib0700: Unknown remote controller key: 13 36 1 0 [30938.589764] dib0700: Unknown remote controller key: 13 36 1 0 [30938.774132] dib0700: Unknown remote controller key: 13 36 1 0 [30938.967194] dib0700: Unknown remote controller key: 13 36 1 0 [30939.124553] dib0700: Unknown remote controller key: 13 36 1 0 [30939.286452] dib0700: Unknown remote controller key: 13 36 1 0 [30939.439736] dib0700: Unknown remote controller key: 13 36 1 0 [30939.665398] dib0700: Unknown remote controller key: 13 36 1 0 [30939.821875] dib0700: Unknown remote controller key: 13 36 1 0 [30940.020245] dib0700: Unknown remote controller key: 13 36 1 0 [30940.227740] dib0700: Unknown remote controller key: 13 36 1 0 [30940.408496] dib0700: Unknown remote controller key: 13 36 1 0 [30940.567808] dib0700: Unknown remote controller key: 13 36 1 0 [30940.739979] dib0700: Unknown remote controller key: 13 36 1 0 [30940.904184] dib0700: Unknown remote controller key: 13 36 1 0 [30941.088459] dib0700: Unknown remote controller key: 13 36 1 0 [30941.244159] dib0700: Unknown remote controller key: 13 36 1 0 [30941.500904] dib0700: Unknown remote controller key: 13 36 1 0 [30941.664404] dib0700: Unknown remote controller key: 13 36 1 0 [30941.824705] dib0700: Unknown remote controller key: 13 36 1 0 [30941.995886] dib0700: Unknown remote controller key: 13 36 1 0 [30942.167414] dib0700: Unknown remote controller key: 13 36 1 0 [30942.386417] dib0700: Unknown remote controller key: 1
Bug#714736: [Pkg-xfce-devel] Bug#714736: Bug#714736: thunar: GUI freeze while moving to trash a file from a NFS4+Kerberos mount
On 04/07/2013 22:52, Yves-Alexis Perez wrote: It'd help if you could try to reproduce with no thunar at all. Just try to move the same set of files to the trash folder. Using "mv" to move files to .local/share/Trash/files does *not* exhibit that behavior: # This works like a charm: sh$ touch 1 2 3 4 sh$ mv 1 .local/share/Trash/files sh$ mv 2 .local/share/Trash/files sh$ mv 3 .local/share/Trash/files ... As far as I can tell, "move to trash" does some more work than only moving the file. At bare minimum it records the original path an deletion date in the corresponding .trashinfo files located in .local/share/Trash/info/ . Nevertheless ... # ... using the "trash-put" command from "trash-cli" package # works too: sh$ touch 1 2 3 4 sh$ trash-put 1 sh$ trash-put 2 sh$ trash-put 3 ... # But this "hang" for each file... sh$ touch 1 2 3 4 --> from Thunar, drag'n drop "1" to "Trash" --> from Thunar, click on "2", press "delete" -- -- Sylvain Leroux -- sylv...@chicoree.fr -- http://www.chicoree.fr -- 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/51dafa44.9060...@chicoree.fr
Bug#616441: marked as done (linux-image-2.6.32-5-xen-686: NETDEV WATCHDOG: usb0 (cdc_subset): transmit queue 0 timed out)
Your message dated Mon, 8 Jul 2013 19:41:26 +0200 with message-id <20130708174126.GD7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #616441, regarding linux-image-2.6.32-5-xen-686: NETDEV WATCHDOG: usb0 (cdc_subset): transmit queue 0 timed out 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.) -- 616441: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-30 Severity: minor Hi, usb0 is a "crosslink" between two such machines for heartbeat purposes. The below warning appeared when the node on the other end was executing a reboot, right after its heartbeat process (reading/writing the other end of the crosslink) shut down. It does not happen on each such event, though, so I can't readily reproduce it, but if may be feasible if somebody knows what and how to press. It hasn't got any obvious adverse effect on the operation of the machines. Thanks, Feri. -- Package-specific info: ** Version: Linux version 2.6.32-5-xen-686 (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 07:52:18 UTC 2011 ** Command line: root=/dev/mapper/xen1ha-root ro console=hvc0 earlyprintk=xen 3 ** Tainted: W (512) * Taint on warning. ** Kernel log: WARNING: at /build/buildd-linux-2.6_2.6.32-30-i386-UYhWt7/linux-2.6-2.6.32/debian/build/source_i386_xen/net/sched/sch_generic.c:261 dev_watchdog+0xbd/0x15d() Hardware name: PowerEdge 2650 NETDEV WATCHDOG: usb0 (cdc_subset): transmit queue 0 timed out Modules linked in: xt_physdev xen_evtchn xenfs crc32c ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi bridge 8021q garp stp bonding ip6t_REJECT ip6t_LOG nf_conntrack_ipv6 ip6table_filter ip6_tables xt_recent ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_tcpudp ipt_LOG xt_limit xt_multiport iptable_filter ip_tables ebtable_filter ebtables x_tables ext3 jbd mbcache ipmi_devintf ipmi_si ipmi_msghandler evdev snd_pcm snd_timer snd cdc_subset soundcore usbnet dcdbas mii snd_page_alloc pcspkr psmouse serio_raw shpchp i2c_piix4 pci_hotplug i2c_core button processor acpi_processor xfs exportfs dm_mod raid1 md_mod sd_mod crc_t10dif sg sr_mod cdrom ata_generic pata_serverworks ohci_hcd ehci_hcd aic7xxx scsi_transport_spi floppy usbcore libata tg3 libphy thermal nls_base thermal_sys scsi_mod [last unloaded: scsi_wait_scan] Pid: 0, comm: swapper Not tainted 2.6.32-5-xen-686 #1 Call Trace: [] ? warn_slowpath_common+0x5e/0x8a [] ? dev_watchdog+0x0/0x15d [] ? warn_slowpath_fmt+0x26/0x2a [] ? dev_watchdog+0xbd/0x15d [] ? lguest_clockevent_set_next_event+0x0/0x3e [] ? xen_restore_fl_direct_end+0x0/0x1 [] ? _spin_unlock_irqrestore+0xd/0xf [] ? xen_force_evtchn_callback+0xc/0x10 [] ? check_events+0x8/0xc [] ? run_timer_softirq+0x16a/0x1eb [] ? __do_softirq+0xaa/0x151 [] ? do_softirq+0x31/0x3c [] ? irq_exit+0x26/0x58 [] ? xen_evtchn_do_upcall+0x22/0x2c [] ? xen_do_upcall+0x7/0xc [] ? hypercall_page+0x3a7/0x1001 [] ? xen_safe_halt+0xf/0x1b [] ? xen_idle+0x23/0x30 [] ? cpu_idle+0x89/0xa5 ---[ end trace 4720259753e3663e ]--- ** Model information not available ** Loaded modules: Module Size Used by xt_physdev 1228 0 xen_evtchn 3471 11 xenfs 7248 1 crc32c 2172 80 ib_iser21904 0 rdma_cm17846 1 ib_iser ib_cm 22569 1 rdma_cm iw_cm 5119 1 rdma_cm ib_sa 13079 2 rdma_cm,ib_cm ib_mad 26365 2 ib_cm,ib_sa ib_core33215 6 ib_iser,rdma_cm,ib_cm,iw_cm,ib_sa,ib_mad ib_addr 4257 1 rdma_cm iscsi_tcp 6685 34 libiscsi_tcp9358 1 iscsi_tcp libiscsi 24462 3 ib_iser,iscsi_tcp,libiscsi_tcp scsi_transport_iscsi19896 4 ib_iser,iscsi_tcp,libiscsi bridge 33031 0 8021q 14114 0 garp4130 1 8021q stp 996 2 bridge,garp bonding65272 0 ip6t_REJECT 2148 2 ip6t_LOG3666 3 nf_conntrack_ipv6 8363 4 ip6table_filter 1908 1 ip6_tables 8560 2 ip6t_LOG,ip6table_filter xt_recent 4885 2 ipt_REJECT 1517 2 nf_conntrack_ipv4 7597 4 nf_defrag_ipv4 779 1 nf_conntrack_ipv4 xt_state 927 8 nf_conntrack 38
Bug#564476: marked as done (udev: Memory leak)
Your message dated Mon, 8 Jul 2013 19:41:26 +0200 with message-id <20130708174126.GD7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #564476, regarding udev: Memory leak 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.) -- 564476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: udev Version: 149-2 Severity: minor This is a warning and I don't know if there's any useful information here for our udev maintainer. Unless others are seeing it, it may not matter; feel free to close. WARNING: at fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x36/0x58() Hardware name: X8DT3 inotify closing but id=0 for entry=8801bd9143c8 in group=8801bf08c380 still in idr. Probably leaking memory Modules linked in: arcmsr sg fuse nfsd auth_rpcgss nfs lockd nfs_acl sunrpc w83627hf_wdt w83627hf hwmon_vid coretemp ipmi_si ipmi_devintf ipmi_msghandler [last unloaded: sg] Pid: 1393, comm: udevd Not tainted 2.6.32.2 #1 Call Trace: [] ? idr_callback+0x36/0x58 [] ? idr_callback+0x36/0x58 [] ? warn_slowpath_common+0x77/0xa3 [] ? warn_slowpath_fmt+0x51/0x59 [] ? wait_for_common+0xdb/0x140 [] ? default_wake_function+0x0/0x9 [] ? idr_callback+0x36/0x58 [] ? idr_for_each+0x6d/0xb0 [] ? idr_callback+0x0/0x58 [] ? inotify_free_group_priv+0x1a/0x2b [] ? fsnotify_final_destroy_group+0x1b/0x24 [] ? inotify_release+0x25/0x37 [] ? __fput+0xe8/0x190 [] ? filp_close+0x5b/0x62 [] ? put_files_struct+0x64/0xc1 [] ? do_exit+0x1e5/0x660 [] ? do_group_exit+0x75/0x9c [] ? sys_exit_group+0x12/0x16 [] ? system_call_fastpath+0x16/0x1b ---[ end trace d03c424d736c2aea ]--- entry->group=(null) inode=(null) wd=4096 udev: starting version 149 -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 8 -rw-r--r-- 1 root root 788 Dec 3 15:37 70-persistent-cd.rules -rw-r--r-- 1 root root 991 Dec 3 15:40 70-persistent-net.rules -- /sys/: /sys/dev /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1/dev /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:0/block/sdc/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:0/block/sdc/sdc1/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:0/bsg/9:0:0:0/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:0/scsi_generic/sg3/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:1/block/sdd/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:1/block/sdd/sdd1/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:1/bsg/9:0:0:1/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:1/scsi_generic/sg4/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:2/block/sde/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:2/block/sde/sde1/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:2/bsg/9:0:0:2/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:2/scsi_generic/sg5/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:3/block/sdf/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:3/block/sdf/sdf1/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:3/bsg/9:0:0:3/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:3/scsi_generic/sg6/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:4/block/sdg/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:4/block/sdg/sdg1/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:4/bsg/9:0:0:4/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:4/scsi_generic/sg7/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:5/block/sdh/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:5/block/sdh/sdh1/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:5/bsg/9:0:0:5/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:5/scsi_generic/sg8/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:6/block/sdi/dev /sys/devices/pci:00/:00:03.0/:06:00.0/host9/target9:0:0/9:0:0:6/block/sdi/sdi1/dev /sys/devices/pci:00/:00:0
Bug#578763: marked as done (pm-utils: Switches vt despite use of KMS (intel i915))
Your message dated Mon, 8 Jul 2013 19:41:26 +0200 with message-id <20130708174126.GD7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #578763, regarding pm-utils: Switches vt despite use of KMS (intel i915) 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.) -- 578763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pm-utils Version: 1.3.0-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, AFAIK, pm-utils is supposed to avoid a vt switch when KMS is in use. Still: $ sudo pm-suspend switches to vt1 before performing the actual suspend. Please ask if you need any complement ! Cheers, OdyX - -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (750, 'unstable'), (700, 'testing-proposed-updates'), (700, 'testing'), (90, 'experimental'), (50, 'testing-proposed-updates'), (50, 'experimental'), (50, 'unstable'), (50, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pm-utils depends on: ii kbd 1.15.1-3 Linux console font and keytable ut ii powermgmt-base1.31 Common utils and configs for power Versions of packages pm-utils recommends: ii procps1:3.2.8-8 /proc file system utilities pn radeontool (no description available) pn vbetool(no description available) Versions of packages pm-utils suggests: ii cpufrequtils 006-2 utilities to deal with the cpufreq pn uswsusp(no description available) - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iJwEAQECAAYFAkvQZcgACgkQ884eR6Y9JhR/3AP7BXIWTsQT/M+FIjXKnVovpvNL LEjpT3zIQMf6VLGpw09VxQQN6TO0SwG98tW+HWAJz5bI1KTr1pCF8Ps9w7pZS/MJ gW2GUO8RrZ/W8cpN65vJbuYvZQNDg/p4tP669rC1MNB1SDJz0rBBExrkbvydwmLJ MxFxbhISRwz9u0F4oL8= =KZvJ -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#585016: marked as done ([linux-2.6] Logitech QuickCam 4000 Pro USB webcam does not work on Debian Squeeze. It works on Debian Lenny.)
Your message dated Mon, 8 Jul 2013 19:41:26 +0200 with message-id <20130708174126.GD7214@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #585016, regarding [linux-2.6] Logitech QuickCam 4000 Pro USB webcam does not work on Debian Squeeze. It works on Debian Lenny. 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.) -- 585016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: linux-image-2.6.32-3-amd64 Severity: critical --- Please enter the report below this line. --- Logitech QuickCam 4000 Pro USB webcam is detected but does not work on Debian squeeze. Test: * The hardware works absolutely rightly on a Debian Lenny machine. * On Debian squeeze, I plug it in and tt is detected (/var/log/syslog or dmesg), /dev/video0 created. lsusb shows the new device. lsusb: Bus 003 Device 005: ID 046d:08b2 Logitech, Inc. QuickCam Pro 4000 However, even if it is detecte rightly, * 'ekiga' hang when cam is enabled. * 'cheese' shows black screen, both at photo and video mode. * 'xawtv' hangs when USB set as source of video. Linux kernel changed a bit with how it deals with webcams, change from v4l to v4l2, but debian kernel should come with all the needed stuff. Module "pwc" is loaded. Test: * lsmod pwc72006 0 videodev 29977 1 pwc usbcore 121703 9 snd_usb_audio,snd_usb_lib,pwc, dvb_usb_dib0700,dvb_usb,usbhid,uhci_hcd,ehci_hcd Test: * modprobe -r pwc && modprobe pwc /var/log/syslog shows the below lines. Nothing odd: [43819.512527] usbcore: deregistering interface driver Philips webcam [43819.578378] pwc: Philips webcam module removed. [43819.627901] Linux video capture interface: v2.00 [43819.629396] pwc: Philips webcam module version 10.0.13 loaded. [43819.629398] pwc: Supports Philips PCA645/646, PCVC675/680/690, PCVC720[40]/730/740/750 & PCVC830/840. [43819.629400] pwc: Also supports the Askey VC010, various Logitech Quickcams, Samsung MPC-C10 and MPC-C30, [43819.629401] pwc: the Creative WebCam 5 & Pro Ex, SOTEC Afina Eye and Visionite VCS-UC300 and VCS-UM100. [43819.629419] pwc: Logitech QuickCam 4000 Pro USB webcam detected. [43819.629459] pwc: Registered as /dev/video0. [43819.639359] input: PWC snapshot button as /devices/pci:00/:00:1a.0/usb3/3-2/input/input19 [43819.639425] usbcore: registered new interface driver Philips webcam The /devices/pci:00/... device is a button on the webcam to take snapshots. I think that is a Linux kernel problem. Is it specific to Debian or to the mainline Linux kernel 2.6.32? Feel free to ask me for more testing, Linux kernel patching and so on. Also let me know if I am direct this bug report to the main Linux kernel development mailing list. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.32-3-amd64 Debian Release: squeeze/sid 500 testing security.debian.org 500 testing ftp.uk.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#715370: Acknowledgement (linux-image-3.9-1-486: CONFIG_GPIO_CS5535 has been set to 'y' when it should be 'M')
Yes, CONFIG_GPIO_CS5535 is forced to 'Y' because the OLPC XO-1 power management settings (CONFIG_OLPC_XO1_PM, CONFIG_OLPC_XO1_SCI, and a few other related options) are boolean. Making the PM code modular is the only way to fix this, but doing so would be racy due to the various hooks that are registered (and really, are required by the system). It's not impossible, simply difficult. The right answer would be to have a module that doesn't allow removal. There may be additional issues as well, I don't recall. As far as CONFIG_GPIO_SYSFS, I don't know why that's unset. I'm assuming it's the case because GPIOs aren't widely used on x86, and twiddling GPIO lines from userspace even less so? -- 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/20130708134916.19e81...@dev.queued.net
Bug#715413: bc is needed to build a kernel 3.9
Package: linux-source-3.9 Version: 3.9.6-1 Severity: normal This package should recommend bc (the GNU command-line calculator), because it is otherwise impossible to build a kernel -- see around line 135 of kernel/Makefile: quiet_cmd_bc = BC $@ cmd_bc = bc -q $(filter-out FORCE,$^) > $@ Note that all this was not present in kernel 3.2 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.9.6 (PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-source-3.9 depends on: ii binutils 2.22-8 ii bzip2 1.0.6-4 Versions of packages linux-source-3.9 recommends: ii gcc 4:4.7.2-1 ii libc6-dev [libc-dev] 2.17-3 ii make 3.81-8.2 Versions of packages linux-source-3.9 suggests: ii libncurses5-dev [ncurses-dev] 5.9+20130608-1 pn libqt4-dev ii pkg-config 0.26-1 -- no debconf information -- 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/51db3219.4000...@fastwebnet.it
