Re: sparc / Problems with 3.2-kernel
On Sun, Jun 2, 2013 at 11:38 PM, BERTRAND Joël joel.bertr...@systella.fr wrote: Andreas Barth a écrit : Hi, today I tried to resurrect our buildd on schroeder (which is from architecture sparc). While trying to do so, I had a couple of strange behaviours like vi freezing after 20-30 seconds, or I couldn't about tail with ctrl+c or suspend with ctrl+z. This didn't change after a reboot. Machine was running our official 3.2-kernel. Was the machine available via the network at the time of freeze? After Martin rebooted the machine into oldstables 2.6.32 kernel, things are working as they should, and the buildd is up again. Question: Is this a known issue? How can we get a fix for that? (I would assume DSA will consider it a non-option to not be able to upgrade to our default kernels.) I have seen same freezes on Blade 2000 (2 * US III+/900 Cu), on U5 (US IIi/440), but not on a server that run with four US IIIi and not on a T1000 (sun4v/US T1). I have tested 3.2 debian kernels and official ones and both hang. I suppose there is another strange bug with special MMU. 2.6.32 is stable but on sparc64, 3.2 is not. I have not tested newer kernels. Bertrand, Andreas, can you please enable the magic SysRq key and try to see what is the kernel busy with when it hangs? It's also possible to do it via the serial console: send-break and then 't' (without quotes). -- Regards, Artyom Tarasenko linux/sparc and solaris/sparc under qemu blog: http://tyom.blogspot.com/search/label/qemu -- 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/CACXAS8AqdW_3MqoyB=3OOU=Hk70xsDXnemvW6WN-txyt7=f...@mail.gmail.com
Bug#710883: /boot/vmlinuz-3.2.0-4-amd64: iptables PREROUTING match on bridge VLAN interfaces stopped working between 2.6.32 and 3.2
Package: src:linux Version: 3.2.41-2+deb7u2 Severity: minor File: /boot/vmlinuz-3.2.0-4-amd64 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, Intercepting http traffic entering VLAN tagged on a bridge interface stopped working after upgrading from Squeeze to Wheezy. I assume this is an upstream issue, and that it may be fixed upstream with the introduction of the bridge-nf-pass-vlan-input-dev sysctl. This does however not seem easily backported to v3.2, as it is based on other changes to the VLAN/bridge stacking logic. I have not bothered verifying these assumptions, but have instead implemented a workaround which is acceptable to me. Based on this I do not expect anyone else to use any time investigating this issue. I report this bug mostly to document the issue in case someone else hits it. Please close or leave open as you find best. My original setup from squeeze was (simplified and anonymized): auto br0 iface br0 inet manual bridge_ports eth1 up sysctl -w net.bridge.bridge-nf-filter-vlan-tagged=0 auto br0.7 iface br0.7 inet static vlan-raw-device br0 address 192.168.0.1 netmask 255.255.255.0 Setting bridge-nf-filter-vlan-tagged=0 used to be the trick to make iptables match against VLANs stacked on bridge interfaces work. I was using a rule like this to redirect all http traffic to a local squid server: iptables -t nat -A PREROUTING -i br0.7 -p tcp --dport 80 -j REDIRECT --to-port 3128 But with wheezy this stopped matching. Enabling a bit of logging showed that no packets ever appeared with source interface br0.7 in the PREROUTING chain. They all had br0 as source interface regardless of VLAN tag (used icmp for the log rule, but the results are similar for tcp and udp): [862122.574098] IN=br0 OUT= PHYSIN=eth1 MAC=00:15:17:1e:5e:35:00:16:ea:b3:07:88:08:00 SRC=192.168.0.4 DST=91.195.8.200 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=10869 SEQ=1 Oddly enough, tagged packets entering the nat/INPUT chain from the same source would appear twice, once with br0 and once with br0.7 as source interface (both lines triggered by the same packet): [862660.693281] IN=br0 OUT= PHYSIN=eth1 MAC=00:15:17:1e:5e:35:00:16:ea:b3:07:88:08:00 SRC=192.168.0.4 DST=192.168.0.1 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=10916 SEQ=1 [862660.925843] IN=br0.7 OUT= PHYSIN=eth1 MAC=00:15:17:1e:5e:35:00:16:ea:b3:07:88:08:00 SRC=192.168.0.4 DST=192.168.0.1 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0 ID=10916 SEQ=1 I did briefly look through some of the changes between v2.6.32 and v3.2, but could spot any obvious cause of this change. As a workaround I instead modified the rule to use br0 as source interface, adding an IP source address match to mostly limit it to packets from clients on VLAN 7. I also had to add a dummy address to the br0 interface because the REDIRECT target needs to rewrite the destination address. Resulting workaround is: auto br0 iface br0 inet static bridge_ports eth1 address 192.168.255.1 netmask 255.255.255.255 auto br0.7 iface br0.7 inet static vlan-raw-device br0 address 192.168.0.1 netmask 255.255.255.0 iptables -t nat -A PREROUTING -i br0 -p tcp -s 192.168.0.0/24 --dport 80 -j REDIRECT --to-port 3128 This is uglier than the original setup, bit it solves the task. Bjørn - -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.41-2+deb7u2 ** Command line: initrd=/initrd.img root=/dev/mapper/vg00-root ro console=tty0 console=ttyS0,9600n8 BOOT_IMAGE=/vmlinuz ** Not tainted -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlGsVdcACgkQ10rqkowbIslZbACdG8KnbJDTmUnhCGSWvfjNqzQ5 UwwAnApY8abIJW+RbErxLhVdhXNfCFU/ =qHjT -END PGP SIGNATURE- -- 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/20130603083746.7455.9879.report...@canardo.mork.no
Bug#710882: tgt: Added autopkgtests
Package: tgt
Version: 1:1.0.17-1
Severity: wishlist
Tags: patch
User: yolanda.ro...@canonical.com
Usertags: origin-ubuntu ubuntu-patch
Added autopkgtests
*** /tmp/tmpDekwqb/bug_body
In Ubuntu, the attached patch was applied to achieve the following:
Improve QA of packages
* d/tests: added dep-8-tests
Thanks for considering the patch.
-- System Information:
Debian Release: wheezy/sid
APT prefers saucy-updates
APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy')
Architecture: amd64 (x86_64)
Kernel: Linux 3.8.0-14-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'
=== modified file 'debian/control'
--- debian/control 2011-08-08 04:45:03 +
+++ debian/control 2013-06-03 08:34:28 +
@@ -7,6 +7,7 @@
Build-Depends: debhelper (= 7), libibverbs-dev, librdmacm-dev
Standards-Version: 3.9.2
Homepage: http://stgt.berlios.de/
+XS-Testsuite: autopkgtest
Package: tgt
Architecture: any
=== added directory 'debian/tests'
=== added file 'debian/tests/admin'
--- debian/tests/admin 1970-01-01 00:00:00 +
+++ debian/tests/admin 2013-06-03 08:34:13 +
@@ -0,0 +1,13 @@
+#!/bin/bash
+#---
+# Testing tgtadm
+#---
+set -e
+ADMIN=tgtadm
+$ADMIN --help /dev/null 21
+RET=$?
+
+if [[ $RET != 0 ]]; then
+ echo ERROR, ${ADMIN} is not running
+ exit $RET
+fi
=== added file 'debian/tests/control'
--- debian/tests/control 1970-01-01 00:00:00 +
+++ debian/tests/control 2013-06-03 08:34:13 +
@@ -0,0 +1,3 @@
+Tests: daemon admin
+Depends: @
+Restrictions: needs-root
=== added file 'debian/tests/daemon'
--- debian/tests/daemon 1970-01-01 00:00:00 +
+++ debian/tests/daemon 2013-06-03 08:34:13 +
@@ -0,0 +1,13 @@
+#!/bin/bash
+#
+# Testing tgt
+#
+set -e
+DAEMON=tgtd
+
+if pidof -x $DAEMON /dev/null; then
+echo OK
+else
+echo ERROR: ${DAEMON} IS NOT RUNNING
+exit 1
+fi
Bug#681092: linux-image-3.2.0-3-686-pae: Sierra WWAN modem not functioning
Hello, do you still have this problem? I was looking at your log and the USB serial changes introduced around the time you hit this, and one of the suspicious patches seem to be mine... This looks very wrong: [3.075097] usbcore: registered new interface driver usbserial [3.075139] USB Serial support registered for generic [3.262423] [drm] initialized overlay support [3.276289] usbserial_generic 6-1:1.0: generic converter detected [3.276592] usb 6-1: generic converter now attached to ttyUSB0 [3.276876] usb 6-1: generic converter now attached to ttyUSB1 [3.277137] usb 6-1: generic converter now attached to ttyUSB2 [3.277178] usbcore: registered new interface driver usbserial_generic [3.277185] usbserial: USB Serial Driver core [3.279835] USB Serial support registered for Sierra USB modem [3.279902] usbcore: registered new interface driver sierra [3.279907] sierra: v.1.7.16:USB Driver for Sierra Wireless USB modems Your modem should not match the generic converter. It should match the sierra driver. But as you can see, the generic driver has already bound to the three serial ports by the time the sierra driver is loaded, so this won't happen. Do you by any chance set the vendor and product usbserial parameters manually somewhere? That would explain the above log. Look for any usbserial entry in /etc/modules /etc/modprobe.d/*.conf or local init scripts. These are unnecessary and may cause problems. But I still do not understand how this can prevent the modem from working. AFAICS it should still work, only at the slower generic serial driver speed. The change I introdcued in v3.2.20 should only affect probing, and only the case where a device could end up being unintentionally bound to the generic driver. Bjørn -- 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/87ppw34kw8@nemi.mork.no
Bug#708737: BUG: unable to handle kernel NULL pointer dereference
Package: src:linux Version: 3.2.41-2+deb7u2 Followup-For: Bug #708737 Another crash and reboot. Are these at all helpful? [419372.523183] BUG: unable to handle kernel paging request at 0006c92d [419372.526719] IP: [c10da147] __d_instantiate+0x2a/0x6a [419372.526719] *pdpt = 2c141001 *pde = [419372.526719] Oops: 0002 [#1] SMP [419372.526719] Modules linked in: iptable_filter ip_tables x_tables sha1_generic hmac cts autofs4 video ac power_supply binfmt_misc fuse rpcsec_gss_krb5 nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc ext4 crc16 jbd2 sha256_generic cryptd aes_i586 aes_generic cbc dm_crypt raid1 i82875p_edac edac_core md_mod snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer iTCO_wdt snd i2c_i801 iTCO_vendor_support parport_pc soundcore rng_core i2c_core parport ac97_bus evdev pcspkr shpchp processor button ext3 mbcache jbd btrfs crc32c libcrc32c zlib_deflate dm_mod sg sd_mod crc_t10dif sr_mod cdrom usb_storage ata_generic thermal floppy sata_sil fan thermal_sys firewire_ohci ata_piix firewire_core uhci_hcd libata crc_itu_t ehci_hcd scsi_mod usbcore e1000 usb_common [last unloaded: scsi_wait_scan] [419372.550468] [419372.550468] Pid: 30998, comm: deb_checkmd5sum Not tainted 3.2.0-4-686-pae #1 Debian 3.2.41-2+deb7u2/IC7/IC7-G(Intel i875P-ICH5) [419372.550468] EIP: 0060:[c10da147] EFLAGS: 00010246 CPU: 1 [419372.550468] EIP is at __d_instantiate+0x2a/0x6a [419372.550468] EAX: c32f6b10 EBX: c32f6a98 ECX: EDX: 0006c929 [419372.550468] ESI: f4382198 EDI: c32f6ae4 EBP: cd34e000 ESP: cd34ff40 [419372.550468] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [419372.550468] Process deb_checkmd5sum (pid: 30998, ti=cd34e000 task=f3dd6900 task.ti=cd34e000) [419372.550468] Stack: [419372.550468] f4382198 c32f6a98 cd34ff68 c10da3c5 f4382198 c10d316c [419372.550468] c137fc1e f4426580 c32f6a98 ffea c10d3257 [419372.550468] cd34ff98 bfcc3760 09c19c34 cd34e000 c10d330a c3ff6e80 0004 [419372.550468] Call Trace: [419372.550468] [c10da3c5] ? d_instantiate+0x25/0x37 [419372.550468] [c10d316c] ? create_write_pipe+0xdf/0x14e [419372.550468] [c10d3257] ? do_pipe_flags+0x22/0xc6 [419372.550468] [c10d330a] ? sys_pipe2+0xf/0x48 [419372.550468] [c10d334e] ? sys_pipe+0xb/0xe [419372.550468] [c12c6e1f] ? sysenter_do_call+0x12/0x28 [419372.550468] Code: c3 57 56 89 d6 8d 78 4c 53 89 c3 89 f8 e8 58 84 1e 00 85 f6 74 2a f6 46 0d 08 74 06 81 0b 00 00 02 00 8b 96 a0 00 00 00 8d 43 78 89 42 04 89 53 78 8d 96 a0 00 00 00 89 53 7c 89 86 a0 00 00 00 [419372.550468] EIP: [c10da147] __d_instantiate+0x2a/0x6a SS:ESP 0068:cd34ff40 [419372.550468] CR2: 0006c92d [419372.762998] ---[ end trace ab95fd26f93b1745 ]--- [419430.440097] BUG: unable to handle kernel NULL pointer dereference at 0020 [419430.444010] IP: [c10dc9e2] iput+0x32/0x132 [419430.444010] *pdpt = 1a31b001 *pde = [419430.444010] Oops: [#2] SMP [419430.444010] Modules linked in: iptable_filter ip_tables x_tables sha1_generic hmac cts autofs4 video ac power_supply binfmt_misc fuse rpcsec_gss_krb5 nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc ext4 crc16 jbd2 sha256_generic cryptd aes_i586 aes_generic cbc dm_crypt raid1 i82875p_edac edac_core md_mod snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer iTCO_wdt snd i2c_i801 iTCO_vendor_support parport_pc soundcore rng_core i2c_core parport ac97_bus evdev pcspkr shpchp processor button ext3 mbcache jbd btrfs crc32c libcrc32c zlib_deflate dm_mod sg sd_mod crc_t10dif sr_mod cdrom usb_storage ata_generic thermal floppy sata_sil fan thermal_sys firewire_ohci ata_piix firewire_core uhci_hcd libata crc_itu_t ehci_hcd scsi_mod usbcore e1000 usb_common [last unloaded: scsi_wait_scan] [419430.444010] [419430.444010] Pid: 23, comm: kswapd0 Tainted: G D 3.2.0-4-686-pae #1 Debian 3.2.41-2+deb7u2/IC7/IC7-G(Intel i875P-ICH5) [419430.444010] EIP: 0060:[c10dc9e2] EFLAGS: 00010246 CPU: 0 [419430.444010] EIP is at iput+0x32/0x132 [419430.444010] EAX: 0001 EBX: f43822c4 ECX: 0006 EDX: 0601 [419430.444010] ESI: EDI: f43822c4 EBP: ESP: f47a1e74 [419430.444010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [419430.444010] Process kswapd0 (pid: 23, ti=f47a task=f44d1240 task.ti=f47a) [419430.444010] Stack: [419430.444010] ef7d6698 caeaad18 f43822c4 c10da58d ef7d66f8 ef7d6698 f47a1eb4 f73cec80 [419430.444010] c10da5f9 ef7d66f8 f73cec00 f18f40f8 c10daf25 f47a1eac f47a1eac [419430.444010] c4ccac78 ef7d6e78 f73cee00 0400 f73cec00 c10cea20 023e [419430.444010] Call Trace: [419430.444010] [c10da58d] ? dentry_kill+0xc6/0xdb [419430.444010] [c10da5f9] ? shrink_dentry_list+0x57/0x97
Bug#707607: Sound problem remains in 3.9-1-686-pae
Hello: The same problem related to sound I described for kernel 3.8 in this netbook remains in the new 3.9 kernel available in Debian. A. Corbi. -- 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/20130603120809.5a206...@hal9000.dlsi.ua.es
Bug#573483: linux-headers-3.9-1-amd64 : Depends: linux-kbuild-3.9 but it is not installable
And again... $ sudo apt-get install linux-headers-3.9-1-amd64 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-3.9-1-amd64 : Depends: linux-kbuild-3.9 but it is not installable E: Unable to correct problems, you have held broken packages. $ rmadison linux-headers-3.9-1-amd64 linux-headers-3.9-1-amd64 | 3.9.4-1 | sid | amd64, i386 $ rmadison linux-kbuild-3.9 $ rmadison -S linux-tools libusbip-dev | 1.1.1+3.2.17-1 | wheezy| amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc libusbip-dev | 1.1.1+3.2.17-1 | jessie| amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc libusbip-dev | 1.1.1+3.8.11-1 | sid | amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc linux-kbuild-3.2 | 3.2.1-2~bpo60+1 | squeeze-backports | amd64, armel, i386, ia64, mips, mipsel, powerpc, s390, sparc linux-kbuild-3.2 | 3.2.17-1| wheezy| amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc linux-kbuild-3.2 | 3.2.17-1| jessie| amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc linux-kbuild-3.8 | 3.8.11-1| sid | amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc linux-tools | 3.2.1-2~bpo60+1 | squeeze-backports | source linux-tools | 3.2.17-1| wheezy| source linux-tools | 3.2.17-1| jessie| source linux-tools | 3.8.11-1| sid | source linux-tools-3.2 | 3.2.1-2~bpo60+1 | squeeze-backports | amd64, armel, i386, powerpc, s390, sparc linux-tools-3.2 | 3.2.17-1| wheezy| amd64, armel, armhf, i386, powerpc, s390, s390x, sparc linux-tools-3.2 | 3.2.17-1| jessie| amd64, armel, armhf, i386, powerpc, s390, s390x, sparc linux-tools-3.8 | 3.8.11-1| sid | amd64, armel, armhf, i386, powerpc, s390, s390x, sparc usbip| 1.1.1+3.2.17-1 | wheezy| amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc usbip| 1.1.1+3.2.17-1 | jessie| amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc usbip| 1.1.1+3.8.11-1 | sid | amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc signature.asc Description: OpenPGP digital signature
Bug#573483: linux-headers-3.9-1-amd64 : Depends: linux-kbuild-3.9 but it is not installable
On Mon, 2013-06-03 at 14:12 +0200, Carlos Alberto Lopez Perez wrote: And again... [...] ME TOOO!1!! -- Ben Hutchings 73.46% of all statistics are made up. signature.asc Description: This is a digitally signed message part
Processing of linux_3.10~rc4-1~exp1_multi.changes
linux_3.10~rc4-1~exp1_multi.changes uploaded successfully to localhost along with the files: linux_3.10~rc4-1~exp1.dsc linux_3.10~rc4.orig.tar.xz linux_3.10~rc4-1~exp1.debian.tar.xz linux-support-3.10-rc4_3.10~rc4-1~exp1_all.deb linux-doc-3.10_3.10~rc4-1~exp1_all.deb linux-manual-3.10_3.10~rc4-1~exp1_all.deb linux-source-3.10_3.10~rc4-1~exp1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ujury-0005vy...@franck.debian.org
Processed: tagging 707023
Processing commands for cont...@bugs.debian.org:
tags 707023 + pending
Bug #707023 {Done: Ben Hutchings b...@decadent.org.uk} [linux-tools]
linux-kbuild-3.8 is not installable
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
707023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707023
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.137026571127144.transcr...@bugs.debian.org
Processing of linux-tools_3.9.4-1_multi.changes
linux-tools_3.9.4-1_multi.changes uploaded successfully to localhost along with the files: linux-tools_3.9.4-1.dsc linux-tools_3.9.4.orig.tar.xz linux-tools_3.9.4-1.debian.tar.xz libusbip-dev_1.1.1+3.9.4-1_i386.deb linux-kbuild-3.9_3.9.4-1_i386.deb usbip_1.1.1+3.9.4-1_i386.deb linux-tools-3.9_3.9.4-1_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ujuwp-0007hu...@franck.debian.org
Processing of linux-latest_49_multi.changes
linux-latest_49_multi.changes uploaded successfully to localhost along with the files: linux-latest_49.dsc linux-latest_49.tar.gz linux-doc_3.9+49_all.deb linux-source_3.9+49_all.deb linux-tools_3.9+49_all.deb linux-image-486_3.9+49_i386.deb linux-headers-486_3.9+49_i386.deb linux-image-686-pae_3.9+49_i386.deb linux-headers-686-pae_3.9+49_i386.deb xen-linux-system-686-pae_3.9+49_i386.deb linux-image-amd64_3.9+49_i386.deb linux-headers-amd64_3.9+49_i386.deb xen-linux-system-amd64_3.9+49_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ujug8-lb...@franck.debian.org
linux_3.10~rc4-1~exp1_multi.changes is NEW
binary:linux-doc-3.10 is NEW. binary:linux-support-3.10-rc4 is NEW. binary:linux-manual-3.10 is NEW. binary:linux-source-3.10 is NEW. Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. -- 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/e1ujuhq-000142...@franck.debian.org
linux-latest_49_multi.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Jun 2013 14:02:30 +0100 Source: linux-latest Binary: linux-source linux-doc linux-tools linux-image-alpha-generic linux-headers-alpha-generic linux-image-alpha-smp linux-headers-alpha-smp linux-image-alpha-legacy linux-headers-alpha-legacy linux-image-amd64 linux-headers-amd64 xen-linux-system-amd64 linux-image-iop32x linux-headers-iop32x linux-image-ixp4xx linux-headers-ixp4xx linux-image-kirkwood linux-headers-kirkwood linux-image-mv78xx0 linux-headers-mv78xx0 linux-image-orion5x linux-headers-orion5x linux-image-versatile linux-headers-versatile linux-image-armmp linux-headers-armmp linux-image-mx5 linux-headers-mx5 linux-image-omap linux-headers-omap linux-image-vexpress linux-headers-vexpress linux-image-parisc linux-headers-parisc linux-image-parisc-smp linux-headers-parisc-smp linux-image-parisc64 linux-headers-parisc64 linux-image-parisc64-smp linux-headers-parisc64-smp linux-image-486 linux-headers-486 linux-image-686-pae linux-headers-686-pae xen-linux-system-686-pae linux-image-itanium linux-headers-itanium linux-image-mckinley linux-headers-mckinley linux-image-amiga linux-headers-amiga linux-image-atari linux-headers-atari linux-image-bvme6000 linux-headers-bvme6000 linux-image-mac linux-headers-mac linux-image-mvme147 linux-headers-mvme147 linux-image-mvme16x linux-headers-mvme16x linux-image-r4k-ip22 linux-headers-r4k-ip22 linux-image-r5k-ip32 linux-headers-r5k-ip32 linux-image-sb1-bcm91250a linux-headers-sb1-bcm91250a linux-image-sb1a-bcm91480b linux-headers-sb1a-bcm91480b linux-image-4kc-malta linux-headers-4kc-malta linux-image-5kc-malta linux-headers-5kc-malta linux-image-octeon linux-headers-octeon linux-image-r5k-cobalt linux-headers-r5k-cobalt linux-image-loongson-2f linux-headers-loongson-2f linux-image-powerpc linux-headers-powerpc linux-image-powerpc-smp linux-headers-powerpc-smp linux-image-powerpc64 linux-headers-powerpc64 linux-image-powerpcspe linux-headers-powerpcspe linux-image-s390x linux-headers-s390x linux-image-sh7751r linux-headers-sh7751r linux-image-sh7785lcr linux-headers-sh7785lcr linux-image-sparc64 linux-headers-sparc64 linux-image-sparc64-smp linux-headers-sparc64-smp Architecture: all i386 source Version: 49 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Ben Hutchings b...@decadent.org.uk Description: linux-doc - Linux kernel specific documentation (meta-package) linux-headers-486 - Header files for Linux 486 configuration (meta-package) linux-headers-4kc-malta - Header files for Linux 4kc-malta configuration (meta-package) linux-headers-5kc-malta - Header files for Linux 5kc-malta configuration (meta-package) linux-headers-686-pae - Header files for Linux 686-pae configuration (meta-package) linux-headers-alpha-generic - Header files for Linux alpha-generic configuration (meta-package) linux-headers-alpha-legacy - Header files for Linux alpha-legacy configuration (meta-package) linux-headers-alpha-smp - Header files for Linux alpha-smp configuration (meta-package) linux-headers-amd64 - Header files for Linux amd64 configuration (meta-package) linux-headers-amiga - Header files for Linux amiga configuration (meta-package) linux-headers-armmp - Header files for Linux armmp configuration (meta-package) linux-headers-atari - Header files for Linux atari configuration (meta-package) linux-headers-bvme6000 - Header files for Linux bvme6000 configuration (meta-package) linux-headers-iop32x - Header files for Linux iop32x configuration (meta-package) linux-headers-itanium - Header files for Linux itanium configuration (meta-package) linux-headers-ixp4xx - Header files for Linux ixp4xx configuration (meta-package) linux-headers-kirkwood - Header files for Linux kirkwood configuration (meta-package) linux-headers-loongson-2f - Header files for Linux loongson-2f configuration (meta-package) linux-headers-mac - Header files for Linux mac configuration (meta-package) linux-headers-mckinley - Header files for Linux mckinley configuration (meta-package) linux-headers-mv78xx0 - Header files for Linux mv78xx0 configuration (meta-package) linux-headers-mvme147 - Header files for Linux mvme147 configuration (meta-package) linux-headers-mvme16x - Header files for Linux mvme16x configuration (meta-package) linux-headers-mx5 - Header files for Linux mx5 configuration (meta-package) linux-headers-octeon - Header files for Linux octeon configuration (meta-package) linux-headers-omap - Header files for Linux omap configuration (meta-package) linux-headers-orion5x - Header files for Linux orion5x configuration (meta-package) linux-headers-parisc64 - Header files for Linux parisc64 configuration (meta-package) linux-headers-parisc64-smp - Header files for Linux parisc64-smp configuration (meta-package) linux-headers-parisc - Header files for Linux parisc
linux-tools_3.9.4-1_multi.changes is NEW
binary:linux-kbuild-3.9 is NEW. binary:linux-tools-3.9 is NEW. Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. -- 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/e1ujuhx-0001gn...@franck.debian.org
Processed: notfound 573483 in 3.6.4-1~experimental.1
Processing commands for cont...@bugs.debian.org: notfound 573483 3.6.4-1~experimental.1 Bug #573483 [src:linux] linux-headers in unstable regularly uninstallable due to missing linux-kbuild Bug #598504 [src:linux] [experimental] linux-headers-nnn depends on linux-kbuild-nnn which is unavailable Bug #603066 [src:linux] Please always upload linux-kbuild-NNN at the same time as linux-image-NNN Bug #642988 [src:linux] linux-headers packages in experimental are often uninstallable Bug #684623 [src:linux] Missing dependency makes package not usable Bug #684745 [src:linux] linux-headers-3.5-trunk-686-pae depends on linux-kbuild-3.5, which is not available Bug #692252 [src:linux] linux-image-3.6-trunk-amd64: cannot install kernel headers Bug #702038 [src:linux] linux-headers-3.8-trunk-amd64: this package depends on linux-kbuild-3.8, which isn't available No longer marked as found in versions linux/3.6.4-1~experimental.1. No longer marked as found in versions linux/3.6.4-1~experimental.1. No longer marked as found in versions linux/3.6.4-1~experimental.1. No longer marked as found in versions linux/3.6.4-1~experimental.1. No longer marked as found in versions linux/3.6.4-1~experimental.1. No longer marked as found in versions linux/3.6.4-1~experimental.1. No longer marked as found in versions linux/3.6.4-1~experimental.1. No longer marked as found in versions linux/3.6.4-1~experimental.1. thanks Stopping processing here. Please contact me if you need assistance. -- 573483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573483 598504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598504 603066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603066 642988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642988 684623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684623 684745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684745 692252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692252 702038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702038 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.137026885919952.transcr...@bugs.debian.org
Processed: tagging 573483
Processing commands for cont...@bugs.debian.org: tags 573483 + wontfix help Bug #573483 [src:linux] linux-headers in unstable regularly uninstallable due to missing linux-kbuild Bug #598504 [src:linux] [experimental] linux-headers-nnn depends on linux-kbuild-nnn which is unavailable Bug #603066 [src:linux] Please always upload linux-kbuild-NNN at the same time as linux-image-NNN Bug #642988 [src:linux] linux-headers packages in experimental are often uninstallable Bug #684623 [src:linux] Missing dependency makes package not usable Bug #684745 [src:linux] linux-headers-3.5-trunk-686-pae depends on linux-kbuild-3.5, which is not available Bug #692252 [src:linux] linux-image-3.6-trunk-amd64: cannot install kernel headers Bug #702038 [src:linux] linux-headers-3.8-trunk-amd64: this package depends on linux-kbuild-3.8, which isn't available Added tag(s) help and wontfix. Added tag(s) help and wontfix. Added tag(s) help and wontfix. Added tag(s) help and wontfix. Added tag(s) help and wontfix. Added tag(s) help and wontfix. Added tag(s) help and wontfix. Added tag(s) help and wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 573483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573483 598504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598504 603066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603066 642988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642988 684623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684623 684745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684745 692252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692252 702038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702038 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.137026885919950.transcr...@bugs.debian.org
Processed: severity of 573483 is minor
Processing commands for cont...@bugs.debian.org: severity 573483 minor Bug #573483 [src:linux] linux-headers in unstable regularly uninstallable due to missing linux-kbuild Bug #598504 [src:linux] [experimental] linux-headers-nnn depends on linux-kbuild-nnn which is unavailable Bug #603066 [src:linux] Please always upload linux-kbuild-NNN at the same time as linux-image-NNN Bug #642988 [src:linux] linux-headers packages in experimental are often uninstallable Bug #684623 [src:linux] Missing dependency makes package not usable Bug #684745 [src:linux] linux-headers-3.5-trunk-686-pae depends on linux-kbuild-3.5, which is not available Bug #692252 [src:linux] linux-image-3.6-trunk-amd64: cannot install kernel headers Bug #702038 [src:linux] linux-headers-3.8-trunk-amd64: this package depends on linux-kbuild-3.8, which isn't available Severity set to 'minor' from 'grave' Severity set to 'minor' from 'grave' Severity set to 'minor' from 'grave' Severity set to 'minor' from 'grave' Severity set to 'minor' from 'grave' Severity set to 'minor' from 'grave' Severity set to 'minor' from 'grave' Severity set to 'minor' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 573483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573483 598504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598504 603066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603066 642988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642988 684623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684623 684745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684745 692252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692252 702038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702038 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.137026885919956.transcr...@bugs.debian.org
Processed: notfound 573483 in 3.8-1~experimental.1
Processing commands for cont...@bugs.debian.org: notfound 573483 3.8-1~experimental.1 Bug #573483 [src:linux] linux-headers in unstable regularly uninstallable due to missing linux-kbuild Bug #598504 [src:linux] [experimental] linux-headers-nnn depends on linux-kbuild-nnn which is unavailable Bug #603066 [src:linux] Please always upload linux-kbuild-NNN at the same time as linux-image-NNN Bug #642988 [src:linux] linux-headers packages in experimental are often uninstallable Bug #684623 [src:linux] Missing dependency makes package not usable Bug #684745 [src:linux] linux-headers-3.5-trunk-686-pae depends on linux-kbuild-3.5, which is not available Bug #692252 [src:linux] linux-image-3.6-trunk-amd64: cannot install kernel headers Bug #702038 [src:linux] linux-headers-3.8-trunk-amd64: this package depends on linux-kbuild-3.8, which isn't available No longer marked as found in versions linux/3.8-1~experimental.1. No longer marked as found in versions linux/3.8-1~experimental.1. No longer marked as found in versions linux/3.8-1~experimental.1. No longer marked as found in versions linux/3.8-1~experimental.1. No longer marked as found in versions linux/3.8-1~experimental.1. No longer marked as found in versions linux/3.8-1~experimental.1. No longer marked as found in versions linux/3.8-1~experimental.1. No longer marked as found in versions linux/3.8-1~experimental.1. thanks Stopping processing here. Please contact me if you need assistance. -- 573483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573483 598504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598504 603066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603066 642988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642988 684623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684623 684745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684745 692252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692252 702038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702038 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.137026885919954.transcr...@bugs.debian.org
Bug#571251: marked as done (base: hp pavillon won't start (30% success))
Your message dated Mon, 3 Jun 2013 18:25:10 +0200 with message-id 20130603162510.gb28...@inutil.org and subject line Re: base: hp pavillon won't start (30% success) has caused the Debian Bug report #571251, regarding base: hp pavillon won't start (30% success) 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.) -- 571251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: base Severity: important i have installed Debian sid now and it won't start after grub: Fail in evaluating the _REG object of EC device. Broken bios is suspected. After that console wrote System is loading... (or similar) and won't start. I need to shut down the notebook and restart it again!! Pc works fine with(i hate to say that but is real) win7...never problems to startup. i have the last bios relase for my hp Pavillon dv6-2044el (F.13A) dmesg after start: . [0.966826] ACPI: EC: Look up EC in DSDT [0.968466] ACPI: Executed 1 blocks of module-level executable AML code [0.972355] ACPI: BIOS _OSI(Linux) query ignored [0.986906] ACPI Error (psargs-0359): [\_PR_.CPU0._PPC] Namespace lookup failure, AE_NOT_FOUND [0.986913] ACPI Error (psparse-0537): Method parse/execution failed [\CPUT] (Node 88013fa4f620), AE_NOT_FOUND [0.986970] ACPI Error (psparse-0537): Method parse/execution failed [\PSSC] (Node 88013fa4f640), AE_NOT_FOUND [0.987022] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_._REG] (Node 88013fa40b00), AE_NOT_FOUND [0.987097] Fail in evaluating the _REG object of EC device. Broken bios is suspected. [0.987216] ACPI: Interpreter enabled [0.987221] ACPI: (supports S0 S3 S4 S5) [0.987269] ACPI: Using IOAPIC for interrupt routing [1.002273] ACPI Error: No handler for Region [PCFG] (88013fa6b090) [PCI_Config] (20090903/evregion-319) [1.002279] ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) [1.002285] ACPI Error (psparse-0537): Method parse/execution failed [\J380._STA] (Node 88013f00a3e0), AE_NOT_EXIST [1.002554] ACPI: EC: GPE = 0x16, I/O: command/status = 0x66, data = 0x62 [1.002938] ACPI: No dock devices found. [1.004024] _OSC invalid UUID [1.004027] ACPI: PCI Root Bridge [PCI0] (:00) .. [1.072738] pnp: PnP ACPI: found 13 devices [1.072740] ACPI: ACPI bus type pnp unregistered [1.072751] system 00:06: ioport range 0x680-0x69f has been reserved [1.072754] system 00:06: ioport range 0x800-0x80f has been reserved [1.072757] system 00:06: ioport range 0x-0x has been reserved [1.072760] system 00:06: ioport range 0x-0x has been reserved [1.072763] system 00:06: ioport range 0x400-0x47f has been reserved [1.072766] system 00:06: ioport range 0x500-0x57f has been reserved [1.072769] system 00:06: ioport range 0x164e-0x164f has been reserved [1.072772] system 00:06: ioport range 0x380-0x38e has been reserved [1.072780] system 00:0b: iomem range 0xfed1c000-0xfed1 has been reserved [1.072783] system 00:0b: iomem range 0xfed1b000-0xfed1bfff has been reserved [1.072786] system 00:0b: iomem range 0xe000-0xefff has been reserved [1.072789] system 00:0b: iomem range 0xfed2-0xfed3 has been reserved [1.072792] system 00:0b: iomem range 0xfed45000-0xfed8 has been reserved [1.072796] system 00:0b: iomem range 0xff00-0x could not be reserved [1.072799] system 00:0b: iomem range 0xfee0-0xfeef could not be reserved [1.072802] system 00:0b: iomem range 0xdb20-0xdb200fff has been reserved [1.077572] pci :01:00.0: BAR 6: no parent found for of device [0xfff8-0x] [1.077697] pci :03:00.0: BAR 6: no parent found for of device [0x-0x] [1.077874] pci :00:03.0: PCI bridge, secondary bus :01 [1.077877] pci :00:03.0: IO window: 0x6000-0x6fff [1.077881] pci :00:03.0: MEM window: 0xd200-0xd30f [1.077885] pci :00:03.0: PREFETCH window: 0x00c000-0x00d1ff [1.077891] pci :00:1c.0: PCI bridge, secondary bus :02 [1.077899] pci :00:1c.0: IO window: 0x5000-0x5fff [1.077908] pci :00:1c.0: MEM window: 0xda10-0xdb0f [1.077917] pci :00:1c.0: PREFETCH window: 0x00d310-0x00d40f [1.077929] pci :00:1c.1: PCI bridge, secondary bus :03 [1.077937] pci :00:1c.1: IO window: 0x4000-0x4fff
Bug#616689: Root-on-LVM setup fails often due to timing issues
My root-on-lvm system has worked reliably for some time, but fails to boot every time with kernel 3.8. I suspect the change may be due to the removal of the scsi_wait_scan module in 3.6. (init-top/udev waits using the module if available.) Bug 678688 suggests a solution involving repeated calls to a local-block script on availability of a new block device, but it doesn't seem to have been implemented. An alternative would be for LVM to provide udev rules to automatically activate the root vg/lv when the relevant devices are available. I'm not sure at what point the information needed to make this determination becomes available. A third solution would be for the hook scripts to construct a list of block devices needed to bring up the root vg/lv, and have the lvm initramfs script wait for these specific devices to be available. This is more fragile if disks are reconfigured. -- 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/20130603162451.gf4...@leiserson.org
Bug#443979: marked as done (Linux boot hangs on AMD Geode GX systems)
Your message dated Mon, 3 Jun 2013 19:01:55 +0200 with message-id 20130603170155.GA5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #443979, regarding Linux boot hangs on AMD Geode GX systems 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.) -- 443979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: CD with a netinst image Image version: 1st one i am not sure but second attempt was from http://cdimage.debian.org/debian-cd/4.0_r1/i386/iso-cd/debian-40r1-i386-netinst.iso Date: been trying on and off since the week of 10th sept 2007 Machine: ETX-LX-800 R10 board on an mini ITX base board Processor: AMD Geode GX MMX 500MHz Memory: 256MB + 8MB graphics Partitions: none yet, didnt get that far but i am using a 2GB Sandisk Extreme 3 compact flash card via an IDE adapter - set as primary on an ide bus with a CDRW drive as secondary on the same cable Output of lspci -nn and lspci -vnn: i can't get this far/don't know what this is Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ O] Detect network card: [ installer falls over before this] Configure network: [ installer falls over before this] Detect CD: [ Ok for boot but installer doesnt get far enough] Load installer modules: [loads vmlinuxz and initrd.gz then falls over ] Detect hard drives: [ installer falls over before this] Partition hard drives: [ installer falls over before this] Install base system: [ installer falls over before this] Clock/timezone setup: [ installer falls over before this] User/password setup: [ installer falls over before this] Install tasks: [ installer falls over before this] Install boot loader: [ installer falls over before this] Overall install: [E ] Comments/Problems: I run up the system and it boots to the cd which runs the Debian installer app. I get the splash screen with the 'F1 or enter' text. If i just press enter i get a blank screen with a flashing cursor, if i press f1 then install i get: Loading /install.386/vmlinuz... Loading /install.386/initrd.gz... Ready. _ and there is where it sits until i reboot it. I tried another disk image just to make sure the disk was ok and got the same result. I tried installing Fedora, that works fine so i am pretty sure my hardware is functional. I then read through some of the Debian install docs resulting in changes to my Bios as follows: using extended memory disabled virus warnings disabled video bios shadow set power management to APM and disabled all the various other power management This made no difference so i started playing with installer command line arguments. I have tried various combinations of the following (sorry about this next bit): tried expert and install mem=256m priority=low fb=false video=vga16:off DEBIAN_FRONTEND= i 've tried all the options noninteractive, text, newt, gtk BOOT_DEBUG=3 and 2|3 noapic nolapic acpi=off DEBCONF_DEBUG=5 vga=771 also tried 769, 784, 785, 786, 787, 788, 789, 773, 790, 791, 792, 775 but they all give me blank screens - values higher than 792 give me the 'not supported under vesa' type message and a scan of the video modes available gives me the following (but i don't really think this helps you at all): 0 0f00 80x25 1 0f01 80x50 2 0f02 80x43 3 0f03 80x28 4 0f05 80x30 5 0f06 80x34 6 0f07 80x60 7 0100 40x25 at no point do i get any additional debug and alt f1-f12 and alt cntrl f1-f12 do nothing. As you can see i am now in the clutching at straws stage Wink Any help or guidance you might have would be very useful thanks Steve This electronic transmission is strictly confidential and intended solely for the addressee(s). If you are not the intended addressee, you must not disclose, copy or take any action in reliance of this email. If you have received this email in error please notify the sender as soon as possible. Any views expressed within this email may not necessarily be the views held by Calrec Audio Ltd. Calrec Audio Ltd have taken measures to ensure this email is free from computer viruses, however it is recommended that you also employ anti-virus measures on your computer systems. Calrec Audio Ltd. Registered in England. Registration number: 02392336. WEEE registration number: WEE/JE0051TQ/PRO. Registered address: Nutclough Mill, Hebden Bridge, West Yorks, HX7 8EZ. ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6
Bug#495014: marked as done (linux-source-2.6.26: IDE reset, DMA, 32-bit access killed on hald startup, via driver)
Your message dated Mon, 3 Jun 2013 19:01:55 +0200
with message-id 20130603170155.GA5319@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #495014,
regarding linux-source-2.6.26: IDE reset, DMA, 32-bit access killed on hald
startup, via driver
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.)
--
495014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-source-2.6.26
Version: 2.6.26-2
Severity: important
I am compiling in the via ide driver via82cxxx
Kernel boots up fine until hald starts. At this point, an 0xd opcode/busy is
reported and IDE is reset, DMA (and 32bit, etc) disabled.
I can restore these parameters with hdparms but this will lead to problems.
I noticed in the sources compared with 2.6.23 that the timing setup was changed.
This might be the problem (also had on 2.6.25). Possibly the old way is
necessary or a needed option.
Here is the logcheck section (hal startup shows on bootup display)
Aug 12 17:54:58 d_baron kernel: ttyS1: LSR safety check engaged!
Aug 12 17:54:58 d_baron kernel: hdc: dma_intr: status=0xd0 { Busy }
Aug 12 17:54:58 d_baron kernel: ide: failed opcode was: unknown
Aug 12 17:54:58 d_baron kernel: hdc: DMA disabled
Aug 12 17:54:58 d_baron kernel: hdd: DMA disabled
Aug 12 17:54:58 d_baron kernel: ide1: reset: success
(hda, hdb DMA, other parameters disabled as well.)
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (650, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.23-rt1-davidb (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-source-2.6.26 depends on:
ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii bzip2 1.0.5-0.1high-quality block-sorting file co
Versions of packages linux-source-2.6.26 recommends:
ii gcc 4:4.3.1-2 The GNU C compiler
ii libc6-dev [libc-dev] 2.7-13 GNU C Library: Development Librari
ii make 3.81-5 The GNU version of the make util
Versions of packages linux-source-2.6.26 suggests:
ii kernel-package11.001-0.1 A utility for building Linux kerne
ii libncurses5-dev [ncurses- 5.6+20080713-1 developer's libraries and docs for
ii libqt3-mt-dev 3:3.3.8b-5 Qt development files (Threaded)
-- no debconf information
---End Message---
---BeginMessage---
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.0 / 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#447153: marked as done (/usr/bin/scp: Fails to notice write errors)
Your message dated Mon, 3 Jun 2013 19:01:55 +0200 with message-id 20130603170155.GA5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #447153, regarding /usr/bin/scp: Fails to notice write 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.) -- 447153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: openssh-client Version: 1:4.6p1-5 Severity: grave File: /usr/bin/scp Justification: causes non-serious data loss When copying to a cifs share scp fails to notice write errors and happily continues copying when there is no disk space. Note that cifs probably only reports these errors on close(), not write(). -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (300, 'unstable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages openssh-client depends on: ii adduser 3.104 add and remove users and groups ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy ii dpkg 1.14.5 package maintenance system for Deb ii libc6 2.6.1-1GNU C Library: Shared libraries ii libcomerr21.40.2-1 common error description library ii libedit2 2.9.cvs.20050518-4 BSD editline and history libraries ii libkrb53 1.6.dfsg.1-6 MIT Kerberos runtime libraries ii libncurses5 5.6+20070908-1 Shared libraries for terminal hand ii libssl0.9.8 0.9.8e-6 SSL shared libraries ii passwd1:4.0.18.1-11 change and administer password and ii zlib1g1:1.2.3.3.dfsg-5 compression library - runtime openssh-client recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- 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.0 / 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#428615: marked as done (linux-image-2.6.20-1-amd64: ACPI procfs thermal and fan directories are empty on an ASUS P5B-VM motherboard)
Your message dated Mon, 3 Jun 2013 19:01:55 +0200 with message-id 20130603170155.GA5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #428615, regarding linux-image-2.6.20-1-amd64: ACPI procfs thermal and fan directories are empty on an ASUS P5B-VM motherboard 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.) -- 428615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.20-1-amd64 Version: 2.6.20-3 Severity: normal Hi! It seems I'm not able to read ACPI temperature or fan data on a box with an ASUS P5B-VM motherboard. I think the appropriate modules are loaded (see below: thermal and fan), but, nonetheless: $ ls -altrF /proc/acpi/thermal_zone/ total 0 dr-xr-xr-x 10 root root 0 2007-06-10 16:21 ../ dr-xr-xr-x 2 root root 0 2007-06-10 23:00 ./ $ ls -altrF /proc/acpi/fan/ total 0 dr-xr-xr-x 10 root root 0 2007-06-10 16:21 ../ dr-xr-xr-x 2 root root 0 2007-06-10 23:00 ./ What's wrong? What did I fail to understand? -- Package-specific info: ** Version: Linux version 2.6.20-1-amd64 (Debian 2.6.20-3) (wa...@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Tue Apr 24 21:10:58 UTC 2007 ** Not tainted ** Kernel log: drivers/usb/input/hid-core.c: v2.6:USB HID core driver JMB363: IDE controller at PCI slot :03:00.1 PCI: Enabling device :03:00.1 ( - 0001) ACPI: PCI Interrupt :03:00.1[B] - GSI 17 (level, low) - IRQ 17 JMB363: chipset revision 2 JMB363: 100% native mode on irq 17 PCI: Setting latency timer of device :03:00.1 to 64 ide2: BM-DMA at 0xb400-0xb407, BIOS settings: hde:pio, hdf:pio ide3: BM-DMA at 0xb408-0xb40f, BIOS settings: hdg:pio, hdh:pio Probing IDE interface ide2... ieee1394: Host added: ID:BUS[0-00:1023] GUID[0011d8e015d5] hde: LITE-ON DVDRW SOHW-1673S, ATAPI CD/DVD-ROM drive hde: hw_config= hde: hw_config= ide2 at 0xbc00-0xbc07,0xb882 on irq 17 Probing IDE interface ide3... ata_piix :00:1f.2: version 2.00ac7 ata_piix :00:1f.2: MAP [ P0 P2 P1 P3 ] ACPI: PCI Interrupt :00:1f.2[B] - GSI 19 (level, low) - IRQ 19 PCI: Setting latency timer of device :00:1f.2 to 64 ata1: SATA max UDMA/133 cmd 0xE880 ctl 0xE802 bmdma 0xE080 irq 19 ata2: SATA max UDMA/133 cmd 0xE480 ctl 0xE402 bmdma 0xE088 irq 19 scsi0 : ata_piix ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32) ata1.00: ata1: dev 0 multi count 16 ata1.00: configured for UDMA/133 scsi1 : ata_piix ATA: abnormal status 0x7F on port 0xE487 scsi 0:0:0:0: Direct-Access ATA MAXTOR STM325082 3.AA PQ: 0 ANSI: 5 ata_piix :00:1f.5: MAP [ P0 P2 P1 P3 ] ACPI: PCI Interrupt :00:1f.5[B] - GSI 19 (level, low) - IRQ 19 PCI: Setting latency timer of device :00:1f.5 to 64 ata3: SATA max UDMA/133 cmd 0xD080 ctl 0xD002 bmdma 0xC800 irq 19 ata4: SATA max UDMA/133 cmd 0xCC00 ctl 0xC882 bmdma 0xC808 irq 19 scsi2 : ata_piix ATA: abnormal status 0x7F on port 0xD087 scsi3 : ata_piix ATA: abnormal status 0x7F on port 0xCC07 SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda:6hde: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache6hde: hw_config= , UDMA(66) Uniform CD-ROM driver Revision: 3.20 sda1 sda2 sda5 sd 0:0:0:0: Attached scsi disk sda device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-de...@redhat.com Attempting manual resume kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. ACPI: PCI Interrupt :00:1b.0[A] - GSI 22 (level, low) - IRQ 22 PCI: Setting latency timer of device :00:1b.0 to 64 input: PC Speaker as /class/input/input2 pnp: the driver 'parport_pc' has been registered pnp: match found with the PnP device '00:0b' and the driver 'parport_pc' parport: PnPBIOS parport detected. parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (11-Nov-2006) iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, TCOBASE=0x0860) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) hda_codec: Unknown model for AD1988, trying auto-probe
Bug#439435: marked as done (/usr/share/man/man8/mount.cifs.8.gz: include in man mount.cifs: echo 0 /proc/fs/cifs/LinuxExtensionsEnabled to enable uid to work)
Your message dated Mon, 3 Jun 2013 19:01:55 +0200 with message-id 20130603170155.GA5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #439435, regarding /usr/share/man/man8/mount.cifs.8.gz: include in man mount.cifs: echo 0 /proc/fs/cifs/LinuxExtensionsEnabled to enable uid to 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.) -- 439435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: smbfs Version: 3.0.14a-3sarge6 Severity: normal File: /usr/share/man/man8/mount.cifs.8.gz mount.cifs ignores the uid and gid options when the target server supports the CIFS Unix extensions. This causes a serious problem when the target server doesn't do the uid and gid properly. I know because I just experienced this problem tonight. See http://lwn.net/Articles/232430/ as a reference. Ideally, the user should be able to instruct mount.cifs to use the provided uid and gid options regardless of Unix extensions. Another good thing to do would be to put the workaround solution in the man page. I know it works because I tried it tonight. The workaround is echo 0 /proc/fs/cifs/LinuxExtensionsEnabled before mounting. By the way, I actually did this on an Ubuntu Feisty system, but I am reporting to Debian since I love Debian. The SMB file server was an Apple computer running Mac OS X. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages smbfs depends on: ii libc6 2.3.2.ds1-22sarge6 GNU C Library: Shared libraries an ii libcomerr21.37-2sarge1 common error description library ii libkrb53 1.3.6-2sarge5 MIT Kerberos runtime libraries ii libldap2 2.1.30-8 OpenLDAP libraries ii netbase 4.21 Basic TCP/IP networking system ii samba-common 3.0.14a-3sarge6Samba common files used by both th -- no debconf information -- Of all the enemies to public liberty war is, perhaps, the most to be dreaded, because it comprises and develops the germ of every other. War is the parent of armies; from these proceed debts and taxes; and armies, and debts, and taxes are the known instruments for bringing the many under the domination of the few. In war, too, the discretionary power of the Executive is extended; . . . . No nation could preserve its freedom in the midst of continual warfare. James Madison, 1795, from Letters and Other Writings of James Madison ---End Message--- ---BeginMessage--- 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.0 / 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#498576: marked as done (linux-image-2.6.26-1-686: USB Mouse stopped working during copying files to USB drive)
Your message dated Mon, 3 Jun 2013 19:01:55 +0200 with message-id 20130603170155.GA5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #498576, regarding linux-image-2.6.26-1-686: USB Mouse stopped working during copying files to USB drive 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.) -- 498576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-4 Severity: normal Tags: l10n During copying large files (3 files, totally ~600 MB) to USB drive (Sandisk Cruzer) with unicode characters in their names using Nautilus, the USB mouse stopped working (the touchpad still worked). File copying was stuck (after successfully copying 2 of the 3 files), and the device was unmounted (and not recognized any more until restart). When trying to restart the X server, the computer hangs. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-4) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 12:00:54 UTC 2008 ** Command line: root=/dev/sda3 ro ** Tainted: P (1) ** Kernel log: [4.412756] ata1.00: configured for UDMA/100 [4.420042] usbcore: registered new interface driver hiddev [4.429078] input: HID 1241:1166 as /class/input/input1 [4.429078] input,hidraw0: USB HID v1.10 Mouse [HID 1241:1166] on usb-:00:13.0-1 [4.429078] usbcore: registered new interface driver usbhid [4.429078] usbhid: v2.6:USB HID core driver [4.732066] ata2: SATA link down (SStatus 0 SControl 300) [4.732302] scsi 0:0:0:0: Direct-Access ATA TOSHIBA MK4032GS AS21 PQ: 0 ANSI: 5 [4.732653] ATIIXP: IDE controller (0x1002:0x4376 rev 0x80) at PCI slot :00:14.1 [4.732740] ACPI: PCI Interrupt :00:14.1[A] - GSI 16 (level, low) - IRQ 16 [4.732855] ATIIXP: not 100% native mode: will probe irqs later [4.732913] ATIIXP: IDE port disabled [4.732975] ide0: BM-DMA at 0x8468-0x846f [4.733034] Probing IDE interface ide0... [5.468504] hda: DW-224E-C, ATAPI CD/DVD-ROM drive [6.140090] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [6.140318] hda: UDMA/33 mode selected [6.140617] ide0 at 0x170-0x177,0x376 on irq 15 [6.142854] ACPI: PCI Interrupt :09:02.0[A] - GSI 21 (level, low) - IRQ 21 [6.144282] eth0: RealTek RTL8139 at 0xa000, 00:16:36:b5:b2:ed, IRQ 21 [6.144340] eth0: Identified 8139 chip type 'RTL-8100B/8139D' [6.172149] Driver 'sd' needs updating - please use bus_type methods [6.172365] sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB) [6.172450] sd 0:0:0:0: [sda] Write Protect is off [6.172504] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [6.172552] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6.172703] sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB) [6.172785] sd 0:0:0:0: [sda] Write Protect is off [6.172840] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [6.172887] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6.172955] sda:6hda: ATAPI 24X DVD-ROM CD-R/RW drive, 1654kB Cache [6.189970] Uniform CD-ROM driver Revision: 3.20 [6.243093] sda1 sda2 sda5 sda6 sda3 [6.285010] sd 0:0:0:0: [sda] Attached SCSI disk [6.613306] PM: Starting manual resume from disk [6.652918] EXT3-fs: INFO: recovery required on readonly filesystem. [6.652986] EXT3-fs: write access will be enabled during recovery. [ 13.461261] kjournald starting. Commit interval 5 seconds [ 13.461261] EXT3-fs: sda3: orphan cleanup on readonly fs [ 13.461261] ext3_orphan_cleanup: deleting unreferenced inode 556643 [ 13.461261] ext3_orphan_cleanup: deleting unreferenced inode 556627 [ 13.461261] EXT3-fs: sda3: 2 orphan inodes deleted [ 13.461261] EXT3-fs: recovery complete. [ 13.474779] EXT3-fs: mounted filesystem with ordered data mode. [ 15.709402] udevd version 125 started [ 16.868680] Linux agpgart interface v0.103 [ 17.043084] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 17.065178] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 17.334441] input: Power Button (FF) as /class/input/input2 [ 17.360684] ACPI: Power Button (FF) [PWRF] [ 17.360850] input: Lid Switch as /class/input/input3 [ 17.392886] ACPI: Lid Switch [LID] [ 17.393036] input: Power Button (CM) as /class/input/input4 [ 17.416132] ACPI: Power Button (CM)
Bug#497562: marked as done (ext3_free_blocks: Freeing blocks not in datazone error on heavy disk activity)
Your message dated Mon, 3 Jun 2013 19:01:55 +0200 with message-id 20130603170155.GA5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #497562, regarding ext3_free_blocks: Freeing blocks not in datazone error on heavy disk activity 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.) -- 497562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.24-etchnhalf.1-486 Version: 2.6.24-6~etchnhalf.4 Severity: normal Hello, This is a follow up to bug #426409 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426409#17). I switched to the etchnhalf kernel as advised. The error still occurs but is less severe as the affected volume does not re-mount read-only as before. I hope this is because the error is better handled internally in the ext3 code as opposed to just continuing to operate on an inconsistent volume. The error messages are also different than before: there are no journal error messages now, but the ext3_free_blocks_sb: bit already cleared for block error is new. The affected device is an ext3 volume on a LVM device, which is on a RAID 0 mirror of two SATA hard drives. from kern.log Aug 11 18:30:02 menno kernel: EXT3-fs error (device dm-1): ext3_free_blocks: Freeing blocks not in datazone - block = 329867264, count = 1 Aug 11 18:30:02 menno kernel: EXT3-fs error (device dm-1): ext3_free_blocks: Freeing blocks not in datazone - block = 2147487744, count = 1 Aug 11 18:30:02 menno kernel: EXT3-fs error (device dm-1): ext3_free_blocks_sb: bit already cleared for block 10580596 Aug 11 18:30:02 menno kernel: EXT3-fs error (device dm-1): ext3_free_blocks_sb: bit already cleared for block 10580597 Aug 11 18:30:02 menno kernel: EXT3-fs error (device dm-1): ext3_free_blocks_sb: bit already cleared for block 10580598 Aug 11 18:30:02 menno kernel: EXT3-fs error (device dm-1): ext3_free_blocks_sb: bit already cleared for block 10580599 ... Aug 25 15:30:01 menno kernel: EXT3-fs error (device dm-1): ext3_free_blocks: Freeing blocks not in datazone - block = 177790976, count = 1 (no ext3_free_blocks_sb: bit already cleared for block error on Aug. 25) # uname -a Linux menno 2.6.24-etchnhalf.1-486 #1 Mon Jul 21 10:36:16 UTC 2008 i686 GNU/Linux # cat /etc/fstab ... /dev/vg_on_md0/public /data/publicext3acl 0 0 ... Regards, Tim -- Package-specific info: ** Version: Linux version 2.6.24-etchnhalf.1-486 (Debian 2.6.24-6~etchnhalf.4) (da...@debian.org ) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Mon Jul 21 10:36:16 UTC 2008 ** Command line: root=/dev/md1 ro ** Not tainted ** Kernel log: raid1: raid set md2 active with 2 out of 2 mirrors md: md3 stopped. md: bindhdc3 md: bindhda3 raid1: raid set md3 active with 2 out of 2 mirrors device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-de...@redhat.com Attempting manual resume kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Linux agpgart interface v0.102 agpgart: Detected NVIDIA nForce2 chipset agpgart: AGP aperture is 64M @ 0xe000 i2c-adapter i2c-0: nForce2 SMBus adapter at 0x5000 i2c-adapter i2c-1: nForce2 SMBus adapter at 0x5500 input: Power Button (FF) as /class/input/input1 ACPI: Power Button (FF) [PWRF] input: Power Button (CM) as /class/input/input2 ACPI: Power Button (CM) [PWRB] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 input: PC Speaker as /class/input/input3 Real Time Clock Driver v1.12ac Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 Adding 1952120k swap on /dev/md2. Priority:-1 extents:1 across:1952120k EXT3 FS on md1, internal journal i2c /dev entries driver kjournald starting. Commit interval 5 seconds EXT3 FS on dm-1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex NET: Registered protocol family 10 lo: Disabled Privacy Extensions tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com tun0: Disabled Privacy Extensions RPC: Registered udp transport module. RPC: Registered tcp transport module. Installing knfsd (copyright (C) 1996 o...@monad.swb.de). NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace
Bug#507271: marked as done ([linux-image-2.6.26-1-686] kernel cannot be installed: subprocess post-installation script returned error exit status 1)
Your message dated Mon, 3 Jun 2013 19:02:28 +0200 with message-id 20130603170228.GB5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #507271, regarding [linux-image-2.6.26-1-686] kernel cannot be installed: subprocess post-installation script returned error exit status 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.) -- 507271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-10 Hi, I'm currently running a debian testing (Lenny) with the following kernel: linux-image-2.6.24-1-686 (2.6.24-7). I wanted to upgrade my debian and all new packages have been installed/configured correctly except for the 2.6.26 kernel (linux-image-2.6.26-1-686). When I tried to install this package, the postinst failed. See bellow the complete stack of aptitude: ~# aptitude safe-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Reading task descriptions... Done The following partially installed packages will be configured: linux-image-2.6.26-1-686 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0B of archives. After unpacking 0B will be used. Setting up linux-image-2.6.26-1-686 (2.6.26-10) ... Running depmod. Running mkinitramfs-kpkg. initrd.img(/boot/initrd.img-2.6.26-1-686 ) points to /boot/initrd.img-2.6.26-1-686 (/boot/initrd.img-2.6.26-1-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.26-1-686.postinst line 569. vmlinuz(/boot/vmlinuz-2.6.26-1-686 ) points to /boot/vmlinuz-2.6.26-1-686 (/boot/vmlinuz-2.6.26-1-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.26-1-686.postinst line 569. Running postinst hook script update-grub. Searching for GRUB installation directory ... found: /boot/grub User postinst hook script [update-grub] exited with value 1 dpkg: error processing linux-image-2.6.26-1-686 (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-2.6.26-1-686 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.26-1-686 (2.6.26-10) ... Running depmod. Running mkinitramfs-kpkg. initrd.img(/boot/initrd.img-2.6.26-1-686 ) points to /boot/initrd.img-2.6.26-1-686 (/boot/initrd.img-2.6.26-1-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.26-1-686.postinst line 569. vmlinuz(/boot/vmlinuz-2.6.26-1-686 ) points to /boot/vmlinuz-2.6.26-1-686 (/boot/vmlinuz-2.6.26-1-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.26-1-686.postinst line 569. Running postinst hook script update-grub. Searching for GRUB installation directory ... found: /boot/grub User postinst hook script [update-grub] exited with value 1 dpkg: error processing linux-image-2.6.26-1-686 (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-2.6.26-1-686 Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Reading task descriptions... Done My configuration: - Motherboard D201GLY2: http://www.intel.com/Products/Desktop/Motherboards/D201GLY2/D201GLY2-overview.htm - HDD: - 2 1/2: IBM Travelstar (IC25N030ATDA04-0) - 3 1/2: SAMSUNG SpinPoint T166 series (HD501LJ) Let me know if you need more information, Best Regards, Frederic L. ---End Message--- ---BeginMessage--- 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.0 / 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#502434: marked as done (linux-image-2.6.26-1-686 do not boot)
Your message dated Mon, 3 Jun 2013 19:02:28 +0200 with message-id 20130603170228.GB5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #502434, regarding linux-image-2.6.26-1-686 do not boot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 502434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502434 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-8 When i try to boot with the new kernel in lenny, the boot process hangs at a kernel panic. I don't really know where to get the log when the kernel do not boot. If someone could help me, i could send you more info. Regards, David. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92j tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i6862.7-14 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii grub 0.97-47GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none (no description available) -- debconf information: linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686: shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/kimage-is-a-directory: linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686: ---End Message--- ---BeginMessage--- 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.0 / 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#498724: marked as done (ALSA: snd-hda-intel: no working master and unmutable pcm channel)
Your message dated Mon, 3 Jun 2013 19:01:55 +0200 with message-id 20130603170155.GA5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #498724, regarding ALSA: snd-hda-intel: no working master and unmutable pcm channel 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.) -- 498724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-4 Severity: normal When I run alsamixer, I can see a master channel, but it has no volume slider. It's possible to mute the master but it has no effect (sound keeps playing). The PCM channel does control the volume, but it is not mutable (the m key doesn't do anything). Any gui mixer application fails to correctly work in this situation. Muting using shortcuts doesn't work, as the only way it could work is by setting the volume to 0%, not by actually muting. Somehow this problem does not exist in Ubuntu, I don't know how they fixed it. Alexander -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-4) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 12:00:54 UTC 2008 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.26-1-686 root=/dev/sda5 ro ** Not tainted ** Kernel log: [ 36.784798] lp: driver loaded but no devices found [ 36.827608] ppdev: user-space parallel port driver [ 37.489682] NET: Registered protocol family 10 [ 37.489682] lo: Disabled Privacy Extensions [ 37.489682] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 40.154493] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use) [ 41.919589] Bluetooth: Core ver 2.11 [ 41.919589] NET: Registered protocol family 31 [ 41.919589] Bluetooth: HCI device and connection manager initialized [ 41.919589] Bluetooth: HCI socket layer initialized [ 42.031788] Bluetooth: L2CAP ver 2.9 [ 42.031788] Bluetooth: L2CAP socket layer initialized [ 42.058992] Bluetooth: RFCOMM socket layer initialized [ 42.058992] Bluetooth: RFCOMM TTY layer initialized [ 42.058992] Bluetooth: RFCOMM ver 1.8 [ 42.237403] ACPI: PCI Interrupt :05:00.0[A] - GSI 18 (level, low) - IRQ 18 [ 42.237481] PM: Writing back config space on device :05:00.0 at offset 1 (was 12, writing 16) [ 42.237481] firmware: requesting iwlwifi-3945-1.ucode [ 42.372754] Registered led device: iwl-phy0:radio [ 42.372754] Registered led device: iwl-phy0:assoc [ 42.372754] Registered led device: iwl-phy0:RX [ 42.372754] Registered led device: iwl-phy0:TX [ 42.392036] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 46.619752] [drm] Initialized drm 1.1.0 20060810 [ 46.627755] ACPI: PCI Interrupt :00:02.0[A] - GSI 16 (level, low) - IRQ 16 [ 46.627755] PCI: Setting latency timer of device :00:02.0 to 64 [ 46.627755] [drm] Initialized i915 1.6.0 20060119 on minor 0 [ 82.977255] CPU0 attaching NULL sched-domain. [ 82.977272] CPU1 attaching NULL sched-domain. [ 83.007810] CPU0 attaching sched-domain: [ 83.007810] domain 0: span 0-1 [ 83.007810] groups: 0 1 [ 83.007810] CPU1 attaching sched-domain: [ 83.007810] domain 0: span 0-1 [ 83.007810] groups: 1 0 [ 393.828259] CPU0 attaching NULL sched-domain. [ 393.828268] CPU1 attaching NULL sched-domain. [ 393.829423] CPU0 attaching sched-domain: [ 393.829423] domain 0: span 0-1 [ 393.829423] groups: 0 1 [ 393.829423] CPU1 attaching sched-domain: [ 393.829423] domain 0: span 0-1 [ 393.829423] groups: 1 0 [ 402.691384] wlan0: Initial auth_alg=0 [ 402.691384] wlan0: authenticate with AP 00:17:9a:f2:12:c7 [ 402.693069] wlan0: RX authentication from 00:17:9a:f2:12:c7 (alg=0 transaction=2 status=0) [ 402.693080] wlan0: authenticated [ 402.693087] wlan0: associate with AP 00:17:9a:f2:12:c7 [ 402.696047] wlan0: RX AssocResp from 00:17:9a:f2:12:c7 (capab=0x431 status=0 aid=1) [ 402.696047] wlan0: associated [ 402.696047] wlan0: switched to short barker preamble (BSSID=00:17:9a:f2:12:c7) [ 402.699307] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.628975] wlan0: no IPv6 routers present [ 543.840992] wlan0: deauthenticate(reason=3) [ 544.095774] ACPI: PCI interrupt for device :05:00.0 disabled [ 544.168973] ACPI: PCI Interrupt :05:00.0[A] - GSI 18 (level, low) - IRQ 18 [ 544.168973] PM: Writing back config space on device :05:00.0 at offset 1 (was 12, writing 16) [ 544.226241] Registered led device: iwl-phy0:radio [ 544.226241] Registered led device:
Bug#507552: marked as done (linux-image-2.6.18-6-686-bigmem: kernel BUG at fs/locks.c:2001! in nfsd)
Your message dated Mon, 3 Jun 2013 19:02:28 +0200
with message-id 20130603170228.GB5319@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #507552,
regarding linux-image-2.6.18-6-686-bigmem: kernel BUG at fs/locks.c:2001! in
nfsd
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.)
--
507552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.18-6-686-bigmem
Version: 2.6.18.dfsg.1-23
Severity: normal
Dec 1 23:46:50 lmserv kernel: [ cut here ]
Dec 1 23:46:50 lmserv kernel: kernel BUG at fs/locks.c:2001!
Dec 1 23:46:50 lmserv kernel: invalid opcode: [#1]
Dec 1 23:46:50 lmserv kernel: SMP
Dec 1 23:46:50 lmserv kernel: Modules linked in: iptable_filter
ip_tables x_tables ipmi_devintf nfs autofs4 ipv6 dm_snapshot w83793
hwmon_vid ioatdma lock_dlm dlm gfs lock_harness cman ipmi_watchdog
ipmi_si ipmi_msghandler hangcheck_timer nfsd exportfs lockd nfs_acl
sunrpc 8021q bonding tsdev sg sr_mod cdrom shpchp i2c_i801 pci_hotplug
psmouse i2c_core joydev evdev serio_raw rtc pcspkr ext3 jbd mbcache
dm_mirror dm_mod usbhid usb_storage sd_mod piix qla2xxx ahci ehci_hcd
floppy firmware_class libata scsi_transport_fc tg3 scsi_mod generic
ide_core uhci_hcd usbcore e1000 thermal processor fan
Dec 1 23:46:50 lmserv kernel: CPU:4
Dec 1 23:46:50 lmserv kernel: EIP:0060:[c016aaa7]Not tainted
VLI
Dec 1 23:46:50 lmserv kernel: EFLAGS: 00010246 (2.6.18-6-686-bigmem
#1)
Dec 1 23:46:50 lmserv kernel: EIP is at locks_remove_flock+0xc1/0xde
Dec 1 23:46:50 lmserv kernel: eax: f47f1b3c ebx: f291a7cc ecx:
f291a7cc edx: 0001
Dec 1 23:46:50 lmserv kernel: esi: f40b62c0 edi: f291a728 ebp:
f291a728 esp: f6c0deec
Dec 1 23:46:50 lmserv kernel: ds: 007b es: 007b ss: 0068
Dec 1 23:46:50 lmserv kernel: Process nfsd (pid: 3962, ti=f6c0c000
task=dffb9000 task.ti=f6c0c000)
Dec 1 23:46:50 lmserv kernel: Stack:
0f7a
Dec 1 23:46:50 lmserv kernel: f40b62c0
0202 7fff
Dec 1 23:46:50 lmserv kernel:
Dec 1 23:46:50 lmserv kernel: Call Trace:
Dec 1 23:46:50 lmserv kernel: [c015a0ad] __fput+0x76/0x13f
Dec 1 23:46:50 lmserv kernel: [f8bc17a0] release_stateid+0x92/0xbf
[nfsd]
Dec 1 23:46:50 lmserv kernel: [f8bc16dd]
release_stateowner+0x96/0xc7 [nfsd]
Dec 1 23:46:50 lmserv kernel: [f8bc247f] expire_client+0x128/0x13e
[nfsd]
Dec 1 23:46:50 lmserv kernel: [f8bc258c]
nfs4_state_shutdown+0x87/0x163 [nfsd]
Dec 1 23:46:50 lmserv kernel: [f8bae6e7] nfsd+0x2cd/0x30a [nfsd]
Dec 1 23:46:50 lmserv kernel: [f8bae41a] nfsd+0x0/0x30a [nfsd]
Dec 1 23:46:50 lmserv kernel: [c0101005]
kernel_thread_helper+0x5/0xb
Dec 1 23:46:50 lmserv kernel: Code: 34 39 70 28 75 2d 0f b6 50 2c f6 c2
02 74 09 89 d8 e8 b7 fe ff ff eb 1d f6 c2 20 74 0e ba 02 00 00 00 89 d8
e8 12 ff ff ff eb 0a 0f 0b d1 07 20 b8 29 c0 89 c3 8b 03 85 c0 75 c6
e8 50 64 11 00
Dec 1 23:46:50 lmserv kernel: EIP: [c016aaa7]
locks_remove_flock+0xc1/0xde SS:ESP 0068:f6c0deec
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (990, 'stable'), (50, 'testing'), (10, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686-bigmem
Locale: LANG=es_ES@euro, LC_CTYPE=es_ES@euro (charmap=ISO-8859-15) (ignored:
LC_ALL set to es_ES@euro)
Versions of packages linux-image-2.6.18-6-686-bigmem depends on:
ii coreutils5.97-5.3The GNU core utilities
ii debconf [debconf-2.0]1.5.11etch1 Debian configuration management sy
ii initramfs-tools [linux-initr 0.92b tools for generating an initramfs
ii module-init-tools3.3-pre4-2 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.18-6-686-bigmem recommends:
pn libc6-i686none (no description available)
-- debconf information:
linux-image-2.6.18-6-686-bigmem/preinst/abort-overwrite-2.6.18-6-686-bigmem:
linux-image-2.6.18-6-686-bigmem/preinst/failed-to-move-modules-2.6.18-6-686-bigmem:
linux-image-2.6.18-6-686-bigmem/preinst/bootloader-initrd-2.6.18-6-686-bigmem:
true
linux-image-2.6.18-6-686-bigmem/preinst/abort-install-2.6.18-6-686-bigmem:
linux-image-2.6.18-6-686-bigmem/postinst/create-kimage-link-2.6.18-6-686-bigmem:
true
Bug#502901: marked as done (linux-image-2.6.24-etchnhalf.1-686: Epoll failure after running out of, descriptors (DoS?))
Your message dated Mon, 3 Jun 2013 19:02:28 +0200
with message-id 20130603170228.GB5319@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #502901,
regarding linux-image-2.6.24-etchnhalf.1-686: Epoll failure after running out
of, descriptors (DoS?)
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.)
--
502901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.24-etchnhalf.1-686
Version: 2.6.24-6~etchnhalf.5
Severity: normal
Hi,
I've written a web app that should be able to handle a lot of new
connections per second (1000+). On multiple servers I've hit a bug.
After running out of descriptors, then closing descriptors, epoll_wait
doesn't return anymore for the listen socket.
I've attached code to reproduce the issue. And an strace log. Even
before closing the descriptors you see epoll_wait already stops returning.
On the other side, I used a self-written app that just opens tons of
connections. Is there a standard utility to do that?
#include arpa/inet.h
#include cassert
#include ctime
#include errno.h
#include netinet/in.h
#include sys/epoll.h
#include sys/ioctl.h
#include sys/socket.h
#include sys/types.h
#include vector
using namespace std;
int main()
{
int l = socket(AF_INET, SOCK_STREAM, 0);
unsigned long p = true;
ioctl(l, FIONBIO, p);
sockaddr_in a = {0};
a.sin_family = AF_INET;
a.sin_addr.s_addr = INADDR_ANY;
a.sin_port = htons(2710);
bind(l, reinterpret_castsockaddr*(a), sizeof(sockaddr_in));
listen(l, SOMAXCONN);
int fd = epoll_create(1 10);
epoll_event e;
e.data.fd = l;
e.events = EPOLLIN | EPOLLOUT | EPOLLPRI | EPOLLERR | EPOLLHUP
| EPOLLET;
epoll_ctl(fd, EPOLL_CTL_ADD, l, e);
const int c_events = 64;
epoll_event events[c_events];
typedef vectorint sockets_t;
sockets_t sockets;
time_t t = time(NULL);
while (1)
{
int r = epoll_wait(fd, events, c_events, 5000);
if (r == -1)
continue;
if (!r time(NULL) - t 30)
{
for (int i = 0; i sockets.size(); i++)
close(sockets[i]);
sockets.clear();
t = INT_MAX;
}
for (int i = 0; i r; i++)
{
if (events[i].data.fd == l)
{
while (1)
{
int s = accept(l, NULL, NULL);
if (s == -1)
{
if (errno == EAGAIN)
break;
break; // continue;
}
sockets.push_back(s);
}
}
else
assert(false);
}
}
return 0;
}
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
ioctl(3, FIONBIO, [1]) = 0
bind(3, {sa_family=AF_INET, sin_port=htons(2710),
sin_addr=inet_addr(0.0.0.0)}, 16) = 0
listen(3, 128) = 0
epoll_create(1024) = 4
epoll_ctl(4, EPOLL_CTL_ADD, 3,
{EPOLLIN|EPOLLPRI|EPOLLOUT|EPOLLERR|EPOLLHUP|EPOLLET, {u32=3,
u64=13806959039201935363}}) = 0
time(NULL) = 1224527442
epoll_wait(4, {}, 64, 5000) = 0
time(NULL) = 1224527447
epoll_wait(4, {{EPOLLIN, {u32=3, u64=13806959039201935363}}}, 64, 5000) = 1
accept(3, 0, NULL) = 5
brk(0) = 0x804c000
brk(0x806d000) = 0x806d000
accept(3, 0, NULL) = 6
accept(3, 0, NULL) = 7
accept(3, 0, NULL) = 8
accept(3, 0, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
epoll_wait(4, {{EPOLLIN, {u32=3, u64=13806959039201935363}}}, 64, 5000) = 1
accept(3, 0, NULL) = 9
...
accept(3, 0, NULL) = 85
accept(3, 0, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
epoll_wait(4,
Bug#508541: marked as done (redhat-cluster-modules-2.6.26-1-686-bigmem: GFS cannot create files over 4KB)
Your message dated Mon, 3 Jun 2013 19:02:28 +0200 with message-id 20130603170228.GB5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #508541, regarding redhat-cluster-modules-2.6.26-1-686-bigmem: GFS cannot create files over 4KB 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.) -- 508541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: redhat-cluster-modules-2.6.26-1-686-bigmem Version: 2.6.26+2.20080801-4 Severity: normal When we try to copy file bigger then ~3,9KB to gfs partition its size become 0. Also we have tried to create new file and size of new file also is 0 (but we can create file ~3kb in size). We have found similar bug with redhat-cluster-modules-2.6.26-1-amd64 (Bug#502081). -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686-bigmem (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages redhat-cluster-modules-2.6.26-1-686-bigmem depends on: ii linux-image-2.6.26-1-686-bigm 2.6.26-11 Linux 2.6.26 image on PPro/Celeron redhat-cluster-modules-2.6.26-1-686-bigmem recommends no packages. redhat-cluster-modules-2.6.26-1-686-bigmem suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- 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.0 / 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#521723: marked as done (smartmontools: smartd fails on amd64 kernel with 3ware controller)
Your message dated Mon, 3 Jun 2013 19:03:10 +0200
with message-id 20130603170310.GC5319@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #521723,
regarding smartmontools: smartd fails on amd64 kernel with 3ware controller
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.)
--
521723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: smartmontools
Version: 5.38-2
Severity: normal
To get support for 64bit KVM guests I switch from the i686 kernel
(linux-image-2.6.26-1-686) to amd64 (linux-image-2.6.26-1-amd64).
The machine has a 3ware controller which smartmontools is capable
of checking its attached disks. After I rebooted and the amd64
kernel came up, smartd refuses to work. dmesg shows that the
kernel logs out some messages then:
[132307.686213] ioctl32(smartd:23945): Unknown cmd fd(3)
cmd(0108){t:01;sz:0} arg(ffc29c5c) on /dev/twa0
[136015.740193] ioctl32(smartd:27292): Unknown cmd fd(3)
cmd(0108){t:01;sz:0} arg(ff94b10c) on /dev/twa0
[139733.432548] ioctl32(smartd:29680): Unknown cmd fd(3)
cmd(0108){t:01;sz:0} arg(4fbc) on /dev/twa0
[143430.429019] ioctl32(smartd:1066): Unknown cmd fd(3)
cmd(0108){t:01;sz:0} arg(ffbceb8c) on /dev/twa0
[172513.471587] ioctl32(smartd:20721): Unknown cmd fd(3)
cmd(0108){t:01;sz:0} arg(ff7f9fbc) on /dev/twa0
[176182.578514] ioctl32(smartd:23674): Unknown cmd fd(3)
cmd(0108){t:01;sz:0} arg(ffa241ec) on /dev/twa0
If I give smartctl a try, it fails too
unki@cdserver:~$ sudo smartctl -a -d 3ware,0 -a /dev/twa0
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
WARNING - NO DEVICE FOUND ON 3WARE CONTROLLER (disk 0)
Note: /dev/sdX many need to be replaced with /dev/tweN or /dev/twaN
Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)
And causes the same log messages:
unki@cdserver:~$ dmesg |grep smartctl
[212209.819155] ioctl32(smartctl:13265): Unknown cmd fd(3)
cmd(0108){t:01;sz:0} arg(ffaec31c) on /dev/twa0
-- Package-specific info:
Ouput of /usr/share/bug/smartmontools:
# CONFIG_IDE_TASK_IOCTL is not set
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages smartmontools depends on:
ii debianutils 2.30Miscellaneous utilities specific t
ii libc62.7-18 GNU C Library: Shared libraries
ii libgcc1 1:4.3.2-1.1 GCC support library
ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
Versions of packages smartmontools recommends:
ii bsd-mailx [mailx] 8.1.2-0.20071201cvs-3 A simple mail user agent
ii mailx 1:20071201-3 Transitional package for mailx ren
smartmontools suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
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.0 / 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#510621: marked as done (linux-image-2.6.26-1-686: v4l1 doesn't work anymore with bttv)
Your message dated Mon, 3 Jun 2013 19:02:28 +0200 with message-id 20130603170228.GB5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #510621, regarding linux-image-2.6.26-1-686: v4l1 doesn't work anymore with bttv 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.) -- 510621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-12 Severity: normal Hi I got a v4l1 application that worked for years. With the current kernel, it hangs in a state where VIDIOCMCAPTURE always return -EBUSY. After some debug, it seems that VIDIOCMCAPTURE fails the first time because of videobuf_queue_is_busy 'vbuf: busy: buffer #0 mapped'. Then after that error it does a VIDIOCSYNC on all buffer. Then every call of VIDIOCMCAPTURE failed because of check_btres returning -EBUSY. I don't know what cause the first videobuf_queue_is_busy error. But for all the other errors I suppose one of the problem is that VIDIOCSYNC does a STREAMON but never does a STREAMOFF... Matthieu -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-12) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Mon Dec 15 18:15:07 UTC 2008 ** Command line: root=/dev/hdf3 ro vga=791 ** Not tainted ** Kernel log: ** Loaded modules: Module Size Used by bttv 148340 2 tuner 21960 0 videodev 27552 4 bttv,tuner videobuf_dma_sg11140 1 bttv videobuf_core 16100 2 bttv,videobuf_dma_sg v4l1_compat12260 1 videodev snd_seq_oss24992 0 snd_seq_dummy 2660 0 rfcomm 28272 2 l2cap 17248 9 rfcomm bluetooth 44900 4 rfcomm,l2cap ppdev 6468 0 parport_pc 22500 0 lp 8164 0 parport30988 3 ppdev,parport_pc,lp autofs416420 1 nfsd 186704 17 auth_rpcgss33952 1 nfsd exportfs3904 1 nfsd nfs 213896 0 lockd 54248 2 nfsd,nfs nfs_acl 2912 2 nfsd,nfs sunrpc162144 15 nfsd,auth_rpcgss,nfs,lockd,nfs_acl xt_DSCP 2944 18 ipt_MASQUERADE 2592 1 ipt_ULOG6820 2 ipt_LOG 5028 10 ip6table_filter 2432 1 ip6_tables 11376 1 ip6table_filter xt_state2016 16 xt_NFQUEUE 1792 0 xt_hashlimit9360 0 xt_tcpmss 1984 0 xt_tcpudp 2816 43 ipt_addrtype2304 0 xt_pkttype 1728 4 iptable_raw 2176 0 xt_CLASSIFY 1696 0 xt_CONNMARK 2944 0 xt_MARK 2304 0 xt_comment 1664 0 ipt_REJECT 2784 4 xt_length 1760 0 xt_connmark 2368 0 xt_owner2560 0 ipt_recent 6908 0 xt_iprange 2272 0 xt_physdev 2352 0 xt_policy 2848 0 xt_multiport2816 4 xt_conntrack3488 0 iptable_mangle 2688 1 iptable_nat 4680 1 nf_nat 15576 2 ipt_MASQUERADE,iptable_nat nf_conntrack_ipv4 12268 19 iptable_nat,nf_nat nf_conntrack 55508 8 ipt_MASQUERADE,xt_state,xt_CONNMARK,xt_connmark,xt_conntrack,iptable_nat,nf_nat,nf_conntrack_ipv4 iptable_filter 2624 1 ip_tables 10160 4 iptable_raw,iptable_mangle,iptable_nat,iptable_filter x_tables 13284 28 xt_DSCP,ipt_MASQUERADE,ipt_ULOG,ipt_LOG,ip6_tables,xt_state,xt_NFQUEUE,xt_hashlimit,xt_tcpmss,xt_tcpudp,ipt_addrtype,xt_pkttype,xt_CLASSIFY,xt_CONNMARK,xt_MARK,xt_comment,ipt_REJECT,xt_length,xt_connmark,xt_owner,ipt_recent,xt_iprange,xt_physdev,xt_policy,xt_multiport,xt_conntrack,iptable_nat,ip_tables ipv6 235300 26 clip 10512 1 atm32820 3 clip nls_utf81760 1 nls_cp437 5568 1 vfat9152 1 fat40864 1 vfat nls_base6820 4 nls_utf8,nls_cp437,vfat,fat reiserfs 189920 1 fuse 42908 1 dm_snapshot14340 0 dm_mirror 15104 0 dm_log 8452 1 dm_mirror dm_mod 46184 3 dm_snapshot,dm_mirror,dm_log
Bug#508370: marked as done (linux-image-2.6.24-etchnhalf.1-686: Randomly kernel Oops in etch and half kernel image)
Your message dated Mon, 3 Jun 2013 19:02:28 +0200 with message-id 20130603170228.GB5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #508370, regarding linux-image-2.6.24-etchnhalf.1-686: Randomly kernel Oops in etch and half kernel image 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.) -- 508370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.24-etchnhalf.1-686 Version: 2.6.24-6~etchnhalf.5 Severity: normal I was having frequently kernel oops in etch: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481346. Now I have installed etch and half and kernel oops are very rarelyi but I've had one today. These are the messages shown in the ssh console I received: Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: Oops: [#1] SMP Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: Process postmaster (pid: 2918, ti=f6624000 task=f7cce730 task.ti=f6624000) Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: Stack: e5ed7908 0001 073b c02c7885 f6a7a6ac 1000 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel:2000 000d 1000 e5ed7908 f6625cf8 f000 c49893ec Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel:f000 2000 c0194337 1000 424420e3 c17087c0 c000 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: Call Trace: Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c0194337] __getblk+0x23/0x27e Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c0195392] block_write_begin+0x83/0xe0 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [f895764b] ext3_get_block+0x0/0xd0 [ext3] Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [f8922b24] journal_start+0x7d/0xa9 [jbd] Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [f8958add] ext3_write_begin+0xd9/0x18a [ext3] Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [f895764b] ext3_get_block+0x0/0xd0 [ext3] Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c015bb09] generic_file_buffered_write+0x10a/0x5a1 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [f895d987] __ext3_journal_stop+0x19/0x34 [ext3] Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c0190d69] __mark_inode_dirty+0xc9/0x144 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c015c431] __generic_file_aio_write_nolock+0x491/0x4f0 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c015c4e5] generic_file_aio_write+0x55/0xb3 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c0180fa0] do_path_lookup+0x162/0x1c4 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [f8955014] ext3_file_write+0x24/0x8f [ext3] Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c0178593] do_sync_write+0xc7/0x10a Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c0181c87] open_namei+0x276/0x558 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c0135489] autoremove_wake_function+0x0/0x35 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c01784cc] do_sync_write+0x0/0x10a Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c0178dd8] vfs_write+0xa1/0x14d Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c01793f3] sys_write+0x41/0x67 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: [c0103e66] sysenter_past_esp+0x6b/0xa1 Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: === Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost kernel: Code: 24 2c 8b 5c 24 14 89 44 24 20 2b 44 24 2c 39 5c 24 44 89 44 24 1c 76 08 8b 54 24 68 39 d0 72 1f 8b 45 00 a8 08 0f 84 d2 01 00 00 8b 01 a8 01 0f 85 c8 01 00 00 90 0f ba 29 00 e9 be 01 00 00 8b Message from syslogd@localhost at Wed Dec 10 15:54:06 2008 ... localhost
Bug#523039: marked as done (/boot/vmlinuz-2.6.26-1-686: umount -f /net/tesla/foo umount -l -f /net/tesla/foo breaks the whole VFS)
Your message dated Mon, 3 Jun 2013 19:03:10 +0200 with message-id 20130603170310.GC5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #523039, regarding /boot/vmlinuz-2.6.26-1-686: umount -f /net/tesla/foo umount -l -f /net/tesla/foo breaks the whole VFS 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.) -- 523039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-13lenny2 Severity: normal File: /boot/vmlinuz-2.6.26-1-686 I'm not sure how reproducible this is. I use the automounter to automount /net/tesla/whatever, and so on. I think I got NFS confused by changing the exports on tesla without unmounting from llama first. Anyway, I was in one of those nfs-is-stuck-and-I-need-to-umount situations. I ran sudo umount -f /net/tesla/usr sudo umount -f /net/tesla/home sudo umount -f /net/tesla/var/tmp At least one of these mounts shouldn't have had any open files, but I wasn't able to check for sure because lsof blocks on broken NFS mounts. When none of those umounts exitted for several minutes, I ran sudo umount -l -f /net/tesla/var/tmp sudo umount -l -f /net/tesla/usr Within seconds of doing that, _local_ file access started to break. Anything I tried to run hung. e.g. ls didn't return. (I was CDed to a directory in /mnt/large, an ext3 filesystem on a local disk.) The machine wasn't totally locked, though. I was able to fg a vi process, and have it prompt that a file on disk was newer, and then exit cleanly (and this was over SSH). So user-space (and apparently even the VFS) wasn't entirely screwed, but there were major problems. I eventually had to alt+sysrq s, u, b to reboot. Does umount -l need to check if there's already a umount attempt going on? The only thing out of the ordinary that I did was umount -l -f while a umount -f was stuck on the same filesystem. Machine hardware: PIII 500MHz, 440BX chipset, 512MB. tulip NICs. This HW has been stable for ~10 years. :) -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-13lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Fri Mar 13 18:08:45 UTC 2009 ** Command line: root=/dev/md0 lapic ro ** Not tainted ** Loaded modules: Module Size Used by autofs416420 1 nfsd 186704 17 auth_rpcgss33952 1 nfsd exportfs3904 1 nfsd nfs 213896 5 lockd 54248 2 nfsd,nfs nfs_acl 2912 2 nfsd,nfs sunrpc162144 26 nfsd,auth_rpcgss,nfs,lockd,nfs_acl ipt_REJECT 2784 1 xt_tcpudp 2816 16 xt_state2016 1 nf_nat_irc 2080 0 nf_conntrack_irc5124 1 nf_nat_irc nf_conntrack_ftp6852 0 ipt_MASQUERADE 2592 1 iptable_nat 4680 1 nf_nat 15576 3 nf_nat_irc,ipt_MASQUERADE,iptable_nat nf_conntrack_ipv4 12268 4 iptable_nat,nf_nat nf_conntrack 55508 8 xt_state,nf_nat_irc,nf_conntrack_irc,nf_conntrack_ftp,ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4 iptable_filter 2624 1 ip_tables 10160 2 iptable_nat,iptable_filter x_tables 13284 6 ipt_REJECT,xt_tcpudp,xt_state,ipt_MASQUERADE,iptable_nat,ip_tables dm_snapshot14340 0 dm_mirror 15104 0 dm_log 8452 1 dm_mirror dm_mod 46184 3 dm_snapshot,dm_mirror,dm_log ipv6 235300 26 button 6096 0 serio_raw 4740 0 snd_pcm62596 0 psmouse32336 0 i2c_piix4 7216 0 snd_timer 17800 1 snd_pcm i2c_core 19828 1 i2c_piix4 snd45604 2 snd_pcm,snd_timer soundcore 6368 1 snd shpchp 25528 0 pci_hotplug23460 1 shpchp snd_page_alloc 7816 1 snd_pcm intel_agp 22332 1 agpgart28776 1 intel_agp pcspkr 2432 0 evdev 8000 0 ext3 105512 4 jbd39444 1 ext3 mbcache 7108 1 ext3 raid1 18016 3 md_mod 67036 4 raid1 usbhid 35904 1 hid33184 1 usbhid ff_memless 4392 1 usbhid ide_disk 10496 10 ata_generic
Bug#525983: marked as done (bug of nfsd caused by timeout)
Your message dated Mon, 3 Jun 2013 19:03:10 +0200 with message-id 20130603170310.GC5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #525983, regarding bug of nfsd caused by timeout 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.) -- 525983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-kernel-server Version: 1:1.1.2-6lenny1 Severity: normal nfsd caused this bug during last night on a file server. Nothing particular was running (because it was during the night). This morning all exports work well. extract from dmesg: [595034.434618] INFO: task nfsd:1402 blocked for more than 120 seconds. [595034.434656] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [595034.434703] nfsd D 0 1402 2 [595034.434737] 81001ddb1ca0 0046 8100154cb880 [595034.434789] 81001f6f5630 804f8480 81001f6f58b8 0001 [595034.437828] 0282 [595034.437864] Call Trace: [595034.437937] [a00885c0] :jbd:log_wait_commit+0x9f/0xed [595034.437972] [802461b1] autoremove_wake_function+0x0/0x2e [595034.438011] [a00844f9] :jbd:journal_stop+0x165/0x18d [595034.438054] [a00c63b0] :ext3:ext3_sync_file+0x68/0xb0 [595034.438103] [a01ea970] :nfsd:nfsd_sync_dir+0x39/0x52 [595034.438145] [a01ed2e5] :nfsd:nfsd_create_v3+0x319/0x43c [595034.438192] [a01f2ffc] :nfsd:nfsd3_proc_create+0x139/0x14a [595034.438236] [a01e7248] :nfsd:nfsd_dispatch+0xde/0x1b6 [595034.438296] [a019c55b] :sunrpc:svc_process+0x408/0x6e9 [595034.438332] [80429384] __down_read+0x12/0xa1 [595034.438371] [a01e7671] :nfsd:nfsd+0x0/0x2a3 [595034.438410] [a01e7805] :nfsd:nfsd+0x194/0x2a3 [595034.438442] [802301ec] schedule_tail+0x27/0x5c [595034.438472] [8020cf28] child_rip+0xa/0x12 [595034.438511] [a01e7671] :nfsd:nfsd+0x0/0x2a3 [595034.438552] [a01e7671] :nfsd:nfsd+0x0/0x2a3 [595034.438581] [8020cf1e] child_rip+0x0/0x12 [595034.438608] -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF8) Shell: /bin/sh linked to /bin/bash Versions of packages nfs-kernel-server depends on:ii libblkid1 1.41.3-1 block device id library ii libc6 2.7-18 GNU C Library: Shared libraries ii libcomerr2 1.41.3-1 common error description library ii libgssglue1 0.1-2 mechanism-switch gssapi library ii libkrb53 1.6.dfsg.4~beta1-5lenny1 MIT Kerberos runtime libraries ii libnfsidmap2 0.20-1 An nfs idmapping library ii librpcsecgss3 0.18-1 allows secure rpc communication us ii libwrap0 7.6.q-16 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii nfs-common 1:1.1.2-6lenny1 NFS support files common to client ii ucf 3.0016 Update Configuration File: preserv nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- 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.0 / 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#517748: marked as done (linux-image-2.6.26-1-686 System locks up under heavy disk load (MD Resync e.g.))
Your message dated Mon, 3 Jun 2013 19:03:10 +0200 with message-id 20130603170310.GC5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #517748, regarding linux-image-2.6.26-1-686 System locks up under heavy disk load (MD Resync e.g.) 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.) -- 517748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-13 Severity: normal Upgraded the system from Etch to Lenny, last week of february. First of march was periodic mdadm check of the RAID arrays (md0 RAID1, md1+md2 RAID5) revealed a serious issue: The system locked up pretty bad, it stops responding for anywhere between 10~15 minutes. Inspection in /var/log/messages and dmesg revealed loads of soft lockups. Since the system did respond normal in the breef periods between the lockups, I began suspecting disk failure or something similar. CPU and MEM load showed no abnormality. In /proc/mdstat I noticed a resync of the md devices was active, a process which under etch took at most 2 hours to sync all arrays now took around 8 to 10 hours. Some additional info: - Contains Promise FastTrack TX4310 fakeraid (Reason for rapid upgrade to Lenny: Known issues with the Etch kernel which *could* cause corruption). - Contains 4 samsung spinpoint disks, all attached to the Promise controller. Another (possibly unrelated) issue I noticed at boot time. The system seems to hang for a minute or 5 during around the network initialisation, possibly also related to heavy diskio during boot? mdadm periodic checks/resync disabled until the bug is fixed, the concerning machine is a production server. This, unfortunately, also rules out the machine as a testbox for possible fixes... I'll try if I can reproduce this issue on a different hardware platform. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (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 18:29:31 UTC 2009 ** Command line: root=/dev/md0 ro ** Not tainted ** Kernel log: [219328.329768] disk 0, o:1, dev:sdc3 [219328.329768] disk 1, o:1, dev:sdb3 [219328.329768] disk 2, o:1, dev:sdd3 [219328.329768] disk 3, o:1, dev:sda3 [219405.132574] md: md1: data-check done. [219405.278752] RAID5 conf printout: [219405.278752] --- rd:4 wd:4 [219405.278752] disk 0, o:1, dev:sdc2 [219405.278752] disk 1, o:1, dev:sdb2 [219405.278752] disk 2, o:1, dev:sdd2 [219405.278752] disk 3, o:1, dev:sda2 [219719.856024] BUG: soft lockup - CPU#0 stuck for 96s! [pickup:12604] [219719.856024] Modules linked in: ppdev parport_pc lp parport sit tunnel4 ipt_MASQUERADE xt_multiport xt_tcpudp xt_state ip6table_filter iptable_nat nf_nat nf_conntrack_ipv4 iptable_filter ip_tables jfs dm_snapshot dm_mirror dm_log dm_mod ip6t_rt ip6table_mangle ip6_tables x_tables ipv6 cpufreq_ondemand acpi_cpufreq freq_table fuse nf_conntrack_ftp nf_conntrack usb_storage ntfs nls_base loop snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr i2c_viapro button i2c_core shpchp pci_hotplug via_agp agpgart evdev ext3 jbd mbcache usbhid hid ff_memless raid456 async_xor async_memcpy async_tx xor raid1 md_mod sd_mod ide_pci_generic via82cxxx ide_core sata_promise via_rhine mii ata_generic libata ehci_hcd uhci_hcd usbcore scsi_mod dock thermal processor fan thermal_sys [219719.856024] [219719.856024] Pid: 12604, comm: pickup Not tainted (2.6.26-1-686 #1) [219719.856024] EIP: 0060:[c0117c73] EFLAGS: 0286 CPU: 0 [219719.856024] EIP is at kunmap_atomic+0x61/0x8a [219719.856024] EAX: fffb6000 EBX: fffb6000 ECX: c0007ed8 EDX: fffb6000 [219719.856024] ESI: EDI: c0007ed8 EBP: dafc0200 ESP: d2ac9d64 [219719.856024] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 [219719.856024] CR0: 8005003b CR2: b7fe10a4 CR3: 1ae4c000 CR4: 0690 [219719.856024] DR0: DR1: DR2: DR3: [219719.856024] DR6: 0ff0 DR7: 0400 [219719.856024] [c0161c62] ? __do_fault+0x102/0x34d [219719.856024] [c0163d4e] ? handle_mm_fault+0x2d2/0x690 [219719.856024] [c015fc56] ? vma_prio_tree_insert+0x17/0x2a [219719.856024] [c0166361] ? vma_link+0xa3/0xbd [219719.856024] [c01669c9] ? mmap_region+0x2dd/0x393 [219719.856024] [c0115b4f] ? do_page_fault+0x29b/0x5b8 [219719.856024] [c0166dc0] ? do_mmap_pgoff+0x266/0x2b9 [219719.856024] [c01158b4] ? do_page_fault+0x0/0x5b8 [219719.856024] [c02b980a] ? error_code+0x72/0x78 [219719.856024] [c01e1b8d] ?
Bug#525308: marked as done (vmlinuz: cannot mount partition)
Your message dated Mon, 3 Jun 2013 19:03:10 +0200 with message-id 20130603170310.GC5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #525308, regarding vmlinuz: cannot mount partition 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.) -- 525308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-486 Version: 2.6.26-13 Severity: normal File: vmlinuz There's certainly some reason why the partition cannot be mounted but mount does not tell nor does dmesg. # mount /dev/sda1 /mnt mount: /dev/sda1 already mounted or /mnt busy debian-ghost:~# cat /proc/mounts rootfs / rootfs rw 0 0 none /sys sysfs rw,nosuid,nodev,noexec 0 0 none /proc proc rw,nosuid,nodev,noexec 0 0 udev /dev tmpfs rw,size=10240k,mode=755 0 0 ram /live/image ramfs rw 0 0 httpfs /live/image/live fuse.httpfs rw,nosuid,nodev,user_id=0,group_id=0 0 0 /dev/loop0 /filesystem.squashfs squashfs ro,noatime 0 0 tmpfs /live/cow tmpfs rw,noatime,mode=755 0 0 aufs / aufs rw,si=1315af5,xino=/live/cow/.aufs.xino,br:/live/cow=rw:/filesystem.squashfs=rr 0 0 tmpfs /live tmpfs rw 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid,mode=755 0 0 usbfs /proc/bus/usb usbfs rw,nosuid,nodev,noexec 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,nosuid,noexec,gid=5,mode=620 0 0 fusectl /sys/fs/fuse/connections fusectl rw 0 0 tmpfs /tmp tmpfs rw,nosuid,nodev 0 0 //handyman/netghost /home/ghost/mnt cifs rw,mand,nosuid,nodev,unc=\\handyman\netghost,username=mghost,uid=1000,gid=1000,file_mode=02767,dir_mode=0777,rsize=16384,wsize=57344 0 0 -- Package-specific info: ** Version: Linux version 2.6.26-1-486 (Debian 2.6.26-13) (michal.sucha...@ruk.cuni.cz) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 Thu Feb 12 00:35:28 CET 2009 ** Command line: initrd=initrd1.img boot=live xdebconf g username=ghost hostname=debian-ghost union=aufs quickreboot httpfs=http://195.113.15.10/filesystem.squashfs vga=792 splash quiet BOOT_IMAGE=vmlinuz1 ** Not tainted ** Kernel log: [5.68] ata4.00: ATA-8: WDC WD10EACS-00ZJB0, 01.01B01, max UDMA/133 [5.68] ata4.00: 1953523055 sectors, multi 16: LBA48 NCQ (depth 31/32) [5.68] ata4.00: configured for UDMA/133 [5.936021] ata5: SATA link down (SStatus 0 SControl 300) [6.436014] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [6.439910] ata6.00: ATAPI: HL-DT-ST BD-RE GGW-H20L, YL02, max UDMA/133 [6.444007] ata6.00: configured for UDMA/133 [6.460085] scsi 0:0:0:0: Direct-Access ATA Hitachi HDS72101 GKAO PQ: 0 ANSI: 5 [6.460182] scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5 [6.460244] scsi 2:0:0:0: Direct-Access ATA ST31000340SV SV16 PQ: 0 ANSI: 5 [6.460306] scsi 3:0:0:0: Direct-Access ATA WDC WD10EACS-00Z 01.0 PQ: 0 ANSI: 5 [6.463421] scsi 5:0:0:0: CD-ROMHL-DT-ST BD-RE GGW-H20L YL02 PQ: 0 ANSI: 5 [6.472983] Driver 'sd' needs updating - please use bus_type methods [6.480020] sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors (1000205 MB) [6.480029] sd 0:0:0:0: [sda] Write Protect is off [6.480031] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [6.480043] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6.480074] sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors (1000205 MB) [6.480081] sd 0:0:0:0: [sda] Write Protect is off [6.480083] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [6.480095] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6.480098] sda: sda1 [6.497827] sd 0:0:0:0: [sda] Attached SCSI disk [6.497859] sd 1:0:0:0: [sdb] 1953525168 512-byte hardware sectors (1000205 MB) [6.497867] sd 1:0:0:0: [sdb] Write Protect is off [6.497868] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [6.497880] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6.497904] sd 1:0:0:0: [sdb] 1953525168 512-byte hardware sectors (1000205 MB) [6.497912] sd 1:0:0:0: [sdb] Write Protect is off [6.497913] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [6.497925] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6.497927] sdb:4Driver 'sr' needs updating - please use bus_type methods [6.505544] sdb1 [6.505582] sd 1:0:0:0: [sdb] Attached SCSI disk [6.505612] sd 2:0:0:0: [sdc] 1953525168 512-byte hardware sectors
Bug#522820: marked as done (linux-2.6: device mismatches found: 5632 for swap.)
Your message dated Mon, 3 Jun 2013 19:03:10 +0200 with message-id 20130603170310.GC5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #522820, regarding linux-2.6: device mismatches found: 5632 for swap. 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.) -- 522820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux-2.6 Version: 2.6.26-13 Hi, I have seen this error on multiple systems, and always for the device with swap on it: mdadm[2860]: RebuildFinished event detected on md device /dev/md2, component device mismatches found: 5632 This error is logged after the monthly check that is being run for all the md devices. Running the check manually also seems to have the same effect. And the mismatch_cnt does contain that value: # cat /sys/block/md2/md/mismatch_cnt 5632 Kurt ---End Message--- ---BeginMessage--- 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.0 / 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#526693: marked as done (BUG: soft lockup - CPU#0 stuck for 61s (wpa_supplicant + jfs))
Your message dated Mon, 3 Jun 2013 19:03:10 +0200 with message-id 20130603170310.GC5319@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #526693, regarding BUG: soft lockup - CPU#0 stuck for 61s (wpa_supplicant + jfs) 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.) -- 526693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wpasupplicant Version: 0.6.9-2 I get often freezes during shutdown; collecting many clues (stale files when booting after incorrectly terminated shutdown, screen output etc) I have been able to verify that this is what happens: 1) unmounting of my root JFS partition fails, in particular my /etc/mtab file is not unlinked correctly 2) some kernel error dump is shown on screen for less than a second 3) the computer is shutdown anyway, without leaving track of the error (logger is anyway gone when this happens, and there is too little time to read on screen) I know that I should plug a serial connection to get the full output; however today it did not shutdown totally and kept hanging forever spitting out a specific error dump every 61s. I have wrote down these details: --- BUG: soft lockup - CPU#0 stuck for 61s! wpa_supplicant Tainted GD(2.6.28-681 #1) Pro 7000X _spin_lock txBegin security_inode_permission __link_path_walk get_UCSname do_notify_resume jfs_unlink do_unlinkat mntput_no_expire filp_close sys_close sysenter_do_call --- -- Daniele C. ---End Message--- ---BeginMessage--- 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.0 / 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---
Re: sparc / Problems with 3.2-kernel
Artyom Tarasenko a écrit : On Sun, Jun 2, 2013 at 11:38 PM, BERTRAND Joël joel.bertr...@systella.fr wrote: Andreas Barth a écrit : Hi, today I tried to resurrect our buildd on schroeder (which is from architecture sparc). While trying to do so, I had a couple of strange behaviours like vi freezing after 20-30 seconds, or I couldn't about tail with ctrl+c or suspend with ctrl+z. This didn't change after a reboot. Machine was running our official 3.2-kernel. Was the machine available via the network at the time of freeze? After Martin rebooted the machine into oldstables 2.6.32 kernel, things are working as they should, and the buildd is up again. Question: Is this a known issue? How can we get a fix for that? (I would assume DSA will consider it a non-option to not be able to upgrade to our default kernels.) I have seen same freezes on Blade 2000 (2 * US III+/900 Cu), on U5 (US IIi/440), but not on a server that run with four US IIIi and not on a T1000 (sun4v/US T1). I have tested 3.2 debian kernels and official ones and both hang. I suppose there is another strange bug with special MMU. 2.6.32 is stable but on sparc64, 3.2 is not. I have not tested newer kernels. Bertrand, Andreas, can you please enable the magic SysRq key and try to see what is the kernel busy with when it hangs? When freeze occurs, workstation was totaly blocked. SysRq didn't work anymore. I have reinstalled my Blade 2000 with NetBSD but I can try to obtain more information in a couple of weeks. My U5 runs with jessie (and a 2.6.32 kernel). Regards, JKB -- 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/51acd1b3.1020...@systella.fr
Bug#710938: Packard Bell EasyNote LV need i915.invert_brightness on Linux
Package: src:linux Version: 3.2.41-2 Severity: important Dear Maintainer, When installing Debian Wheezy on a Packard Bell EasyNote LV laptop with the firmware (UEFI BIOS) set to legacy mode, the installation work just fine, but after boot the screen go completely black and the laptop become unusable. This problem also affect Ubuntu Raring (launchpad bug 765438). See URL: http://www.linlap.com/packard_bell_easynote_lv for the notes on installing Ubuntu on this laptop. The fix is to either set the kernel option i915.invert_brightness=1 during boot, or to create a file in /etc/ like this (as root): echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf update-initramfs -u -k all URL: http://bugs.debian.org/681743 contain a similar bug report for a different laptop. According to that bug report and URL: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955 there is a mechanism in the Linux kernel that can be used to enable the invert_brightness=1 setting for hardware that need it. According to 'modinfo i915', this is the definition for invert_brightness: invert_brightness:Invert backlight brightness (-1 force normal, 0 machine defaults, 1 force inversion), please report PCI device ID, subsystem vendor and subsystem device ID to dri-de...@lists.freedesktop.org, if your machine needs it. It will then be included in an upcoming module version. (int) Please change the i915 module for the hardware in question, to get this laptop working out of the box with Debian Wheezy (and future versions). I've already sent an email to dri-de...@lists.freedesktop.org about this, but it is not (yet, at least) shown up on URL: http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html so far. I might have included too little detail in that email, as I am a bit unsure what kind of information they need to fix it. I hope this bug report contain everything that is needed. PS: I changed the version number of this bug from 3.2.41-2+deb7u2 to 3.2.41-2, to make sure BTS assume this bug exist in all versions of Debian. Happy hacking Petter Reinholdtsen -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.41-2+deb7u2 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/vg_system-root ro quiet i915.invert_brightness=1 ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [6.257272] scsi6 : SCSI emulation for PCI-Express Mass Storage devices [6.257409] rts_pstor: waiting for device to settle before scanning [6.268938] [drm] failed to retrieve link info, disabling eDP [6.398416] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' [6.398917] Registered led device: ath9k-phy0 [6.398926] ieee80211 phy0: Atheros AR9485 Rev:1 mem=0xc9000550, irq=17 [6.438057] ACPI: AC Adapter [AC0] (on-line) [6.530098] ACPI: Battery Slot [BAT0] (battery present) [6.540793] audit: name_count maxed, losing inode data: dev=00:06, inode=1917 [6.540798] audit: name_count maxed, losing inode data: dev=00:06, inode=1917 [6.540803] audit: name_count maxed, losing inode data: dev=00:06, inode=1917 [6.540807] audit: name_count maxed, losing inode data: dev=00:06, inode=1904 [6.540810] audit: name_count maxed, losing inode data: dev=00:06, inode=1922 [6.540813] audit: name_count maxed, losing inode data: dev=00:06, inode=1922 [6.540817] audit: name_count maxed, losing inode data: dev=00:06, inode=1922 [6.540821] audit: name_count maxed, losing inode data: dev=00:06, inode=1922 [6.540824] audit: name_count maxed, losing inode data: dev=00:06, inode=1904 [6.540829] audit: name_count maxed, losing inode data: dev=00:06, inode=1927 [6.540832] audit: name_count maxed, losing inode data: dev=00:06, inode=1927 [6.540837] audit: name_count maxed, losing inode data: dev=00:06, inode=1927 [6.540840] audit: name_count maxed, losing inode data: dev=00:06, inode=1927 [6.540844] audit: name_count maxed, losing inode data: dev=00:06, inode=1904 [6.540848] audit: name_count maxed, losing inode data: dev=00:06, inode=1932 [6.540851] audit: name_count maxed, losing inode data: dev=00:06, inode=1932 [6.540856] audit: name_count maxed, losing inode data: dev=00:06, inode=1932 [6.540859] audit: name_count maxed, losing inode data: dev=00:06, inode=1932 [6.588764] Linux media interface: v0.10 [6.591185] Linux video capture interface: v2.00 [6.597418] uvcvideo: Found UVC 1.00 device HD WebCam (1bcf:2c18) [6.603538] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [6.606189] input: HD WebCam as /devices/pci:00/:00:1a.0/usb3/3-1/3-1.1/3-1.1:1.0/input/input6 [6.606248] usbcore: registered new interface driver uvcvideo [6.606250] USB Video Class driver
linux-tools_3.9.4-1_multi.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Jun 2013 13:45:52 +0100 Source: linux-tools Binary: linux-kbuild-3.9 linux-tools-3.9 libusbip-dev usbip Architecture: i386 source Version: 3.9.4-1 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Ben Hutchings b...@decadent.org.uk Description: libusbip-dev - USB device sharing system over IP network (development files) linux-kbuild-3.9 - Kbuild infrastructure for Linux 3.9 linux-tools-3.9 - Performance analysis tools for Linux 3.9 usbip - USB device sharing system over IP network Changes: linux-tools (3.9.4-1) unstable; urgency=low . * New upstream release Checksums-Sha1: 01e75356d103cb574dc5d13d28dd963debeb6bca 2305 linux-tools_3.9.4-1.dsc aaae3f9e0ebfcac541e712c8b671b24f5f08175d 7156568 linux-tools_3.9.4.orig.tar.xz 37c1e6a2fde41d0320c76496594d94fe3f9985d5 19584 linux-tools_3.9.4-1.debian.tar.xz 4edfef28dcb3a4a15b4df3e5eb8b15295bf54562 28540 libusbip-dev_1.1.1+3.9.4-1_i386.deb 117e01c8d793c4d48c9a8fee96d6659ff31e9846 240008 linux-kbuild-3.9_3.9.4-1_i386.deb 8f2fe65efef39f69b8badf80cd185c82326ab2ca 48746 usbip_1.1.1+3.9.4-1_i386.deb 5862cd2d8b8608b539e7e28ff051a44bccca87ae 554514 linux-tools-3.9_3.9.4-1_i386.deb Checksums-Sha256: edd6c2b5d5713dec955566d4350fa92cd639f0978b5df908f1f39867610198ec 2305 linux-tools_3.9.4-1.dsc 7694f7348e7524bdd4da3f7cb73f516293ad87d61a308696708b33d9c3ac5f24 7156568 linux-tools_3.9.4.orig.tar.xz 16deef9fc424c5b2894996be0161c56e610bee2282f759a6ccb45bf84b5f2591 19584 linux-tools_3.9.4-1.debian.tar.xz 32b02cdf73130e28506cd801f2a1a55034f3a97fffc84f345724b39f97c54210 28540 libusbip-dev_1.1.1+3.9.4-1_i386.deb b6fd334988afa4954b612b26e4bc0ad3c5dacc2e390e807f3bc4325b529b083c 240008 linux-kbuild-3.9_3.9.4-1_i386.deb eba37019f8488f098e48ed6338fcca4b4c956f88eaa545ad32cd1094eba26093 48746 usbip_1.1.1+3.9.4-1_i386.deb a64dc52876df0ecffc8a08da8f5b36378bbae4e54592d1a4d5c38d498317eb0f 554514 linux-tools-3.9_3.9.4-1_i386.deb Files: 1e4c7a4c95d56d7b00b42bbee1da91a1 2305 kernel optional linux-tools_3.9.4-1.dsc b6192fda7d85931d956ac15cae18a626 7156568 kernel optional linux-tools_3.9.4.orig.tar.xz c13066b8bccbbf29ff298db96e68c476 19584 kernel optional linux-tools_3.9.4-1.debian.tar.xz 31b60384a11bdb1159149fee7b4a2e04 28540 libdevel optional libusbip-dev_1.1.1+3.9.4-1_i386.deb 51b439616c39972599dbdea513982510 240008 kernel optional linux-kbuild-3.9_3.9.4-1_i386.deb 280d3ce2854f6031dd0c3b6b5d3bf312 48746 admin optional usbip_1.1.1+3.9.4-1_i386.deb a53b30c40188435a558165336dd0ab8b 554514 devel optional linux-tools-3.9_3.9.4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBUayT0ee/yOyVhhEJAQr+MxAAzsFynWrb+BZz8oxz/Ue4TFs10xap+ivb K4FTGRgKDAcboW/Ak3kizTxsTg5DQrSjsM92KXS3l+UDTGfEDEpV8unFCpxdVM6X BF7OLaoXqN4CDRO2ltdMOIH0awwPik0k7iQofYl7g0/qA3848d0t6+q2czaCOGPd hFys6poj8wzZRaPMNLvFLpPlJ9l2Kp31HH+gMPrvd7dz0mHIrBeQUfTRbwCOM8Cl uVX8MOh4YmF/NJkBYKhIe97//1xPfIVYC2RzjKIr+zhWdDwnH2Z8473CRWCxNrNF GBxa5MsdsZ/B489/l9Ki5od2JCnH0T8kZn+sOl3N4IyPZTPC3GHz914mlfwK2Cht YHhIFx/crfOc1JIkGIEVLrYhdyk3tMvr/9JAApPp/FwLtxKU5FZ3YJLViFtn2EYS JjNUjpO/ZbaHGdPzk4lqvgbQLdXBn0/KacXcnwmqmYtBgG0D1NTji1zx4h3d8k0E cGD2JHGSY5ntYcwNJTSX/yzHNfOKFine9GAnXi1DisLpvulIdksusGSVd45fKwip ESCc+SB1GpvL5fXl9byP2EZq3ano11MzbpNdl4vTQF7kw8CDY3JIxrNVoIIDrCgM gwagRdF5xXkuPI+zt82uFIzaFSbM4aFyiwopeW5jEYkFpphlutVjL8kVJTqak3S8 urgdh1RGrIk= =cKm8 -END PGP SIGNATURE- Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ujz38-aa...@franck.debian.org
Processed: not for wheezy
Processing commands for cont...@bugs.debian.org:
tags 707560 + jessie sid
Bug #707560 [libucommon5-dbg,libucommon6-dbg] libucommon6-dbg and
libucommon5-dbg: error when trying to install together
Added tag(s) sid and jessie.
tags 707671 + jessie sid
Bug #707671 {Done: Roland Stigge sti...@antcom.de} [rtai] librtai-dev and
gcc-multilib: error when trying to install together
Added tag(s) sid and jessie.
tags 707657 + jessie sid
Bug #707657 [libimobiledevice-dev] unsatisfied dependencies: Depends:
libtasn1-3-dev but it is not going to be installed
Added tag(s) sid and jessie.
tags 707665 + jessie sid
Bug #707665 [ndiswrapper-dkms] [ndiswrapper-dkms] Version 1.57 fails to build
with linux kernel 3.8. Needs to be upgraded to 1.58
Added tag(s) sid and jessie.
tags 707589 + jessie sid
Bug #707589 {Done: Luk Claes l...@zomers.be} [nfs-kernel-server]
nfs-kernel-server: NFSv3 is broken with libc-bin 2.17
Added tag(s) sid and jessie.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
707560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707560
707589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707589
707657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707657
707665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707665
707671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707671
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.13702865032180.transcr...@bugs.debian.org
Processed: still endianness issues and more on second screen with quad G5 (PowerPC 64 bits) with wheezy kernel
Processing commands for cont...@bugs.debian.org:
reopen 655511
Bug #655511 {Done: Moritz Mühlenhoff j...@inutil.org} [src:linux-2.6]
Endianness issues with Nvidia card second port (NV43) on PowerPC (quad G5, PCIe)
Warning: Unknown package 'src:linux-2.6'
Bug reopened
Warning: Unknown package 'src:linux-2.6'
Warning: Unknown package 'src:linux-2.6'
Ignoring request to alter fixed versions of bug #655511 to the same values
previously set
Warning: Unknown package 'src:linux-2.6'
reassign 655511 src:linux
Bug #655511 [src:linux-2.6] Endianness issues with Nvidia card second port
(NV43) on PowerPC (quad G5, PCIe)
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.1.0-1.
Ignoring request to alter fixed versions of bug #655511 to the same values
previously set
End of message, stopping processing here.
Please contact me if you need assistance.
--
655511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655511
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.13702905112940.transcr...@bugs.debian.org
Bug#464595: marked as done (linux-source-2.6.24: booting takes far longer than 2.6.22)
Your message dated Tue, 4 Jun 2013 00:28:55 +0200 with message-id 20130603222855.GB5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #464595, regarding linux-source-2.6.24: booting takes far longer than 2.6.22 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.) -- 464595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-source-2.6.24 Version: 2.6.24-1 Severity: normal File: linux-source-2.6.24 this bug report will be dismissed as both useless and unimportant, but slow boots greatly increase the time it takes for users to fix issues trying to get their kernels to work, so it is important to some of us. 2.6.22 booted with no delay. 2.6.24 takes several minutes before there is any user-visible action, making the user wonder whether it is completely hung. ..config is identical. dual athlon mp 1200 mhz. nothing special in kernel config or command line. identical grub command line. no hardware changes. nothing else changed. go ahead and dismiss the report on the grounds that booting doesn't matter, but it'll be here for a search and perhaps somebody who knows what this is will search it and fix the offending code. thanks. -- System Information: Debian Release: lenny/sid Architecture: i386 (i686) Kernel: Linux 2.6.24myver-2-first (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.24 depends on: ii binutils2.18.1~cvs20080103-1 The GNU assembler, linker and bina ii bzip2 1.0.4-2 high-quality block-sorting file co Versions of packages linux-source-2.6.24 recommends: ii gcc 4:4.2.2-2 The GNU C compiler ii libc6-dev [libc-dev] 2.7-6 GNU C Library: Development Librari ii make 3.81-3 The GNU version of the make util -- no debconf information ---End Message--- ---BeginMessage--- 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.0 / 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#465677: marked as done (linux-source-2.6.24: Cannot build qconf due to renaming of moc)
Your message dated Tue, 4 Jun 2013 00:28:55 +0200 with message-id 20130603222855.GB5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #465677, regarding linux-source-2.6.24: Cannot build qconf due to renaming of moc 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.) -- 465677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-source-2.6.24 Version: 2.6.24-4 Severity: important Building kernel 2.6.24 fails as shown below. A solution is to symbolicly link /usr/bin/moc-qt3 to /usr/bin/moc: lrwxrwxrwx 1 root root7 2008-02-13 16:57 moc - moc-qt3* -rwxr-xr-x 1 root root 505K 2008-02-09 13:38 moc-qt3* and all is copacetic. See also bug #409953 ``/usr/bin/moc must not be handled by alternatives'' - build output - mhyre@elmore:/usr/src/linux$ time make-kpkg --append-to-version=-mh-svn.285 kernel-image exec debian/rules DEBIAN_REVISION=1 APPEND_TO_VERSION=-mh-svn.285 kernel-image [...snip...] This is kernel package version 11.001-0.1. [...snip...] == making target debian/stamp-kernel-conf [new prereqs: .config Makefile]== /usr/bin/make EXTRAVERSION=-mh-svn.285 ARCH=i386 \ xconfig make[1]: Entering directory `/usr/src/linux-source-2.6.24' CHECK qt /usr/bin/moc -i scripts/kconfig/qconf.h -o scripts/kconfig/qconf.moc make[2]: /usr/bin/moc: Command not found make[2]: *** [scripts/kconfig/qconf.moc] Error 127 make[1]: *** [xconfig] Error 2 make[1]: Leaving directory `/usr/src/linux-source-2.6.24' make: *** [debian/stamp-kernel-conf] Error 2 real0m21.809s user0m10.281s sys 0m3.748s mhyre@elmore:/usr/src/linux$ - end build output - - versions -- mhyre@elmore:~$ uname -a Linux elmore 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686 GNU/Linux mhyre@elmore:~$ dpkg -s qt3-dev-tools Package: qt3-dev-tools Status: install ok installed [...snip...] Source: qt-x11-free Version: 3:3.3.8b-1 [...snip...] mhyre@elmore:~$ - end versions -- -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.23-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.24 depends on: ii binutils2.18.1~cvs20080103-1 The GNU assembler, linker and bina ii bzip2 1.0.4-3 high-quality block-sorting file co Versions of packages linux-source-2.6.24 recommends: ii gcc 4:4.2.2-2 The GNU C compiler ii libc6-dev [libc-dev] 2.7-6 GNU C Library: Development Librari ii make 3.81-3 The GNU version of the make util -- no debconf information ---End Message--- ---BeginMessage--- 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.0 / 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#458191: marked as done (linux-image-2.6.22-3-amd64: serial port is detected but doesn't get an interrupt so it doesn't work)
Your message dated Tue, 4 Jun 2013 00:28:55 +0200 with message-id 20130603222855.GB5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #458191, regarding linux-image-2.6.22-3-amd64: serial port is detected but doesn't get an interrupt so it doesn't 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.) -- 458191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=458191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.22-3-amd64 Version: 2.6.22-6 Severity: normal serial port is detected: folkert@belle:~$ dmesg | grep ttyS0 serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A but it doesn't get an irc allocated: folkert@belle:~$ cat /proc/interrupts CPU0 CPU1 0: 176913 0 IO-APIC-edge timer 1:426 0 IO-APIC-edge i8042 7: 0 0 IO-APIC-edge parport0 8: 1 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-fasteoi acpi 12:130 0 IO-APIC-edge i8042 16:273 5957 IO-APIC-fasteoi uhci_hcd:usb1, ide0 18:146 71 IO-APIC-fasteoi uhci_hcd:usb5, ehci_hcd:usb6 19: 9876 12332 IO-APIC-fasteoi uhci_hcd:usb4, ahci, libata, libata, eth3 21: 0 0 IO-APIC-fasteoi uhci_hcd:usb2 22:188 0 IO-APIC-fasteoi HDA Intel 23: 2 0 IO-APIC-fasteoi uhci_hcd:usb3, ehci_hcd:usb7 NMI: 0 0 LOC: 176879 176858 ERR: 0 so it doesn't work -- Package-specific info: ** Version: Linux version 2.6.22-3-amd64 (Debian 2.6.22-6) (m...@debian.org) (gcc version 4.1.3 20071019 (prerelease) (Debian 4.1.2-17)) #1 SMP Sun Nov 4 18:18:09 UTC 2007 ** Not tainted ** Kernel log: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdb: sdb1 sd 2:0:0:0: [sdb] Attached SCSI disk ata_piix :00:1f.5: MAP [ P0 P2 P1 P3 ] ACPI: PCI Interrupt :00:1f.5[B] - GSI 19 (level, low) - IRQ 19 PCI: Setting latency timer of device :00:1f.5 to 64 scsi4 : ata_piix scsi5 : ata_piix ata5: SATA max UDMA/133 cmd 0x0001d000 ctl 0x0001d402 bmdma 0x0001e000 irq 19 ata6: SATA max UDMA/133 cmd 0x0001d800 ctl 0x0001dc02 bmdma 0x0001e008 irq 19 usb 5-2: new full speed USB device using uhci_hcd and address 3 usb 5-2: configuration #1 chosen from 1 choice device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-de...@redhat.com Attempting manual resume kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. usbcore: registered new interface driver usbserial drivers/usb/serial/usb-serial.c: USB Serial support registered for generic input: PC Speaker as /class/input/input1 pnp: the driver 'parport_pc' has been registered pnp: match found with the PnP device '00:07' and the driver 'parport_pc' parport_pc 00:07: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007) ACPI: PCI Interrupt :00:1f.3[C] - GSI 18 (level, low) - IRQ 18 usbcore: registered new interface driver usbserial_generic drivers/usb/serial/usb-serial.c: USB Serial Driver core usb0: register 'plusb' at usb-:00:1d.2-2, Prolific PL-2301/PL-2302, 06:b9:e3:2f:fa:4d usbcore: registered new interface driver plusb drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303 pl2303 1-2:1.0: pl2303 converter detected usb 1-2: pl2303 converter now attached to ttyUSB0 usbcore: registered new interface driver pl2303 drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver input: ImPS/2 Logitech Wheel Mouse as /class/input/input2 iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, TCOBASE=0x0460) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) ACPI: PCI Interrupt :00:1b.0[A] - GSI 22 (level, low) - IRQ 22 PCI: Setting latency timer of device :00:1b.0 to 64 EXT3 FS on dm-1, internal journal loop: module loaded ns83820.c: National Semiconductor DP83820 10/100/1000 driver. it87: Found IT8718F chip at 0x290, revision 2 it87: in3 is VCC (+5V) coretemp coretemp.0: Using undocumented features, absolute temperature might be wrong! coretemp coretemp.1: Using undocumented features, absolute temperature might be wrong! kjournald starting. Commit interval 5 seconds EXT3 FS on sda1, internal journal EXT3-fs: mounted
Bug#487452: marked as done (quirk needed for some USB disk enclosures)
Your message dated Tue, 4 Jun 2013 00:28:24 +0200 with message-id 20130603222824.GA5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #487452, regarding quirk needed for some USB disk enclosures 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.) -- 487452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Version: 2.35 Severity: normal Image version: http://www.cyrius.com/debian/nslu2/files/tmp/debian-armel-5.0beta2.zip Machine: nslu2 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [E] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [ ] Install boot loader:[O] Overall install:[O] Comments/Problems: There was no /etc/environment installed. pam already has a long-open bug about that. I always forget to select the usb-storage and ext3 modules when installing a slug, and this time was no exception; I ended up having to go back from partman twice to get all the necessary bits for it to see the drive. For some reason, partman did not detect that my existing /dev/hda3 was a pre-formatted ext3 filesystem with /home on it. So I couldn't set up the mounting of that in partman (without reformatting it). /etc/fstab ended up with an /media/floppy mountpoint for /dev/sda. Which was weird, because /dev/sda is a (very cheap) USB ide laptop disk enclosure; /dev/sda1 is the root filesystem. Seems to happen because ID_TYPE is reported as floppy: root@slug:/etc/ssl/certsudevinfo -q env -p /block/sda ID_VENDOR=Myson_Century,_Inc. ID_MODEL=USB_Mass_Storage_Device ID_REVISION=b008 ID_SERIAL=Myson_Century,_Inc._USB_Mass_Storage_Device_100 ID_SERIAL_SHORT=100 ID_TYPE=floppy ID_BUS=usb ID_PATH=pci-:00:01.2-usb-0:1:1.0-scsi-0:0:0:0 I don't know if this is a kernel or a hardware bug. I do wonder if d-i should trust the ID_TYPE at all. Armel is so much faster on this de-underclocked slug than arm that it's a pleasure to use! -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20080522 X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == umame -a: Linux snail 2.6.24-1-ixp4xx #1 Tue May 13 10:43:34 UTC 2008 armv5tel unknown lspci -knn: 00:01.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: Kernel modules: ohci-hcd lspci -knn: 00:01.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: Kernel modules: ohci-hcd lspci -knn: 00:01.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lsmod: Module Size Used by lsmod: reiserfs 259572 0 lsmod: sd_mod 26896 3 lsmod: usb_storage84263 2 lsmod: scsi_mod 120276 2 sd_mod,usb_storage lsmod: ext3 138056 1 lsmod: jbd49748 1 ext3 lsmod: vfat 13024 0 lsmod: fat55228 1 vfat lsmod: ext2 73320 0 lsmod: mbcache 9088 2 ext3,ext2 lsmod: ehci_hcd 34252 0 lsmod: ohci_hcd 21284 0 lsmod: evdev 11520 0 lsmod: ixp4xx_eth 16088 0 lsmod: ixp4xx_npe 8608 2 ixp4xx_eth lsmod: firmware_class 10048 1 ixp4xx_npe lsmod: ixp4xx_beeper 3488 0 lsmod: ixp4xx_qmgr 6040 6 ixp4xx_eth lsmod: usbcore 139032 4 usb_storage,ehci_hcd,ohci_hcd df: Filesystem 1k-blocks Used Available Use% Mounted on df: tmpfs1484820 14828 0% /dev df: tmpfs1484820 14828 0% /dev df: /dev/sda1 2893628545252 2201384 20% /target df: /dev/sda1 2893628545252 2201384 20% /dev/.static/dev df: tmpfs14848
Bug#501416: marked as done (linux-image-2.6.24-etchnhalf.1-686-bigmem: md resyncing again and again)
Your message dated Tue, 4 Jun 2013 00:28:55 +0200
with message-id 20130603222855.GB5604@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #501416,
regarding linux-image-2.6.24-etchnhalf.1-686-bigmem: md resyncing again and
again
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
501416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.24-etchnhalf.1-686-bigmem
Version: 2.6.24-6~etchnhalf.5
Severity: normal
i have two separate computer with this sata controller:
00:1f.2 SATA controller: Intel Corporation 631xESB/632xESB SATA Storage
Controller AHCI (rev 09)
i got errors on ata1 (on ata0 never) while resync md.
i didn't get any errors while check this partition with badblocks.
after the resync done that's starting from the beginning agin and again.
-- Package-specific info:
** Version:
Linux version 2.6.24-etchnhalf.1-686-bigmem (Debian 2.6.24-6~etchnhalf.5)
(da...@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21))
#1 SMP Mon Sep 8 07:08:27 UTC 2008
** Command line:
root=/dev/md0 ro
** Not tainted
** Kernel log:
raid1: sda: unrecoverable I/O read error for block 5064704
sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: irq_stat 0x4001
ata1.00: cmd c8/00:08:8f:49:4d/00:00:00:00:00/e0 tag 0 dma 4096 in
res 51/40:08:95:49:4d/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: irq_stat 0x4001
ata1.00: cmd c8/00:08:8f:49:4d/00:00:00:00:00/e0 tag 0 dma 4096 in
res 51/40:08:95:49:4d/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: irq_stat 0x4001
ata1.00: cmd c8/00:08:8f:49:4d/00:00:00:00:00/e0 tag 0 dma 4096 in
res 51/40:08:95:49:4d/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: irq_stat 0x4001
ata1.00: cmd c8/00:08:8f:49:4d/00:00:00:00:00/e0 tag 0 dma 4096 in
res 51/40:08:95:49:4d/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: irq_stat 0x4001
ata1.00: cmd c8/00:08:8f:49:4d/00:00:00:00:00/e0 tag 0 dma 4096 in
res 51/40:08:95:49:4d/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: irq_stat 0x4001
ata1.00: cmd c8/00:08:8f:49:4d/00:00:00:00:00/e0 tag 0 dma 4096 in
res 51/40:08:95:49:4d/00:00:00:00:00/e0 Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC
Bug#476926: marked as done (linux-image-2.6.24-1-686: crashes at boot on a VIA C3 (VIA Nehemiah / CentaurHauls) system)
Your message dated Tue, 4 Jun 2013 00:28:55 +0200 with message-id 20130603222855.GB5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #476926, regarding linux-image-2.6.24-1-686: crashes at boot on a VIA C3 (VIA Nehemiah / CentaurHauls) system 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.) -- 476926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.24-1-686 Version: 2.6.24-5 Severity: normal linux-image-2.6.24-1-686: crashes at boot on a VIA C3 (VIA Nehemiah / CentaurHauls) system around the moment where it decompresses the kernel -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.24-1-686 depends on: ii debconf [debconf-2.0] 1.5.20 Debian configuration management sy ii initramfs-tools [linux-initra 0.91e tools for generating an initramfs ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-24 Yet Another mkInitRD Versions of packages linux-image-2.6.24-1-686 recommends: ii libc6-i6862.7-10 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.24-1-686/preinst/overwriting-modules-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/bootloader-error-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/create-kimage-link-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/old-system-map-link-2.6.24-1-686: true linux-image-2.6.24-1-686/prerm/would-invalidate-boot-loader-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/initrd-2.6.24-1-686: linux-image-2.6.24-1-686/preinst/failed-to-move-modules-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/depmod-error-initrd-2.6.24-1-686: false linux-image-2.6.24-1-686/preinst/bootloader-initrd-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/old-initrd-link-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.24-1-686/postinst/old-dir-initrd-link-2.6.24-1-686: true linux-image-2.6.24-1-686/preinst/abort-install-2.6.24-1-686: linux-image-2.6.24-1-686/prerm/removing-running-kernel-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/depmod-error-2.6.24-1-686: false linux-image-2.6.24-1-686/preinst/abort-overwrite-2.6.24-1-686: linux-image-2.6.24-1-686/preinst/elilo-initrd-2.6.24-1-686: true linux-image-2.6.24-1-686/postinst/bootloader-test-error-2.6.24-1-686: linux-image-2.6.24-1-686/postinst/kimage-is-a-directory: linux-image-2.6.24-1-686/preinst/lilo-initrd-2.6.24-1-686: true ---End Message--- ---BeginMessage--- 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.0 / 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#494393: marked as done (linux-image-2.6.24-etchnhalf.1-686: lockups under X)
Your message dated Tue, 4 Jun 2013 00:28:55 +0200 with message-id 20130603222855.GB5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #494393, regarding linux-image-2.6.24-etchnhalf.1-686: lockups under X 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.) -- 494393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.24-etchnhalf.1-686 Version: 2.6.24-6~etchnhalf.4 Severity: normal *** Please type your report below this line *** Hi, I'm reporting what appears to be a regression in 2.6.24 vs 2.6.18. I noticed the problem also in bp.o 2.6.25-2-686. Everything works fine on 2.6.18-6-686. At first I thought it was related to my wireless card, but tests I've done now point the finger at something related to X sessions. The lockups do not occur immediately, only after a period of use. This can vary from a few minutes to well over an hour. When the lockups occur, the system appears frozen. I could not get any response from cabackspace in an X session, nor switch VTs with caFn nor reboot with cadel. I can't see the disk light blink. /var/log/debug shows many messages like this Aug 7 14:34:16 localhost kernel: [ 96.578706] eth4: Information frame lost. before the lockups, which made me suspect the wireless card drivers. This does not happen in all cases however. The lockup is sudden enough that I get little help from the files in /var/log. I tried monitoring memory usage, and could not see any evidence that this is related to the system running out of memory. I tried leaving the system booted up with the card installed and associated but doing nothing - no X, no typing on the VTs, etc. After a couple of hours it still seemed to be fine. I started X and left it running but with no user input. The system locked up after approximately 2 hours. I tried to refine this test and I can now get a reliable freeze. The test procedure was to leave a shell script running that wrote timestamps (and 'free' output) to a file and called 'sync' to make sure the writes hit the disk. I ran it both from an xterm in an X session (xfce) and from a VT (no X running anywhere on the machine). THe tests come out like this: pcmcia card X windowsFreeze out no no (tested for 208min) in no no (tested for 164min) out yes yes (at 123min) in yes yes (at 26min, 155min, 158min) In active use (card in and X running) the lockup occurs after 5 or 6 minutes. This makes the kernel unusable for me. I had one lockup during X startup - I had the card installed before powerup. The boot went ok, the card got an IP address and seemed to be working. This was all in text console mode. Then I typed 'startx'. The system wedged during the X startup, with this error: --- ...snip... Synaptics DeviceOn called (--) Synaptics Touchpad auto-dev sets device to /dev/input/event2 (**) Option Device /dev/input/event2 (--) Synaptics Touchpad touchpad found Synaptics DeviceOff called (II) AIGLX: Suspending AIGLX clients for VT switch Error in I830WaitLpRing(), now is -1679791316, start is -1679793317 pgetbl_ctl: 0x1ffe0001 pgetbl_err: 0x0 ipeir: 0 iphdr: 54b7 LP ring tail: 1858 head: 144 len: 1f001 start 0 eir: 0 esr: 0 emr: instdone: ffc1 instpm: 0 memmode: 108 instps: 24 hwstam: fffe ier: 82 imr: 0 iir: 50 space: 125156 wanted 131064 (II) I810(0): [drm] removed 1 reserved context for kernel (II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xe0ad4000 at 0xb7a95000 Fatal server error: lockup (II) AIGLX: Suspending AIGLX clients for VT switch Error in I830WaitLpRing(), now is -1679788617, start is -1679790618 pgetbl_ctl: 0x1ffe0001 pgetbl_err: 0x0 ipeir: 0 iphdr: 54b7 LP ring tail: 1860 head: 144 len: 1f001 start 0 eir: 0 esr: 0 emr: instdone: ffc1 instpm: 0 memmode: 108 instps: 24 hwstam: fffe ier: 82 imr: 0 iir: 50 space: 125148 wanted 131064 FatalError re-entered, aborting lockup - However I have not been able to reproduce this failure mode. Before reporting, I took a brief look for regression reports etc. I searched bugzilla.k.o for reports mentioning lockup since 2.6.18. None seemed relevant here. More info on the system (lspci etc) is included below. It's a dell latitude c400 with bios revision A11. Cheers Vince -- Package-specific info: -- System Information: Debian
Bug#309405: marked as done (mount.cifs: poor performance and high CPU load with large files (500MB+) compared to mount.smbfs)
Your message dated Tue, 4 Jun 2013 00:29:27 +0200 with message-id 20130603222926.GC5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #309405, regarding mount.cifs: poor performance and high CPU load with large files (500MB+) compared to mount.smbfs 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.) -- 309405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: smbfs Version: 3.0.14a-1 Severity: normal I run a Linux box within a VMware, a Windows Server 2003 and a Windows 2000 Server (both not in VMware). When copying a CD image file from within Linux to a cifs mounted Win2003 share, I see a very poor performance and high CPU load (about 90% system) on the Linux VM. Copying begins with 3 MB/s (measured by mc), after 4% it suddenly stops for say 10-20 seconds, then continues with 1..2 MB/s, but stopping from time to time for several seconds. CPU load is only high while copying, not in the pauses. Copying the whole file (700MB) took about 10 minutes. Copying the same file in the same direction from a samba share at the W2K3 box is very much faster, copying is finished in about a minute, and CPU load on the Linux side is by far less. When copying the same file from Linux to a cifs mounted Windows 2000 share, I get a similar picture: Copying begins with 3 MB/s, but soon slows down to 1 MB/s with high CPU load. But here, it doesn't seem to have these long idle times. Nevertheless copying takes about 10 minutes, too. When mounting the Win2000 share with smbfs, however, I get about 4 MB/s and a system load of approx. 35%. (This may indicate, that bug #203887 is indeed solved.) I don't think it has anything to do with VMware as all other transfers from and to this Linux VM are fast (NFS, HTTP, FTP, and Samba as mentioned). (FTP and NFS copy performs with 10 MB/s) I tried to compile a new kernel with the newest CIFS (1.34), but unfortunately it doesn't compile with the Debian sarge kernel sources for 2.6.8, neither plain 1.34 nor 1.34-RHEL4. CIFS 1.34 does compile with Debian sid kernel 2.6.11, but unfortunately, the VMware net driver doesn't work with this kernel, so I cannot test this. I cannot test smbfs with W2K3 for comparison either, as I don't want to modify the W2K3 settings to allow non-signed SMB. On the Linux side I could test nearly everything, however, if somebody has some more ideas what to test. Martin -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-vmware-1 (from sarge kernel-source-2.6.8-15) Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) Versions of packages smbfs depends on: ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libcomerr2 1.37-2 common error description library ii libkrb531.3.6-2 MIT Kerberos runtime libraries ii libldap22.1.30-6 OpenLDAP libraries ii netbase 4.21 Basic TCP/IP networking system ii samba-common3.0.14a-1Samba common files used by both th -- no debconf information ---End Message--- ---BeginMessage--- 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.0 / 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#607055: marked as done (linux-image-2.6.32-5-686-bigmem: WI-FI constantly disconnects)
Your message dated Tue, 4 Jun 2013 00:28:24 +0200 with message-id 20130603222824.GA5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #607055, regarding linux-image-2.6.32-5-686-bigmem: WI-FI constantly disconnects 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.) -- 607055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-28 Severity: normal Please see here for what's happening: http://unix.stackexchange.com/questions/4645/wi-fi-constantly-disconnects. -- Package-specific info: ** Version: Linux version 2.6.32-5-686-bigmem (Debian 2.6.32-28) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Nov 25 19:30:54 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686-bigmem root=UUID=06ec5bbe-0c90-4212-8446-432c302e3847 ro vga=769 quiet ** Not tainted ** Kernel log: [59277.384294] scsi7 : SCSI emulation for USB Mass Storage devices [59277.388237] usb-storage: device found at 7 [59277.388239] usb-storage: waiting for device to settle before scanning [59282.388225] usb-storage: device scan complete [59282.397611] scsi 7:0:0:0: Direct-Access SAMSUNG HD102UJ PQ: 0 ANSI: 2 [59282.398392] sd 7:0:0:0: Attached scsi generic sg3 type 0 [59282.404156] sd 7:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [59282.406459] sd 7:0:0:0: [sdc] Write Protect is off [59282.406463] sd 7:0:0:0: [sdc] Mode Sense: 38 00 00 00 [59282.406465] sd 7:0:0:0: [sdc] Assuming drive cache: write through [59282.409705] sd 7:0:0:0: [sdc] Assuming drive cache: write through [59282.409710] sdc: sdc1 [59282.426199] sd 7:0:0:0: [sdc] Assuming drive cache: write through [59282.426204] sd 7:0:0:0: [sdc] Attached SCSI disk [59414.432054] gvfsd-metadata[12642]: segfault at 8 ip 0804d2da sp bf9cb040 error 4 in gvfsd-metadata[8048000+c000] [59595.489157] gvfsd-metadata[8566]: segfault at 8 ip 0804d2da sp bff56e20 error 4 in gvfsd-metadata[8048000+c000] [59666.469082] gvfsd-metadata[27953]: segfault at 8 ip 0804d2da sp bfc0c2d0 error 4 in gvfsd-metadata[8048000+c000] [60116.488066] gvfsd-metadata[29673]: segfault at 8 ip 0804d2da sp bfe4dd60 error 4 in gvfsd-metadata[8048000+c000] [62060.757315] usb 3-1: USB disconnect, address 6 [62085.125063] usb 3-1: new high speed USB device using ehci_hcd and address 8 [62085.257060] usb 3-1: New USB device found, idVendor=152d, idProduct=2329 [62085.257069] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5 [62085.257076] usb 3-1: Product: USB to ATA/ATAPI bridge [62085.257081] usb 3-1: Manufacturer: JMicron [62085.257086] usb 3-1: SerialNumber: 7A37 [62085.257300] usb 3-1: configuration #1 chosen from 1 choice [62085.257985] scsi8 : SCSI emulation for USB Mass Storage devices [62085.258239] usb-storage: device found at 8 [62085.258244] usb-storage: waiting for device to settle before scanning [62090.256276] usb-storage: device scan complete [62090.299434] scsi 8:0:0:0: Direct-Access TOSHIBA MK1646GSX PQ: 0 ANSI: 2 CCS [62090.302016] sd 8:0:0:0: Attached scsi generic sg2 type 0 [62090.302970] sd 8:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB) [62090.303717] sd 8:0:0:0: [sdb] Write Protect is off [62090.303724] sd 8:0:0:0: [sdb] Mode Sense: 28 00 00 00 [62090.303730] sd 8:0:0:0: [sdb] Assuming drive cache: write through [62090.305573] sd 8:0:0:0: [sdb] Assuming drive cache: write through [62090.305582] sdb: sdb1 sdb2 [62090.319080] sd 8:0:0:0: [sdb] Assuming drive cache: write through [62090.319089] sd 8:0:0:0: [sdb] Attached SCSI disk [62257.448088] gvfsd-metadata[13823]: segfault at 8 ip 0804d2da sp bfa698f0 error 4 in gvfsd-metadata[8048000+c000] [62358.406246] sd 8:0:0:0: [sdb] Unhandled sense code [62358.406254] sd 8:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [62358.406264] sd 8:0:0:0: [sdb] Sense Key : Medium Error [current] [62358.406274] sd 8:0:0:0: [sdb] Add. Sense: Unrecovered read error [62358.406285] sd 8:0:0:0: [sdb] CDB: Read(10): 28 00 0b 12 60 c8 00 00 f0 00 [62358.406306] end_request: I/O error, dev sdb, sector 185753800 [62358.406316] Buffer I/O error on device sdb2, logical block 20915737 [62358.406329] Buffer I/O error on device sdb2, logical block 20915738 [62358.406337] Buffer I/O error on device sdb2, logical block 20915739 [62358.406344] Buffer I/O error on device sdb2, logical block 20915740 [62358.406352] Buffer I/O error on device sdb2, logical block 20915741 [62358.406359] Buffer I/O error on device sdb2, logical block
Bug#481390: marked as done (linux-image-2.6.18-6-amd64: System halts, GPF message: 0000 [1] SMP)
Your message dated Tue, 4 Jun 2013 00:28:24 +0200 with message-id 20130603222824.GA5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #481390, regarding linux-image-2.6.18-6-amd64: System halts, GPF message: [1] SMP 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.) -- 481390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.18-6-amd64 Version: 2.6.18.dfsg.1-18etch4 Severity: normal Between one to three times a forthnight my box freezes. Around half of the times the syslog and system stops (completly) with no info. The other half the syslog has catched info. The following is from the latest stop: May 15 18:24:12 localhost kernel: general protection fault: [1] SMP May 15 18:24:12 localhost kernel: CPU 1 May 15 18:24:12 localhost kernel: Modules linked in: ipt_MASQUERADE iptable_nat ip_nat ip_conntrack nfnetlink iptable_filter ip_tables x_tables nfs nfsd exportfs lockd nfs_acl sunrpc ppdev parport_pc lp parport button ac battery ipv6 sbp2 loop psmouse serio_raw i2c_nforce2 pcspkr i2c_core tsdev evdev eth1394 ext3 jbd mbcache dm_mirror dm_snapshot dm_mod raid456 md_mod xor sd_mod ide_disk usbhid sata_nv ohci1394 ieee1394 sata_sil24 libata scsi_mod forcedeth amd74xx ehci_hcd generic ide_core ohci_hcd thermal processor fan May 15 18:24:12 localhost kernel: Pid: 9, comm: events/1 Not tainted 2.6.18-6-amd64 #1 May 15 18:24:12 localhost kernel: RIP: 0010:[802b60a5] [802b60a5] drain_array+0x25/0xc8 May 15 18:24:12 localhost kernel: RSP: :810037f49e00 EFLAGS: 00010286 May 15 18:24:12 localhost kernel: RAX: 0001025e001b RBX: RCX: May 15 18:24:12 localhost kernel: RDX: 01003ddd2c00 RSI: 81003d8d9e40 RDI: 81003dfe2540 May 15 18:24:12 localhost kernel: RBP: 81003d8d9e40 R08: R09: 81003799bf30 May 15 18:24:12 localhost kernel: R10: 8100012b4540 R11: 0008 R12: 01003ddd2c00 May 15 18:24:12 localhost kernel: R13: R14: 81003d8d9e40 R15: 81003dfe2540 May 15 18:24:12 localhost kernel: FS: 2ac6dd704e00() GS:8100379d2ac0() knlGS: May 15 18:24:12 localhost kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b May 15 18:24:12 localhost kernel: CR2: 2b7022df CR3: 18bba000 CR4: 06e0 May 15 18:24:12 localhost kernel: Process events/1 (pid: 9, threadinfo 810037f48000, task 810037fef140) May 15 18:24:12 localhost kernel: Stack: 0008 81003d8d9e40 81003dfe2540 May 15 18:24:12 localhost kernel: 802b6b24 802b6bfb May 15 18:24:12 localhost kernel: 810001015040 810001015048 81003e9c6740 0282 May 15 18:24:12 localhost kernel: Call Trace: May 15 18:24:12 localhost kernel: [802b6b24] cache_reap+0x0/0x21c May 15 18:24:12 localhost kernel: [802b6bfb] cache_reap+0xd7/0x21c May 15 18:24:12 localhost kernel: [80249111] run_workqueue+0x94/0xe5 May 15 18:24:12 localhost kernel: [80245ae3] worker_thread+0x0/0x122 May 15 18:24:12 localhost kernel: [80245bd3] worker_thread+0xf0/0x122 May 15 18:24:12 localhost kernel: [8027c973] default_wake_function+0x0/0xe May 15 18:24:12 localhost kernel: [802305dc] kthread+0xd4/0x107 May 15 18:24:12 localhost kernel: [80258a60] child_rip+0xa/0x12 May 15 18:24:12 localhost kernel: [80230508] kthread+0x0/0x107 May 15 18:24:12 localhost kernel: [80258a56] child_rip+0x0/0x12 May 15 18:24:12 localhost kernel: May 15 18:24:12 localhost kernel: May 15 18:24:12 localhost kernel: Code: 83 3a 00 0f 84 8d 00 00 00 83 7a 0c 00 0f 95 c2 85 c9 0f 94 May 15 18:24:12 localhost kernel: RIP [802b60a5] drain_array+0x25/0xc8 May 15 18:24:12 localhost kernel: RSP 810037f49e00 -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-6-amd64 depends on: ii cor 5.97-5.3 The GNU core utilities ii deb 1.5.11etch1 Debian configuration management sy ii e2f 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 ext2 file system utilities and lib ii ini 0.85h
Bug#511062: marked as done (linux-image-2.6.26-1-686: NFS client hang and packet flood after resume from suspend to ram)
Your message dated Tue, 4 Jun 2013 00:28:24 +0200 with message-id 20130603222824.GA5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #511062, regarding linux-image-2.6.26-1-686: NFS client hang and packet flood after resume from suspend to ram 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.) -- 511062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-12 Severity: normal Within four hours after a client system resumes from suspend to ram, access on the client to the NFS filesystem hangs, access to all other filesystems eventually hang once cache is filled, and a flood of packets is observed on the NFS server being emitted by the NFS client. Both the NFS server and NFS client are running linux-image-2.6.26-1-686 2.6.26-12, and are on the same network switch. The symptom is cleared by typing /etc/init.d/nfs-kernel-server restart on the NFS server system dors. At that time, the client regains normal operation and the flood ceases. The client has in dmesg: [13969.896074] Restarting tasks ... done. [24837.320033] nfs: server dors not responding, still trying [25140.408048] nfs: server dors not responding, timed out [25140.408048] nfs: server dors not responding, timed out [25140.500429] nfs: server dors OK A tcpdump of the packet flood shows 23783 packets over a period of 1.37 seconds. The packets consist of TCP SYN from the client to the server, followed by a TCP RST from the server to the client. The same port numbers are reused in each packet; source port rxe, destination port 2049. The tcpdump is available if required for analysis, but the user data in the packets is confidential. The symptom does not occur unless the NFS client system is first suspended or hibernated, using pm-suspend and pm-hibernate, and then resumed. Possibly unrelated observation; the disk access LED of the system is normally off unless the disk is being accessed, but after resume from suspend or hibernate the LED stays on. The disk can still be accessed. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-12) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Mon Dec 15 18:15:07 UTC 2008 ** Command line: root=UUID=ce95ab50-301b-418b-8546-07b4d6cdd419 ro quiet splash resume=/dev/hda2 ** Not tainted ** Kernel log: [5.516369] ACPI: PCI Interrupt :02:08.0[A] - GSI 20 (level, low) - IRQ 20 [5.607348] e100: eth0: e100_probe: addr 0xfe20, irq 20, MAC addr 00:08:02:1b:d4:99 [5.664866] hda: max request size: 128KiB [5.668676] hda: 80063424 sectors (40992 MB) w/2048KiB Cache, CHS=65535/16/63 [5.668688] hda: cache flushes not supported [5.668787] hda: hda1 hda2 [5.691559] hdc: ATAPI 48X DVD-ROM CD-R/RW drive, 2048kB Cache [5.691574] Uniform CD-ROM driver Revision: 3.20 [6.007825] PM: Starting manual resume from disk [6.078592] kjournald starting. Commit interval 5 seconds [6.078592] EXT3-fs: mounted filesystem with ordered data mode. [8.240986] udevd version 125 started [9.795423] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [9.818454] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [9.834535] Linux agpgart interface v0.103 [9.856651] agpgart: Detected an Intel 845G Chipset. [9.860738] agpgart: AGP aperture is 64M @ 0xf800 [9.870616] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008) [9.870742] iTCO_wdt: Found a ICH2 TCO device (Version=1, TCOBASE=0xf860) [9.870787] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [9.956340] intel_rng: Firmware space is locked read-only. If you can't or [9.956346] intel_rng: don't want to disable this in firmware setup, and if [9.956348] intel_rng: you are certain that your system has a functional [9.956351] intel_rng: RNG, try using the 'no_fwh_detect' option. [ 10.465563] input: Power Button (FF) as /class/input/input0 [ 10.476119] ACPI: Power Button (FF) [PWRF] [ 10.476339] input: Power Button (CM) as /class/input/input1 [ 10.495886] ACPI: Power Button (CM) [PBTN] [ 11.936524] input: PC Speaker as /class/input/input2 [ 12.559162] parport_pc 00:07: reported by Plug and Play ACPI [ 12.559226] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 12.862052] ACPI: PCI Interrupt :00:1f.5[B] - GSI 17 (level, low) - IRQ 17 [ 12.862088] PCI: Setting latency timer of device :00:1f.5 to 64 [ 13.480018]
Bug#498727: marked as done (linux-image-2.6.26-1-686: laptop multimedia buttons generate scancodes but don't get mapped to keycodes)
Your message dated Tue, 4 Jun 2013 00:28:24 +0200 with message-id 20130603222824.GA5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #498727, regarding linux-image-2.6.26-1-686: laptop multimedia buttons generate scancodes but don't get mapped to keycodes 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.) -- 498727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-4 Severity: normal On a Fujitsu Siemens Amilo Pi 1505 laptop, the multimedia buttons don't work correctly. The mute button generates a keycode, but the volume up/down don't, and neither does the 'information' button, which usually brings up a webbrower. The scancodes for those keys are: Fn+F3 == Mute: 0xe0 0x20 0xe0 0xa0 Fn+F5 == VolUp: 0xe0 0x30 Fn+F6 == VolDown: 0xe0 0x2e I == Information: 0xe0 0x32 0xe0 0xb2 The keycode generated by the mute button is 160. These basic things should work out of the box. It really makes the laptop experience alot less fun. These buttons do work on Ubuntu, I don't know how they fixed it. Alexander -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-4) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 12:00:54 UTC 2008 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.26-1-686 root=/dev/sda5 ro ** Not tainted ** Kernel log: [ 36.784798] lp: driver loaded but no devices found [ 36.827608] ppdev: user-space parallel port driver [ 37.489682] NET: Registered protocol family 10 [ 37.489682] lo: Disabled Privacy Extensions [ 37.489682] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 40.154493] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use) [ 41.919589] Bluetooth: Core ver 2.11 [ 41.919589] NET: Registered protocol family 31 [ 41.919589] Bluetooth: HCI device and connection manager initialized [ 41.919589] Bluetooth: HCI socket layer initialized [ 42.031788] Bluetooth: L2CAP ver 2.9 [ 42.031788] Bluetooth: L2CAP socket layer initialized [ 42.058992] Bluetooth: RFCOMM socket layer initialized [ 42.058992] Bluetooth: RFCOMM TTY layer initialized [ 42.058992] Bluetooth: RFCOMM ver 1.8 [ 42.237403] ACPI: PCI Interrupt :05:00.0[A] - GSI 18 (level, low) - IRQ 18 [ 42.237481] PM: Writing back config space on device :05:00.0 at offset 1 (was 12, writing 16) [ 42.237481] firmware: requesting iwlwifi-3945-1.ucode [ 42.372754] Registered led device: iwl-phy0:radio [ 42.372754] Registered led device: iwl-phy0:assoc [ 42.372754] Registered led device: iwl-phy0:RX [ 42.372754] Registered led device: iwl-phy0:TX [ 42.392036] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 46.619752] [drm] Initialized drm 1.1.0 20060810 [ 46.627755] ACPI: PCI Interrupt :00:02.0[A] - GSI 16 (level, low) - IRQ 16 [ 46.627755] PCI: Setting latency timer of device :00:02.0 to 64 [ 46.627755] [drm] Initialized i915 1.6.0 20060119 on minor 0 [ 82.977255] CPU0 attaching NULL sched-domain. [ 82.977272] CPU1 attaching NULL sched-domain. [ 83.007810] CPU0 attaching sched-domain: [ 83.007810] domain 0: span 0-1 [ 83.007810] groups: 0 1 [ 83.007810] CPU1 attaching sched-domain: [ 83.007810] domain 0: span 0-1 [ 83.007810] groups: 1 0 [ 393.828259] CPU0 attaching NULL sched-domain. [ 393.828268] CPU1 attaching NULL sched-domain. [ 393.829423] CPU0 attaching sched-domain: [ 393.829423] domain 0: span 0-1 [ 393.829423] groups: 0 1 [ 393.829423] CPU1 attaching sched-domain: [ 393.829423] domain 0: span 0-1 [ 393.829423] groups: 1 0 [ 402.691384] wlan0: Initial auth_alg=0 [ 402.691384] wlan0: authenticate with AP 00:17:9a:f2:12:c7 [ 402.693069] wlan0: RX authentication from 00:17:9a:f2:12:c7 (alg=0 transaction=2 status=0) [ 402.693080] wlan0: authenticated [ 402.693087] wlan0: associate with AP 00:17:9a:f2:12:c7 [ 402.696047] wlan0: RX AssocResp from 00:17:9a:f2:12:c7 (capab=0x431 status=0 aid=1) [ 402.696047] wlan0: associated [ 402.696047] wlan0: switched to short barker preamble (BSSID=00:17:9a:f2:12:c7) [ 402.699307] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.628975] wlan0: no IPv6 routers present [ 543.840992] wlan0: deauthenticate(reason=3) [ 544.095774] ACPI: PCI interrupt for device :05:00.0 disabled [ 544.168973] ACPI: PCI Interrupt :05:00.0[A] - GSI 18 (level, low) - IRQ 18 [ 544.168973] PM: Writing back config space on device :05:00.0 at
Bug#494822: marked as done (linux-image-2.6.25-2-686: DVD-writing with VIA IDE controller produce kernel error hdd: status timeout)
Your message dated Tue, 4 Jun 2013 00:28:55 +0200 with message-id 20130603222855.GB5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #494822, regarding linux-image-2.6.25-2-686: DVD-writing with VIA IDE controller produce kernel error hdd: status timeout 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.) -- 494822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.25-2-686 Version: 2.6.25-7 Severity: normal When I use the writing-capabilities (in simulation!), after a while, the (simulated) writing process will terminate and my syslog begins to get filled with plenty of repeated kernel error messages related to my DVD-writer. My DVD-writer, from that time on, is unusable until the next reboot. The only thing I found to stop kernel error logging is to unload the ide_cd_mod module. Here attached, you will find my setup and what I exactly did to produce the problem. Please note that the first DVD-writing attempt did NOT trigger the error, thus I guess there is some randomness included. But I got the problem each time I tried to write at speed=1 (I guess, because the time to terminate the process is longer so more chance to trigger the problem). -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-6) (m...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Fri Jun 27 03:23:20 UTC 2008 ** Command line: BOOT_IMAGE=Linux-2.6.25-2 ro root=301 ** Not tainted -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-2-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.25-2-686 recommends: ii libc6-i6862.7-10 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.25-2-686 suggests: ii lilo 1:22.8-5 LInux LOader - The Classic OS load pn linux-doc-2.6.25 none (no description available) - setup and bug triggering, 23 juil, 18h - ~#uname -a Linux Olivier 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686 GNU/Linux /var/log#apt-show-versions | grep image-2.6.25 linux-image-2.6.25-2-686/testing uptodate 2.6.25-6 ~#lsmod | grep ide_ ide_disk 13952 3 ide_cd_mod 32864 0 cdrom 31872 1 ide_cd_mod ide_pci_generic 4228 0 [permanent] ide_core 100312 4 ide_disk,ide_cd_mod,via82cxxx,ide_pci_generic ~#lspci | grep IDE 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) ~#wodim --devices wodim: Overview of accessible drives (2 found) : - 0 dev='/dev/hdc' rwrw-- : 'SAMSUNG' 'DVD-ROM SD-616Q' 1 dev='/dev/hdd' rwrw-- : 'PLEXTOR' 'DVDR PX-708A' - mounting a CD with mount /dev/hdc and mount /dev/hdd: works (I can read the content). Then I unmount and load an empty DVD in the Plextor drive. ~#hdparm /dev/hdd /dev/hdd: IO_support= 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 256 (on) HDIO_GETGEO failed: Inappropriate ioctl for device ~#dvd+rw-mediainfo /dev/hdd INQUIRY:[PLEXTOR ][DVDR PX-708A ][1.02] GET [CURRENT] CONFIGURATION: Mounted Media: 11h, DVD-R Sequential Current Write Speed: 4.0x1385=5540KB/s Write Speed #0:4.0x1385=5540KB/s Write Speed #1:2.0x1385=2770KB/s Write Speed #2:1.0x1385=1385KB/s GET [CURRENT] PERFORMANCE: Write Performance: 4.0x1385=5540KB/s@[0 - 2294911] Speed Descriptor#0:02/2298495 R@8.0x1385=11080KB/s W@4.0x1385=5540KB/s Speed Descriptor#1:02/2298495 R@8.0x1385=11080KB/s W@2.0x1385=2770KB/s Speed Descriptor#2:02/2298495 R@8.0x1385=11080KB/s W@1.0x1385=1385KB/s READ DVD STRUCTURE[#0h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy
Bug#501764: marked as done (linux-image-2.6.24-etchnhalf.1-486: ssh -X breaks Xauthority on NFS mounted home dir)
Your message dated Tue, 4 Jun 2013 00:28:24 +0200 with message-id 20130603222824.GA5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #501764, regarding linux-image-2.6.24-etchnhalf.1-486: ssh -X breaks Xauthority on NFS mounted home dir 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.) -- 501764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.24-etchnhalf.1-486 Version: 2.6.24-6~etchnhalf.5 Severity: normal Apparently 2.6.24 does some extra caching for stat() which causes ssh -X to break when home is on NFS (it does not see the change to ..Xauthority). I found detailed description of the bug at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/269954 and I find it quite critical since it breaks a very common use case. ---End Message--- ---BeginMessage--- 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.0 / 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#408746: marked as done (snd* modules are not autoloaded when udev is installed)
Your message dated Tue, 4 Jun 2013 00:29:27 +0200 with message-id 20130603222926.GC5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #408746, regarding snd* modules are not autoloaded when udev is installed 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.) -- 408746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: udev Version: 0.103-2 Severity: critical Justification: breaks unrelated software After installing udev (as advised in the debian-powerpc mailing-list), ALSA no longer works, e.g., with ogg123: ALSA lib confmisc.c:670:(snd_func_card_driver) cannot find card '0' ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_concat returned error: No such device ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_refer returned error: No such device ALSA lib conf.c:3968:(snd_config_expand) Evaluate error: No such device ALSA lib pcm.c:2143:(snd_pcm_open_noupdate) Unknown PCM default ALSA snd_pcm_open error: No such device Error: Cannot open device alsa09. I can see that the snd* modules are no longer loaded. -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 8 lrwxrwxrwx 1 root root 20 2007-01-28 04:09:29 020_permissions.rules - ../permissions.rules lrwxrwxrwx 1 root root 19 2005-10-26 00:14:44 025_libgphoto2.rules - ../libgphoto2.rules lrwxrwxrwx 1 root root 15 2006-02-09 03:13:54 85-pcmcia.rules - ../pcmcia.rules lrwxrwxrwx 1 root root 13 2007-01-28 04:09:29 udev.rules - ../udev.rules lrwxrwxrwx 1 root root 25 2007-01-28 04:09:29 z20_persistent-input.rules - ../persistent-input.rules lrwxrwxrwx 1 root root 19 2007-01-28 04:09:29 z20_persistent.rules - ../persistent.rules -rw-r--r-- 1 root root 511 2007-01-28 03:56:01 z25_persistent-cd.rules -rw-r--r-- 1 root root 436 2007-01-28 03:55:59 z25_persistent-net.rules lrwxrwxrwx 1 root root 33 2007-01-28 04:09:29 z45_persistent-net-generator.rules - ../persistent-net-generator.rules lrwxrwxrwx 1 root root 12 2007-01-28 04:09:29 z50_run.rules - ../run.rules lrwxrwxrwx 1 root root 16 2007-01-28 04:09:29 z55_hotplug.rules - ../hotplug.rules lrwxrwxrwx 1 root root 19 2006-08-06 20:13:22 z60_alsa-utils.rules - ../alsa-utils.rules lrwxrwxrwx 1 root root 15 2005-12-14 01:36:20 z60_hdparm.rules - ../hdparm.rules lrwxrwxrwx 1 root root 33 2006-09-10 11:33:11 z60_xserver-xorg-input-wacom.rules - ../xserver-xorg-input-wacom.rules lrwxrwxrwx 1 root root 29 2007-01-28 04:09:29 z75_cd-aliases-generator.rules - ../cd-aliases-generator.rules -- /sys/: /sys/block/hda/dev /sys/block/hda/hda1/dev /sys/block/hda/hda2/dev /sys/block/hda/hda3/dev /sys/block/hda/hda4/dev /sys/block/hda/hda5/dev /sys/block/hdc/dev /sys/block/ram0/dev /sys/block/ram1/dev /sys/block/ram10/dev /sys/block/ram11/dev /sys/block/ram12/dev /sys/block/ram13/dev /sys/block/ram14/dev /sys/block/ram15/dev /sys/block/ram2/dev /sys/block/ram3/dev /sys/block/ram4/dev /sys/block/ram5/dev /sys/block/ram6/dev /sys/block/ram7/dev /sys/block/ram8/dev /sys/block/ram9/dev /sys/class/adb/adb/dev /sys/class/graphics/fb0/dev /sys/class/input/input0/event0/dev /sys/class/input/input0/mouse0/dev /sys/class/input/input0/ts0/dev /sys/class/input/input1/event1/dev /sys/class/input/input2/event2/dev /sys/class/input/input3/event3/dev /sys/class/input/input3/mouse1/dev /sys/class/input/input3/ts1/dev /sys/class/input/input4/event4/dev /sys/class/input/mice/dev /sys/class/misc/agpgart/dev /sys/class/misc/device-mapper/dev /sys/class/misc/nvram/dev /sys/class/misc/pmu/dev /sys/class/misc/psaux/dev /sys/class/misc/rtc/dev /sys/class/misc/snapshot/dev /sys/class/usb_device/usbdev1.1/dev /sys/class/usb_device/usbdev1.2/dev /sys/class/usb_device/usbdev2.1/dev /sys/devices/pci0001:10/0001:10:18.0/usb1/1-0:1.0/usbdev1.1_ep81/dev /sys/devices/pci0001:10/0001:10:18.0/usb1/1-1/1-1:1.0/usbdev1.2_ep02/dev /sys/devices/pci0001:10/0001:10:18.0/usb1/1-1/1-1:1.0/usbdev1.2_ep81/dev /sys/devices/pci0001:10/0001:10:18.0/usb1/1-1/1-1:1.0/usbdev1.2_ep85/dev /sys/devices/pci0001:10/0001:10:18.0/usb1/1-1/usbdev1.2_ep00/dev /sys/devices/pci0001:10/0001:10:18.0/usb1/usbdev1.1_ep00/dev /sys/devices/pci0001:10/0001:10:19.0/usb2/2-0:1.0/usbdev2.1_ep81/dev /sys/devices/pci0001:10/0001:10:19.0/usb2/usbdev2.1_ep00/dev -- Kernel configuration:
Bug#333776: marked as done (linux-2.6: vfat driver in 2.6.12 is not properly case-insensitive)
Your message dated Tue, 4 Jun 2013 00:29:27 +0200 with message-id 20130603222926.GC5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #333776, regarding linux-2.6: vfat driver in 2.6.12 is not properly case-insensitive 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.) -- 333776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=333776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.12-6 The vfat driver in 2.6.12 appears to include a regression compared with earlier versions. VFAT is a case-insensitive filesystem, but with this kernel filenames are not handled in a case-insensitive manner: $ cd /media/usb0/ $ touch foo $ ls -l foo -rw--- 1 vorlon vorlon 0 2005-10-08 03:25 foo $ touch fOo touch: cannot touch `fOo': File exists $ cat fOo cat fOo: No such file or directory $ rm foo $ touch FOO $ ls FOO ls: FOO: No such file or directory $ ls foo foo $ touch foo_not_8.3.txt $ touch fOO_not_8.3.txt $ ls -l f*txt -rw--- 1 vorlon vorlon 0 2005-10-08 03:28 foo_not_8.3.txt -rw--- 1 vorlon vorlon 0 2005-10-08 03:28 fOO_not_8.3.txt $ This poses a significant compatibility problem when sharing vfat volumes between Debian and Windows (which, y'know, is the whole point). Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vor...@debian.org http://www.debian.org/ signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- 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.0 / 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#511412: marked as done (clocksource/0: Time went backwards)
Your message dated Tue, 4 Jun 2013 00:29:27 +0200 with message-id 20130603222926.GC5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #511412, regarding clocksource/0: Time went backwards 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.) -- 511412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-xen-686 Version: 2.6.26-12 Severity: normal After upgrading a domU from etch to lenny kernel, I've faced a hard domU lockup that very looks like http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1098 after severak hours f running. I've applied the workaround descried there at comment 13, and since then domU worked several days under high load without issues. Maybe make debian kernels not to use xen clocksource until the issue is fixed? -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- 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.0 / 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#493304: marked as done (/boot/vmlinuz-2.6.24-etchnhalf.1-686: switch to utf8 breaks console for systems with legacy encodings)
Your message dated Tue, 4 Jun 2013 00:29:27 +0200 with message-id 20130603222926.GC5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #493304, regarding /boot/vmlinuz-2.6.24-etchnhalf.1-686: switch to utf8 breaks console for systems with legacy encodings 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.) -- 493304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.24-etchnhalf.1-686 Version: 2.6.24-6~etchnhalf.4 Severity: normal File: /boot/vmlinuz-2.6.24-etchnhalf.1-686 Hi, after installing the etchnhalf kernel, I found that only the ascii portion of my keyboard worked on the linux console. It turned out that, as of 2.6.24, the kernel defaults to starting the console in unicode mode (vt.default_utf8=1). On my i386 desktop, this only seemed to set the wrong keyboard mode; but on my powerpc machine, it somehow messed up the entire keymap. I don't know what's the policy WRT to such breakage caused by the etchnhalf kernels, but this has bitten my quite badly, so I'm filing a bug. Nikolaus -- Package-specific info: ** Version: Linux version 2.6.24-etchnhalf.1-686 (Debian 2.6.24-6~etchnhalf.4) (da...@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Mon Jul 21 11:17:43 UTC 2008 ** Command line: BOOT_IMAGE=Debian ro root=301 reboot=warm noapic vt.default_utf8=0 S ** Not tainted ** Kernel log: ACPI: PCI Interrupt :00:11.4[D] - Link [LNKD] - GSI 5 (level, low) - IRQ 5 uhci_hcd :00:11.4: UHCI Host Controller uhci_hcd :00:11.4: new USB bus registered, assigned bus number 3 uhci_hcd :00:11.4: irq 5, io base 0x1c00 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9 PCI: setting IRQ 9 as level-triggered ACPI: PCI Interrupt :00:14.0[A] - Link [LNKB] - GSI 9 (level, low) - IRQ 9 uhci_hcd :00:14.0: UHCI Host Controller uhci_hcd :00:14.0: new USB bus registered, assigned bus number 4 uhci_hcd :00:14.0: irq 9, io base 0x2800 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:14.1[B] - Link [LNKC] - GSI 11 (level, low) - IRQ 11 uhci_hcd :00:14.1: UHCI Host Controller uhci_hcd :00:14.1: new USB bus registered, assigned bus number 5 uhci_hcd :00:14.1: irq 11, io base 0x2c00 usb usb5: configuration #1 chosen from 1 choice hub 5-0:1.0: USB hub found hub 5-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:14.2[C] - Link [LNKD] - GSI 5 (level, low) - IRQ 5 ehci_hcd :00:14.2: EHCI Host Controller ehci_hcd :00:14.2: new USB bus registered, assigned bus number 6 ehci_hcd :00:14.2: irq 5, io mem 0xe8008400 ehci_hcd :00:14.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb6: configuration #1 chosen from 1 choice hub 6-0:1.0: USB hub found hub 6-0:1.0: 4 ports detected hda: max request size: 512KiB hda: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63 hda: cache flushes supported hda: hda1 hda2 hda3 hda4 hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 hda13 hda14 hda15 hda16 hda17 hda18 hda19 hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache Uniform CD-ROM driver Revision: 3.20 spurious 8259A interrupt: IRQ7. Attempting manual resume swsusp: Marking nosave pages: 0009f000 - 0010 swsusp: Marking nosave pages: 0fef - 0ff0 swsusp: Basic memory bitmaps created swsusp: Basic memory bitmaps freed kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Real Time Clock Driver v1.12ac input: PC Speaker as /class/input/input1 Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 parport_pc 00:09: reported by Plug and Play ACPI parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] irda_init() NET: Registered protocol family 23 Linux agpgart interface v0.102 agpgart: Detected VIA KT266/KY266x/KT333 chipset agpgart: AGP aperture is 128M @ 0xf000 input: Power Button (FF) as /class/input/input2 ACPI: Power Button (FF) [PWRF] input: Power Button (CM) as /class/input/input3 ACPI: Power Button (CM) [PWRB] input: PS2++ Logitech Wheel Mouse as /class/input/input4 ACPI: PCI Interrupt :00:12.0[A] - Link [LNKA] - GSI 5 (level, low) - IRQ 5 firmware request failed: -2 ACPI: PCI interrupt for device
Bug#532386: marked as done (XFS on LVM2 filesystem crashses)
Your message dated Tue, 4 Jun 2013 00:29:27 +0200 with message-id 20130603222926.GC5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #512779, regarding XFS on LVM2 filesystem crashses 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.) -- 512779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15lenny3 Followup-For: Bug #512779 Yesterday we made an upgrade of our samba servers previuosl we had similar configuration but server was build on Intel Server Board and the same PERC controller. Then it was 32 bit Linux (Gentoo) and only one MD1000 array. We had similar issues.. So we upgraded system to 64bits Debian Lenny. WE also extended system with one more array. Main Filesystem is LVM2 based: storage:~# pvs PV VGFmt Attr PSize PFree /dev/sdc storage01 lvm2 a- 1.91T0 /dev/sdd storage01 lvm2 a- 1.91T0 /dev/sde storage01 lvm2 a- 1.91T0 /dev/sdf storage01 lvm2 a- 1.91T0 /dev/sdg storage01 lvm2 a- 1.91T 4.00M /dev/sdh storage01 lvm2 a- 1.91T0 storage:~# vgs VG#PV #LV #SN Attr VSize VFree storage01 6 1 0 wz--n- 11.45T 4.00M storage:~# lvdisplay --- Logical volume --- LV Name/dev/storage01/storage01logical VG Namestorage01 LV UUIDaY42UL-j0NN-8fPa-jwIZ-OH1I-QPWz-Z20jfu LV Write Accessread/write LV Status available # open 1 LV Size11.45 TB Current LE 3000699 Segments 6 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 Filesystem on it is XFS: storage:~# xfs_info /dev/mapper/storage01-storage01logical meta-data=/dev/mapper/storage01-storage01logical isize=256 agcount=97, agsize=31983584 blks = sectsz=512 attr=1 data = bsize=4096 blocks=3072715776, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 log =internal bsize=4096 blocks=32768, version=1 = sectsz=512 sunit=0 blks, lazy-count=0 realtime =none extsz=65536 blocks=0, rtextents=0 Hardware is Dell PE 1950 III with 2 PowerVault MD1000 arrays connected to Perc 5/E (30 SAS drives) VDisks configured on controller: storage:~# omreport storage vdisk controller=0 List of Virtual Disks on Controller PERC 5/E Adapter (Slot 1) Controller PERC 5/E Adapter (Slot 1) ID : 0 Status : Ok Name: Array0 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,953.12 GB (2097149902848 bytes) Device Name : /dev/sdc Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 1 Status : Ok Name: Array1 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,951.13 GB (2095006613504 bytes) Device Name : /dev/sdd Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 2 Status : Ok Name: Array2 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,953.12 GB (2097151737856 bytes) Device Name : /dev/sde Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 3 Status : Ok Name: Array3 State : Ready Progress: Not Applicable Layout : RAID-5 Size: 1,953.12 GB (2097151737856 bytes) Device Name : /dev/sdf Type: SAS Read Policy : Adaptive Read Ahead Write Policy: Write Back Cache Policy: Not Applicable Stripe Element Size : 64 KB Disk Cache Policy : Disabled ID : 4 Status : Ok Name
Bug#515205: marked as done (linux-image-2.6.26-1-amd64: freshly installed debian with 64-bit kernel does not boot-up correctly)
Your message dated Tue, 4 Jun 2013 00:29:54 +0200 with message-id 20130603222954.GD5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #515205, regarding linux-image-2.6.26-1-amd64: freshly installed debian with 64-bit kernel does not boot-up correctly 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.) -- 515205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: important when booting, it holds on 'Waiting for /dev to be fully populated'. CTRL+C continues boot. when started kernel without QUIET parameter, there is following in the log [9.937812] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 20 [9.937852] ACPI: PCI Interrupt :00:0e.1[B] - Link [AAZA] - GSI 20 (level, low) - IRQ 20 [9.937968] PCI: Setting latency timer of device :00:0e.1 to 64 [9.938504] parport_pc 00:09: driver attached [ 10.350261] ACPI: PCI Interrupt Link [APC8] enabled at IRQ 16 [ 10.350261] ACPI: PCI Interrupt :04:01.0[A] - Link [APC8] - GSI 16 (level, low) - IRQ 16 [ 48.888355] Adding 12586916k swap on /dev/sdb3. Priority:-1 extents:1 across:12586916k [ 49.270818] EXT3 FS on sdb1, internal journal as it is visible, booting holds at 10th second. cheers. -- 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/sdb1 ro ** Tainted: P (1) ** Kernel log: [5.730388] sd 1:0:0:0: [sdb] Attached SCSI disk [6.348530] hda: Optiarc DVD RW AD-7203A, ATAPI CD/DVD-ROM drive [7.133026] hdb: HL-DT-STDVD-RAM GSA-H55L, ATAPI CD/DVD-ROM drive [7.188476] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [7.188752] hda: UDMA/66 mode selected [7.192934] hdb: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [7.192934] hdb: UDMA/66 mode selected [7.192934] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [7.388906] hda: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 974kB Cache [7.388906] Uniform CD-ROM driver Revision: 3.20 [7.396908] hdb: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache [7.489331] EXT3-fs: INFO: recovery required on readonly filesystem. [7.489331] EXT3-fs: write access will be enabled during recovery. [7.589330] kjournald starting. Commit interval 5 seconds [7.589330] EXT3-fs: recovery complete. [7.589330] EXT3-fs: mounted filesystem with ordered data mode. [8.440850] udevd version 125 started [9.068284] input: Power Button (FF) as /class/input/input4 [9.130585] ACPI: Power Button (FF) [PWRF] [9.130682] input: Power Button (CM) as /class/input/input5 [9.189948] ACPI: Power Button (CM) [PWRB] [9.395130] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x1c00 [9.395130] i2c-adapter i2c-1: nForce2 SMBus adapter at 0x1c40 [9.486076] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [9.545265] shpchp: HPC vendor_id 1033 device_id 125 ss_vid 0 ss_did 0 [9.545557] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [9.617821] usb-storage: device scan complete [9.618672] scsi 4:0:0:0: Direct-Access Generic USB SD Reader1.00 PQ: 0 ANSI: 0 [9.620416] scsi 4:0:0:1: Direct-Access Generic USB CF Reader1.01 PQ: 0 ANSI: 0 [9.622091] scsi 4:0:0:2: Direct-Access Generic USB SM Reader1.02 PQ: 0 ANSI: 0 [9.624086] scsi 4:0:0:3: Direct-Access Generic USB MS Reader1.03 PQ: 0 ANSI: 0 [9.628913] sd 4:0:0:0: [sdc] Attached SCSI removable disk [9.632466] sd 4:0:0:1: [sdd] Attached SCSI removable disk [9.635994] sd 4:0:0:2: [sde] Attached SCSI removable disk [9.640036] sd 4:0:0:3: [sdf] Attached SCSI removable disk [9.705410] input: PC Speaker as /class/input/input6 [9.730262] gameport: EMU10K1 is pci:04:01.1/gameport0, io 0xa800, speed 725kHz [9.842156] pnp: the driver 'parport_pc' has been registered [9.842156] parport_pc 00:09: reported by Plug and Play ACPI [9.842156] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [9.937812] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 20 [9.937852] ACPI: PCI Interrupt :00:0e.1[B] - Link [AAZA] - GSI 20 (level, low) - IRQ 20 [9.937968] PCI: Setting latency timer of device :00:0e.1 to 64 [9.938504] parport_pc 00:09: driver attached [ 10.350261] ACPI: PCI Interrupt Link [APC8] enabled at IRQ 16 [
Bug#515170: marked as done ([linux-image-2.6-amd64] ACPI Error (psparse-0530): Method parse/execution failed [\_TZ_.THRM._TMP])
Your message dated Tue, 4 Jun 2013 00:29:54 +0200 with message-id 20130603222954.GD5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #515170, regarding [linux-image-2.6-amd64] ACPI Error (psparse-0530): Method parse/execution failed [\_TZ_.THRM._TMP] 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.) -- 515170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6-amd64 Version: 2.6.26-13 Severity: normal --- Please enter the report below this line. --- just got this error trying to get some temperature reading from ACPI (i guess) with the kde 4.2 plasmoid - system info. thou, it seems to report the temperature correctly. here are the lines form /var/log/messages: [ 1750.952251] ACPI: EC: missing confirmations, switch off interrupt mode. [ 1751.481551] ACPI Exception (evregion-0420): AE_TIME, Returned by Handler for [EmbeddedControl] [20080321] [ 1751.481569] ACPI Error (psparse-0530): Method parse/execution failed [\_TZ_.THRM._TMP] (Node 8100bf66ca10), AE_TIME --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26-1-amd64 Debian Release: 5.0 500 unstablewww.debian-multimedia.org 500 unstablesnapshots.ekiga.net 500 unstablemirror.isoc.org.il 500 testing security.debian.org 1 experimentalmirror.isoc.org.il --- Package information. --- Depends (Version) | Installed =-+-=== linux-image-2.6.26-1-amd64| 2.6.26-13 ---End Message--- ---BeginMessage--- 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.0 / 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#513984: marked as done (linux-image-2.6.24-etchnhalf.1-amd64: PS2 keyboard doesn't work)
Your message dated Tue, 4 Jun 2013 00:29:54 +0200 with message-id 20130603222954.GD5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #513984, regarding linux-image-2.6.24-etchnhalf.1-amd64: PS2 keyboard doesn't 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.) -- 513984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.24-etchnhalf.1-amd64 Version: 2.6.24-6~etchnhalf.7 Severity: normal Hi, My PS2 keyboard doesn't work with this kernel. However, if gdm is launched, it's able to fix it somehow. I've never had this problem with any other kernel I tried, including vanilla 2.6.24 and 2.6.24.3. -- Package-specific info: ** Version: Linux version 2.6.24-etchnhalf.1-amd64 (Debian 2.6.24-6~etchnhalf.7) (da...@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Tue Dec 2 17:21:26 UTC 2008 ** Command line: root=/dev/sda2 ro ** Not tainted ** Kernel log: (see attachment) ** Loaded modules: Module Size Used by cpufreq_ondemand 13840 1 cpufreq_userspace 9860 0 cpufreq_powersave 6400 0 powernow_k818592 0 freq_table 9728 2 cpufreq_ondemand,powernow_k8 nfs 259056 0 lockd 73520 1 nfs nfs_acl 8320 1 nfs sunrpc201736 6 nfs,lockd,nfs_acl ppdev 13960 0 lp 17604 0 ac 11528 0 battery20104 0 iptable_nat12292 0 nf_nat 25900 1 iptable_nat xt_tcpudp 8064 4 ipt_LOG11008 3 nf_conntrack_ipv4 24464 4 iptable_nat iptable_filter 7808 1 ip_tables 25704 2 iptable_nat,iptable_filter ip6t_LOG 11264 2 nf_conntrack_ipv6 22864 2 xt_state7168 4 nf_conntrack 78576 5 iptable_nat,nf_nat,nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state ip6table_filter 7552 1 ip6_tables 20296 2 ip6t_LOG,ip6table_filter x_tables 24968 7 iptable_nat,xt_tcpudp,ipt_LOG,ip_tables,ip6t_LOG,xt_state,ip6_tables ipv6 287016 22 nf_conntrack_ipv6 ext3 139664 1 jbd56232 1 ext3 mbcache14208 1 ext3 sha256_generic 13440 0 aes_x86_64 30248 2 aes_generic31168 0 cbc 9216 1 blkcipher 11780 1 cbc dm_crypt 18824 1 dm_snapshot22216 0 dm_mirror 27264 0 dm_mod 68344 5 dm_crypt,dm_snapshot,dm_mirror w83627ehf 28424 0 hwmon_vid 7552 1 w83627ehf fuse 53936 2 sbp2 29196 0 loop 23044 0 snd_hda_intel 362408 0 snd_pcm_oss46880 0 snd_mixer_oss 21632 1 snd_pcm_oss snd_pcm89736 2 snd_hda_intel,snd_pcm_oss snd_timer 28936 1 snd_pcm snd66280 5 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer button 14112 0 parport_pc 34984 1 parport45068 3 ppdev,lp,parport_pc soundcore 13344 1 snd snd_page_alloc 15504 2 snd_hda_intel,snd_pcm k8temp 10624 0 evdev 17152 1 irtty_sir 13440 0 sir_dev21768 1 irtty_sir irda 198636 2 irtty_sir,sir_dev crc_ccitt 6784 1 irda pcspkr 7936 0 reiserfs 225024 2 ide_cd 44960 0 cdrom 39848 1 ide_cd sd_mod 33792 5 usbhid 35168 0 hid42048 1 usbhid amd74xx14488 0 [permanent] ahci 34820 4 generic 9860 0 [permanent] ide_core 145432 3 ide_cd,amd74xx,generic ohci1394 37172 0 forcedeth 54668 0 ata_generic13188 0 ieee1394 102360 2 sbp2,ohci1394 libata164016 2 ahci,ata_generic scsi_mod 170808 3 sbp2,sd_mod,libata ehci_hcd 39948 0 ohci_hcd 28292 0 thermal22944 0 processor 45416 2 powernow_k8,thermal fan 9992 0 ** PCI devices: 00:00.0 RAM memory [0500]: nVidia Corporation Unknown device [10de:0547] (rev
Bug#514989: marked as done (linux-image-2.6.24-etchnhalf.1-686: rmap problem)
Your message dated Tue, 4 Jun 2013 00:29:54 +0200
with message-id 20130603222954.GD5604@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #514989,
regarding linux-image-2.6.24-etchnhalf.1-686: rmap 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.)
--
514989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.24-etchnhalf.1-686
Version: 2.6.24-6~etchnhalf.7
Severity: normal
I previously send e report on a similar problem concerning
linux-image-2.6.18-6-686
Bug #457775 at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457775
I have the same problem with the new kernel linux-image-2.6.24-etchnhalf.1-686.
I don't know if the problem cames from hardware but it looks like very similar
of my previous report.
I'm unable to reproduce this bug.
-- Package-specific info:
** Version:
Linux version 2.6.24-etchnhalf.1-686 (Debian 2.6.24-6~etchnhalf.7)
(da...@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21))
#1 SMP Tue Dec 2 07:56:33 UTC 2008
** Command line:
root=/dev/sda5 ro
** Tainted: G B (160)
** Kernel log:
DS: 007b ES: 007b FS: 00d8 GS: SS: 0068
Process php-cgi (pid: 17172, ti=f5f8a000 task=f7ce6d70 task.ti=f5f8a000)
Stack: c03130f4 f48d0ea8 dfb81f40 b6fd c0166d35 f5f8bfb8 0afbf067 000b
f7cd5ef0 f5f8be64 0001 b700 f7513b6c c201d120
00010940 6311e10f 0065726f c011d6ab ffed c13f702c 0011d6d2
Call Trace:
[c0166d35] unmap_vmas+0x2e0/0x57c
[c011d6ab] enqueue_task+0x52/0x5d
[c0169c8a] exit_mmap+0x76/0xe7
[c0122b06] mmput+0x20/0x76
[c0127788] do_exit+0x1ff/0x6ab
[c0127caa] sys_exit_group+0x0/0xd
[c012f080] get_signal_to_deliver+0x428/0x455
[c011bd98] do_page_fault+0x0/0x5a8
[c010352b] do_notify_resume+0x84/0x60c
[c0257223] sock_set_timeout+0x27/0xdd
[c02be18e] _spin_lock_bh+0x8/0x18
[c0256a81] release_sock+0x12/0x8e
[c0125293] printk+0x1b/0x1f
[c011c335] do_page_fault+0x59d/0x5a8
[c011bd98] do_page_fault+0x0/0x5a8
[c0103fb2] work_notifysig+0x13/0x19
===
Code: 8b 46 40 8b 50 08 b8 43 31 31 c0 e8 0d 7c fd ff 8b 46 48 85 c0 74 14 8b
40 10 85 c0 74 0d 8b 50 2c b8 61 31 31 c0 e8 f2 7b fd ff 0f 0b eb fe 8b 53 10
89 d8 59 5b 83 e2 01 5b f7 da 83 c2 04 5e
EIP: [c016c8cc] page_remove_rmap+0xe5/0x104 SS:ESP 0068:f5f8bdcc
---[ end trace 137aa004741bfd8f ]---
Fixing recursive fault but reboot is needed!
php-cgi[17733]: segfault at f724ef7c eip 082d172d esp bfd68d10 error 7
php-cgi[17781]: segfault at f730c864 eip 082d172d esp bfd52c80 error 7
php-cgi[19824]: segfault at f724973c eip 082a8440 esp bf92f470 error 5
php-cgi[23625]: segfault at f7103738 eip 082918ac esp bfd18ea0 error 7
Bad page state in process 'kswapd0'
page:c115f7e0 flags:0x40010008 mapping: mapcount:-1 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
Pid: 205, comm: kswapd0 Tainted: G D 2.6.24-etchnhalf.1-686 #1
[c015e711] bad_page+0x64/0x8e
[c015eb73] free_hot_cold_page+0x5c/0x16c
[c015ec97] __pagevec_free+0x14/0x1a
[c0161c59] __pagevec_release_nonlru+0x44/0x4f
[c01631d8] shrink_page_list+0x46e/0x507
[c0162609] isolate_lru_pages+0x44/0x17f
[c0161c0d] __pagevec_release+0x15/0x1d
[c016336d] shrink_inactive_list+0xfc/0x30d
[c016363a] shrink_zone+0xbc/0xda
[c0163a93] kswapd+0x296/0x40a
[c013548d] autoremove_wake_function+0x0/0x35
[c01637fd] kswapd+0x0/0x40a
[c01353c6] kthread+0x38/0x5e
[c013538e] kthread+0x0/0x5e
[c0104b17] kernel_thread_helper+0x7/0x10
===
php-cgi[29550]: segfault at f7011b50 eip 082918ac esp bfa30bf0 error 7
php-cgi[5389]: segfault at f790ca50 eip 082918ac esp bf99c3a0 error 7
php-cgi[11617]: segfault at f72826bc eip 082849a7 esp bfe09840 error 5
php-cgi[13944]: segfault at f72019e0 eip 082a8440 esp bfae8c00 error 5
php-cgi[14711]: segfault at f718d2b8 eip 082918ac esp bfbde770 error 7
php-cgi[21291]: segfault at f728b460 eip 082918ac esp bfa24da0 error 7
php-cgi[23901]: segfault at f790c298 eip 082918ac esp bfcec7c0 error 7
php-cgi[424]: segfault at f73089b4 eip 082a8440 esp bfa22150 error 5
php-cgi[16093]: segfault at f721c4dc eip 082849a7 esp bf92eec0 error 5
php-cgi[19892]: segfault at f730d190 eip 082a8440 esp bf98e630 error 5
php-cgi[21128]: segfault at f728ab44 eip 082918ac esp bfe23060 error 7
php-cgi[21441]: segfault at f724ec28 eip 082849a7 esp bfbbd060 error 5
php-cgi[22750]: segfault at f7308f08 eip 082849a7 esp bfa5ec10 error 5
php-cgi[23495]: segfault at f703a38c eip 082d172d esp bfd917d0 error 7
Bug#515733: marked as done (Stuck bootlogd causes kernel crash)
Your message dated Tue, 4 Jun 2013 00:29:54 +0200 with message-id 20130603222954.GD5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #515733, regarding Stuck bootlogd causes kernel crash 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.) -- 515733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sysvinit Version: 2.86.ds1-38 Severity: normal File: /sbin/bootlogd Hi, there is problem with bootlogd under Xen domU, unless right console device is specified on kernel command line. Valid console device is tty1 for domU me and I'm not certein, this is constant behavior (no knowledge). If I create domain with xm create -c etch then logs in there and type tty, I get /dev/tty1. When I add console=tty1 to kernel params of domain config file, then bootlogd works as expected probably. In the case of no console= in kernel command line bootlogd leaves in deadlock eating up 100% VCPU and strace on it shows neverending: open(/dev/ttyS0, O_WRONLY|O_NONBLOCK|O_NOCTTY) = 3 fcntl64(3, F_GETFL) = 0x801 (flags O_WRONLY|O_NONBLOCK) fcntl64(3, F_SETFL, O_WRONLY) = 0 write(3, .\r\n, 3)= -1 EIO (Input/output error) close(3)= 0 open(/dev/ttyS0, O_WRONLY|O_NONBLOCK|O_NOCTTY) = 3 fcntl64(3, F_GETFL) = 0x801 (flags O_WRONLY|O_NONBLOCK) fcntl64(3, F_SETFL, O_WRONLY) = 0 write(3, .\r\n, 3)= -1 EIO (Input/output error) close(3)= 0 ... There is comment in the source (before write_err() function) /* * We got a write error on the real console. If its an EIO, * somebody hung up our filedescriptor, so try to re-open it. */ For some reason bootlogd suppose /dev/ttyS0 console device. Regards. -- zito -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-xen-686 Locale: LANG=C, LC_CTYPE=cs_CZ.ISO-8859-2 (charmap=ISO-8859-2) Versions of packages sysvinit depends on: ii initscripts2.86.ds1-38 Scripts for initializing and shutt ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries ii libselinux12.0.35-0.icz.2SELinux shared libraries ii libsepol1 2.0.11-0.icz.1Security Enhanced Linux policy lib ii sysv-rc2.86.ds1-38 System-V-like runlevel change mech ii sysvinit-utils 2.86.ds1-38 System-V-like utilities sysvinit recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- 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.0 / 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#512779: marked as done (linux-image-2.6.26-1-amd64: XFS internal error / xfs_force_shutdown)
Your message dated Tue, 4 Jun 2013 00:29:27 +0200 with message-id 20130603222926.GC5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #512779, regarding linux-image-2.6.26-1-amd64: XFS internal error / xfs_force_shutdown 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.) -- 512779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-12 Severity: important In the last three month I had around five crashes with my XFS filesystem # dmesg snip [7688274.093948] Filesystem dm-2: XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c. Caller 0xa01b59bb [7688274.093976] Pid: 32049, comm: rsnapshot Not tainted 2.6.26-1-amd64 #1 [7688274.093987] [7688274.093988] Call Trace: [7688274.094051] [a01b59bb] :xfs:xfs_link+0x2c1/0x2d2 [7688274.094092] [a01af9be] :xfs:xfs_trans_cancel+0x55/0xed [7688274.094130] [a01b59bb] :xfs:xfs_link+0x2c1/0x2d2 [7688274.094166] [a01b0151] :xfs:xfs_trans_unlocked_item+0x24/0x3d [7688274.094189] [802ab124] d_instantiate+0x52/0x67 [7688274.094227] [a01bea66] :xfs:xfs_vn_link+0x41/0x97 [7688274.094246] [802a201a] vfs_link+0x128/0x1c1 [7688274.094261] [802a4d9e] sys_linkat+0xe1/0x143 [7688274.094304] [8020be9a] system_call_after_swapgs+0x8a/0x8f [7688274.094326] [7688274.094334] xfs_force_shutdown(dm-2,0x8) called from line 1164 of file fs/x fs/xfs_trans.c. Return address = 0xa01af9d7 [7688274.108381] Filesystem dm-2: Corruption of in-memory data detected. Shutting down filesystem: dm-2 [7688274.108407] Please umount the filesystem, and rectify the problem(s) [7688278.316256] Filesystem dm-2: xfs_log_force: error 5 returned. /snip Filesystem setup is XFS on luks on lvm on mdraid5. Filesystem size is 600G, raid5 is around 932G -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-12) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Mon Dec 15 17:25:36 UTC 2008 ** Command line: root=/dev/hda3 ro ** Not tainted ** Kernel log: [106838.354171] Filesystem dm-2: XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c. Caller 0xa01b59e3 [106838.354191] Pid: 18252, comm: rsnapshot Not tainted 2.6.26-1-amd64 #1 [106838.354199] [106838.354199] Call Trace: [106838.354264] [a01b59e3] :xfs:xfs_link+0x2c1/0x2d2 [106838.354303] [a01af9e6] :xfs:xfs_trans_cancel+0x55/0xed [106838.354338] [a01b59e3] :xfs:xfs_link+0x2c1/0x2d2 [106838.354372] [a01b0179] :xfs:xfs_trans_unlocked_item+0x24/0x3d [106838.354392] [802ab354] d_instantiate+0x52/0x67 [106838.354429] [a01bea8e] :xfs:xfs_vn_link+0x41/0x97 [106838.354446] [802a2282] vfs_link+0x128/0x1c1 [106838.354459] [802a5006] sys_linkat+0xe1/0x143 [106838.354504] [8020beca] system_call_after_swapgs+0x8a/0x8f [106838.354523] [106838.354530] xfs_force_shutdown(dm-2,0x8) called from line 1164 of file fs/xfs/xfs_trans.c. Return address = 0xa01af9ff [106838.366481] Filesystem dm-2: Corruption of in-memory data detected. Shutting down filesystem: dm-2 [106838.366481] Please umount the filesystem, and rectify the problem(s) [106839.400243] Filesystem dm-2: xfs_log_force: error 5 returned. [106861.772015] Filesystem dm-2: xfs_log_force: error 5 returned. [106892.317648] nfsd: last server has exited [106892.317659] nfsd: unexporting all filesystems [106897.772016] Filesystem dm-2: xfs_log_force: error 5 returned. [106933.772013] Filesystem dm-2: xfs_log_force: error 5 returned. [106969.772015] Filesystem dm-2: xfs_log_force: error 5 returned. [106990.807276] Filesystem dm-2: xfs_log_force: error 5 returned. [106990.807296] Filesystem dm-2: xfs_log_force: error 5 returned. [106990.807307] xfs_force_shutdown(dm-2,0x1) called from line 420 of file fs/xfs/xfs_rw.c. Return address = 0xa01b7dab [106990.807322] Filesystem dm-2: xfs_log_force: error 5 returned. [106990.807330] Filesystem dm-2: xfs_log_force: error 5 returned. [106990.807338] xfs_force_shutdown(dm-2,0x1) called from line 420 of file fs/xfs/xfs_rw.c. Return address = 0xa01b7dab [106991.176046] Filesystem dm-2: xfs_log_force: error 5 returned. [106991.176067] Filesystem dm-2: xfs_log_force: error 5 returned. [106991.176101] Filesystem dm-2: xfs_log_force: error 5 returned. [106991.176110] Filesystem dm-2: xfs_log_force: error 5 returned.
Bug#515009: marked as done (linux-image-2.6.26-1-686: call trace without error - system load at 10)
Your message dated Tue, 4 Jun 2013 00:29:54 +0200 with message-id 20130603222954.GD5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #515009, regarding linux-image-2.6.26-1-686: call trace without error - system load at 10 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.) -- 515009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-13 Severity: normal [resending via thunderbird because reportbug would not send via my smtp server] I encountered the following when closing Totem: the window closed succesfully, but the commandline would not return to bash. I could not background it with C-Z, and could not kill it with C-C. In the kernel log I can find a number of backtraces but no BUG: or deadlock messages are given. The dmesg output below is incomplete, I will attach some output from /var/log/messages later. totem output: ** (totem:4575): DEBUG: Init of Python module ** (totem:4575): DEBUG: Registering Python plugin instance: YouTube+TotemPythonPlugin ** (totem:4575): DEBUG: Creating object of type YouTube+TotemPythonPlugin ** (totem:4575): DEBUG: Creating Python plugin instance ** (totem:4575): DEBUG: Finalizing Python plugin instance E: thread-posix.c: Assertion 'pthread_setspecific(t-key, userdata) == 0' failed at pulsecore/thread-posix.c:194, function pa_tls_set(). Aborting. top cpu line: Cpu(s): 6.6%us, 84.8%sy, 8.6%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st aschuring@neminis:~$ ps awux | grep totem 1000 4575 50.4 10.1 195824 79016 pts/5DNl+ 16:06 38:15 totem 1000 5128 0.0 0.0 3616 720 pts/4SN+ 17:21 0:00 grep totem aschuring@neminis:~$ uptime 17:23:29 up 1:49, 6 users, load average: 10.16, 10.35, 10.07 Even though the system load appears at 10 and the processor is 0% idle, there are no ill effects noticable: even Quodlibet is still playing audio through the Pulseaudio sound server, and the system is only slightly less responsive. The kernel is still spamming syslog with call traces, though. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (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 18:29:31 UTC 2009 ** Command line: root=UUID=6388def3-b3cd-4785-88c3-6b1ffbed6a9b ro irqpoll selinux=1 quiet splash ** Not tainted ** Kernel log: [ 6254.549262]7fff 7fff cb781e70 0002 c02b84f1 df042248 0001 c011fd4c [ 6254.549268] Call Trace: [ 6254.549281] [c01190e6] hrtick_start_fair+0xeb/0x12c [ 6254.549289] [c02b84f1] schedule_timeout+0x13/0x86 [ 6254.549295] [c011fd4c] check_preempt_wakeup+0xa2/0xc2 [ 6254.549302] [c011b679] try_to_wake_up+0xe8/0xf1 [ 6254.549312] [c02b7c15] wait_for_common+0xaf/0x10f [ 6254.549318] [c011b682] default_wake_function+0x0/0x8 [ 6254.549327] [c0123c52] exit_mm+0x60/0xd1 [ 6254.549334] [c0124ff2] do_exit+0x1e5/0x5c9 [ 6254.549344] [c012543a] do_group_exit+0x64/0x8d [ 6254.549351] [c012c69b] get_signal_to_deliver+0x30d/0x32d [ 6254.549363] [c0102fc6] do_notify_resume+0x7e/0x649 [ 6254.549371] [c013b673] do_futex+0x68/0x6ff [ 6254.549386] [f090042f] ide_timer_expiry+0x26a/0x27f [ide_core] [ 6254.549402] [c0139472] tick_dev_program_event+0x1e/0x82 [ 6254.549417] [c013bddb] sys_futex+0xd1/0xe6 [ 6254.549430] [c01039a8] work_notifysig+0x13/0x1b [ 6254.549448] === [ 6254.549451] INFO: task totem:4589 blocked for more than 120 seconds. [ 6254.549454] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 6254.549456] totem D c2344a23 0 4589 4532 [ 6254.549460]cc1cd960 0086 002f72c6 c2344a23 03b1 cc1cdaec c160bfa0 [ 6254.549466] 0445 0023239a 003d0163 c01190e6 cc1cd960 [ 6254.549472]7fff 7fff cc1cfe70 0002 c02b84f1 cc1cd988 0001 c011fd4c [ 6254.549478] Call Trace: [ 6254.549491] [c01190e6] hrtick_start_fair+0xeb/0x12c [ 6254.549499] [c02b84f1] schedule_timeout+0x13/0x86 [ 6254.549505] [c011fd4c] check_preempt_wakeup+0xa2/0xc2 [ 6254.549512] [c011b679] try_to_wake_up+0xe8/0xf1 [ 6254.549521] [c02b7c15] wait_for_common+0xaf/0x10f [ 6254.549528] [c011b682] default_wake_function+0x0/0x8 [ 6254.549537] [c0123c52] exit_mm+0x60/0xd1 [ 6254.549544] [c0124ff2] do_exit+0x1e5/0x5c9 [ 6254.549554] [c012543a] do_group_exit+0x64/0x8d [ 6254.549561] [c012c69b] get_signal_to_deliver+0x30d/0x32d [ 6254.549571] [c01158b4]
Bug#532561: marked as done (nfs problem?)
Your message dated Tue, 4 Jun 2013 00:29:54 +0200 with message-id 20130603222954.GD5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #516376, regarding nfs 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.) -- 516376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15lenny3 I am doing a stress test of my HA fileserver based upon Lenny on 2 hosts. It uses drbd (protocol C), nfs-kernel-server and heartbeat. The exported partition is formatted in XFS. /etc/exports is /data 172.22.96.0/23(rw,async,no_root_squash,no_subtree_check) /var/lib/nfs is on a cluster file system shared between both hosts, too. /etc/init.d/nfs-kernel-server had to be patched to make sure the nfs daemons terminate (see http://bugs.debian.org/532276). During the test I run on host1 while true; do \ /etc/init.d/heartbeat stop; \ sleep 120; \ /etc/init.d/heartbeat start; \ sleep 120; \ ssh host2 /etc/init.d/heartbeat stop; \ sleep 120; \ ssh host2 /etc/init.d/heartbeat start; \ sleep 120; \ done The NFS partition was mounted on a Linux client (Opensuse). On this host I ran cd /mnt for i in $(seq -w 0 99); do \ date; \ mkdir -p $i; \ pushd $i; \ tar xpf /var/tmp/linux-2.6.29.4.tar.bz2; \ popd; \ done sync date Of course both loops were running in parallel. Host1 showed after some time: [ 8083.250212] [ cut here ] [ 8083.273156] kernel BUG at include/linux/module.h:386! [ 8083.293976] invalid opcode: [1] SMP [ 8083.293976] CPU 1 [ 8083.293976] Modules linked in: nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc xfs sha256_generic drbd cn battery bonding loop snd_pcm snd_timer snd soundcore snd_page_alloc psmouse serio_raw pcspkr k8temp i2c_piix4 i2c_core shpchp button pci_hotplug joydev evdev reiserfs usbhid hid ff_memless raid10 usb_storage raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear md_mod ide_pci_generic sd_mod serverworks ide_core ehci_hcd ohci_hcd ata_generic sata_svw libata scsi_mod e1000 dock thermal processor fan thermal_sys [ 8083.477886] Pid: 11547, comm: mount Not tainted 2.6.26-2-amd64 #1 [ 8083.477886] RIP: 0010:[802ae91d] [802ae91d] get_filesystem+0x16/0x32 [ 8083.477886] RSP: 0018:81005247bd08 EFLAGS: 00010246 [ 8083.477886] RAX: RBX: a032cd00 RCX: a032c810 [ 8083.477886] RDX: 1000 RSI: a0319168 RDI: a032cd00 [ 8083.477886] RBP: 81007e899800 R08: 81007e899a68 R09: 81005247bc58 [ 8083.477886] R10: 8100748ed000 R11: 802f1fa2 R12: [ 8083.477886] R13: a032c7e0 R14: R15: 8029c130 [ 8083.477886] FS: 7ffeefcf87c0() GS:81007fb799c0() knlGS: [ 8083.477886] CS: 0010 DS: ES: CR0: 8005003b [ 8083.477886] CR2: 0071c000 CR3: 7e0c4000 CR4: 06e0 [ 8083.477886] DR0: DR1: DR2: [ 8083.477886] DR3: DR6: 0ff0 DR7: 0400 [ 8083.477886] Process mount (pid: 11547, threadinfo 81005247a000, task 81007f11cb50) [ 8083.477886] Stack: 81007e899800 8029c6d3 8029cff2 81007e15a780 [ 8083.477886] a031276a [ 8083.477886] 81007e15a780 8029d2a0 81007e15a780 81007e15a780 [ 8083.477886] Call Trace: [ 8083.477886] [8029c6d3] ? sget+0x37b/0x38a [ 8083.477886] [8029cff2] ? set_anon_super+0x0/0xa3 [ 8083.477886] [a031276a] ? :sunrpc:rpc_fill_super+0x0/0x9b [ 8083.477886] [8029d2a0] ? get_sb_single+0x2f/0xb3 [ 8083.477886] [8029cbb8] ? vfs_kern_mount+0x93/0x11b [ 8083.477886] [8029cc93] ? do_kern_mount+0x43/0xdc [ 8083.477886] [802b16a5] ? do_new_mount+0x5b/0x95 [ 8083.477886] [802b189c] ? do_mount+0x1bd/0x1e7 [ 8083.477886] [80276894] ? __alloc_pages_internal+0xd6/0x3bf [ 8083.477886] [802b1950] ? sys_mount+0x8a/0xce [ 8083.477886] [8020beca] ? system_call_after_swapgs+0x8a/0x8f [ 8083.477886] [ 8083.477886] [ 8083.477886] Code: 8a
Bug#517017: marked as done (linux-image-2.6.26-1-powerpc: kernel oops on reading from HFS plus filesystem)
Your message dated Tue, 4 Jun 2013 00:29:54 +0200 with message-id 20130603222954.GD5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #517017, regarding linux-image-2.6.26-1-powerpc: kernel oops on reading from HFS plus filesystem 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.) -- 517017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-powerpc Version: 2.6.26-13 Severity: normal I had mounted a journaled HFS plus filesystem read-only to access a single file on that filesystem. The only file i was accessing at all was an 80G disk image stored at /Users/xxx/Desktop/laptop.dmg. no other hfsplus filesystems were mounted. In fact, the only non-tmpfs filesystem in use was a vfat filesystem. I was running photorec on the laptop.dmg file to try to recover data from it, when i got the kernel oops below. --dkg -- Package-specific info: ** Version: Linux version 2.6.26-1-powerpc (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 Sat Jan 10 14:00:38 CET 2009 ** Command line: root=/dev/ram ro ramdisk_size=7000 ** Tainted: G D (128) ** Kernel log: [ 263.225298] usb 4-2: Manufacturer: USB [ 263.234473] usb 4-2: SerialNumber: XZ187S087WMGK8IG [ 263.285729] usb-storage: device found at 2 [ 263.285738] usb-storage: waiting for device to settle before scanning [ 263.789714] hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache [ 263.799193] Uniform CD-ROM driver Revision: 3.20 [ 263.895416] PowerMac i2c bus pmu 2 registered [ 263.904572] PowerMac i2c bus pmu 1 registered [ 263.913502] PowerMac i2c bus mac-io 0 registered [ 263.922371] PowerMac i2c bus uni-n 1 registered [ 263.931152] PowerMac i2c bus uni-n 0 registered [ 264.645907] ieee1394: Host added: ID:BUS[0-00:1023] GUID[000d93fffe346eba] [ 264.884913] b43-phy0: Broadcom 4306 WLAN found [ 264.982274] phy0: Selected rate control algorithm 'pid' [ 265.529072] Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ] [ 265.561573] snd-aoa-fabric-layout: found bus with layout 51 [ 265.570172] snd-aoa-fabric-layout: Using direct GPIOs [ 265.594474] snd-aoa-codec-tas: found 'deq' node [ 265.594512] snd-aoa-fabric-layout: can use this codec [ 265.672897] snd-aoa-codec-tas: tas found, addr 0x35 on /pci@f200/mac-io@17/i2c@18000/deq@6a [ 268.263068] device-mapper: uevent: version 1.0.3 [ 268.272791] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-de...@redhat.com [ 268.293782] usb-storage: device scan complete [ 268.294832] scsi 1:0:0:0: Direct-Access USB DISK 2.0 1219 PQ: 0 ANSI: 0 CCS [ 268.639061] Driver 'sd' needs updating - please use bus_type methods [ 268.665639] sd 1:0:0:0: [sda] 1957888 512-byte hardware sectors (1002 MB) [ 268.674967] sd 1:0:0:0: [sda] Write Protect is off [ 268.683191] sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 268.683196] sd 1:0:0:0: [sda] Assuming drive cache: write through [ 268.721810] sd 1:0:0:0: [sda] 1957888 512-byte hardware sectors (1002 MB) [ 268.741738] sd 1:0:0:0: [sda] Write Protect is off [ 268.750258] sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 268.750262] sd 1:0:0:0: [sda] Assuming drive cache: write through [ 268.758731] sda: [mac] sda1 sda2 sda3 [ 268.775102] sd 1:0:0:0: [sda] Attached SCSI removable disk [ 587.801824] ieee1394: Error parsing configrom for node 0-00:1023 [ 587.809815] ieee1394: Node changed: 0-00:1023 - 0-01:1023 [ 604.334145] ieee1394: Node added: ID:BUS[0-00:1023] GUID[00d04b00e550] [ 604.515561] scsi2 : SBP-2 IEEE-1394 [ 605.528565] ieee1394: sbp2: Logged into SBP-2 device [ 605.537136] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048] [ 605.548466] scsi 2:0:0:0: Direct-Access-RBC IC35L060 AVER07-0 ER6O PQ: 0 ANSI: 4 [ 605.593723] sd 2:0:0:0: [sdb] 120103200 512-byte hardware sectors (61493 MB) [ 605.613742] sd 2:0:0:0: [sdb] Write Protect is off [ 605.62] sd 2:0:0:0: [sdb] Mode Sense: 11 00 00 00 [ 605.634084] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 605.643655] sd 2:0:0:0: [sdb] 120103200 512-byte hardware sectors (61493 MB) [ 605.665714] sd 2:0:0:0: [sdb] Write Protect is off [ 605.674342] sd 2:0:0:0: [sdb] Mode Sense: 11 00 00 00 [ 605.686083] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 605.694909] sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 [ 605.740840] sd
Bug#538000: marked as done (NFS bug in stable kernel)
Your message dated Tue, 4 Jun 2013 00:29:54 +0200 with message-id 20130603222954.GD5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #516376, regarding NFS bug in stable kernel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 516376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Version: 2.6.26-17 I just upgraded my nas-box with new disks, and took the time to migrate the OS from Etch to Lenny. This morning I was rebuilding and testing NFS exports. When I completed this task, I ran exportfs -a to activate all the NFS shares. I got a very strange error message, which seems to be related to a kernel bug. More strange : I got this message only for the first export. I couldn't reproduce it later... Jul 22 12:44:19 nas kernel: [72230.403919] nfsd: last server has exited Jul 22 12:44:19 nas kernel: [72230.403919] nfsd: unexporting all filesystems Jul 22 12:44:20 nas kernel: [72231.548528] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Jul 22 12:44:20 nas kernel: [72231.548597] NFSD: starting 90-second grace period Jul 22 12:44:26 nas kernel: [72238.061697] [ cut here ] Jul 22 12:44:26 nas kernel: [72238.061726] kernel BUG at include/linux/module.h:386! Jul 22 12:44:26 nas kernel: [72238.061749] invalid opcode: [#1] SMP Jul 22 12:44:26 nas kernel: [72238.061775] Modules linked in: xfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs ipv6 dm_mod loop parport_pc parport snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr psmouse serio_raw button i2c_i801 i2c_core iTCO_wdt rng_core edac_core shpchp pci_hotplug intel_agp agpgart evdev ext3 jbd mbcache sd_mod i2o_core ide_cd_mod cdrom piix ide_pci_generic ide_core floppy ata_generic dpt_i2o skge e1000 libata scsi_mod dock ehci_hcd uhci_hcd usbcore thermal processor fan thermal_sys Jul 22 12:44:26 nas kernel: [72238.062094] Jul 22 12:44:26 nas kernel: [72238.062110] Pid: 3614, comm: nfsd Not tainted (2.6.26-2-686 #1) Jul 22 12:44:26 nas kernel: [72238.062134] EIP: 0060:[f8bc8489] EFLAGS: 00010246 CPU: 0 Jul 22 12:44:26 nas kernel: [72238.062188] EIP is at svc_recv+0x38f/0x64e [sunrpc] Jul 22 12:44:26 nas kernel: [72238.062209] EAX: EBX: f8bdbd40 ECX: f8bdbd40 EDX: 0100 Jul 22 12:44:26 nas kernel: [72238.062232] ESI: f7886400 EDI: f6b45f9c EBP: c4014000 ESP: f6b45f8c Jul 22 12:44:26 nas kernel: [72238.062255] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 Jul 22 12:44:26 nas kernel: [72238.062277] Process nfsd (pid: 3614, ti=f6b44000 task=f7a1b980 task.ti=f6b44000) Jul 22 12:44:26 nas kernel: [72238.062301] Stack: 000dbba0 f7a8b600 f7a13d00 f7daa840 f7a1b980 c011b6ce 00100100 Jul 22 12:44:26 nas kernel: [72238.062364]00200200 f783a8c0 f8bfaa8f c4014000 f8be1691 feff Jul 22 12:44:26 nas kernel: [72238.062426]fef8 f8be15bb c01044f3 c4014000 Jul 22 12:44:26 nas kernel: [72238.062487] Call Trace: Jul 22 12:44:26 nas kernel: [72238.062520] [c011b6ce] default_wake_function+0x0/0x8 Jul 22 12:44:26 nas kernel: [72238.062554] [f8be1691] nfsd+0xd6/0x269 [nfsd] Jul 22 12:44:26 nas kernel: [72238.062598] [f8be15bb] nfsd+0x0/0x269 [nfsd] Jul 22 12:44:26 nas kernel: [72238.062638] [c01044f3] kernel_thread_helper+0x7/0x10 Jul 22 12:44:26 nas kernel: [72238.062669] === Jul 22 12:44:26 nas kernel: [72238.062687] Code: 01 00 00 8b 44 24 04 8b 50 04 ff 52 04 85 c0 89 c6 0f 84 25 01 00 00 8b 00 8b 58 04 85 db 74 1f 89 d8 e8 b2 49 57 c7 85 c0 75 04 0f 0b eb fe 64 a1 04 40 3b c0 c1 e0 05 ff 84 18 00 01 00 00 8b Jul 22 12:44:26 nas kernel: [72238.062954] EIP: [f8bc8489] svc_recv+0x38f/0x64e [sunrpc] SS:ESP 0068:f6b45f8c Jul 22 12:44:26 nas kernel: [72238.063351] ---[ end trace 0bbcb6ca27fbf387 ]--- ---End Message--- ---BeginMessage--- 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.0 / 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#522046: marked as done (Crash in DomU when running java)
Your message dated Tue, 4 Jun 2013 00:30:38 +0200 with message-id 20130603223038.GE5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #522046, regarding Crash in DomU when running java 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.) -- 522046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-xen-686 Version: 2.6.26-13lenny2 When I am running with this kernel as a 32-bit Lenny DomU on a 64-bit CentOS 5.2 Dom0, the DomU crashes whenever I try anything intensive with Java. I have tried openjdk-6 and sun-java6, both exhibit the same issue, for instance when performing a dpkg-reconfigure - crash messages below. If I boot using an older kernel, e.g. one from Etch (linux-image-2.6.18-6-xen-686, 2.6.18.dfsg.1-23), this doesn't happen. un linux-image none (no description available) un linux-image-2.6 none (no description available) ii linux-image-2.6-xen-686 2.6.26+17 Linux 2.6 image on i686, oldstyle Xen support ii linux-image-2.6.18-6-xen-686 2.6.18.dfsg.1-23 Linux 2.6.18 image on i686 ii linux-image-2.6.26-1-xen-686 2.6.26-13 Linux 2.6.26 image on i686, oldstyle Xen support By DomU configuration looks like : bootloader='/usr/bin/pygrub' memory = '1024' root= '/dev/xvda ro' disk= [ 'phy:mapper/java-dev-1-root,xvda,w', 'phy:xenimages/java-dev-1-swap,xvdb,w' ] name= 'java-dev-1' vif = [ 'bridge=xenbr0,mac=00:16:3e:5a:95:18' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash= 'restart' The following is an example of the error messages that appear on the DomU console, these can be triggered on-demand by issuing a dpkg-reconfigure sun-java6-bin for instance. [ 549.636440] [ cut here ] [ 549.636452] kernel BUG at arch/x86/mm/hypervisor.c:75! [ 549.636456] invalid opcode: [#1] SMP [ 549.636460] Modules linked in: ipv6 nfs lockd nfs_acl sunrpc dm_snapshot dm_mirror dm_log dm_mod ext3 jbd mbcache thermal_sys [ 549.636477] [ 549.636480] Pid: 2029, comm: java Not tainted (2.6.26-1-xen-686 #1) [ 549.636484] EIP: 0061:[c0112fb1] EFLAGS: 00010282 CPU: 0 [ 549.636491] EIP is at xen_l3_entry_update+0x8d/0x98 [ 549.636494] EAX: ffea EBX: ed7b7ea0 ECX: 0001 EDX: [ 549.636498] ESI: 7ff0 EDI: 0002 EBP: 8002 ESP: ed7b7e98 [ 549.636502] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0069 [ 549.636506] Process java (pid: 2029, ti=ed7b6000 task=ecb7c4a0 task.ti=ed7b6000) [ 549.636510] Stack: fcb08001 0002 d6ec3008 0001 fcb08001 0002 0002 fcb08001 [ 549.636520]0002 c0111863 ec9fd008 ecf6d3c0 2ca35001 ecf6d3c0 eca35000 ec9fd008 [ 549.636531]ecf6d3c0 c015a221 ec9fd008 ecf6d3f8 0001 c015e34d ecf17ea8 7b88 [ 549.636542] Call Trace: [ 549.636546] [c0111863] pud_populate+0x19d/0x233 [ 549.636552] [c015a221] __pmd_alloc+0x56/0x7b [ 549.636558] [c015e34d] handle_mm_fault+0x5c/0xd46 [ 549.636562] [c01610d7] vma_link+0x4a/0xe7 [ 549.636568] [c0161853] mmap_region+0x2dc/0x392 [ 549.636573] [c010ea38] do_page_fault+0x5fe/0xb26 [ 549.636578] [c0161c27] do_mmap_pgoff+0x243/0x296 [ 549.636583] [c01072f6] sys_mmap2+0x62/0xa0 [ 549.636589] [c010e43a] do_page_fault+0x0/0xb26 [ 549.636594] [c02cbd15] error_code+0x35/0x3c [ 549.636601] === [ 549.636603] Code: 01 00 00 00 89 44 24 0c 8b 04 24 8d 5c 24 08 89 74 24 08 be f0 7f 00 00 89 54 24 14 31 d2 89 44 24 10 e8 73 e0 fe ff 85 c0 79 04 0f 0b eb fe 83 c4 18 5b 5e 5f c3 56 b9 01 00 00 00 53 31 d2 83 [ 549.636655] EIP: [c0112fb1] xen_l3_entry_update+0x8d/0x98 SS:ESP 0069:ed7b7e98 [ 549.63] ---[ end trace 98118b7494d3275c ]--- kernel:[ 549.636506] Process java (pid: 2029, ti=ed7b6000 task=ecb7c4a0 task.ti=ed7b6000) [ 614.181654] BUG: soft lockup - CPU#0 stuck for 61s! [java:2028] [ 614.181654] Modules linked in: ipv6 nfs lockd nfs_acl sunrpc dm_snapshot dm_mirror dm_log dm_mod ext3 jbd mbcache thermal_sys [ 614.181654] [ 614.181654] Pid: 2028, comm: java Tainted: G D (2.6.26-1-xen-686 #1) [ 614.181654] EIP: 0061:[c01013a7] EFLAGS: 0246 CPU: 0 [ 614.181654] EIP is at 0xc01013a7 [ 614.181654] EAX: EBX: 0003 ECX: ecb77ea8 EDX: 00372f12 [ 614.181654] ESI: 0103 EDI: ecb77eb8 EBP: ecf6d408 ESP: ecb77ea4 [ 614.181654] DS: 007b ES: 007b FS: 00d8 GS: SS: 0069 [ 614.181654] CR0: 8005003b CR2: bfce1fec CR3: 0132f000 CR4: 2620 [
Bug#517122: marked as done (linux-2.6: very slow access/open/... syscalls on NFS mounted files)
Your message dated Tue, 4 Jun 2013 00:30:38 +0200
with message-id 20130603223038.GE5604@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #517122,
regarding linux-2.6: very slow access/open/... syscalls on NFS mounted files
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.)
--
517122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libc6
Version: 2.7-18
Severity: normal
I am sorry if I should have originally filed it against kernel but I am not
sure if it is actually an NFS client issue.. It seems to be not nfs server
issue either since other clients of the same server perform fine. It shouldn't
be issue bonded interface on this box, since other nodes in the cluster with
bonded interfaces perform fine.
2 days ago I upgraded our cluster from etch to lenny.
Yesterday I've mentioned (it could be that it wasn't that slow before) that it
takes too long to start bash/zsh. strace showed that syscalls dealing with NFS
mounted files:
13:10:46.301746 access(/home/yoh/.zsh/sourcedir, F_OK) = 0 0.019635
whenever on other nodes it takes just 0.0001 or so
I've done obvious checks of nfsstat and netstat -- no obvious reasons for
slow-down.
Here is an excerpt from my notes in tiddlywiki. I would appreciate any hints on
what else to look at, since nfs client traffic seems to be going quite fast,
but there is significant delays between transactions, which probably what boils
down to slow syscalls.
examples from main node
{{{
strace -fF -o /tmp/zsh2.strace -T -ttt zsh-beta
1235583796.011574 access(/home/yoh/.zshenv, F_OK) = 0 0.023661
1235583796.035416 munmap(0x7fd834c96000, 2100856) = 0 0.53
1235583796.035562 stat(/home/yoh/.zshenv.zwc, 0x7fff3e262f00) = -1 ENOENT (No
such file or directory) 0.009246
}}}
has corresponding tcpdump:
{{{
tcpdump -i bond0 -tt -vvv -n (dst host raider or src host raider) -s 192 |
/tmp/zsh-beta.tcpdump
1235583796.020630 IP (tos 0x0, ttl 64, id 43841, offset 0, flags [DF], proto
TCP (6), length 224) 10.0.0.1.514335490 10.0.0.252.2049: 172 access [|nfs]
1235583796.020777 IP (tos 0x0, ttl 64, id 46892, offset 0, flags [DF], proto
TCP (6), length 176) 10.0.0.252.2049 10.0.0.1.514335490: reply ok 124 access
attr: DIR 40755 ids 47521/47522 sz 16384 nlink 221 rdev 0/0 fsid
7d6310991d5a808d fileid 51855823 a/m/ctime 1235582942.843330957
1235583781.787331514 1235583781.787331514 c 001f
1235583796.020857 IP (tos 0x0, ttl 64, id 43842, offset 0, flags [DF], proto
TCP (6), length 232) 10.0.0.1.531112706 10.0.0.252.2049: 180 lookup [|nfs]
1235583796.021001 IP (tos 0x0, ttl 64, id 46893, offset 0, flags [DF], proto
TCP (6), length 292) 10.0.0.252.2049 10.0.0.1.531112706: reply ok 240 lookup
fh Unknown/010006013CC4464909BF4398B1441C5490AF20E507AF8051ED1A0001 LNK
120777 ids 47521/47522 sz 16 [|nfs]
1235583796.025559 IP (tos 0x0, ttl 64, id 43843, offset 0, flags [DF], proto
TCP (6), length 228) 10.0.0.1.547889922 10.0.0.252.2049: 176 lookup [|nfs]
1235583796.025709 IP (tos 0x0, ttl 64, id 46894, offset 0, flags [DF], proto
TCP (6), length 292) 10.0.0.252.2049 10.0.0.1.547889922: reply ok 240 lookup
fh Unknown/010006013CC4464909BF4398B1441C5490AF20E513906E780701 DIR
40700 ids 47521/47522 sz 90 [|nfs]
1235583796.030339 IP (tos 0x0, ttl 64, id 43844, offset 0, flags [DF], proto
TCP (6), length 224) 10.0.0.1.564667138 10.0.0.252.2049: 172 access [|nfs]
1235583796.030489 IP (tos 0x0, ttl 64, id 46895, offset 0, flags [DF], proto
TCP (6), length 176) 10.0.0.252.2049 10.0.0.1.564667138: reply ok 124 access
attr: DIR 40700 ids 47521/47522 sz 90 nlink 10 rdev 0/0 fsid 7d6310991d5a808d
fileid 786e9013 a/m/ctime 1231731824.355110521 1231737665.659793897
1231737665.659793897 c 001f
1235583796.035048 IP (tos 0x0, ttl 64, id 43845, offset 0, flags [DF], proto
TCP (6), length 224) 10.0.0.1.581444354 10.0.0.252.2049: 172 access [|nfs]
1235583796.035191 IP (tos 0x0, ttl 64, id 46896, offset 0, flags [DF], proto
TCP (6), length 176) 10.0.0.252.2049 10.0.0.1.581444354: reply ok 124 access
attr: DIR 40775 ids 47521/47522 sz 66 nlink 6 rdev 0/0 fsid 7d6310991d5a808d
fileid 18005733 a/m/ctime 1218207520.461796280 1218207523.890125418
1218207523.890125418 c 001f
1235583796.044623 IP (tos 0x0, ttl 64, id 43846, offset 0, flags [DF], proto
TCP (6), length 236) 10.0.0.1.598221570 10.0.0.252.2049: 184 lookup [|nfs]
1235583796.044773 IP (tos 0x0, ttl 64, id 46897, offset 0, flags [DF], proto
TCP (6), length 172) 10.0.0.252.2049 10.0.0.1.598221570: reply ok
Bug#519348: marked as done (kernel bug in nfs on powerpc)
Your message dated Tue, 4 Jun 2013 00:29:54 +0200 with message-id 20130603222954.GD5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #516376, regarding kernel bug in nfs on powerpc 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.) -- 516376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: linux-image-2.6.26-1-vserver-powerpc version: 2.6.26-13 Hi, suddenly the nfs exports on one server running lenny stopped working here, the only thing I could found was in dmesg: Linux fubar 2.6.26-1-vserver-powerpc #1 SMP Sat Jan 10 15:01:56 CET 2009 ppc GNU/Linux [1221442.454304] kernel BUG at include/linux/module.h:386! [1221442.454384] Oops: Exception in kernel mode, sig: 5 [#1] [1221442.454457] SMP NR_CPUS=4 PowerMac [1221442.454522] Modules linked in: ip6table_filter ip6_tables iptable_raw xt_comment xt_policy ipt_ULOG ipt_TTL ipt_ttl ipt_REJECT ipt_REDIRECT ipt_recent ipt_NETMAP ipt_MASQUERADE ipt_LOG ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG xt_MARK xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_mangle nfnetlink xt_multiport lp parport nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc iptable_filter ip_tables x_tables sbp2 scsi_mod loop snd_aoa_i2sbus snd_pcm snd_timer snd_page_alloc snd soundcore snd_aoa_soundbus usblp uninorth_agp agpgart evdev ext3 jbd mbcache ide_disk ohci1394 sungem sungem_phy ieee1394 ns83820 i2c_powermac [1221442.456665] NIP: f6491188 LR: f6491180 CTR: [1221442.456741] REGS: c0c33ec0 TRAP: 0700 Not tainted (2.6.26-1-vserver-powerpc) [1221442.456848] MSR: 00029032 EE,ME,IR,DR CR: 84000488 XER: [1221442.456995] TASK = ef8e90f0[4431,#0] 'nfsd' THREAD: c0c32000 CPU: 0 [1221442.457074] GPR00: c0c33f70 ef8e90f0 0001 c0c33ee0 ee8c4658 [1221442.457264] GPR08: ee8c4644 c0073ce4 1001a71c 100e 100df49c [1221442.457455] GPR16: 10002118 bfd1fa18 10002134 10012724 0008 0801 c0c4e000 [1221442.457646] GPR24: 0001 000dbba0 ee1163a0 ee9d1ba0 ee8c4600 f64a6b40 efb3b000 ee258600 [1221442.457854] NIP [f6491188] svc_recv+0x400/0x7c4 [sunrpc] [1221442.458123] LR [f6491180] svc_recv+0x3f8/0x7c4 [sunrpc] [1221442.458293] Call Trace: [1221442.458341] [c0c33f70] [f6491160] svc_recv+0x3d8/0x7c4 [sunrpc] (unreliable) [1221442.458556] [c0c33fc0] [f6550a84] nfsd+0xc0/0x30c [nfsd] [1221442.458724] [c0c33ff0] [c0013af4] kernel_thread+0x44/0x60 [1221442.458831] Instruction dump: [1221442.458906] 7d2903a6 4e800421 7c7c1b79 41820184 813c 83a90004 2f9d 419e003c [1221442.459114] 7fa3eb78 48001045 7c630034 5463d97e 0f03 54290024 81290008 55292834 [1221442.466384] ---[ end trace 70d66edf5224f9a3 ]--- ii linux-image-2.6-vserver-powerpc 2.6.26+17 Linux 2.6 image on uniprocessor 32-bit PowerPC, Linux-VServer su ii linux-image-2.6.26-1-vserver-powerpc2.6.26-13 Linux 2.6.26 image on uniprocessor 32-bit PowerPC, Linux-VServer ii nfs-common 1:1.1.2-6lenny1 NFS support files common to client and server ii nfs-kernel-server 1:1.1.2-6lenny1 support for NFS kernel server processor : 0 cpu : 7400, altivec supported temperature : 27-32 C (uncalibrated) clock : 466.65MHz revision: 2.9 (pvr 000c 0209) bogomips: 66.30 total bogomips : 66.30 timebase: 33290001 platform: PowerMac model : PowerMac3,4 machine : PowerMac3,4 motherboard : PowerMac3,4 MacRISC2 MacRISC Power Macintosh detected as : 69 (PowerMac G4 Silver) pmac flags : 0010 L2 cache: 1024K unified pmac-generation : NewWorld regards, Holger signature.asc Description: This is a digitally signed message part. ---End Message---
Bug#516376: marked as done (kernel BUG at include/linux/module.h:386! | nfsd crash)
Your message dated Tue, 4 Jun 2013 00:29:54 +0200 with message-id 20130603222954.GD5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #516376, regarding kernel BUG at include/linux/module.h:386! | nfsd crash 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.) -- 516376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 After 35 days uptime nfsd died. System runs with deadline elevator and echo 1 /sys/devices/system/edac/pci/check_pci_errors echo 1 /sys/devices/system/cpu/sched_mc_power_savings cpufreq uses ondemand governor I tried to restart nfs-kernel-server, nfs-common and portmap to see if nfs clients reconnect back but without any success. After few rmmod/modprobe attempts I gave up and rebooted server. I will try to get more info if nfsd dies again. dmesg output: Feb 20 23:46:23 atlas kernel: [3371974.871167] [ cut here ] Feb 20 23:46:23 atlas kernel: [3371974.871167] kernel BUG at include/linux/module.h:386! Feb 20 23:46:23 atlas kernel: [3371974.871167] invalid opcode: [1] SMP Feb 20 23:46:23 atlas kernel: [3371974.871167] CPU 0 Feb 20 23:46:23 atlas kernel: [3371974.871167] Modules linked in: xts gf128mul acpi_cpufreq cpufreq_ondemand cpufreq_conservative cpufreq_userspace cpufreq_powersave cpufreq_stats freq_table nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc ipv6 ext2 serio_raw iTCO_wdt snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr psmouse i2c_i801 rng_core i2c_core i3000_edac button ipmi_msghandler edac_core evdev ext3 jbd mbcache sha256_generic aes_x86_64 aes_generic cbc dm_crypt dm_mod crypto_blkcipher raid1 raid0 md_mod ide_cd_mod cdrom ide_pci_generic sd_mod piix ide_core usbhid hid ff_memless floppy ata_generic ahci ehci_hcd libata scsi_mod dock uhci_hcd e1000e thermal processor fan thermal_sys [last unloaded: vmnet] Feb 20 23:46:23 atlas kernel: [3371974.871167] Pid: 7778, comm: nfsd Not tainted 2.6.26-1-amd64 #1 Feb 20 23:46:23 atlas kernel: [3371974.871167] RIP: 0010:[a02afce2] [a02afce2] :sunrpc:svc_recv+0x421/0x743 Feb 20 23:46:23 atlas kernel: [3371974.871167] RSP: 0018:810114dd3e90 EFLAGS: 00010246 Feb 20 23:46:23 atlas kernel: [3371974.871167] RAX: RBX: a02c7b80 RCX: Feb 20 23:46:23 atlas kernel: [3371974.871167] RDX: 1000 RSI: 810114dd3db0 RDI: a02c7b80 Feb 20 23:46:23 atlas kernel: [3371974.871167] RBP: 81011bdac000 R08: 81011e5b1480 R09: Feb 20 23:46:23 atlas kernel: [3371974.871167] R10: 8100010268f0 R11: 803fe4cf R12: 81011d2e2e00 Feb 20 23:46:23 atlas kernel: [3371974.871167] R13: 810114dd3ea0 R14: 8100b519b400 R15: 81011cd689c0 Feb 20 23:46:23 atlas kernel: [3371974.871167] FS: 7f714a45e6e0() GS:8053c000() knlGS: Feb 20 23:46:23 atlas kernel: [3371974.871167] CS: 0010 DS: ES: CR0: 8005003b Feb 20 23:46:23 atlas kernel: [3371974.871167] CR2: 7facc2a1 CR3: 00011df26000 CR4: 06e0 Feb 20 23:46:23 atlas kernel: [3371974.871167] DR0: DR1: DR2: Feb 20 23:46:23 atlas kernel: [3371974.871167] DR3: DR6: 0ff0 DR7: 0400 Feb 20 23:46:23 atlas kernel: [3371974.871167] Process nfsd (pid: 7778, threadinfo 810114dd2000, task 81011d214580) Feb 20 23:46:23 atlas kernel: [3371974.871167] Stack: 81011cd02018 000dbba0 81011d214580 Feb 20 23:46:23 atlas kernel: [3371974.871167] 8022c202 00100100 00200200 80429c74 Feb 20 23:46:23 atlas kernel: [3371974.871167] 0110 0001 81011bdac000 a032d67c Feb 20 23:46:23 atlas kernel: [3371974.871167] Call Trace: Feb 20 23:46:23 atlas kernel: [3371974.871167] [8022c202] ? default_wake_function+0x0/0xe Feb 20 23:46:23 atlas kernel: [3371974.871167] [80429c74] ? __down_read+0x12/0xa1 Feb 20 23:46:23 atlas kernel: [3371974.871167] [a032d67c] ? :nfsd:nfsd+0x0/0x2a4 Feb 20 23:46:23 atlas kernel: [3371974.871167] [a032d767] ? :nfsd:nfsd+0xeb/0x2a4 Feb 20 23:46:23 atlas kernel: [3371974.871167] [80230196] ? schedule_tail+0x27/0x5c Feb 20 23:46:23 atlas kernel: [3371974.871167] [8020cf28] ? child_rip+0xa/0x12 Feb 20 23:46:23 atlas kernel: [3371974.871167] [a032d67c] ? :nfsd:nfsd+0x0/0x2a4
Bug#528422: marked as done (linux-image-2.6.26-2-amd64: repeated warning scheduling from the idle thread)
Your message dated Tue, 4 Jun 2013 00:30:38 +0200 with message-id 20130603223038.GE5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #528422, regarding linux-image-2.6.26-2-amd64: repeated warning scheduling from the idle thread 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.) -- 528422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6-amd64 Version: 2.6.26+17+lenny1 Linux 2.6.26-2-amd64 #1 SMP Fri Mar 27 04:02:59 UTC 2009 x86_64 GNU/Linux # cat syslog OR # cat kern.log will show: May 12 11:43:39 drako kernel: [ 1257.684686] bad: scheduling from the idle thread! May 12 11:43:39 drako kernel: [ 1257.684694] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1 May 12 11:43:39 drako kernel: [ 1257.684698] May 12 11:43:39 drako kernel: [ 1257.684700] Call Trace: May 12 11:43:39 drako kernel: [ 1257.684710] [80230783] dequeue_task_idle+0x29/0x34 May 12 11:43:39 drako kernel: [ 1257.684721] [8022810a] dequeue_task+0x13/0x1e May 12 11:43:39 drako kernel: [ 1257.684731] [8022813b] deactivate_task+0x26/0x43 May 12 11:43:39 drako kernel: [ 1257.684743] [80427b69] schedule+0x14a/0x635 May 12 11:43:39 drako kernel: [ 1257.684752] [8024d246] clockevents_notify+0x24/0x6d May 12 11:43:39 drako kernel: [ 1257.684769] [803a9ad1] cpuidle_idle_call+0x0/0xaf May 12 11:43:39 drako kernel: [ 1257.684782] [8020ac9e] cpu_idle+0xae/0xb3 May 12 11:43:39 drako kernel: [ 1257.684810] May 12 11:43:39 drako kernel: [ 1257.776962] bad: scheduling from the idle thread! May 12 11:43:39 drako kernel: [ 1257.776962] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1 May 12 11:43:39 drako kernel: [ 1257.776962] May 12 11:43:39 drako kernel: [ 1257.776962] Call Trace: May 12 11:43:39 drako kernel: [ 1257.776962] [8024e153] tick_dev_program_event+0x29/0x9b May 12 11:43:39 drako kernel: [ 1257.776962] [80230783] dequeue_task_idle+0x29/0x34 May 12 11:43:39 drako kernel: [ 1257.776962] [8022810a] dequeue_task+0x13/0x1e May 12 11:43:39 drako kernel: [ 1257.776962] [8022813b] deactivate_task+0x26/0x43 May 12 11:43:39 drako kernel: [ 1257.776962] [80427b69] schedule+0x14a/0x635 May 12 11:43:39 drako kernel: [ 1257.776962] [80248b8e] hrtimer_start+0x112/0x134 May 12 11:43:39 drako kernel: [ 1257.776962] [803a9ad1] cpuidle_idle_call+0x0/0xaf May 12 11:43:39 drako kernel: [ 1257.776962] [8020ac9e] cpu_idle+0xae/0xb3 ... and on and on. Syslog is more than 400MB and kern.log is more than 500MB. This is in about 3h of laptop usage. The system is a Dell Latitude D630. I am using Debian Squeeze with kernel 2.6.26-2-amd64. After a long time on, when I try to open a file from the Internet, Iceweasel says there is not enough room in tmp to store the file. I can see regular activity in the hard drive, in the system monitor, which I'm sure is log writing. Thank you, António ---End Message--- ---BeginMessage--- 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.0 / 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#516705: marked as done (linux-image-2.6.26-1-686: tulip_stop_rxtx() failed, problem tulip -- dmfe)
Your message dated Tue, 4 Jun 2013 00:30:38 +0200 with message-id 20130603223038.GE5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #516705, regarding linux-image-2.6.26-1-686: tulip_stop_rxtx() failed, problem tulip -- dmfe 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.) -- 516705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-13 Severity: normal Hi, after I upgraded one of my DSL gateways from Debian Etch to Lenny one of the network cards did not work properly any longer, syslog was reporting this constantly (roughly every 3 seconds) ... :02:0b.0: tulip_stop_rxtx() failed (CSR5 0xfc74 CSR6 0x20422c2) and the network on this network card was down. Both modules - dmfe and tulip - were loaded by the system automatically. After manually removing both and loading just dmfe the network card worked again as expected. kind regards, Joerg. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (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 18:29:31 UTC 2009 ** Command line: root=/dev/hda2 ro ** Not tainted ** Loaded modules: Module Size Used by dmfe 16536 0 act_police 4676 1 cls_u32 6116 1 sch_ingress 2144 1 cls_fw 3840 4 sch_htb13248 1 ipt_MASQUERADE 2592 2 ipt_LOG 5028 2 xt_limit2180 3 xt_length 1760 2 xt_MARK 2304 12 xt_multiport2816 6 xt_state2016 3 iptable_mangle 2688 1 iptable_nat 4680 1 nf_nat 15576 2 ipt_MASQUERADE,iptable_nat nf_conntrack_ipv4 12268 6 iptable_nat,nf_nat nf_conntrack 55508 5 ipt_MASQUERADE,xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4 xt_TCPMSS 3616 0 xt_tcpmss 1984 0 xt_tcpudp 2816 10 iptable_filter 2624 1 ip_tables 10160 3 iptable_mangle,iptable_nat,iptable_filter x_tables 13284 12 ipt_MASQUERADE,ipt_LOG,xt_limit,xt_length,xt_MARK,xt_multiport,xt_state,iptable_nat,xt_TCPMSS,xt_tcpmss,xt_tcpudp,ip_tables ppp_deflate 4224 0 zlib_deflate 17624 1 ppp_deflate zlib_inflate 14144 1 ppp_deflate bsd_comp4864 0 nfsd 186704 17 auth_rpcgss33952 1 nfsd exportfs3904 1 nfsd nfs 213896 0 lockd 54248 2 nfsd,nfs nfs_acl 2912 2 nfsd,nfs sunrpc162144 13 nfsd,auth_rpcgss,nfs,lockd,nfs_acl ppp_async 7488 1 crc_ccitt 2080 1 ppp_async ppp_generic20028 7 ppp_deflate,bsd_comp,ppp_async slhc5408 1 ppp_generic ipv6 235300 28 dm_snapshot14340 0 dm_mirror 15104 0 dm_log 8452 1 dm_mirror dm_mod 46184 3 dm_snapshot,dm_mirror,dm_log asb100 14996 0 hwmon_vid 2720 1 asb100 ide_generic 2464 0 [permanent] evdev 8000 0 snd_cmipci 28992 0 gameport 10700 1 snd_cmipci snd_opl3_lib9344 1 snd_cmipci snd_hwdep 6212 1 snd_opl3_lib snd_mpu401_uart 6368 1 snd_cmipci snd_rawmidi18496 1 snd_mpu401_uart snd_seq_device 6380 2 snd_opl3_lib,snd_rawmidi parport_pc 22500 0 parport30988 1 parport_pc snd_pcsp8576 0 snd_pcm62596 2 snd_cmipci,snd_pcsp snd_timer 17800 2 snd_opl3_lib,snd_pcm snd45604 9 snd_cmipci,snd_opl3_lib,snd_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device,snd_pcsp,snd_pcm,snd_timer soundcore 6368 1 snd snd_page_alloc 7816 1 snd_pcm i2c_i8017920 0 i2c_core 19828 2 asb100,i2c_i801 iTCO_wdt9508 0 shpchp 25528 0 pci_hotplug23460 1 shpchp rng_core3940 0 intel_agp 22332 1 agpgart28776 1 intel_agp ext3 105512 1 jbd39444 1 ext3 mbcache 7108 1 ext3 ide_cd_mod 27652 0 cdrom 30176 1
Bug#577211: marked as done (linux-image-2.6.32-3-686: intermittent spiking iowait)
Your message dated Tue, 4 Jun 2013 00:30:38 +0200 with message-id 20130603223038.GE5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #516815, regarding linux-image-2.6.32-3-686: intermittent spiking iowait 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.) -- 516815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-9 Severity: normal Tags: sid This is the configuration: root on a raid 1 on top of an lvm consisting of two PVs (two 1TB Western digital hdds). This is what I'm experiencing: While mounted, the system suddenly will become unresponsive / freeze for a period of up to 20-30 seconds. Running iostat on a 10 second interval revealed iowait percentages up to 99% over a 30 second period (max). Looking at iotop output I could see the following at the top of the list during the spikes:430 be/4 root0.00 B/s0.00 B/s 0.00 % 99.99 % [kjournald] -- Package-specific info: ** Version: Linux version 2.6.32-3-686 (Debian 2.6.32-9) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Thu Feb 25 06:14:20 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-3-686 root=/dev/mapper/vg01-lv01 ro quiet ** Tainted: P (1) * Proprietary module has been loaded. ** Kernel log: [ 4812.706236] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 4812.707163] SGI XFS Quota Management subsystem [ 4812.729103] JFS: nTxBlock = 8192, nTxLock = 65536 [ 4812.793628] NTFS driver 2.1.29 [Flags: R/W MODULE]. [ 4812.16] QNX4 filesystem 0.2.3 registered. ** Model information not available ** Loaded modules: Module Size Used by ufs56150 0 qnx45118 0 hfsplus61001 0 hfs33093 0 minix 17814 0 ntfs 163909 0 vfat6538 0 msdos 5118 0 fat34908 2 vfat,msdos jfs 134642 0 xfs 415456 0 exportfs2618 1 xfs reiserfs 176200 0 ext2 46289 0 ppdev 4058 0 lp 5570 0 sco 5837 2 bridge 32983 0 stp 996 1 bridge bnep7444 2 rfcomm 25131 4 l2cap 21677 16 bnep,rfcomm vboxnetadp 5154 0 vboxnetflt 10202 0 vboxdrv 114837 2 vboxnetadp,vboxnetflt nls_utf8 908 0 cifs 234274 0 fuse 43750 1 loop9753 0 firewire_sbp2 9639 0 ext4 254909 1 jbd2 56059 1 ext4 crc16 1027 2 l2cap,ext4 snd_hda_codec_realtek 163098 1 snd_hda_intel 16427 5 btusb 7997 2 snd_hda_codec 46002 2 snd_hda_codec_realtek,snd_hda_intel bluetooth 36327 9 sco,bnep,rfcomm,l2cap,btusb rfkill 10260 2 bluetooth ipaq 14628 0 snd_hwdep 4054 1 snd_hda_codec snd_pcm_oss28671 0 snd_mixer_oss 10461 1 snd_pcm_oss snd_pcm47362 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi3576 0 usbserial 21843 1 ipaq snd_rawmidi12505 1 snd_seq_midi snd_seq_midi_event 3684 1 snd_seq_midi snd_seq35459 2 snd_seq_midi,snd_seq_midi_event i2c_nforce2 4464 0 joydev 6771 0 asus_atk01106770 0 pcspkr 1207 0 evdev 5609 10 snd_timer 12258 3 snd_pcm,snd_seq parport_pc 15799 1 snd_seq_device 3673 3 snd_seq_midi,snd_rawmidi,snd_seq parport22554 3 ppdev,lp,parport_pc snd34363 19 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 3450 1 snd psmouse44413 0 serio_raw 2916 0 processor 26571 2 snd_page_alloc 5041 2 snd_hda_intel,snd_pcm ext3 94192 1 jbd32161 1 ext3 mbcache 3762 3 ext2,ext4,ext3 dm_mod 46074 7 raid1 16099 1 md_mod 67165 2
Bug#516815: marked as done (linux-image-2.6.26-1-686: iowait spikes after lenny upgrade, pdflush kjournald use 99% io on xfs filesystem])
Your message dated Tue, 4 Jun 2013 00:30:38 +0200 with message-id 20130603223038.GE5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #516815, regarding linux-image-2.6.26-1-686: iowait spikes after lenny upgrade, pdflush kjournald use 99% io on xfs filesystem] 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.) -- 516815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-13 Severity: important System was upgraded from etch to lenny. pdflush and kjournald take 99% of IO, iostat shows increasing IO wait % whenever disk is accessed /dev/sda10 is xfs formatted, running from a Dell perc raid. http://forums.debian.net/viewtopic.php?t=35993 http://people.binf.ku.dk/~hanne/b2evolution/blogs/index.php?blog=5title=tuning-vm-on-24-core-128-gb-ram-machinedisp=singlemore=1c=1tb=1pb=1 -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (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 18:29:31 UTC 2009 ** Command line: root=/dev/sda5 ro ** Not tainted ** Kernel log: [5.076337] usb usb1: Manufacturer: Linux 2.6.26-1-686 ohci_hcd [5.076337] usb usb1: SerialNumber: :00:0f.2 [5.132337] tg3.c:v3.92.1 (June 9, 2008) [5.132337] ACPI: PCI Interrupt :03:06.0[A] - GSI 28 (level, low) - IRQ 28 [5.132337] ACPI: PCI Interrupt :04:08.1[A] - GSI 30 (level, low) - IRQ 30 [5.174534] eth0: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:133MHz:64-bit) 10/100/1000Base-T Ethernet 00:0d:56:bb:bf:6a [5.174646] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1] [5.174646] eth0: dma_rwctrl[769c4000] dma_mask[64-bit] [5.175803] AAC0: kernel 2.8-1[6098] [5.174646] ACPI: PCI Interrupt :03:08.0[A] - GSI 29 (level, low) - IRQ 29 [5.176007] AAC0: monitor 2.8-1[6098] [5.176074] AAC0: bios 2.8-1[6098] [5.176140] AAC0: serial ABC881D3 [5.174647] scsi0 : percraid [5.174647] scsi 0:0:0:0: Direct-Access DELL PERC RAID5 V1.0 PQ: 0 ANSI: 2 [5.174647] scsi 0:0:1:0: Direct-Access DELL BACKUP_DRIVE V1.0 PQ: 0 ANSI: 2 [5.194427] scsi 0:1:0:0: Direct-Access MAXTOR ATLAS15K_73SCA DT60 PQ: 0 ANSI: 3 [5.195766] scsi 0:1:1:0: Direct-Access MAXTOR ATLAS15K_73SCA DT60 PQ: 0 ANSI: 3 [5.198427] scsi 0:1:2:0: Direct-Access MAXTOR ATLAS15K_73SCA DT60 PQ: 0 ANSI: 3 [5.198427] scsi 0:1:3:0: Direct-Access MAXTOR ATLAS15K_73SCA DT60 PQ: 0 ANSI: 3 [5.202453] scsi 0:1:4:0: Direct-Access SEAGATE ST3146807LC DS09 PQ: 0 ANSI: 3 [5.221224] eth1: Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:133MHz:64-bit) 10/100/1000Base-T Ethernet 00:0d:56:bb:bf:6c [5.221322] eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1] [5.221407] eth1: dma_rwctrl[769c4000] dma_mask[64-bit] [5.242956] hda: ATAPI 24X CD-ROM drive, 128kB Cache [5.243167] Uniform CD-ROM driver Revision: 3.20 [5.420020] scsi 0:1:6:0: Processor PE/PV1x5 SCSI BP 1.1 PQ: 0 ANSI: 2 [ 13.669945] Driver 'sd' needs updating - please use bus_type methods [ 13.669945] sd 0:0:0:0: [sda] 430071552 512-byte hardware sectors (220197 MB) [ 13.669945] sd 0:0:0:0: [sda] Write Protect is off [ 13.669945] sd 0:0:0:0: [sda] Mode Sense: 06 00 00 00 [ 13.669945] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 13.670151] sd 0:0:0:0: [sda] 430071552 512-byte hardware sectors (220197 MB) [ 13.670302] sd 0:0:0:0: [sda] Write Protect is off [ 13.670382] sd 0:0:0:0: [sda] Mode Sense: 06 00 00 00 [ 13.670929] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 13.671034] sda: sda1 sda2 sda3 sda5 sda6 sda7 sda8 sda9 sda10 [ 13.707323] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 13.707630] sd 0:0:1:0: [sdb] 286716544 512-byte hardware sectors (146799 MB) [ 13.707774] sd 0:0:1:0: [sdb] Write Protect is off [ 13.707848] sd 0:0:1:0: [sdb] Mode Sense: 06 00 00 00 [ 13.707939] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 13.708129] sd 0:0:1:0: [sdb] 286716544 512-byte hardware sectors (146799 MB) [ 13.708129] sd 0:0:1:0: [sdb] Write Protect is off [ 13.708129] sd 0:0:1:0: [sdb] Mode Sense: 06 00 00 00 [ 13.708129] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled,
Bug#528173: marked as done (linux-image-2.6.26-2-686: using xorg do not honour SWCursor (is ok with 2.6.18))
Your message dated Tue, 4 Jun 2013 00:30:38 +0200 with message-id 20130603223038.GE5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #528173, regarding linux-image-2.6.26-2-686: using xorg do not honour SWCursor (is ok with 2.6.18) 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.) -- 528173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Version: 2.6.26-15 Severity: normal Updating to lenny xorg stopped to work. rienstalling it it changed is autodetection from vesa to openchrome drivers (this coukd be acceptable, since these are specific for that chipset) but on the other part it stopped working, since cursor handling is incorrect, leaving tail and resetting to background image on passing on a non-focused window. I added SW cursor but unable to let it work. booting with 2.6.18 from etch it WORKS OK, both with openchrome and with vesa, either with or without swcursor. video board is: 01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890CE/K8N890CE [Chrome 9] (rev 11) -- Package-specific info: -- System Information: Debian Release: 5.0.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-5-686 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-686 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-2-686 recommends: ii libc6-i6862.7-18 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-2-686 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none(no description available) -- debconf information excluded ---End Message--- ---BeginMessage--- 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.0 / 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#530026: marked as done (usb 2.0 hdd copy error)
Your message dated Tue, 4 Jun 2013 00:30:38 +0200 with message-id 20130603223038.GE5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #530026, regarding usb 2.0 hdd copy error 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.) -- 530026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Subject: usb 2.0 hdd copy error Package: linux-image-2.6.26-1-686 Version: 2.6.26-13 Severity: normal *** Please type your report below this line *** I have problems using a 640GB USB 2.0 mass storage device store alu from Toshiba with lenny (kernel 2.6.26-1-686). The device was formated with vfat. When I tried to copy files from it this lead to an error. As saving very large files is not possible with vfat and I needed this feature, i formated the harddisk with an ntfs partition. But the copy problem did not go away. When I try to copy larger files (happend for instance with something more than 4MB) the cpu gets busy, copying does not proceed at some point, the device can not be unmounted. The only way to stop this was putting the power of the usb device off. Dmesg reported the following: [ 564.502023] usb 5-1: new high speed USB device using ehci_hcd and address 2 [ 564.637216] usb 5-1: configuration #1 chosen from 1 choice [ 564.648994] usb 5-1: New USB device found, idVendor=0930, idProduct=0b09 [ 564.649031] usb 5-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 564.649038] usb 5-1: Product: USB 3.5-HDD [ 564.649043] usb 5-1: Manufacturer: TOSHIBA [ 564.649048] usb 5-1: SerialNumber: 0013F007 [ 564.823762] Initializing USB Mass Storage driver... [ 564.824985] scsi0 : SCSI emulation for USB Mass Storage devices [ 564.826309] usbcore: registered new interface driver usb-storage [ 564.826700] USB Mass Storage support registered. [ 564.873554] usb-storage: device found at 2 [ 564.873935] usb-storage: waiting for device to settle before scanning [ 569.874337] usb-storage: device scan complete [ 569.880322] scsi 0:0:0:0: Direct-Access TOSHIBA USB 3.5-HDD 100 PQ: 0 ANSI: 2 [ 569.999406] Driver 'sd' needs updating - please use bus_type methods [ 570.001079] sd 0:0:0:0: [sda] 1250263728 512-byte hardware sectors (640135 MB) [ 570.004128] sd 0:0:0:0: [sda] Write Protect is off [ 570.004518] sd 0:0:0:0: [sda] Mode Sense: 38 00 00 00 [ 570.004747] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 570.007424] sd 0:0:0:0: [sda] 1250263728 512-byte hardware sectors (640135 MB) [ 570.009798] sd 0:0:0:0: [sda] Write Protect is off [ 570.009814] sd 0:0:0:0: [sda] Mode Sense: 38 00 00 00 [ 570.009821] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 570.009832] sda: sda1 [ 570.023425] sd 0:0:0:0: [sda] Attached SCSI disk [ 609.623029] usb 5-1: reset high speed USB device using ehci_hcd and address 2 [ 639.848043] usb 5-1: reset high speed USB device using ehci_hcd and address 2 [ 670.073064] usb 5-1: reset high speed USB device using ehci_hcd and address 2 [ 700.298030] usb 5-1: reset high speed USB device using ehci_hcd and address 2 [ 730.523065] usb 5-1: reset high speed USB device using ehci_hcd and address 2 [ 760.748057] usb 5-1: reset high speed USB device using ehci_hcd and address 2 [ 760.871027] sd 0:0:0:0: [sda] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK,SUGGEST_OK [ 760.871027] end_request: I/O error, dev sda, sector 443815 [ 760.871027] Buffer I/O error on device sda1, logical block 55469 [ 760.872442] Buffer I/O error on device sda1, logical block 55470 [ 760.872456] Buffer I/O error on device sda1, logical block 55471 [ 760.872465] Buffer I/O error on device sda1, logical block 55472 [ 760.872473] Buffer I/O error on device sda1, logical block 55473 [ 760.872481] Buffer I/O error on device sda1, logical block 55474 [ 760.872489] Buffer I/O error on device sda1, logical block 55475 [ 760.872497] Buffer I/O error on device sda1, logical block 55476 [ 760.872505] Buffer I/O error on device sda1, logical block 55477 [ 760.872513] Buffer I/O error on device sda1, logical block 55478 [ 790.974073] usb 5-1: reset high speed USB device using ehci_hcd and address 2 [ 821.199034] usb 5-1: reset high speed USB device using ehci_hcd and address 2 This error also occured using Ubuntu 8.10 and an older Kanotix. For detailed information from Lenny I compiled a kernel with usb and usb mass storage debugging enabled. In addition I removed some unused drivers from the kernel configuration. Dmesg reported the following when I put the
Processed: found 655511 in 3.2.41-2+deb7u2
Processing commands for cont...@bugs.debian.org: found 655511 3.2.41-2+deb7u2 Bug #655511 [src:linux] Endianness issues with Nvidia card second port (NV43) on PowerPC (quad G5, PCIe) Marked as found in versions linux/3.2.41-2+deb7u2. thanks Stopping processing here. Please contact me if you need assistance. -- 655511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655511 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.13702990595962.transcr...@bugs.debian.org
Bug#517936: marked as done (nfs-kernel-server: kernel BUG at include/linux/module.h:386! (starting nfs))
Your message dated Tue, 4 Jun 2013 00:29:54 +0200 with message-id 20130603222954.GD5604@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #516376, regarding nfs-kernel-server: kernel BUG at include/linux/module.h:386! (starting nfs) 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.) -- 516376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-kernel-server Version: 1:1.1.2-6lenny1 Severity: critical Justification: breaks the whole system I have two machines set up to do DRBD, providing an NFS share started and stopped by heartbeat. Similar to these configurations: http://www.linuxjournal.com/article/9074 http://www.linux-ha.org/DRBD/NFS Occasionally when starting NFS during a fail-over during active I/O, the kernel bugs as follows and RPC/NFS become completely unresponsive until hard reboot using reset or power cycle: [378605.477866] [ cut here ] [378605.477866] kernel BUG at include/linux/module.h:386! [378605.477866] invalid opcode: [#1] SMP [378605.477866] Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs xfs drbd cn ipv6 loop snd_pcm snd_timer snd soundcore parport_pc snd_page_alloc parport i2c_i801 i2c_core iTCO_wdt pcspkr intel_rng rng_core button edac_core intel_agp agpgart shpchp pci_hotplug evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sg sd_mod sr_mod cdrom ata_piix ata_generic libata scsi_mod dock usbhid hid ff_memless floppy ide_pci_generic ide_core e1000 ehci_hcd uhci_hcd usbcore thermal processor fan thermal_sys [378605.477866] [378605.477866] Pid: 8108, comm: mount Not tainted (2.6.26-1-686 #1) [378605.477866] EIP: 0060:[c0185d7e] EFLAGS: 00010246 CPU: 0 [378605.477866] EIP is at get_filesystem+0x13/0x29 [378605.477866] EAX: EBX: f9720bc0 ECX: f9720bc0 EDX: 0100 [378605.477866] ESI: f796dc00 EDI: EBP: f9720900 ESP: f6881e78 [378605.477866] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [378605.477866] Process mount (pid: 8108, ti=f688 task=f770ca80 task.ti=f688) [378605.477866] Stack: f796dc00 c0175a07 c01761c2 c017557b f794b300 f9720900 [378605.477866]c0176404 f794b300 f970b376 f794b300 f9720900 fff4 [378605.477866]c0175e2d f970b376 f794b300 f680b000 f680b000 ffed f9720900 [378605.477866] Call Trace: [378605.477866] [c0175a07] sget+0x2c2/0x2cb [378605.477866] [c01761c2] set_anon_super+0x0/0x93 [378605.477866] [c017557b] compare_single+0x0/0x6 [378605.477866] [c0176404] get_sb_single+0x2b/0x97 [378605.477866] [f970b376] rpc_fill_super+0x0/0x85 [sunrpc] [378605.477866] [c0175e2d] vfs_kern_mount+0x7b/0xed [378605.477866] [f970b376] rpc_fill_super+0x0/0x85 [sunrpc] [378605.477866] [c0175edd] do_kern_mount+0x2f/0xb4 [378605.477866] [c01882ce] do_new_mount+0x55/0x89 [378605.477866] [c01884a9] do_mount+0x1a7/0x1c6 [378605.477866] [c01864bb] copy_mount_options+0x26/0x109 [378605.477866] [c0188535] sys_mount+0x6d/0xa8 [378605.477866] [c0103853] sysenter_past_esp+0x78/0xb1 [378605.477866] === [378605.477866] Code: 85 c0 75 f8 f0 ff 05 e0 66 35 c0 eb 05 bb ea ff ff ff 89 d8 5b 5e 5f c3 53 8b 58 10 85 db 74 1f 89 d8 e8 35 70 fb ff 85 c0 75 04 0f 0b eb fe 64 a1 04 40 3b c0 c1 e0 05 ff 84 18 00 01 00 00 5b [378605.477866] EIP: [c0185d7e] get_filesystem+0x13/0x29 SS:ESP 0068:f6881e78 [378605.478686] ---[ end trace d5c6d15c9b5c0034 ]--- -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- 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.0 / 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#695968: linux-image-3.2.0-4-amd64: ath.ko starts printing thousands of error messages several minutes after boot
A patch has been posted to linux-wireless which accomplishes the workaround of disabling wireless power saving (ie. iw dev wlan0 set power_save off) by disabling power saving in the ath9k driver itself. http://marc.info/?l=linux-wirelessm=137005085710866w=2 I applied it to Debian's 3.2.41 kernel and verified that power saving is indeed disabled (after disabling my on-boot shell script which accomplished the same thing of course): root@debian:~# iw dev wlan0 get power_save Power save: off -- 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/1370301187.11426.3.camel@debian
Bug#517122: closed by Moritz Mühlenhoff j...@inutil.org (Closing)
RIP my lovely bug report On Mon, 03 Jun 2013, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the linux-2.6 package: #517122: linux-2.6: very slow access/open/... syscalls on NFS mounted files It has been closed by Moritz Mühlenhoff j...@inutil.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Moritz Mühlenhoff j...@inutil.org by replying to this email. -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20130604000818.gt10...@onerussian.com
Bug#517122: very slow access/open/... syscalls on NFS mounted files
Yaroslav Halchenko wrote: RIP my lovely bug report It had a good run of four years. ;-) Can you reproduce the absurdly slow NFS access times on some machine with a more recent kernel? Thanks, Jonathan -- 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/20130604010555.gf28...@google.com
Bug#709647: linux-source-3.2: USB 1.1 no longer works
On Fri, May 31, 2013 at 02:50:11AM +0100, Ben Hutchings wrote: Now I see this is a rather old computer (BIOS dated 1999), so I'm not so surprised that ACPI is not supported! Does the kernel in linux-image-3.2.0-4-486 work? Can you send a boot log and output of 'lspci -s :01.2' from a working kernel (old or new)? lspci -s :01.2: 00:01.2 USB controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) linux-image-3.2.0-4-486 no difference (no USB) linux-3.1.1 and linux-3.9.4 (from kernel.org) no difference (no USB) Compilation of linux-2.6.3[89] failed, error (for ...39): arch/x86/kernel/e820.c: In function 'e820_setup_gap': arch/x86/kernel/e820.c:640:6: warning: variable 'found' set but not used [-Wunused-but-set-variable] arch/x86/kernel/ptrace.c:1366:17: error: conflicting types for 'syscall_trace_enter' In file included from /home/bg/src/linux-2.6.39/arch/x86/include/asm/vm86.h:130:0, from /home/bg/src/linux-2.6.39/arch/x86/include/asm/processor.h:10, from /home/bg/src/linux-2.6.39/arch/x86/include/asm/thread_info.h:22, from include/linux/thread_info.h:53, from include/linux/preempt.h:9, from include/linux/spinlock.h:50, from include/linux/seqlock.h:29, from include/linux/time.h:8, from include/linux/timex.h:56, from include/linux/sched.h:57, from arch/x86/kernel/ptrace.c:8: /home/bg/src/linux-2.6.39/arch/x86/include/asm/ptrace.h:146:13: note: previous declaration of 'syscall_trace_enter' was here arch/x86/kernel/ptrace.c:1411:17: error: conflicting types for 'syscall_trace_leave' In file included from /home/bg/src/linux-2.6.39/arch/x86/include/asm/vm86.h:130:0, from /home/bg/src/linux-2.6.39/arch/x86/include/asm/processor.h:10, from /home/bg/src/linux-2.6.39/arch/x86/include/asm/thread_info.h:22, from include/linux/thread_info.h:53, from include/linux/preempt.h:9, from include/linux/spinlock.h:50, from include/linux/seqlock.h:29, from include/linux/time.h:8, from include/linux/timex.h:56, from include/linux/sched.h:57, from arch/x86/kernel/ptrace.c:8: /home/bg/src/linux-2.6.39/arch/x86/include/asm/ptrace.h:147:13: note: previous declaration of 'syscall_trace_leave' was here make[2]: *** [arch/x86/kernel/ptrace.o] Error 1 make[1]: *** [arch/x86/kernel] Error 2 make: *** [arch/x86] Error 2 --- Boot log (/var/log/kern.log) (with USB): Jun 3 02:21:21 jeti kernel: imklog 5.8.11, log source = /proc/kmsg started. Jun 3 02:21:21 jeti kernel: [0.00] Linux version 2.6.32-47 (2.6.32) (b...@jeti.jeti.is) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 Thu Feb 14 00:07:19 GMT 2013 Jun 3 02:21:21 jeti kernel: [0.00] KERNEL supported cpus: Jun 3 02:21:21 jeti kernel: [0.00] Intel GenuineIntel Jun 3 02:21:21 jeti kernel: [0.00] AMD AuthenticAMD Jun 3 02:21:21 jeti kernel: [0.00] NSC Geode by NSC Jun 3 02:21:21 jeti kernel: [0.00] Cyrix CyrixInstead Jun 3 02:21:21 jeti kernel: [0.00] Centaur CentaurHauls Jun 3 02:21:21 jeti kernel: [0.00] Transmeta GenuineTMx86 Jun 3 02:21:21 jeti kernel: [0.00] Transmeta TransmetaCPU Jun 3 02:21:21 jeti kernel: [0.00] UMC UMC UMC UMC Jun 3 02:21:21 jeti kernel: [0.00] BIOS-provided physical RAM map: Jun 3 02:21:21 jeti kernel: [0.00] BIOS-e801: - 0009f000 (usable) Jun 3 02:21:21 jeti kernel: [0.00] BIOS-e801: 0010 - 0a00 (usable) Jun 3 02:21:21 jeti kernel: [0.00] DMI 2.2 present. Jun 3 02:21:21 jeti kernel: [0.00] last_pfn = 0xa000 max_arch_pfn = 0x10 Jun 3 02:21:21 jeti kernel: [0.00] initial memory mapped : 0 - 0180 Jun 3 02:21:21 jeti kernel: [0.00] init_memory_mapping: -0a00 Jun 3 02:21:21 jeti kernel: [0.00] 00 - 40 page 4k Jun 3 02:21:21 jeti kernel: [0.00] 40 - 000a00 page 2M Jun 3 02:21:21 jeti kernel: [0.00] kernel direct mapping tables up to a00 @ 7000-b000 Jun 3 02:21:21 jeti kernel: [0.00] 160MB LOWMEM available. Jun 3 02:21:21 jeti kernel: [0.00] mapped low ram: 0 - 0a00 Jun 3 02:21:21 jeti kernel: [0.00] low ram: 0 - 0a00 Jun 3 02:21:21 jeti kernel: [0.00] node 0 low ram: - 0a00 Jun 3 02:21:21 jeti kernel: [0.00] node 0 bootmap 1000 - 2400 Jun 3 02:21:21 jeti kernel: [0.00] (5 early reservations) == bootmem [00 - 000a00] Jun 3 02:21:21 jeti kernel: [0.00] #0 [00 - 001000] BIOS data page == [00 - 001000] Jun 3 02:21:21 jeti
Bug#517122: very slow access/open/... syscalls on NFS mounted files
On Mon, 03 Jun 2013, Jonathan Nieder wrote: Yaroslav Halchenko wrote: RIP my lovely bug report It had a good run of four years. ;-) LOL -- you beat me to my comment ;) Can you reproduce the absurdly slow NFS access times on some machine with a more recent kernel? I do not think I have ran into it since then and that system is... probably reinstalled from clean slate by now (can't even login) ;) -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- 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/20130604014431.gz10...@onerussian.com
Bug#711021: mount.nfs timeout for GETPORT is much too short
Package: nfs-common Version: 1:1.2.6-3 Severity: important This NFS client stopped being able to mount from my NFS server at boot time, around the time I upgraded them both to wheezy. I think the problem started when only the server was upgraded and was ultimately triggered by avahi-daemon being installed. Since cups now recommends avahi-daemon, this can be considered a common configuration. I took a packet capture on both sides (which matched, so no packets are being lost) and saw that: - The client makes a GETPORT call - The client retries a few times at 1 second intervals, then (if using TCP) closes the connection - About 5 seconds after the first call from the client, the server sends a reply. (strace-ing rpcbind showed it requesting a reverse DNS lookup from avahi, which apparently has a 5 second timeout for mDNS lookups. The client should have had a proper reverse DNS entry, but didn't.) - The client sends a RST (TCP) or ICMP port unreachable error (UDP) when receiving the reply The relevant functions include nfs_pmap_getport() in support/nfs/getport.c, which even has a comment to say: * 2. This version times out quickly by default. It time-limits the * connect process as well as the actual RPC call, and even allows the * caller to specify the timeout. I don't know why it does this, though perhaps the intent was to fail-over quickly when auto-detecting whether the remote portmap/rpcbind uses TCP or UDP. But having failed to query on both protocols, the timeout ought to be increased when retrying. Ben. -- Package-specific info: -- rpcinfo -- program vers proto port 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 46254 status 1000241 tcp 58492 status 1000211 udp 33374 nlockmgr 1000213 udp 33374 nlockmgr 1000214 udp 33374 nlockmgr 1000211 tcp 40195 nlockmgr 1000213 tcp 40195 nlockmgr 1000214 tcp 40195 nlockmgr -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- shadbolt:/home /home nfs nfsvers=3,nodev,nosuid,mountproto=tcp 0 0 shadbolt:/usr/local /usr/local nfs nfsvers=3,nodev,nosuid,mountproto=tcp 0 0 -- /proc/mounts -- rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0 shadbolt:/home /home nfs rw,nosuid,nodev,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.2.1,mountvers=3,mountport=33045,mountproto=tcp,local_lock=none,addr=192.168.2.1 0 0 shadbolt:/usr/local /usr/local nfs rw,nosuid,nodev,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.2.1,mountvers=3,mountport=33045,mountproto=tcp,local_lock=none,addr=192.168.2.1 0 0 -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-41 ii libc6 2.13-38 ii libcap2 1:2.22-1.2 ii libcomerr2 1.42.5-1.1 ii libdevmapper1.02.1 2:1.02.74-7 ii libevent-2.0-5 2.0.19-stable-3 ii libgssglue1 0.4-2 ii libk5crypto31.10.1+dfsg-5 ii libkeyutils11.5.5-3 ii libkrb5-3 1.10.1+dfsg-5 ii libmount1 2.20.1-5.3 ii libnfsidmap20.25-4 ii libtirpc1 0.2.2-5 ii libwrap07.6.q-24 ii lsb-base4.1+Debian8 ii rpcbind 0.2.0-8 ii ucf 3.0025+nmu3 Versions of packages nfs-common recommends: ii python 2.7.3-4 Versions of packages nfs-common suggests: pn open-iscsi none pn watchdognone -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#709647: linux-source-3.2: USB 1.1 no longer works
On Tue, 2013-06-04 at 01:32 +, Bjarni Ingi Gislason wrote: On Fri, May 31, 2013 at 02:50:11AM +0100, Ben Hutchings wrote: Now I see this is a rather old computer (BIOS dated 1999), so I'm not so surprised that ACPI is not supported! Does the kernel in linux-image-3.2.0-4-486 work? Can you send a boot log and output of 'lspci -s :01.2' from a working kernel (old or new)? lspci -s :01.2: 00:01.2 USB controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) Oops, sorry, I meant 'lspci -v -s :01.2'. Anyway, I don't think that's needed as the boot log shows enough information. [...] Jun 3 02:21:21 jeti kernel: [0.108491] pci :00:01.2: reg 20 io port: [0x00-0x1f] [...] Jun 3 02:21:21 jeti kernel: [0.124483] pci :00:01.2: enabling device ( - 0001) Jun 3 02:21:21 jeti kernel: [0.124657] PCI: setting IRQ 5 as level-triggered Jun 3 02:21:21 jeti kernel: [0.124674] pci :00:01.2: assigned PCI INT D - IRQ 5 [...] So there's the IRQ it should get. Now, IRQ routing is done in the file arch/x86/pci/irq.c. Add '#define DEBUG' to the top of that file to enable more detailed log messages. Since your machine doesn't have an IO-APIC, the relevant code should be in pcibios_lookup_irq(). If the log messages still aren't sufficient to work out where it fails, you could add more dev_dbg() calls there. Ben. -- Ben Hutchings Sturgeon's Law: Ninety percent of everything is crap. signature.asc Description: This is a digitally signed message part
