Bug#542358: linux-image-2.6.30-1-686: "e100" module refuses to load
Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: normal Hello ! I have recently upgraded the kernel to 2.6.30 (squeeze) from a running 2.6.26. During the upgrade I got this error: Setting up linux-image-2.6.30-1-686 (2.6.30-5) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module e100 W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module e100 W: Possible missing firmware /lib/firmware/e100/d101m_ucode.bin for module e100 Running update-grub. In 2.6.26 kernel the dmesg will tell me: [ 10.884256] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex [ 10.888710] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Which enables the "e100" module to be working. However in 2.6.30 I cannot connect anymore to the machine over the internet, I assume that it is becouse of this ethernet module which I am using. The machine seems to boot into 2.6.30 and then it hangs there. I cannot investigate any further, becouse of the remote access. Kind regards, Jan Prunk -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-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 linux-image-2.6.30-1-686 depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.9-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.30-1-686 recommends: ii libc6-i6862.9-23 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.30-1-686 suggests: ii grub 0.97-55GRand Unified Bootloader (dummy pa ii grub-legacy [grub]0.97-55GRand Unified Bootloader (Legacy v pn linux-doc-2.6.30 (no description available) -- debconf information: linux-image-2.6.30-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.30-1-686/postinst/create-kimage-link-2.6.30-1-686: true linux-image-2.6.30-1-686/prerm/would-invalidate-boot-loader-2.6.30-1-686: true linux-image-2.6.30-1-686/preinst/overwriting-modules-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/old-dir-initrd-link-2.6.30-1-686: true linux-image-2.6.30-1-686/preinst/failed-to-move-modules-2.6.30-1-686: linux-image-2.6.30-1-686/preinst/initrd-2.6.30-1-686: linux-image-2.6.30-1-686/prerm/removing-running-kernel-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/kimage-is-a-directory: linux-image-2.6.30-1-686/preinst/abort-overwrite-2.6.30-1-686: linux-image-2.6.30-1-686/preinst/bootloader-initrd-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/depmod-error-initrd-2.6.30-1-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.30-1-686/postinst/old-initrd-link-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/depmod-error-2.6.30-1-686: false linux-image-2.6.30-1-686/postinst/old-system-map-link-2.6.30-1-686: true linux-image-2.6.30-1-686/preinst/lilo-initrd-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/bootloader-test-error-2.6.30-1-686: linux-image-2.6.30-1-686/preinst/abort-install-2.6.30-1-686: linux-image-2.6.30-1-686/postinst/bootloader-error-2.6.30-1-686: linux-image-2.6.30-1-686/preinst/elilo-initrd-2.6.30-1-686: true -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542372: linux-modules-extra-2.6: please add dahdi
Package: linux-modules-extra-2.6 Severity: wishlist Please add include the DAHDI modules in linux-modules-extra-2.6 builds. The kernel modules of DAHDI are in the source package dahdi-linux and dahdi-source is one that can be built with module-assistant. Note that the package dahdi includes userspace utilities and comes from a different source package (dahdi-tools). -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542377: linux-image-2.6.30-1-686-bigmem: Module gspca_stv06xx image problem using Logitech Quickcam Express
Package: linux-image-2.6.30-1-686-bigmem Version: 2.6.30-6 Severity: important Using a Logitech Quickcam Express using the gspca module only gives a broken image. Bus 003 Device 002: ID 046d:0870 Logitech, Inc. QuickCam Express Dmesg output: [ 10.554655] gspca: main v2.5.0 registered [ 10.556144] STV06xx: Probing for a stv06xx device [ 10.556148] gspca: probing 046d:0870 [ 10.556152] STV06xx: Configuring camera [ 10.566049] STV06xx: HDCS-1020 sensor detected [ 10.566052] STV06xx: Initializing camera [ 10.848079] gspca: probe ok [ 10.848100] usbcore: registered new interface driver STV06xx [ 10.848104] STV06xx: registered When starting e. g. Cheese or gstreamer-properties, the following dmesg output appears: [ 8331.020392] gspca: ISOC data error: [5] len=329, status=-63 The image in Cheese or gstreamer-properties is completely messed up. Hexdump of the video output: u...@localhost:~$ hexdump /dev/video0 000 010 0501 0104 0402 0502 020 0408 0507 0402 0104 030 0307 0305 0004 0105 040 0604 0205 0001 0106 050 0607 060a 0807 040a 060 0706 0705 0905 0306 070 0506 0204 0204 0206 080 0506 010a 0a06 0606 090 0b05 050a 0606 0807 0a0 0306 0205 0505 0206 0b0 0803 0506 0604 0507
Processed: severity of 542377 is normal
Processing commands for cont...@bugs.debian.org: > severity 542377 normal Bug #542377 [linux-image-2.6.30-1-686-bigmem] linux-image-2.6.30-1-686-bigmem: Module gspca_stv06xx image problem using Logitech Quickcam Express Severity set to 'normal' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542250: Another backtrace of the same
Here is one more backtrace of the same crash.
[ 9199.462928] Call Trace:
[ 9199.462928][] ? _spin_lock+0x3a/0x42
[ 9199.462928] [] ? :sata_sil:sil_interrupt+0x2b/0x275
[ 9199.462928] [] ? handle_IRQ_event+0x47/0x8e
[ 9199.462928] [] ? handle_level_irq+0xae/0x116
[ 9199.462928] [] ? do_IRQ+0x4e/0x9a
[ 9199.462928] [] ? evtchn_do_upcall+0x13c/0x1fc
[ 9199.462928] [] ? do_hypervisor_callback+0x1e/0x30
[ 9199.462928][] ? dummy_inode_permission+0x0/0x3
[ 9199.462928] [] ? xen_poll_irq+0x67/0x74
[ 9199.462928] [] ? xen_spin_wait+0xfa/0x139
[ 9199.462928] [] ? lock_kernel+0x4f/0x63
[ 9199.462928] [] ? :nfs:nfs_permission+0xb0/0x15f
[ 9199.462928] [] ? permission+0xb5/0x118
[ 9199.462928] [] ? __link_path_walk+0x145/0xdfa
[ 9199.462928] [] ? :nfs:nfs_sync_mapping_wait+0x151/0x33f
[ 9199.462928] [] ? path_walk+0x46/0x8b
[ 9199.462928] [] ? do_path_lookup+0x158/0x1ce
[ 9199.462928] [] ? __path_lookup_intent_open+0x56/0x97
[ 9199.462928] [] ? do_filp_open+0x9c/0x7c4
[ 9199.462928] [] ? get_unused_fd_flags+0x74/0x13f
[ 9199.462928] [] ? do_sys_open+0x46/0xc3
[ 9199.462928] [] ? system_call+0x68/0x6d
[ 9199.462928] [] ? system_call+0x0/0x6d
What is similar in all instances - it enters
... -> lock_kernel() -> xen_spin_wait() -> xen_poll_irq(),
then gets an interrupt, then enters
... -> :sata_sil:sil_interrupt() -> _spin_lock()
and gets kernel BUG at drivers/xen/core/spinlock.c:74
which is xen_spin_wait():
...
66 /* announce we're spinning */
67 spinning = &__get_cpu_var(spinning);
68 if (spinning->lock) {
69 BUG_ON(spinning->lock == lock);
70 if(raw_irqs_disabled()) {
71 BUG_ON(__get_cpu_var(spinning_bh).lock == lock);
72 spinning = &__get_cpu_var(spinning_irq);
73 } else {
74 BUG_ON(!in_softirq());
75 spinning = &__get_cpu_var(spinning_bh);
76 }
77 BUG_ON(spinning->lock);
78 }
...
So code thies to take BKL and spins there.
While spinning, interrupt arrives.
Interrupt handler tries to take another lock.
But xen_spin_wait() is not expecting attempt to take another lock when
not raw_irqs_disabled() and not in_softirq().
Here we are in interrupt handler, bit hard irq are not disabled.
Looks like check in line 70 is wrong.
Nikita
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
> This asserts that if we spin on a lock after interrupting another spin,
> and interrupts are enabled, we must be in a softirq.
Looking at the bottom of the same file drivers/xen/core/spinlock.c:
void xen_spin_kick(raw_spinlock_t *lock, unsigned int token)
{
unsigned int cpu;
token &= (1U << TICKET_SHIFT) - 1;
for_each_online_cpu(cpu) {
if (spinning(&per_cpu(spinning, cpu), cpu, lock, token))
return;
if (in_interrupt()
&& spinning(&per_cpu(spinning_bh, cpu), cpu, lock, token))
return;
if (raw_irqs_disabled()
&& spinning(&per_cpu(spinning_irq, cpu), cpu, lock, token))
return;
}
}
EXPORT_SYMBOL(xen_spin_kick);
... I may guess that line 74 should check for in_interrupt() instead of
in_softirq().
However it is just a guess based on analogy.
I don't currently understand the logic of that code.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing of linux-2.6_2.6.26-19_i386.changes
linux-2.6_2.6.26-19_i386.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.26-19.dsc linux-2.6_2.6.26-19.diff.gz linux-doc-2.6.26_2.6.26-19_all.deb linux-manual-2.6.26_2.6.26-19_all.deb linux-patch-debian-2.6.26_2.6.26-19_all.deb linux-source-2.6.26_2.6.26-19_all.deb linux-support-2.6.26-2_2.6.26-19_all.deb linux-tree-2.6.26_2.6.26-19_all.deb linux-image-2.6.26-2-486_2.6.26-19_i386.deb linux-headers-2.6.26-2-486_2.6.26-19_i386.deb linux-image-2.6.26-2-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-686_2.6.26-19_i386.deb linux-image-2.6.26-2-686-bigmem_2.6.26-19_i386.deb linux-headers-2.6.26-2-686-bigmem_2.6.26-19_i386.deb linux-image-2.6.26-2-amd64_2.6.26-19_i386.deb linux-headers-2.6.26-2-amd64_2.6.26-19_i386.deb linux-headers-2.6.26-2-common_2.6.26-19_i386.deb linux-image-2.6.26-2-openvz-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-openvz-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-common-openvz_2.6.26-19_i386.deb linux-headers-2.6.26-2-all_2.6.26-19_i386.deb linux-headers-2.6.26-2-all-i386_2.6.26-19_i386.deb linux-libc-dev_2.6.26-19_i386.deb linux-image-2.6.26-2-vserver-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-vserver-686_2.6.26-19_i386.deb linux-image-2.6.26-2-vserver-686-bigmem_2.6.26-19_i386.deb linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-19_i386.deb linux-headers-2.6.26-2-common-vserver_2.6.26-19_i386.deb linux-image-2.6.26-2-xen-686_2.6.26-19_i386.deb linux-modules-2.6.26-2-xen-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-xen-686_2.6.26-19_i386.deb xen-linux-system-2.6.26-2-xen-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-common-xen_2.6.26-19_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542358: linux-image-2.6.30-1-686: "e100" module refuses to load
On Wed, Aug 19, 2009 at 10:28:44AM +0200, Jan Prunk wrote: > Package: linux-image-2.6.30-1-686 > Version: 2.6.30-5 > Severity: normal > > Hello ! > > I have recently upgraded the kernel to 2.6.30 (squeeze) from a running 2.6.26. > During the upgrade I got this error: > > Setting up linux-image-2.6.30-1-686 (2.6.30-5) ... > Running depmod. > Running update-initramfs. > update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 > W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module > e100 > W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module > e100 > W: Possible missing firmware /lib/firmware/e100/d101m_ucode.bin for module > e100 You probably need to install the firmware-linux package from non-free. Please let us know if this fixes the issue for you. > Running update-grub. > > In 2.6.26 kernel the dmesg will tell me: > [ 10.884256] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex > [ 10.888710] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > Which enables the "e100" module to be working. > > However in 2.6.30 I cannot connect anymore to the machine over the internet, > I assume > that it is becouse of this ethernet module which I am using. The machine > seems to boot > into 2.6.30 and then it hangs there. I cannot investigate any further, > becouse of the > remote access. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542358: marked as done (linux-image-2.6.30-1-686: "e100" module refuses to load)
Your message dated Wed, 19 Aug 2009 10:09:42 -0600 with message-id <20090819160942.gb21...@lackof.org> and subject line Re: Bug#542358: linux-image-2.6.30-1-686: "e100" module refuses to load has caused the Debian Bug report #542358, regarding linux-image-2.6.30-1-686: "e100" module refuses to load 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.) -- 542358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: normal Hello ! I have recently upgraded the kernel to 2.6.30 (squeeze) from a running 2.6.26. During the upgrade I got this error: Setting up linux-image-2.6.30-1-686 (2.6.30-5) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module e100 W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module e100 W: Possible missing firmware /lib/firmware/e100/d101m_ucode.bin for module e100 Running update-grub. In 2.6.26 kernel the dmesg will tell me: [ 10.884256] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex [ 10.888710] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Which enables the "e100" module to be working. However in 2.6.30 I cannot connect anymore to the machine over the internet, I assume that it is becouse of this ethernet module which I am using. The machine seems to boot into 2.6.30 and then it hangs there. I cannot investigate any further, becouse of the remote access. Kind regards, Jan Prunk -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-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 linux-image-2.6.30-1-686 depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.9-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.30-1-686 recommends: ii libc6-i6862.9-23 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.30-1-686 suggests: ii grub 0.97-55GRand Unified Bootloader (dummy pa ii grub-legacy [grub]0.97-55GRand Unified Bootloader (Legacy v pn linux-doc-2.6.30 (no description available) -- debconf information: linux-image-2.6.30-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.30-1-686/postinst/create-kimage-link-2.6.30-1-686: true linux-image-2.6.30-1-686/prerm/would-invalidate-boot-loader-2.6.30-1-686: true linux-image-2.6.30-1-686/preinst/overwriting-modules-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/old-dir-initrd-link-2.6.30-1-686: true linux-image-2.6.30-1-686/preinst/failed-to-move-modules-2.6.30-1-686: linux-image-2.6.30-1-686/preinst/initrd-2.6.30-1-686: linux-image-2.6.30-1-686/prerm/removing-running-kernel-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/kimage-is-a-directory: linux-image-2.6.30-1-686/preinst/abort-overwrite-2.6.30-1-686: linux-image-2.6.30-1-686/preinst/bootloader-initrd-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/depmod-error-initrd-2.6.30-1-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.30-1-686/postinst/old-initrd-link-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/depmod-error-2.6.30-1-686: false linux-image-2.6.30-1-686/postinst/old-system-map-link-2.6.30-1-686: true linux-image-2.6.30-1-686/preinst/lilo-initrd-2.6.30-1-686: true linux-image-2.6.30-1-686/postinst/bootloader-test-error-2.6.30-1-686: linux-image-2.6.30-1-686/preinst/abort-install-2.6.30-1-686: linux-image-2.6.30-1-686/postinst/bootloader-error-2.6.30-1-686: linux-image-2.6.30-1-686/preinst/elilo-initrd-2.6.30-1-686: true --- End Message --- --- Begin Message --- On Wed, Aug 19, 2009 at 05:59:29PM +0200, Jan Prunk wrote: > Thank you for your suggestion, this indeed fixes this bug report ! Great, closing. -- dann frazier --- End Message ---
Bug#542358: linux-image-2.6.30-1-686: "e100" module refuses to load
Thank you for your suggestion, this indeed fixes this bug report ! Kind regards, Jan On Wed, Aug 19, 2009 at 4:40 PM, dann frazier wrote: > On Wed, Aug 19, 2009 at 10:28:44AM +0200, Jan Prunk wrote: >> Package: linux-image-2.6.30-1-686 >> Version: 2.6.30-5 >> Severity: normal >> >> Hello ! >> >> I have recently upgraded the kernel to 2.6.30 (squeeze) from a running >> 2.6.26. >> During the upgrade I got this error: >> >> Setting up linux-image-2.6.30-1-686 (2.6.30-5) ... >> Running depmod. >> Running update-initramfs. >> update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 >> W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module >> e100 >> W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module >> e100 >> W: Possible missing firmware /lib/firmware/e100/d101m_ucode.bin for module >> e100 > > You probably need to install the firmware-linux package from non-free. > Please let us know if this fixes the issue for you. > >> Running update-grub. >> >> In 2.6.26 kernel the dmesg will tell me: >> [ 10.884256] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex >> [ 10.888710] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready >> Which enables the "e100" module to be working. >> >> However in 2.6.30 I cannot connect anymore to the machine over the internet, >> I assume >> that it is becouse of this ethernet module which I am using. The machine >> seems to boot >> into 2.6.30 and then it hangs there. I cannot investigate any further, >> becouse of the >> remote access. > > > -- > dann frazier > > -- Jan Prunk http://www.prunk.si 0x00E80E86 - http://pgpkeys.pca.dfn.de/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542358: linux-image-2.6.30-1-686: "e100" module refuses to load
On Wed, Aug 19, 2009 at 05:59:29PM +0200, Jan Prunk wrote: > Thank you for your suggestion, this indeed fixes this bug report ! Great, closing. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542440: linux-image-2.6.26-2-686: pcimcia sata not detecting dvd burner
Package: linux-image-2.6.26-2-686 Version: 2.6.26-17 Severity: normal *** Please type your report below this line *** I have pcmcia sata card working on chipset Silicon Image Sil 3512. My previous distribution was Kubutu Jaunty. Under Debian Lenny Pioneer dvd-writer connected to this card not working. On Kubuntu everything working fine. -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-17) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Sun Jun 21 04:57:38 UTC 2009 ** Command line: root=/dev/sda1 ro quiet ** Not tainted ** Kernel log: [ 41.792026] ata4: link is slow to respond, please be patient (ready=-19) [ 71.472024] ata4: COMRESET failed (errno=-16) [ 76.496026] ata4: COMRESET failed (errno=-16) [ 76.496098] ata4: reset failed, giving up [ 76.816081] ata5: SATA link down (SStatus 0 SControl 310) [ 77.736012] Adding 1951888k swap on /dev/sda3. Priority:-1 extents:1 across:1951888k [ 78.117075] EXT3 FS on sda1, internal journal [ 78.308838] loop: module loaded [ 79.292071] fuse init (API version 7.9) [ 79.344043] kjournald starting. Commit interval 5 seconds [ 79.344075] EXT3 FS on sda5, internal journal [ 79.344075] EXT3-fs: mounted filesystem with ordered data mode. [ 79.344430] kjournald starting. Commit interval 5 seconds [ 79.344462] EXT3 FS on sda6, internal journal [ 79.344462] EXT3-fs: mounted filesystem with ordered data mode. [ 82.421242] NET: Registered protocol family 10 [ 82.421592] lo: Disabled Privacy Extensions [ 82.64] lp: driver loaded but no devices found [ 82.637025] ppdev: user-space parallel port driver [ 85.880544] input: b43-phy0 as /class/input/input8 [ 85.968068] firmware: requesting b43/ucode5.fw [ 86.060298] firmware: requesting b43/pcm5.fw [ 86.072580] firmware: requesting b43/b0g0initvals5.fw [ 86.079677] firmware: requesting b43/b0g0bsinitvals5.fw [ 86.200044] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) [ 87.524473] Registered led device: b43-phy0::tx [ 87.524492] Registered led device: b43-phy0::rx [ 87.524508] Registered led device: b43-phy0::radio [ 87.576259] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 87.983794] Bluetooth: Core ver 2.11 [ 87.984953] NET: Registered protocol family 31 [ 87.984958] Bluetooth: HCI device and connection manager initialized [ 87.984961] Bluetooth: HCI socket layer initialized [ 88.001570] Bluetooth: L2CAP ver 2.9 [ 88.001575] Bluetooth: L2CAP socket layer initialized [ 88.249126] Bluetooth: RFCOMM socket layer initialized [ 88.249140] Bluetooth: RFCOMM TTY layer initialized [ 88.249141] Bluetooth: RFCOMM ver 1.8 [ 88.695197] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 91.011429] input: b43-phy0 as /class/input/input9 [ 91.208034] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) [ 92.087257] [drm] Initialized drm 1.1.0 20060810 [ 92.093782] ACPI: PCI Interrupt :00:02.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 92.093792] PCI: Setting latency timer of device :00:02.0 to 64 [ 92.093869] [drm] Initialized i915 1.6.0 20060119 on minor 0 [ 93.296496] Registered led device: b43-phy0::tx [ 93.296518] Registered led device: b43-phy0::rx [ 93.296534] Registered led device: b43-phy0::radio [ 93.348287] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 94.972100] wlan0: Initial auth_alg=0 [ 94.972107] wlan0: authenticate with AP 00:21:27:e3:95:e8 [ 94.972577] wlan0: Initial auth_alg=0 [ 94.972582] wlan0: authenticate with AP 00:21:27:e3:95:e8 [ 94.973545] wlan0: RX authentication from 00:21:27:e3:95:e8 (alg=0 transaction=2 status=0) [ 94.973550] wlan0: authenticated [ 94.973553] wlan0: associate with AP 00:21:27:e3:95:e8 [ 94.980009] wlan0: authentication frame received from 00:21:27:e3:95:e8, but not in authenticate state - ignored [ 94.980074] wlan0: RX AssocResp from 00:21:27:e3:95:e8 (capab=0x431 status=0 aid=1) [ 94.980074] wlan0: associated [ 94.980074] wlan0: switched to short barker preamble (BSSID=00:21:27:e3:95:e8) [ 94.980074] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 98.401097] atkbd.c: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0). [ 98.401097] atkbd.c: Use 'setkeycodes e078 ' to make it known. [ 98.408480] atkbd.c: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0). [ 98.408480] atkbd.c: Use 'setkeycodes e078 ' to make it known. [ 105.944017] wlan0: no IPv6 routers present [ 1211.714650] ACPI: PCI interrupt for device :10:00.0 disabled [ 1266.317819] sata_sil :10:00.0: version 2.3 [ 1266.317864] ACPI: PCI Interrupt :10:00.0[A] -> GSI 22 (level, low) -> IRQ 22 [ 1266.317881] sata_sil :10:00.0: cache line size not set. Driver may not function [ 1266.319575] scsi5 : sata_sil [ 1266.321109] scsi6 : sata_sil [ 1266.321162] ata6: SATA max UDMA/100 mmio m...@0x8848 tf 0x88480080 irq 22 [ 1266.321167
Bug#492853: problem exists
Alexandra N. Kossovsky wrote: > On Sat, Aug 15, 2009 at 07:41:56PM +0200, Moritz Muehlenhoff wrote: > > Sorry for the late followup. Are these messages appearing for any traffic > > or just specific patterns? > > As far as I've seen it, the problem is VLAN-related. It occurs if > I enable some VLANs on the interface. These VLANs are used by test boxes > (a lot of embedded linuxes with various software onboard), so it is hard > to predict what do they send to the net because of software and hardware > errors. > > Currently, I've disabled VLANs (they are not really necessary on that > computer), > and there are no problems... Do some of your embedded devices use big endian byte order? It suspect your issue is fixed by the following commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b9389796fa4c87fbdff33816e317cdae5f36dd0b Could you please test, whether the problem is fixed if running one of he trunk kernels based on 2.6.31-rcX (which already include the patch)? http://wiki.debian.org/DebianKernel If it fixes the problem, we can add the patch to a kernel update in a stable point update. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#484593: marked as done (linux-image-2.6.25-2-686: su gets stuck for root -- stty getting stuck in T state)
Your message dated Wed, 19 Aug 2009 19:52:13 +0200 with message-id <20090819175213.ga21...@inutil.org> and subject line Re: linux-image-2.6.25-2-686: su gets stuck for root -- stty getting stuck in T state has caused the Debian Bug report #484593, regarding linux-image-2.6.25-2-686: su gets stuck for root -- stty getting stuck in T state 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.) -- 484593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.25-2-686 Version: 2.6.25-4 Severity: normal There's an upstream bug that has started affecting me. stty gets backgrounded, and you can only kill -9 it to get your shell back. A thread titled "su gets stuck for root" is on LKML with all the details, and when there's an eventual patch, it would be good to include it in the debian patchset. -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-4) (m...@debian.org) (gcc version 4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Tue May 27 15:38:35 UTC 2008 ** Command line: root=/dev/mapper/scuzzie_36gb-scuzzie_36gb--i386 ro quiet ** Not tainted ** Kernel log: [ 798.258922] EXT3-fs: mounted filesystem with journal data mode. [ 798.262669] kjournald starting. Commit interval 5 seconds [ 798.263137] EXT3 FS on dm-11, internal journal [ 798.263137] EXT3-fs: mounted filesystem with journal data mode. [ 800.290714] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 [ 800.292024] martian source 192.168.1.3 from 192.168.1.254, on dev eth0 [ 800.292024] ll header: ff:ff:ff:ff:ff:ff:00:04:ed:78:c8:50:08:06 [ 800.292024] martian source 192.168.1.3 from 192.168.1.254, on dev eth0 [ 800.292024] ll header: ff:ff:ff:ff:ff:ff:00:04:ed:78:c8:50:08:06 [ 800.292024] martian source 192.168.1.3 from 192.168.1.254, on dev eth0 [ 800.292024] ll header: ff:ff:ff:ff:ff:ff:00:04:ed:78:c8:50:08:06 [ 800.292024] martian source 192.168.1.3 from 192.168.1.254, on dev eth0 [ 800.292024] ll header: ff:ff:ff:ff:ff:ff:00:04:ed:78:c8:50:08:06 [ 800.292024] martian source 192.168.1.3 from 192.168.1.254, on dev eth0 [ 800.292024] ll header: ff:ff:ff:ff:ff:ff:00:04:ed:78:c8:50:08:06 [ 800.292024] martian source 192.168.1.3 from 192.168.1.254, on dev eth0 [ 800.292024] ll header: ff:ff:ff:ff:ff:ff:00:04:ed:78:c8:50:08:06 [ 800.292024] martian source 192.168.1.3 from 192.168.1.17, on dev eth0 [ 800.292024] ll header: ff:ff:ff:ff:ff:ff:00:13:e8:9b:36:d7:08:06 [ 800.292024] martian source 192.168.1.3 from 192.168.1.17, on dev eth0 [ 800.292024] ll header: ff:ff:ff:ff:ff:ff:00:13:e8:9b:36:d7:08:06 [ 800.292024] martian source 192.168.1.3 from 192.168.1.17, on dev eth0 [ 800.292024] ll header: ff:ff:ff:ff:ff:ff:00:13:e8:9b:36:d7:08:06 [ 800.292024] martian source 192.168.1.3 from 192.168.1.17, on dev eth0 [ 800.292024] ll header: ff:ff:ff:ff:ff:ff:00:13:e8:9b:36:d7:08:06 [ 800.398584] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 [ 803.688006] NET: Registered protocol family 10 [ 803.689850] lo: Disabled Privacy Extensions [ 804.550877] RPC: Registered udp transport module. [ 804.550888] RPC: Registered tcp transport module. [ 806.573597] nf_conntrack version 0.5.0 (4096 buckets, 16384 max) [ 806.744359] ip_tables: (C) 2000-2006 Netfilter Core Team [ 809.082179] ACPI: WMI: Mapper loaded [ 810.454758] eth0: no IPv6 routers present [ 811.969727] ondemand governor failed, too long transition latency of HW, fallback to performance governor [ 812.105224] lp0: using parport0 (interrupt-driven). [ 812.151297] ppdev: user-space parallel port driver [ 817.783840] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 817.889025] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 817.903852] NFSD: starting 90-second grace period [ 818.843517] warning: `ntpd' uses 32-bit capabilities (legacy support in use) [ 821.734771] ondemand governor failed, too long transition latency of HW, fallback to performance governor [ 1184.070018] [drm] Initialized drm 1.1.0 20060810 [ 1184.270097] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [ 1184.270121] ACPI: PCI Interrupt :01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 [ 1184.270625] [drm] Initialized r128 2.5.0 20030725 on minor 0 [ 1184.276458] agpgart: Found an AGP 1.0 compliant device at :00:00.0. [ 1184.276502] agpgart: Putting AGP V2 device at :00:00.0 into 1x mode [ 1184.276543] agpgart: Putting AGP V2 device at :01:00.0 into 1x mode [ 1249.002445] printk: 134 messages suppressed. [ 1249.00
Bug#451045: linux-image-2.6.22-3-amd64: snd-hda-intel: Speakers do not turn off when headphones plugged into front headphone jack
On Thu, Aug 13, 2009 at 04:39:03PM -0700, Josh Triplett wrote: > On Fri, Aug 14, 2009 at 01:11:18AM +0200, Moritz Muehlenhoff wrote: > > On Fri, Dec 26, 2008 at 06:09:57PM +0100, Moritz Muehlenhoff wrote: > > > On Mon, Nov 12, 2007 at 04:42:39PM -0800, Josh Triplett wrote: > > > > Package: linux-image-2.6.22-3-amd64 > > > > Version: 2.6.22-5 > > > > Severity: normal > > > > > > > > I have a 965G chipset with built-in audio, supported by the > > > > snd-hda-intel driver. (More specific details below under "** PCI > > > > devices".) It has rear audio connections for various speaker > > > > configurations, and front jacks for headphones and microphone. I have > > > > speakers connected to the rear jack appropriate for a single pair of > > > > stereo speakers (labelled Front in ALSA, meaning the front stereo > > > > speakers). When I plug headphones into the front headphone jack, the > > > > headphones work, but the speakers continue to emit sound. I'd like > > > > the speakers to mute when I plug in headphones. > > > > > > > > Some Googling suggests the "model" option of the snd-hda-intel driver, > > > > but I've tried numerous models and none achieve the desired effect. > > > > In any case, the default model=auto should Do The Right Thing. > > > > > > > > Happy to test patches or test kernels from Git, if that would help. > > > > Does this error still occur with more recent kernel versions? > > Yes, this error still occurs with 2.6.30. Please report this upstream at bugzilla.kernel.org and tell us the bug number. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#453747: linux-image-2.6.18-5-amd64: inconsistent RPC record marking prevents nfsroot from Solaris NFS server
On Sat, Dec 01, 2007 at 12:18:04AM +0200, Hristo Iliev wrote: > Package: linux-image-2.6.18-5-amd64 > Version: 2.6.18.dfsg.1-13etch4 > Severity: normal > > *** Please type your report below this line *** > While trying to network boot Debian 2.6.18-5-amd64 kernel and mounting > root from an OpenSolaris NFS server boot process hangs like that: > ... > Begin: Running /scripts/nfs-premount ... > Done. > > > Looking at the network stream with tshark reveals that the RPC request > to server's portmapper is malformed: RPC fragment header states > incorrect fragment size - 4 bytes more. The malformed request never > gets answered by Sun's rpcbind and thus boot process halts. > > The RPC request sent looks like this (Ethernet addresses masked out): > ** ** ** ** ** ** ** ** ** ** ** ** 08 00 45 00 ..E. > 0010 00 70 9d a5 40 00 40 06 85 dc 0a 01 01 0b 0a 01 @.@. > 0020 01 fa ad e2 00 6f 5e 6b 77 02 e2 5b 3d 3d 80 18 .o^kw..[==.. > 0030 00 2e db ed 00 00 01 01 08 0a ff fe ea a4 20 87 .. . > 0040 d1 46 80 00 00 3c ff e1 76 18 00 00 00 00 00 00 .F...<..v... > ^^^ > 0050 00 02 00 01 86 a0 00 00 00 02 00 00 00 03 00 00 > 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 > 0070 86 a3 00 00 00 03 00 00 00 06 00 00 00 00 f1 af > 0080 86 4e > > The last four bytes (0xf1af864e) are Ethernet trailer and are NOT part > of the TCP payload. Sorry for the late response. Did you upgrade to Lenny in the mean time? If so, does the error still occur? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#455195: linux-image-2.6.18-5-vserver-amd64: forcedeth hears no dhcp reply; linux-image-2.6.18-5-xen-vserver-amd64 IS GOOD
On Sat, Dec 08, 2007 at 08:25:56PM -0500, supaplex wrote: > Package: linux-image-2.6.18-5-vserver-amd64 > Version: 2.6.18.dfsg.1-13etch4 > Severity: normal > > I've stripped the interfaces(5) config down to a plain ordinary dhcp > host for eth0, loopback etc. No vlans, No bridging, and no other > network interfaces in the system. > > For the time being, I wanted to keep it simple, and use a kernel without > xen support, so I installed this release. After rebooting between each > kernel back and forth, dhcp always works in the dom0 xen kernel, and > never has when not using xen. At present none of the vserver guests > have dedicated network interfaces. They're used in development testing > and mostly for isolated compiling of packages (eg, backports, one off > tests, etc). > > syslog on the dhcp server says it's assigning the address, tcpdump on > the dhcp server says it's assigning an address, but tcpdump running on > the client only sees dhcp requests until it eventually gives up and goes > idle. > > I also attempted to stop util-vserver on the bad kernel, stop > networking, and start it again with no progress on the issue. Did you upgrade to Lenny in the mean time? If so, did it fix the problem? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
tags 542250 +patch
thanks
> ... I may guess that line 74 should check for in_interrupt() instead of
> in_softirq().
I've tried that and it really fixed the problem. Server already runs the
same backup procedure for several hours. Previously it crashed within 15
minutes.
Here is the patch I've applied:
--- a/drivers/xen/core/spinlock.c 2009-08-19 16:20:17.0 +0400
+++ b/drivers/xen/core/spinlock.c 2009-08-19 17:36:55.0 +0400
@@ -71,7 +71,7 @@
BUG_ON(__get_cpu_var(spinning_bh).lock == lock);
spinning = &__get_cpu_var(spinning_irq);
} else {
- BUG_ON(!in_softirq());
+ BUG_ON(!in_interrupt());
spinning = &__get_cpu_var(spinning_bh);
}
BUG_ON(spinning->lock);
signature.asc
Description: This is a digitally signed message part.
Processed: Re: Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
Processing commands for cont...@bugs.debian.org: > tags 542250 +patch Bug #542250 [linux-image-2.6.26-2-xen-amd64] repeatable crashes while copying 500G from NFS mount to local logical volume Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542470: linux-image-2.6.30-1-686: IPv6 can not be disabled
Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: normal IPv6 is enabled by default in kernel 2.6.30 and can't be disabled, at least not in an easy way. I've tried both echo 1 >/proc/sys/net/ipv6/conf/all/disable_ipv6 and sysctl -w net.ipv6.conf.all.disable_ipv6=1 methods without any success. I think this bug is related to https://bugs.launchpad.net/bugs/351656 in Ubuntu. In that report someone says there's a fix from upstream and that's already fixed in 2.6.31 series. There'd be a possible security risk in this whole thing. Regards. -- Package-specific info: ** Version: Linux version 2.6.30-1-686 (Debian 2.6.30-5) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-15) ) #1 SMP Mon Aug 3 16:18:30 UTC 2009 ** Command line: root=/dev/mapper/gregson-root ro ** Not tainted ** Kernel log: [4.635990] usb usb4: configuration #1 chosen from 1 choice [4.636167] hub 4-0:1.0: USB hub found [4.636241] hub 4-0:1.0: 2 ports detected [4.636866] ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 11 [4.636932] uhci_hcd :02:01.1: PCI INT B -> Link[LNKF] -> GSI 11 (level, low) -> IRQ 11 [4.637012] uhci_hcd :02:01.1: UHCI Host Controller [4.637165] uhci_hcd :02:01.1: new USB bus registered, assigned bus number 5 [4.637270] uhci_hcd :02:01.1: irq 11, io base 0xa400 [4.637409] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 [4.637471] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.637540] usb usb5: Product: UHCI Host Controller [4.637595] usb usb5: Manufacturer: Linux 2.6.30-1-686 uhci_hcd [4.637653] usb usb5: SerialNumber: :02:01.1 [4.637876] usb usb5: configuration #1 chosen from 1 choice [4.638004] hub 5-0:1.0: USB hub found [4.639029] hub 5-0:1.0: 2 ports detected [4.674466] SCSI subsystem initialized [4.823370] libata version 3.00 loaded. [4.848144] ide-gd driver 1.18 [4.848263] hda: max request size: 128KiB [4.875398] ide-cd driver 5.00 [4.876202] hda: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=65535/16/63 [4.877455] hda: cache flushes supported [4.877635] hda: hda1 hda2 [4.901097] ide-cd: hdc: ATAPI 40X DVD-ROM drive, 512kB Cache [4.901318] Uniform CD-ROM driver Revision: 3.20 [4.913464] ide-cd: hdd: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache [5.081943] device-mapper: uevent: version 1.0.3 [5.084084] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-de...@redhat.com [5.423958] PM: Starting manual resume from disk [5.489211] kjournald starting. Commit interval 5 seconds [5.489292] EXT3-fs: mounted filesystem with ordered data mode. [7.240796] udev: starting version 141 [7.473488] Marking TSC unstable due to TSC halts in idle [7.473650] ACPI: CPU0 (power states: C1[C1] C2[C2]) [7.473894] processor ACPI_CPU:00: registered as cooling_device1 [7.473958] ACPI: Processor [CPU0] (supports 2 throttling states) [7.476314] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 [7.476395] ACPI: Power Button [PWRF] [7.476594] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2 [7.476668] ACPI: Power Button [PWRB] [7.476851] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3 [7.476927] ACPI: Sleep Button [SLPB] [7.666465] parport_pc 00:0b: reported by Plug and Play ACPI [7.666582] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] [7.882075] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [7.913328] input: PC Speaker as /devices/platform/pcspkr/input/input4 [8.052585] gameport: NS558 PnP Gameport is pnp00:0e/gameport0, io 0x201, speed 755kHz [8.057431] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [8.086799] intel_rng: FWH not detected [8.176868] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11 [8.176938] i801_smbus :00:1f.3: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11 [8.827555] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input5 [9.086851] Intel ICH :00:1f.5: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11 [9.086951] Intel ICH :00:1f.5: setting latency timer to 64 [9.408067] intel8x0_measure_ac97_clock: measured 55157 usecs (2650 samples) [9.408136] intel8x0: clocking to 48000 [ 10.232835] EXT3 FS on dm-0, internal journal [ 11.048986] loop: module loaded [ 12.807334] fuse init (API version 7.11) [ 12.933062] kjournald starting. Commit interval 5 seconds [ 12.933372] EXT3 FS on dm-5, internal journal [ 12.933472] EXT3-fs: mounted filesystem with ordered data mode. [ 12.962840] kjournald starting. Commit interval 5 seconds [ 12.963197] EXT3 FS on dm-4, internal journal [ 12.963295] EXT3-fs: mounted filesystem with ordered data mode. [ 12.990717] kjournald starting. Commit interval 5 seconds [ 12.991052] EXT3 FS on dm-1,
linux-2.6_2.6.26-19_i386.changes ACCEPTED
Accepted: linux-2.6_2.6.26-19.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.26-19.diff.gz linux-2.6_2.6.26-19.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.26-19.dsc linux-doc-2.6.26_2.6.26-19_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.26_2.6.26-19_all.deb linux-headers-2.6.26-2-486_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-486_2.6.26-19_i386.deb linux-headers-2.6.26-2-686-bigmem_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-686-bigmem_2.6.26-19_i386.deb linux-headers-2.6.26-2-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-all-i386_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-all-i386_2.6.26-19_i386.deb linux-headers-2.6.26-2-all_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-19_i386.deb linux-headers-2.6.26-2-amd64_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-19_i386.deb linux-headers-2.6.26-2-common-openvz_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-19_i386.deb linux-headers-2.6.26-2-common-vserver_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-19_i386.deb linux-headers-2.6.26-2-common-xen_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-19_i386.deb linux-headers-2.6.26-2-common_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-19_i386.deb linux-headers-2.6.26-2-openvz-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-openvz-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-19_i386.deb linux-headers-2.6.26-2-vserver-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-vserver-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-xen-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-xen-686_2.6.26-19_i386.deb linux-image-2.6.26-2-486_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-486_2.6.26-19_i386.deb linux-image-2.6.26-2-686-bigmem_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-686-bigmem_2.6.26-19_i386.deb linux-image-2.6.26-2-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-686_2.6.26-19_i386.deb linux-image-2.6.26-2-amd64_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-19_i386.deb linux-image-2.6.26-2-openvz-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-openvz-686_2.6.26-19_i386.deb linux-image-2.6.26-2-vserver-686-bigmem_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-vserver-686-bigmem_2.6.26-19_i386.deb linux-image-2.6.26-2-vserver-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-vserver-686_2.6.26-19_i386.deb linux-image-2.6.26-2-xen-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-xen-686_2.6.26-19_i386.deb linux-libc-dev_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.26-19_i386.deb linux-manual-2.6.26_2.6.26-19_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.26_2.6.26-19_all.deb linux-modules-2.6.26-2-xen-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-modules-2.6.26-2-xen-686_2.6.26-19_i386.deb linux-patch-debian-2.6.26_2.6.26-19_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-19_all.deb linux-source-2.6.26_2.6.26-19_all.deb to pool/main/l/linux-2.6/linux-source-2.6.26_2.6.26-19_all.deb linux-support-2.6.26-2_2.6.26-19_all.deb to pool/main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-19_all.deb linux-tree-2.6.26_2.6.26-19_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.26_2.6.26-19_all.deb xen-linux-system-2.6.26-2-xen-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/xen-linux-system-2.6.26-2-xen-686_2.6.26-19_i386.deb Override entries for your package: linux-2.6_2.6.26-19.dsc - optional devel linux-doc-2.6.26_2.6.26-19_all.deb - optional doc linux-headers-2.6.26-2-486_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-686-bigmem_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-686_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-all-i386_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-all_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-amd64_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-common-openvz_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-common-vserver_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-common-xen_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-common_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-openvz-686_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-19_i386.deb - optional devel linux-headers-2.6.26-2-vserver-686_2.6.26-19_i386.deb - optional
Bug#537771: marked as done (HP ML150G2 : kernel 2.6.26-2-686-bigmem, module aacraid crashing)
Your message dated Wed, 19 Aug 2009 19:58:44 + with message-id and subject line Bug#537771: fixed in linux-2.6 2.6.26-19 has caused the Debian Bug report #537771, regarding HP ML150G2 : kernel 2.6.26-2-686-bigmem, module aacraid crashing 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.) -- 537771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-2-686-bigmem Version: 2.6.26-15lenny3 Hi, I've been working with this server for nearly 3 years, without any problem. Yesterday I tried to upgrade it to Lenny. No problem with the base kernel (2.6.26-2-686) : it just works perfectly. But of course it cannot take advantage of the 8 Gb installed. So I tried to install the "bigmem" kernel. It just refuses to boot ; I get thousand of messages like : "aac_srb: aac_fib_send failed with status: 8195". And it finally drops into busybox, from where I have access to nothing. It seems to be an aacraid problem, but it sounds very strange since the "basic" kernel works like a charm ? --- End Message --- --- Begin Message --- Source: linux-2.6 Source-Version: 2.6.26-19 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.26-19.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.26-19.diff.gz linux-2.6_2.6.26-19.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.26-19.dsc linux-doc-2.6.26_2.6.26-19_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.26_2.6.26-19_all.deb linux-headers-2.6.26-2-486_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-486_2.6.26-19_i386.deb linux-headers-2.6.26-2-686-bigmem_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-686-bigmem_2.6.26-19_i386.deb linux-headers-2.6.26-2-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-all-i386_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-all-i386_2.6.26-19_i386.deb linux-headers-2.6.26-2-all_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-19_i386.deb linux-headers-2.6.26-2-amd64_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-19_i386.deb linux-headers-2.6.26-2-common-openvz_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-19_i386.deb linux-headers-2.6.26-2-common-vserver_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-19_i386.deb linux-headers-2.6.26-2-common-xen_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-19_i386.deb linux-headers-2.6.26-2-common_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-19_i386.deb linux-headers-2.6.26-2-openvz-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-openvz-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-vserver-686-bigmem_2.6.26-19_i386.deb linux-headers-2.6.26-2-vserver-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-vserver-686_2.6.26-19_i386.deb linux-headers-2.6.26-2-xen-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.26-2-xen-686_2.6.26-19_i386.deb linux-image-2.6.26-2-486_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-486_2.6.26-19_i386.deb linux-image-2.6.26-2-686-bigmem_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-686-bigmem_2.6.26-19_i386.deb linux-image-2.6.26-2-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-686_2.6.26-19_i386.deb linux-image-2.6.26-2-amd64_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-19_i386.deb linux-image-2.6.26-2-openvz-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-openvz-686_2.6.26-19_i386.deb linux-image-2.6.26-2-vserver-686-bigmem_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-vserver-686-bigmem_2.6.26-19_i386.deb linux-image-2.6.26-2-vserver-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-vserver-686_2.6.26-19_i386.deb linux-image-2.6.26-2-xen-686_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.26-2-xen-686_2.6.26-19_i386.deb linux-libc-dev_2.6.26-19_i386.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.26-19_i386.deb linux-manual-2.6.26_2.6.26-19_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.26_2.6.26-19_
Bug#434722: marked as done (linux-image-2.6.18-4-686: touchpad is not detected correct)
Your message dated Wed, 19 Aug 2009 19:58:44 + with message-id and subject line Bug#434722: fixed in linux-2.6 2.6.26-19 has caused the Debian Bug report #434722, regarding linux-image-2.6.18-4-686: touchpad is not detected correct 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.) -- 434722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.18-4-686 Version: 2.6.18.dfsg.1-12etch2 Severity: normal After upgrading my notebook from sarge to etch special touchpad features like scrolling with fingers didn't work any longer. I was able to track down the problem to the psmouse module, which is not able to detect my touchpad correct. Instead it detects only a generic PS/2 mouse: atpcvc8c:/home/gerald# dmesg | grep input input: AT Translated Set 2 keyboard as /class/input/input0 input: USB Mouse as /class/input/input1 input: USB HID v1.00 Mouse [USB Mouse] on usb-:00:1d.1-2 drivers/usb/input/hid-core.c: v2.6:USB HID core driver input: PS/2 Generic Mouse as /class/input/input2 input: PC Speaker as /class/input/input3 I tried to load the psmouse module with different parameters like proto=exps, but nothing helped. I also tried to set the correct protocol manually, but the driver seems to think that it is smarter than the user and ignores my request: atpcvc8c:/home/gerald# echo -n "SynPS/2" > /sys/devices/platform/i8042/serio3/protocol atpcvc8c:/home/gerald# dmesg | grep input input: AT Translated Set 2 keyboard as /class/input/input0 input: USB Mouse as /class/input/input1 input: USB HID v1.00 Mouse [USB Mouse] on usb-:00:1d.1-2 drivers/usb/input/hid-core.c: v2.6:USB HID core driver input: PS/2 Generic Mouse as /class/input/input2 input: PC Speaker as /class/input/input3 input: PS/2 Generic Mouse as /class/input/input4 Only when I touch on my touchpad and then try to set the protocol manually, it works: atpcvc8c:/home/gerald# echo -n "SynPS/2" > /sys/devices/platform/i8042/serio3/protocol atpcvc8c:/home/gerald# dmesg | grep input atpcvc8c:/home/gerald# dmesg | tail [drm] Initialized drm 1.0.1 20051102 ACPI: PCI Interrupt :00:02.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 [drm] Initialized i915 1.5.0 20060119 on minor 0 [drm] Initialized i915 1.5.0 20060119 on minor 1 eth1: no IPv6 routers present input: PS/2 Generic Mouse as /class/input/input4 Synaptics Touchpad, model: 1, fw: 5.9, id: 0x8f8eb1, caps: 0xa04793/0x102000 serio: Synaptics pass-through port at isa0060/serio4/input0 input: SynPS/2 Synaptics TouchPad as /class/input/input5 input: PS/2 Generic Mouse as /class/input/input6 Please feel free to contact me if you need more information. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-4-686 depends on: ii coreutils 5.97-5.3 The GNU core utilities ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii initramfs-tools [linux-initra 0.85g tools for generating an initramfs ii module-init-tools 3.3-pre4-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-4-686 recommends: ii libc6-i686 2.3.6.ds1-13 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.18-4-686/preinst/failed-to-move-modules-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/lilo-initrd-2.6.18-4-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-686/preinst/elilo-initrd-2.6.18-4-686: true linux-image-2.6.18-4-686/preinst/overwriting-modules-2.6.18-4-686: true linux-image-2.6.18-4-686/prerm/removing-running-kernel-2.6.18-4-686: true linux-image-2.6.18-4-686/prerm/would-invalidate-boot-loader-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/bootloader-test-error-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/abort-overwrite-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/old-system-map-link-2.6.18-4-686: true linux-image-2.6.18-4-686/postinst/depmod-error-2.6.18-4-686: false linux-image-2.6.18-4-686/preinst/abort-install-2.6.18-4-686: linux-image-2.6.18-4-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-686/postinst/bootloader-error-2.6.18-4-686: linux-image-2.6.18-4-686/postinst/depmod-error-initrd-2.6.18-4-686: false linux-image-2.6.18-4-686/postinst/old-initrd-link-2.6.18-4-686: true li
Processed: bug 451297 is forwarded to http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1097
Processing commands for cont...@bugs.debian.org: > forwarded 451297 http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1097 Bug #451297 [linux-2.6] linux-image-2.6.18-5-xen-686: kernel page allocation failure causes networking freeze Set Bug forwarded-to-address to 'http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1097'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542358: linux-image-2.6.30-1-686: "e100" module refuses to load
On Wed, 2009-08-19 at 10:28 +0200, Jan Prunk wrote: > Package: linux-image-2.6.30-1-686 > Version: 2.6.30-5 > Severity: normal > > Hello ! > > I have recently upgraded the kernel to 2.6.30 (squeeze) from a running 2.6.26. > During the upgrade I got this error: > > Setting up linux-image-2.6.30-1-686 (2.6.30-5) ... > Running depmod. > Running update-initramfs. > update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 > W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module > e100 > W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module > e100 > W: Possible missing firmware /lib/firmware/e100/d101m_ucode.bin for module > e100 > Running update-grub. > > In 2.6.26 kernel the dmesg will tell me: > [ 10.884256] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex > [ 10.888710] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > Which enables the "e100" module to be working. > > However in 2.6.30 I cannot connect anymore to the machine over the internet, > I assume > that it is becouse of this ethernet module which I am using. The machine > seems to boot > into 2.6.30 and then it hangs there. I cannot investigate any further, > becouse of the > remote access. Does the kernel log show "Failed to load firmware"? If so then you will need to install the (non-free) firmware-linux package. Ben. -- Ben Hutchings If at first you don't succeed, you're doing about average. signature.asc Description: This is a digitally signed message part
Processed: reassign 516479 to src:linux-2.6, reassign 542250 to src:linux-2.6, forcibly merging 516479 542250 ...
Processing commands for cont...@bugs.debian.org: > reassign 516479 src:linux-2.6 Bug #516479 [src:linux-2.6] linux-image-2.6.26-1-xen-amd64: kernel-panic in xen_spin_wait an mutlicore dom0 with high load, not interruption save? Bug #542250 [src:linux-2.6] repeatable crashes while copying 500G from NFS mount to local logical volume Ignoring request to reassign bug #516479 to the same package Ignoring request to reassign bug #542250 to the same package > reassign 542250 src:linux-2.6 Bug #542250 [src:linux-2.6] repeatable crashes while copying 500G from NFS mount to local logical volume Bug #516479 [src:linux-2.6] linux-image-2.6.26-1-xen-amd64: kernel-panic in xen_spin_wait an mutlicore dom0 with high load, not interruption save? Ignoring request to reassign bug #542250 to the same package Ignoring request to reassign bug #516479 to the same package > forcemerge 516479 542250 Bug#516479: linux-image-2.6.26-1-xen-amd64: kernel-panic in xen_spin_wait an mutlicore dom0 with high load, not interruption save? Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume Forcibly Merged 516479 542250. > found 516479 2.6.26-13 Bug #516479 [src:linux-2.6] linux-image-2.6.26-1-xen-amd64: kernel-panic in xen_spin_wait an mutlicore dom0 with high load, not interruption save? Bug #542250 [src:linux-2.6] repeatable crashes while copying 500G from NFS mount to local logical volume Ignoring request to alter found versions of bug #516479 to the same values previously set Ignoring request to alter found versions of bug #542250 to the same values previously set > found 542250 2.6.26-17lenny2 Bug #542250 [src:linux-2.6] repeatable crashes while copying 500G from NFS mount to local logical volume Bug #516479 [src:linux-2.6] linux-image-2.6.26-1-xen-amd64: kernel-panic in xen_spin_wait an mutlicore dom0 with high load, not interruption save? The source linux-2.6 and version do not appear to match any binary packages Ignoring request to alter found versions of bug #542250 to the same values previously set Ignoring request to alter found versions of bug #516479 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: reassign 516479 to src:linux-2.6, reassign 542250 to src:linux-2.6, forcibly merging 516479 542250 ...
Processing commands for cont...@bugs.debian.org: > reassign 516479 src:linux-2.6 Bug #516479 [linux-image-2.6.26-1-xen-amd64] linux-image-2.6.26-1-xen-amd64: kernel-panic in xen_spin_wait an mutlicore dom0 with high load, not interruption save? Bug reassigned from package 'linux-image-2.6.26-1-xen-amd64' to 'src:linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.26-13. > reassign 542250 src:linux-2.6 Bug #542250 [linux-image-2.6.26-2-xen-amd64] repeatable crashes while copying 500G from NFS mount to local logical volume Bug reassigned from package 'linux-image-2.6.26-2-xen-amd64' to 'src:linux-2.6'. Bug No longer marked as found in versions 2.6.26-17lenny2. > forcemerge 516479 542250 Bug#516479: linux-image-2.6.26-1-xen-amd64: kernel-panic in xen_spin_wait an mutlicore dom0 with high load, not interruption save? Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume Forcibly Merged 516479 542250. > found 516479 2.6.26-13 Bug #516479 [src:linux-2.6] linux-image-2.6.26-1-xen-amd64: kernel-panic in xen_spin_wait an mutlicore dom0 with high load, not interruption save? Bug #542250 [src:linux-2.6] repeatable crashes while copying 500G from NFS mount to local logical volume Bug Marked as found in versions linux-2.6/2.6.26-13. Bug Marked as found in versions linux-2.6/2.6.26-13. > found 542250 2.6.26-17lenny2 Bug #542250 [src:linux-2.6] repeatable crashes while copying 500G from NFS mount to local logical volume Bug #516479 [src:linux-2.6] linux-image-2.6.26-1-xen-amd64: kernel-panic in xen_spin_wait an mutlicore dom0 with high load, not interruption save? The source linux-2.6 and version do not appear to match any binary packages Bug Marked as found in versions linux-2.6/2.6.26-17lenny2. Bug Marked as found in versions linux-2.6/2.6.26-17lenny2. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
On Wed, 2009-08-19 at 22:36 +0400, Nikita V. Youshchenko wrote:
> tags 542250 +patch
> thanks
>
> > ... I may guess that line 74 should check for in_interrupt() instead of
> > in_softirq().
>
> I've tried that and it really fixed the problem. Server already runs the
> same backup procedure for several hours. Previously it crashed within 15
> minutes.
>
> Here is the patch I've applied:
>
> --- a/drivers/xen/core/spinlock.c 2009-08-19 16:20:17.0 +0400
> +++ b/drivers/xen/core/spinlock.c 2009-08-19 17:36:55.0 +0400
> @@ -71,7 +71,7 @@
> BUG_ON(__get_cpu_var(spinning_bh).lock == lock);
> spinning = &__get_cpu_var(spinning_irq);
> } else {
> - BUG_ON(!in_softirq());
> + BUG_ON(!in_interrupt());
> spinning = &__get_cpu_var(spinning_bh);
> }
> BUG_ON(spinning->lock);
I'm glad it works for you, but it isn't a proper fix.
Ben.
--
Ben Hutchings
If at first you don't succeed, you're doing about average.
signature.asc
Description: This is a digitally signed message part
Processed: tagging 542250
Processing commands for cont...@bugs.debian.org: > tags 542250 - patch Bug #542250 [src:linux-2.6] repeatable crashes while copying 500G from NFS mount to local logical volume Bug #516479 [src:linux-2.6] linux-image-2.6.26-1-xen-amd64: kernel-panic in xen_spin_wait an mutlicore dom0 with high load, not interruption save? Removed tag(s) patch. Removed tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 541702
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny3 > tags 541702 + pending Bug #541702 [src:linux-2.6] Should warn about missing firmware on upgrade Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume
> On Wed, 2009-08-19 at 22:36 +0400, Nikita V. Youshchenko wrote:
> > tags 542250 +patch
> > thanks
> >
> > > ... I may guess that line 74 should check for in_interrupt() instead
> > > of in_softirq().
> >
> > I've tried that and it really fixed the problem. Server already runs
> > the same backup procedure for several hours. Previously it crashed
> > within 15 minutes.
> >
> > Here is the patch I've applied:
> >
> > --- a/drivers/xen/core/spinlock.c 2009-08-19 16:20:17.0
> > +0400 +++ b/drivers/xen/core/spinlock.c 2009-08-19
> > 17:36:55.0 +0400 @@ -71,7 +71,7 @@
> > BUG_ON(__get_cpu_var(spinning_bh).lock ==
> > lock); spinning = &__get_cpu_var(spinning_irq); } else {
> > - BUG_ON(!in_softirq());
> > + BUG_ON(!in_interrupt());
> > spinning = &__get_cpu_var(spinning_bh);
> > }
> > BUG_ON(spinning->lock);
>
> I'm glad it works for you, but it isn't a proper fix.
Could you please explain? How that code line cod hit if not in interrupt
handler?
Here is my understanding of the logic of that code. They try to track
spinlocks CPU currently spins at. CPU spinning may be interrupted only by
irq. There "normal" (not SA_NODELAY) interrupt handlers can't be active at
the same CPU at the same time. That leads to maximum 3 spinings:
- one from process context,
- one from "normal" irq handler that interrupted that process context,
- and one from SA_NODELAY irq handler that interrupted normal irq handler.
This one can't be interrupted since it runs with interrupts disabled.
If such, the code path in question corresponds to "normal" interrupt
handler starting to spin. Thus it should be in_interrupt().
How this is wrong?
Perhaps softirq handler could be activated at exit of the "normal" handler?
Maybe better check is BUG_ON(!in_interrupt() && !in_softrq()). Need to
check the code ...
Nikita
signature.asc
Description: This is a digitally signed message part.
