Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.
On Thu, Nov 02, 2023 at 03:37:39PM +0100, Diederik de Haas wrote: > Control: tag -1 moreinfo > > On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz wrote: > > Package: src:linux > > Version: 6.1.27-1 > > Can you try with the latest version in the 6.1.x series to see if the problem > is still there? As I need to setup ASAP the servers in production I do not know if I have time in the next days. It works with backports kernels. The latest kernels I tested were: Fail : Linux afs31 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.37-1 (2023-07-03) x86_64 GNU/Linux OK : Linux afs31 6.4.0-0.deb12.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.4.4-3~bpo12+1 (2023-08-08) x86_64 GNU/Linux > > > On this hardware I am chasing a data corruption for several months on > > Debian V11 and Debian v12. Now that I was pointed that linux kernel > > had some problems with XFS solved in later 6.3 kernel I can reproduce > > the problem. > > > > It seams the problem went away with current Debian testing kernel: > > > > ii linux-image-6.3.0-1-amd646.3.7-1 amd64Linux 6.3 > > for 64-bit PCs (signed) > > > > Is there anyone willing to backport the XFS fixes into > > linux-image-6.1.0 and linux-image-5.10.0? > > If the problem is still present in the latest 6.1 kernel, then you need to > find > out which patch(es) actually fix the problem. > The easiest way to start with that is to find the last kernel which exhibits > the issue and then the first one where it is fixed. > https://snapshot.debian.org/binary/linux-image-amd64/ should help > with that. The bug is present on Debian v11 too. So is an old bug with fixes on kernel 6.2 rc something. > > When the range has been narrowed, a `git bisect` should identify the specific > commit(s) which fixes the issue. > https://wiki.debian.org/DebianKernel/GitBisect should help with that > > When that/those have been identified, it should be reported to the upstream > kernel so that they can incorporate those fixes in their LTS kernel(s) which > Debian then will pick up automatically. > > HTH -- -- A vida feliz, meu Deus, consiste em nos alegrarmos em vos, de vos e por vos signature.asc Description: PGP signature
Bug#1032391: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.
Hi, After some research it was found the problem was not HW related, but related with XFS driver and is present until linux 6.1. So I opened new bug report on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040416 Kind regards Jose M Calhariz -- -- A vida feliz, meu Deus, consiste em nos alegrarmos em vos, de vos e por vos signature.asc Description: PGP signature
Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.
Hi On Thu, Nov 02, 2023 at 07:40:38PM +0100, Diederik de Haas wrote: > > On Thursday, 2 November 2023 18:03:25 CET Jose M Calhariz wrote: > > On Thu, Nov 02, 2023 at 03:37:39PM +0100, Diederik de Haas wrote: > > > On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz wrote: > > > > Package: src:linux > > > > Version: 6.1.27-1 > > > > > > Can you try with the latest version in the 6.1.x series to see if the > > > problem is still there? > > > > As I need to setup ASAP the servers in production I do not know if I > > have time in the next days. It works with backports kernels. > > No problem. > > > The latest kernels I tested were: > > Fail : Linux afs31 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.37-1 > > (2023-07-03) x86_64 GNU/Linux > > Ok. Please test (when you have time) 6.1.55-1. Fail : Linux afs31 6.1.0-0-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1~rc3-1~exp1 (2022-11-02) x86_64 GNU/Linux Fail : Linux afs31 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux Done. I tested even the first 6.1 on Debian. Both of them failed. > Also verify if it's also present in 6.1~rc3-1~exp1 to make sure it's present > in the whole 6.1 series. > Use https://snapshot.debian.org/binary/linux-image-amd64/ to get it/them. > > If the bug is NOT present in either the latest or the first, then try other > versions till you find the last one that work and the first one that fails. > > > OK : Linux afs31 6.4.0-0.deb12.2-amd64 #1 SMP PREEMPT_DYNAMIC Debian > > 6.4.4-3~bpo12+1 (2023-08-08) x86_64 GNU/Linux > > It was fixed in 6.3.7-1, so it was expected that a later versions also works. > But let's ignore bpo as it likely won't provide useful data points. > > Unfortunately there isn't a 6.2 kernel uploaded to the Debian archive and > thus > not available on snapshot.d.o, but testing 6.3.1-1~exp1 should be useful. > > > The bug is present on Debian v11 too. So is an old bug with fixes on > > kernel 6.2 rc something. > > I'd recommend to focus first on the 6.1 series for now. > If at a later point testing with 5.10 may be useful, we can do that then. Kind regards Jose M Calhariz -- -- A vida feliz, meu Deus, consiste em nos alegrarmos em vos, de vos e por vos signature.asc Description: PGP signature
Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.
Hi On Tue, Nov 07, 2023 at 08:33:58PM +0100, Diederik de Haas wrote: > Control: found -1 6.1~rc3-1~exp1 > Control: found -1 6.1.55-1 > > On Saturday, 4 November 2023 20:35:43 CET Jose M Calhariz wrote: > > > Ok. Please test (when you have time) 6.1.55-1. > > > > Fail : Linux afs31 6.1.0-0-amd64 #1 SMP PREEMPT_DYNAMIC Debian > > 6.1~rc3-1~exp1 (2022-11-02) x86_64 GNU/Linux > > > > Fail : Linux afs31 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 > > (2023-09-29) x86_64 GNU/Linux > > > > Done. I tested even the first 6.1 on Debian. Both of them failed. > > Thanks, updated metadata accordingly. > So now we know it's indeed present in the whole 6.1 series. > > > > Unfortunately there isn't a 6.2 kernel uploaded to the Debian archive and > > > thus not available on snapshot.d.o, but testing 6.3.1-1~exp1 should be > > > useful. > > Please test with with 6.3.1-1~exp1 to make sure it was fixed then (too). > > Unfortunately, the commit list between 6.1 and 6.3.1 is quite large: > me@pc:~/dev/kernel.org/linux$ git log --oneline v6.1..v6.3.1 -- fs/xfs | wc -l > 159 > > If that list was small, I could've suggested to try 'backporting' a couple of > patches, but that avenue seems rather pointless in this case. > > It's probably also useful to verify whether it's also present in the whole > 5.10 series, which should give (even) more data points. > > I think the next step should be to 'forward' this bug report to the upstream > mailing list at linux-...@vger.kernel.org I do not follow closely linux-xfs mailing list, but I think other people already reported problems with 6.1 and are trying to do the effort of delimiting the patch and test a backport to 6.1. Kind regards Jose M Calhariz -- -- Egoista, s. m. Um sujeito mais interessado em si próprio que em mim. -- Ambrose Bierce signature.asc Description: PGP signature
Bug#785564: initramfs-tools: Boot fails do to missing switch_root
Package: initramfs-tools Version: 0.120 Severity: normal If busybox is not installed and the option is BUSYBOX=y the system don't boot. Where the previous initramfs-tools could generate a bootable initrd image. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 3.0M Apr 26 2004 /boot/initrd.img-2.4.18-1-586tsc -rw-r--r-- 1 root root 4.8M Jun 16 2006 /boot/initrd.img-2.6.16-1-486.bak -rw-r--r-- 1 root root 4.8M Oct 30 2006 /boot/initrd.img-2.6.16-2-486.bak -rw-r--r-- 1 root root 5.2M Apr 6 2007 /boot/initrd.img-2.6.16-2-686-smp.bak -rw-r--r-- 1 root root 6.4M Mar 7 2010 /boot/initrd.img-2.6.18-6-486 -rw-r--r-- 1 root root 5.1M Jan 25 2010 /boot/initrd.img-2.6.18-6-486.bak -rw-r--r-- 1 root root 7.4M May 16 2011 /boot/initrd.img-2.6.26-2-486 -rw-r--r-- 1 root root 7.4M Mar 15 2010 /boot/initrd.img-2.6.26-2-486.bak -rw-r--r-- 1 root root 7.4M May 17 2011 /boot/initrd.img-2.6.26-2-686 -rw-r--r-- 1 root root 9.4M Jun 2 2013 /boot/initrd.img-2.6.32-5-486 -rw-r--r-- 1 root root 9.4M Jun 2 2013 /boot/initrd.img-2.6.32-5-686 -rw-r--r-- 1 root root 9.5M Jun 2 2013 /boot/initrd.img-2.6.32-5-amd64 -rw-r--r-- 1 root root 9.4M Jun 2 2013 /boot/initrd.img-2.6.32-5-openvz-686 -rw-r--r-- 1 root root 8.9M Jan 29 2012 /boot/initrd.img-2.6.32-bpo.5-686 -rw-r--r-- 1 root root 8.9M Oct 16 2011 /boot/initrd.img-2.6.32-bpo.5-686.bak -rw-r--r-- 1 root root 13M Jan 1 2014 /boot/initrd.img-3.11-0.bpo.2-486 -rw-r--r-- 1 root root 13M Jan 1 2014 /boot/initrd.img-3.11-0.bpo.2-686-pae -rw-r--r-- 1 root root 13M Jan 1 2014 /boot/initrd.img-3.11-0.bpo.2-686-pae.bak -rw-r--r-- 1 root root 13M Jan 1 2014 /boot/initrd.img-3.11-0.bpo.2-amd64 -rw-r--r-- 1 root root 14M Mar 2 2014 /boot/initrd.img-3.12-0.bpo.1-686-pae -rw-r--r-- 1 root root 14M Mar 2 2014 /boot/initrd.img-3.12-0.bpo.1-amd64 -rw-r--r-- 1 root root 14M Aug 9 2014 /boot/initrd.img-3.13-0.bpo.1-amd64 -rw-r--r-- 1 root root 14M Jun 22 2014 /boot/initrd.img-3.13-0.bpo.1-amd64.bak -rw-r--r-- 1 root root 15M Sep 7 2014 /boot/initrd.img-3.14-0.bpo.2-amd64 -rw-r--r-- 1 root root 15M Oct 11 2014 /boot/initrd.img-3.16-0.bpo.2-amd64 -rw-r--r-- 1 root root 15M Jan 24 19:29 /boot/initrd.img-3.16-0.bpo.3-amd64 -rw-r--r-- 1 root root 15M Nov 27 23:16 /boot/initrd.img-3.16-0.bpo.3-amd64.bak -rw-r--r-- 1 root root 17M May 16 21:26 /boot/initrd.img-3.16.0-0.bpo.4-amd64 -rw-r--r-- 1 root root 16M May 3 17:20 /boot/initrd.img-3.16.0-0.bpo.4-amd64.bak -rw-r--r-- 1 root root 18M May 17 12:21 /boot/initrd.img-3.16.0-4-586 -rw-r--r-- 1 root root 18M May 17 12:22 /boot/initrd.img-3.16.0-4-686-pae -rw-r--r-- 1 root root 17M May 17 20:32 /boot/initrd.img-3.16.0-4-amd64 -rw-r--r-- 1 root root 17M May 16 21:37 /boot/initrd.img-3.16.0-4-amd64.bak -rw-r--r-- 1 root root 11M Sep 22 2012 /boot/initrd.img-3.2.0-0.bpo.3-amd64 -rw-r--r-- 1 root root 11M Sep 15 2012 /boot/initrd.img-3.2.0-0.bpo.3-amd64.bak -rw-r--r-- 1 root root 11M Sep 23 2012 /boot/initrd.img-3.2.0-3-486 -rw-r--r-- 1 root root 11M Oct 28 2012 /boot/initrd.img-3.2.0-3-686-pae -rw-r--r-- 1 root root 11M Sep 23 2012 /boot/initrd.img-3.2.0-3-686-pae.bak -rw-r--r-- 1 root root 11M Sep 22 2012 /boot/initrd.img-3.2.0-3-amd64 -rw-r--r-- 1 root root 13M May 3 17:21 /boot/initrd.img-3.2.0-4-486 -rw-r--r-- 1 root root 13M May 3 17:21 /boot/initrd.img-3.2.0-4-686-pae -rw-r--r-- 1 root root 11M Dec 21 2013 /boot/initrd.img-3.2.0-4-686-pae.bak -rw-r--r-- 1 root root 13M May 3 17:21 /boot/initrd.img-3.2.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=/dev/sda2 ro printk.time=n hpet=force -- resume # RESUME=/dev/hda2 RESUME='UUID=3be4d10b:9bcd6eda:770c01a5:90fe33e3' -- /proc/filesystems btrfs ext3 ext2 ext4 fuseblk vfat xfs -- lsmod Module Size Used by cfg80211 405538 0 bnep 17431 2 cpufreq_stats 12782 0 cpufreq_conservative14184 0 cpufreq_userspace 12525 0 bluetooth 374429 5 bnep 6lowpan_iphc 16588 1 bluetooth rfkill 18867 3 cfg80211,bluetooth cpufreq_powersave 12454 0 sit25982 0 tunnel412629 1 sit ip_tunnel 21463 1 sit binfmt_misc16949 1 nfsd 263032 13 auth_rpcgss51211 1 nfsd oid_registry 12419 1 auth_rpcgss nfs_acl12511 1 nfsd nfs 188136 0 lockd 83389 2 nfs,nfsd fscache45542 1 nfs sunrpc237402 19 nfs,nfsd,auth_rpcgss,lockd,nfs_acl xt_multiport 12518 0 xt_LOG 17171 1 ipt_MASQUERADE 12594 1 xt_tcpudp 12527 18 nf_nat_tftp12422 0 nft_nat12507 0 nf_nat_proto_udplite12489 0 nf_nat_proto_dccp 12480 0 nf_nat_proto_sctp 12563 0 nf_nat_amanda 12424 0 xt_
Bug#711202: linux-image-3.2.0-4-amd64: e1000e Detected Hardware Unit Hang only on kernel 3.2
Package: src:linux Version: 3.2.41-2+deb7u2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? The openafs fileserver, under normal workload, the kernel says: Jun 4 13:33:25 tania kernel: e1000e :06:00.0: eth0: Detected Hardware Unit Hang: Jun 4 13:33:25 tania kernel: TDH <93> Jun 4 13:33:25 tania kernel: TDT <96> Jun 4 13:33:25 tania kernel: next_to_use <96> Jun 4 13:33:25 tania kernel: next_to_clean<92> Jun 4 13:33:25 tania kernel: buffer_info[next_to_clean]: Jun 4 13:33:25 tania kernel: time_stamp <10532d958> Jun 4 13:33:25 tania kernel: next_to_watch<93> Jun 4 13:33:25 tania kernel: jiffies <10532db0b> Jun 4 13:33:25 tania kernel: next_to_watch.status <0> Jun 4 13:33:25 tania kernel: MAC Status <80080783> Jun 4 13:33:25 tania kernel: PHY Status <796d> Jun 4 13:33:25 tania kernel: PHY 1000BASE-T Status <7800> Jun 4 13:33:25 tania kernel: PHY Extended Status<3000> Jun 4 13:33:25 tania kernel: PCI Status <10> Jun 4 13:33:27 tania kernel: e1000e :06:00.0: eth0: Detected Hardware Unit Hang: Jun 4 13:33:27 tania kernel: TDH <93> Jun 4 13:33:27 tania kernel: TDT <96> Jun 4 13:33:27 tania kernel: next_to_use <96> Jun 4 13:33:27 tania kernel: next_to_clean<92> Jun 4 13:33:27 tania kernel: buffer_info[next_to_clean]: Jun 4 13:33:27 tania kernel: time_stamp <10532d958> Jun 4 13:33:27 tania kernel: next_to_watch<93> Jun 4 13:33:27 tania kernel: jiffies <10532dcff> Jun 4 13:33:27 tania kernel: next_to_watch.status <0> Jun 4 13:33:27 tania kernel: MAC Status <80080783> Jun 4 13:33:27 tania kernel: PHY Status <796d> Jun 4 13:33:27 tania kernel: PHY 1000BASE-T Status <7800> Jun 4 13:33:27 tania kernel: PHY Extended Status<3000> Jun 4 13:33:27 tania kernel: PCI Status <10> Jun 4 13:33:29 tania kernel: e1000e :06:00.0: eth0: Detected Hardware Unit Hang: Jun 4 13:33:29 tania kernel: TDH <93> Jun 4 13:33:29 tania kernel: TDT <96> Jun 4 13:33:29 tania kernel: next_to_use <96> Jun 4 13:33:29 tania kernel: next_to_clean<92> Jun 4 13:33:29 tania kernel: buffer_info[next_to_clean]: Jun 4 13:33:29 tania kernel: time_stamp <10532d958> Jun 4 13:33:29 tania kernel: next_to_watch<93> Jun 4 13:33:29 tania kernel: jiffies <10532def3> Jun 4 13:33:29 tania kernel: next_to_watch.status <0> Jun 4 13:33:29 tania kernel: MAC Status <80080783> Jun 4 13:33:29 tania kernel: PHY Status <796d> Jun 4 13:33:29 tania kernel: PHY 1000BASE-T Status <7800> Jun 4 13:33:29 tania kernel: PHY Extended Status<3000> Jun 4 13:33:29 tania kernel: PCI Status <10> Jun 4 13:33:31 tania kernel: e1000e :06:00.0: eth0: Detected Hardware Unit Hang: Jun 4 13:33:31 tania kernel: TDH <93> Jun 4 13:33:31 tania kernel: TDT <96> Jun 4 13:33:31 tania kernel: next_to_use <96> Jun 4 13:33:31 tania kernel: next_to_clean<92> Jun 4 13:33:31 tania kernel: buffer_info[next_to_clean]: Jun 4 13:33:31 tania kernel: time_stamp <10532d958> Jun 4 13:33:31 tania kernel: next_to_watch<93> Jun 4 13:33:31 tania kernel: jiffies <10532e0e7> Jun 4 13:33:31 tania kernel: next_to_watch.status <0> Jun 4 13:33:31 tania kernel: MAC Status <80080783> Jun 4 13:33:31 tania kernel: PHY Status <796d> Jun 4 13:33:31 tania kernel: PHY 1000BASE-T Status <7800> Jun 4 13:33:31 tania kernel: PHY Extended Status<3000> Jun 4 13:33:31 tania kernel: PCI Status <10> Jun 4 13:33:31 tania kernel: e1000e :06:00.0: eth0: Reset adapter Jun 4 13:33:35 tania kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None This bug is diferent than the bug 657689. This bug is not seen on older Debian stable kernels, from squeeze or etch. As a workaround the kernel was booted with option pcie_aspm=off. The kernel taint is from the openafs client module. * What exactly did you do (or not do) that was effective (or ineffective)? As a workaround the kernel was booted with option pcie_aspm=off, but the results are the same. The kernel information is from the boot with pcie_aspm=off. -- 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=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=286f18e7-33e5-4598-a37f-139157b0207d ro console=ttyS1,115200n8 console=tty0 printk.time=n pcie_aspm=off ** Tainted: PWO (4609) * Proprietary module has been loaded. * Taint on
Bug#680366: linux-image-3.2.0-0.bpo.2-amd64: md raid6 deadlock on write
Package: src:linux Version: 3.2.20-1~bpo60+1 Severity: important Tags: upstream We have a group of servers with a LVM over a RAID6 of 16 drives. During normal work loads, sometimes, the md raid enter on deadlock for writes and only a power off/power on allows to recover the machine. The raid was created some time ago with something like: mdadm --create /dev/md2 --level=6 -n=16 /dev/sd[a-p] Following an old discussion on this list http://www.spinics.net/lists/raid/msg37708.html. And another discussion http://marc.info/?l=linux-raid&m=134126754029228&w=4 The back ported kernel 3.2.0 for squeeze is affected by this and it's possible to confirm that running the fio command can make the raid enter on deadlock. The command used was: fio --name=global --rw=randwrite --size=1G --bsrange=1k-128k \ --filename=/dev/md2 --name=job1 --name=job2 --name=job3 --name=job4 \ --end_fsync=1 I have been doing tests to see what kernels where affected by this bug. For the deadlock by running fio on back ported 3.2.0 was observed on the raid: - increasing the stripe_cache_size would allow some extra IO. This problem was found in back ported kernel 3.2.0 for squeeze and in the vanilla kernels 3.4.0, 3.4.0-rc2, 3.2.0. The Debian kernel 2.6.32 seams to be immune. It's under investigation if a possible fix is now in the Linus git tree. Jose Calhariz -- Package-specific info: ** Version: Linux version 3.2.0-0.bpo.2-amd64 (Debian 3.2.20-1~bpo60+1) (debian-kernel@lists.debian.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Fri Jun 29 20:42:29 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-0.bpo.2-amd64 root=UUID=8ceab9f5-8d93-44f1-ac09-c2f0ca118275 ro printk.time=n quiet ** Not tainted ** Kernel log: [] ? writeback_sb_inodes+0x169/0x1ff [] ? __writeback_inodes_wb+0x6d/0xab [] ? wb_writeback+0x128/0x222 [] ? determine_dirtyable_memory+0xd/0x1d [] ? global_dirty_limits+0x29/0x10b [] ? wb_do_writeback+0x1be/0x1de [] ? del_timer_sync+0x34/0x3e [] ? bdi_writeback_thread+0xc3/0x1fe [] ? wb_do_writeback+0x1de/0x1de [] ? wb_do_writeback+0x1de/0x1de [] ? kthread+0x7a/0x82 [] ? kernel_thread_helper+0x4/0x10 [] ? kthread_worker_fn+0x147/0x147 [] ? gs_change+0x13/0x13 INFO: task md2_resync:3145 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. md2_resync D 880037842140 0 3145 2 0x 880037842140 0046 8800 88007d3e5610 00013540 88007c137fd8 88007c137fd8 00013540 880037842140 88007c136010 880037b83000 0001a019c970 Call Trace: [] ? get_active_stripe+0x2ab/0x588 [raid456] [] ? try_to_wake_up+0x190/0x190 [] ? sync_request+0x257/0x1084 [raid456] [] ? lock_timer_base+0x49/0x49 [] ? md_do_sync+0x78a/0xb98 [md_mod] [] ? update_curr+0xbc/0x160 [] ? __switch_to+0x175/0x2b1 [] ? update_curr+0xbc/0x160 [] ? md_thread+0x105/0x123 [md_mod] [] ? md_rdev_init+0xea/0xea [md_mod] [] ? md_rdev_init+0xea/0xea [md_mod] [] ? kthread+0x7a/0x82 [] ? kernel_thread_helper+0x4/0x10 [] ? kthread_worker_fn+0x147/0x147 [] ? gs_change+0x13/0x13 INFO: task fio:4922 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. fio D 88007a290730 0 4922 4917 0x 88007a290730 0082 8800 88007d3a20c0 00013540 88000c61bfd8 88000c61bfd8 00013540 88007a290730 88000c61a010 0046 00017a290730 Call Trace: [] ? get_active_stripe+0x2ab/0x588 [raid456] [] ? __wake_up_common+0x41/0x78 [] ? try_to_wake_up+0x190/0x190 [] ? make_request+0x1b9/0x373 [raid456] [] ? wake_up_bit+0x20/0x20 [] ? T.1024+0x17/0x17 [] ? md_make_request+0xbe/0x1b1 [md_mod] [] ? generic_make_request+0x8e/0xcd [] ? submit_bio+0xd9/0xf7 [] ? T.1024+0x17/0x17 [] ? bio_alloc_bioset+0x44/0xb3 [] ? submit_bh+0xe5/0x105 [] ? __block_write_full_page+0x1dd/0x2b5 [] ? blkdev_max_block+0x2e/0x2e [] ? __writepage+0xa/0x21 [] ? write_cache_pages+0x226/0x31e [] ? set_page_dirty+0x61/0x61 [] ? generic_writepages+0x3e/0x55 [] ? __filemap_fdatawrite_range+0x4b/0x50 [] ? filemap_write_and_wait_range+0x27/0x50 [] ? blkdev_fsync+0x15/0x3a [] ? do_fsync+0x27/0x3b [] ? sys_fsync+0xb/0xf [] ? system_call_fastpath+0x16/0x1b INFO: task flush-9:2:3096 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. flush-9:2 D 88007b2890a0 0 3096 2 0x 88007b2890a0 0046 81013a01 88007c814f60 00013540 88007b103fd8 88007b103fd8 00013540 88007b2890a0 88007b102010 88007b103990 88007b103990 Call Trace: [] ? read_tsc+0x5/0x16 [] ? __lock_page+0x63/0x63 [] ? io_schedule+0x84/0xc3 [] ? sleep_on_page+0x9/0xd [] ? __wait_on_bit_lock+0x3c/0x85 [] ? __block_write_full_page+0x1ed/0x2b5 [] ?
Bug#832925: firmware-atheros: Please add the firmware for the wireless QCA9377 from atheros
Package: firmware-atheros Version: 20160110-1 Severity: normal I have a new laptop Asus E200HA. I was able to use the stretch DVD to install Debian. I found that this package is missing the firmware for the QCA9377. The firmware can be download from "git clone https://github.com/ajaybhatia/Qualcomm-Atheros-QCA9377-Wifi-Linux"; It contains too a driver, but that is not needed on kernel 4.6. The install.sh script is not good for Debian too. lspci 00:00.0 Host bridge: Intel Corporation Braswell SoC Transaction Router (rev 22) 00:02.0 VGA compatible controller: Intel Corporation Braswell PCI Configuration Registers (rev 22) 00:0b.0 Signal processing controller: Intel Corporation Braswell P-Unit Power Management (rev 22) 00:14.0 USB controller: Intel Corporation Braswell USB xHCI Host Controller (rev 22) 00:1a.0 Encryption controller: Intel Corporation Braswell Trusted Execution Engine Interface (rev 22) 00:1c.0 PCI bridge: Intel Corporation Braswell PCIe Port 1 (rev 22) 00:1f.0 ISA bridge: Intel Corporation Braswell Platform Controller Unit LPC (rev 22) 01:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 30) Kind regards Jose M Calhariz -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-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 Init: systemd (via /run/systemd/system) firmware-atheros depends on no packages. firmware-atheros recommends no packages. Versions of packages firmware-atheros suggests: ii initramfs-tools 0.125 -- no debconf information
Bug#833009: linux-image-4.6.0-1-amd64: Hibernation does not work on Asus E200HA because of i915 and i2c_designware
Package: src:linux Version: 4.6.4-1 Severity: normal Tags: upstream I have problems that I can not suspend or hibernate my E200HA. After some reserach I found this Web page: https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues Maybe the suspend is not supported, but the hibernate should, because of this message on kern.log: Jul 28 22:56:00 lal kernel: [0.472724] ACPI: (supports S0 S4 S5) So, doing some extra research I suspect the problem is in the module i915 and on the module i2c_designware. Because switching to a text console and issuing the command: "echo disk > /sys/power/state" the system hibernate and awakes when I request. But it awakes without keyboard and with following messages on the console: [ 50.827873] [drm] stuck on blitter ring [ 50.834932] [drm] stuck on bsd ring [ 50.841830] [drm] stuck on video enhancement ring [ 50.851177] [drm] GPU HANG: ecode 8:0:0x7a2af415, reason: Ring hung, action: reset [ 50.854730] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 50.858380] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 50.860886] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 50.863336] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 50.865839] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 50.868532] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning! [ 50.873485] drm/i915: Resetting chip after gpu hang [ 51.729188] IPv6: ADDRCONF(NETDEV_CHANGE): enx0019fd4cb596: link becomes ready [ 51.737806] asix 1-4:1.0 enx0019fd4cb596: link up, 100Mbps, full-duplex, lpa 0xCDE1 [ 129.340496] i2c_designware 808622C1:00: timeout in enabling adapter [ 130.348085] i2c_designware 808622C1:00: controller timed out [ 130.355959] i2c_designware 808622C1:00: Unknown Synopsys component type: 0x0000 Kind regards Jose M Calhariz -- Package-specific info: ** Version: Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0 20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 root=UUID=577ff77a-2aa2-4c43-9c83-91e107b674c2 ro printk.time=n initcall_debug no_console_suspend ** Tainted: E (8192) * Unsigned module has been loaded (currently expected). ** Kernel log: [ 49.008511] call regulatory.0+ returned 0 after 0 usecs [ 49.010919] calling intel_backlight+ @ 2728, parent: card0-eDP-1 [ 49.013223] call intel_backlight+ returned 0 after 0 usecs [ 49.015521] calling input6+ @ 2728, parent: LNXVIDEO:00 [ 49.017797] call input6+ returned 0 after 0 usecs [ 49.020078] calling input7+ @ 2728, parent: pcspkr [ 49.021968] call input7+ returned 0 after 17 usecs [ 49.023843] calling input8+ @ 2728, parent: i2c-ELAN0100:00 [ 49.025720] call input8+ returned 0 after 0 usecs [ 49.027601] calling coretemp.0+ @ 2728, parent: platform [ 49.029487] call coretemp.0+ returned 0 after 0 usecs [ 49.031392] calling asus-nb-wmi+ @ 2728, parent: platform [ 49.033284] call asus-nb-wmi+ returned 0 after 1 usecs [ 49.035181] calling input9+ @ 2728, parent: asus-nb-wmi [ 49.037073] call input9+ returned 0 after 0 usecs [ 49.038960] calling input10+ @ 2728, parent: 0018:0B05:8585.0001 [ 49.040893] call input10+ returned 0 after 19 usecs [ 49.042822] calling input10::numlock+ @ 2728, parent: input10 [ 49.044753] call input10::numlock+ returned 0 after 0 usecs [ 49.046684] calling input10::capslock+ @ 2728, parent: input10 [ 49.048625] call input10::capslock+ returned 0 after 0 usecs [ 49.050570] calling input10::scrolllock+ @ 2728, parent: input10 [ 49.052528] call input10::scrolllock+ returned 0 after 0 usecs [ 49.054491] calling input10::compose+ @ 2728, parent: input10 [ 49.056460] call input10::compose+ returned 0 after 0 usecs [ 49.058429] calling input10::kana+ @ 2728, parent: input10 [ 49.060402] call input10::kana+ returned 0 after 0 usecs [ 49.062379] calling rfkill1+ @ 2728, parent: phy0 [ 49.064358] call rfkill1+ returned 0 after 10 usecs [ 49.066337] PM: restore of devices complete after 4600.592 msecs [ 49.068386] usb 1-4:1.0: rebind failed: -517 [ 49.070372] usb 1-3:1.0: rebind failed: -517 [ 49.072323] usb 1-3:1.1: rebind failed: -517 [ 49.074671] PM: Image restored successfully. [ 49.074693] PM: Basic memory bitmaps freed [ 49.074699] Restarting tasks ... done. [ 49.089295] pci_bus :01: Allocating resources [ 49.089491] pcieport :00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 01] add_size 1000 [ 49.089498] pcieport :00:1c.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 01] add_size 20 add_align 10 [ 49.089509] pcieport :00:1c.0: res[15]=[mem 0x0010-0x000f 64bit pref] res_to_de
Bug#833016: linux-image-4.7.0-rc7-amd64-unsigned: Shutdown when pressed any key of the keyboard
Package: src:linux Version: 4.7~rc7-1~exp1 Severity: important Tags: upstream Being affected by #833009 I decided to try a kernel from experimental. Both of the kernels for amd64, the unsigned and the other, cause a orderly shutodwn when I press any key of the keyboard. I have no clue why this happens, but being a regression, I decided to report. Kind regards Jose M Calhariz -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUSTeK COMPUTER INC. product_name: E200HA product_version: 1.0 chassis_vendor: ASUSTeK COMPUTER INC. chassis_version: 1.0 bios_vendor: American Megatrends Inc. bios_version: E200HA.210 board_vendor: ASUSTeK COMPUTER INC. board_name: E200HA board_version: 1.0 ** Network interface configuration: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Braswell SoC Transaction Router [8086:2280] (rev 22) Subsystem: ASUSTeK Computer Inc. Braswell SoC Transaction Router [1043:10b0] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:0b.0 Signal processing controller [1180]: Intel Corporation Braswell P-Unit Power Management [8086:22dc] (rev 22) Subsystem: ASUSTeK Computer Inc. Braswell P-Unit Power Management [1043:10b0] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller [0c03]: Intel Corporation Braswell USB xHCI Host Controller [8086:22b5] (rev 22) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Braswell USB xHCI Host Controller [1043:10b0] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:1a.0 Encryption controller [1080]: Intel Corporation Braswell Trusted Execution Engine Interface [8086:2298] (rev 22) Subsystem: ASUSTeK Computer Inc. Braswell Trusted Execution Engine Interface [1043:10b0] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:1c.0 PCI bridge [0604]: Intel Corporation Braswell PCIe Port 1 [8086:22c8] (rev 22) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:1f.0 ISA bridge [0601]: Intel Corporation Braswell Platform Controller Unit LPC [8086:229c] (rev 22) Subsystem: ASUSTeK Computer Inc. Braswell Platform Controller Unit LPC [1043:10b0] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: lpc_ich Kernel modules: lpc_ich 01:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 30) Subsystem: AzureWave QCA9377 802.11ac Wireless Network Adapter [1a3b:2b31] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci ** USB devices: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b95:7720 ASIX Electronics Corp. AX88772 Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Can
Bug#833016: linux-image-4.7.0-rc7-amd64-unsigned: Shutdown when pressed any key of the keyboard
Hi, I have just tried a vanilla kernel 4.7 and it just works. Kind regards Jose M Calhariz signature.asc Description: OpenPGP digital signature
Bug#833009: linux-image-4.6.0-1-amd64: Hibernation does not work on Asus E200HA because of i915 and i2c_designware
Hi, I have tried the vanilla kernel 4.7. Now the hibernation almost works. When I select hibernation after some minutes I need to turn off the laptop. But when I turn on it awakes and return to the previous state. I still see the same error messages, but this time the keyboard works. Kind regards Jose M Calhariz signature.asc Description: OpenPGP digital signature
Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA
Package: src:linux Version: 4.8~rc8-1~exp1 Severity: important Dear Maintainer, * What led up to the situation? Using a very recent Debian kernel 4.7 or 4.8. The vanilla 4.7.0 from kernel.org works. I simply boot the laptop. When the X11 is up and ready to input the user name, if I press any key it will shutdown. I found no message in /var/log/kernel.log that explains the problem. * What exactly did you do (or not do) that was effective (or ineffective)? For reporting this bug I am connecting by SSH to the laptop over a USB/Ethernet adaptor. What measures can I do to gather more debugging information? Kind regards Jose M Calhariz -- Package-specific info: ** Version: Linux version 4.8.0-rc8-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.8~rc8-1~exp1 (2016-09-26) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-rc8-amd64 root=UUID=577ff77a-2aa2-4c43-9c83-91e107b674c2 ro printk.time=n initcall_debug no_console_suspend ** Tainted: E (8192) * Unsigned module has been loaded. ** Kernel log: [6.100201] initcall init_fat_fs+0x0/0xfd0 [fat] returned 0 after 46151 usecs [6.100962] initcall ghash_pclmulqdqni_mod_init+0x0/0x1000 [ghash_clmulni_intel] returned 0 after 17143 usecs [6.102575] calling init_vfat_fs+0x0/0x1000 [vfat] @ 303 [6.102588] initcall init_vfat_fs+0x0/0x1000 [vfat] returned 0 after 5 usecs [6.104151] calling crc32_pclmul_mod_init+0x0/0x1000 [crc32_pclmul] @ 257 [6.107983] initcall crc32_pclmul_mod_init+0x0/0x1000 [crc32_pclmul] returned 0 after 3726 usecs [6.111215] calling crct10dif_intel_mod_init+0x0/0x1000 [crct10dif_pclmul] @ 267 [6.124523] calling init_nls_cp437+0x0/0x1000 [nls_cp437] @ 316 [6.124531] initcall init_nls_cp437+0x0/0x1000 [nls_cp437] returned 0 after 0 usecs [6.135566] initcall crct10dif_intel_mod_init+0x0/0x1000 [crct10dif_pclmul] returned 0 after 23765 usecs [6.137107] calling evdev_init+0x0/0x1000 [evdev] @ 261 [6.139222] initcall evdev_init+0x0/0x1000 [evdev] returned 0 after 2050 usecs [6.143220] calling init_nls_ascii+0x0/0x1000 [nls_ascii] @ 320 [6.143228] initcall init_nls_ascii+0x0/0x1000 [nls_ascii] returned 0 after 0 usecs [6.171881] calling vmx_init+0x0/0x435 [kvm_intel] @ 266 [6.179360] calling asus_wmi_init+0x0/0x1000 [asus_wmi] @ 260 [6.179367] asus_wmi: ASUS WMI generic driver loaded [6.179386] initcall asus_wmi_init+0x0/0x1000 [asus_wmi] returned 0 after 16 usecs [6.181794] calling asus_nb_wmi_init+0x0/0x1000 [asus_nb_wmi] @ 260 [6.182142] asus_wmi: Initialization: 0x1 [6.182258] asus_wmi: BIOS WMI version: 7.9 [6.182352] asus_wmi: SFUN value: 0x37 [6.185752] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input8 [6.201743] asus_wmi: Number of fans: 1 [6.208232] ath10k_pci :01:00.0: firmware: failed to load ath10k/pre-cal-pci-:01:00.0.bin (-2) [6.208254] ath10k_pci :01:00.0: Direct firmware load for ath10k/pre-cal-pci-:01:00.0.bin failed with error -2 [6.208297] ath10k_pci :01:00.0: firmware: failed to load ath10k/cal-pci-:01:00.0.bin (-2) [6.208311] ath10k_pci :01:00.0: Direct firmware load for ath10k/cal-pci-:01:00.0.bin failed with error -2 [6.211045] initcall asus_nb_wmi_init+0x0/0x1000 [asus_nb_wmi] returned 0 after 28549 usecs [6.220335] ath10k_pci :01:00.0: firmware: direct-loading firmware ath10k/QCA9377/hw1.0/firmware-5.bin [6.220374] ath10k_pci :01:00.0: qca9377 hw1.0 target 0x0502 chip_id 0x003820ff sub 1a3b:2b31 [6.220388] ath10k_pci :01:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 [6.221359] ath10k_pci :01:00.0: firmware ver WLAN.TF.1.0-00267-1 api 5 features ignore-otp crc32 79cea2c7 [6.223919] calling iTCO_vendor_init_module+0x0/0x1000 [iTCO_vendor_support] @ 271 [6.223923] iTCO_vendor_support: vendor-support=0 [6.223940] initcall iTCO_vendor_init_module+0x0/0x1000 [iTCO_vendor_support] returned 0 after 12 usecs [6.225084] calling iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @ 271 [6.225086] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [6.225220] iTCO_wdt: Found a Braswell SoC TCO device (Version=3, TCOBASE=0x0460) [6.225553] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [6.225610] initcall iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] returned 0 after 504 usecs [6.251830] initcall vmx_init+0x0/0x435 [kvm_intel] returned 0 after 78051 usecs [6.254285] calling coretemp_init+0x0/0x1000 [coretemp] @ 257 [6.254616] initcall coretemp_init+0x0/0x1000 [coretemp] returned 0 after 314 usecs [6.256501] calling powerclamp_init+0x0/0x1000 [intel_powerclamp] @ 267 [6.256619] initcall powerclamp_init+0x0/0x1000 [intel_powerclamp] returned 0 after 105 usecs [6.257469] calling acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq] @ 257 [6.257479] initcall acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq
Bug#906107: linux-image-3.16.0-6-amd64: Latests kernel 3.16 on KVM host breaks Linux guest with lastests kernels
Package: src:linux Version: 3.16.57-2 Severity: important We use OpenNebula on Debian 8 to run KVM guests. Our latest upgrade of the host and guests broke badly. The host can not run guests with the latest kernels from Debian 8 and 9. If we downgrade the kernel on host or guest the problem is no longer present. To localize the root problem, I managed to launch a KVM guest on the command line using the lastest Debian live CD and the problem was the same. This is not a problem of OpenNebula. I need help to collect more information about what is going wrong on the guest and the host. Kind regards Jose M Calhariz -- Package-specific info: ** Version: Linux version 3.16.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10+deb8u1) ) #1 SMP Debian 3.16.57-2 (2018-07-14) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-amd64 root=/dev/mapper/system-root ro quiet ** Tainted: I (2048) * Working around severe firmware bug. ** Kernel log: [ 1176.926137] kvm [12584]: vcpu0 unhandled rdmsr: 0x1c9 [ 1176.926209] kvm [12584]: vcpu0 unhandled rdmsr: 0x1a6 [ 1176.926275] kvm [12584]: vcpu0 unhandled rdmsr: 0x1a7 [ 1176.926341] kvm [12584]: vcpu0 unhandled rdmsr: 0x3f6 ** Model information sys_vendor: Dell Inc. product_name: PowerEdge R410 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: 1.9.0 board_vendor: Dell Inc. board_name: 01V648 board_version: A04 ** Loaded modules: nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack xt_physdev ip_set nfnetlink vhost_net vhost macvtap macvlan tun xt_multiport iptable_filter ip_tables x_tables dm_round_robin ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rpcsec_gss_krb5 nfsv4 dns_resolver nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc bridge 8021q garp stp mrp llc dm_queue_length dm_multipath scsi_dh intel_powerclamp coretemp kvm_intel ttm drm_kms_helper kvm drm crc32_pclmul ipmi_devintf iTCO_wdt iTCO_vendor_support dcdbas joydev evdev aesni_intel acpi_power_meter serio_raw aes_x86_64 pcspkr ipmi_si lrw lpc_ich gf128mul tpm_tis glue_helper tpm mfd_core ablk_helper cryptd i7core_edac ipmi_msghandler edac_core shpchp processor thermal_sys button xfs libcrc32c dm_mod raid1 md_mod sd_mod crc_t10dif crct10dif_generic hid_generic usbhid hid usb_storage sg sr_mod cdrom mptsas ahci libahci scsi_transport_sas ehci_pci uhci_hcd mptscsih ehci_hcd libata mptbase igb i2c_algo_bit crct10dif_pclmul crct10dif_common i2c_core crc32c_intel dca usbcore ptp psmouse usb_common scsi_mod pps_core bnx2 ** Network interface configuration: (...) Privacy concerns ** Network status: *** IP interfaces and addresses: (...) Privacy concerns *** Device statistics: Inter-| Receive| Transmit face |bytespackets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed eth0.600: 464024832 5969272000 0 0 2853 17974996 97260000 0 0 0 lo: 901381748000 0 0 090138 1748000 0 0 0 eth3: 1783009756 3986650 17260 0 0 30266 71899026 240175000 0 0 0 br0011: 55169743 796451000 0 0 035956 418000 0 0 0 eth2: 14674510167 64522160 17260 0 0 30478 559178254 6193727000 0 0 0 eth0.11: 91505035 1195004000 0 0895144 98536503 364324000 0 0 0 brj600: 14577853219 6342345000 0 0 0 559177990 6193723000 0 0 0 eth1: 0 0000 0 0 00 0000 0 0 0 brj601: 1772277206 299405000 0 0 0 71645058 236327000 0 0 0 eth0: 2119825552 12748932 81 1723081 0 1859406 21539361933 14723412000 0 0 0 *** Protocol statistics: Ip: 8615928 total packets received 1518 with invalid addresses 0 forwarded 0 incoming packets discarded 8002257 incoming packets delivered 7038705 requests sent out 4 fragments received ok 8 fragments created Icmp: 9817 ICMP messages received 0 input ICMP message failed. ICMP input histogram: destination unreachable: 11 echo requests: 9806 9822 ICMP messages sent 0 ICMP messages failed ICMP output histogram: destination unreachable: 16 echo replies: 9806 IcmpMsg: InType3: 11 InType8: 9806 OutType0: 9806 OutType3: 16 Tcp: active connections openings 415 passive
Bug#906107: linux-image-3.16.0-6-amd64: Latests kernel 3.16 on KVM host breaks Linux guest with lastests kernels
On Tue, Aug 14, 2018 at 10:39:12AM +0100, Jose M Calhariz wrote: > Package: src:linux > Version: 3.16.57-2 > Severity: important > > We use OpenNebula on Debian 8 to run KVM guests. Our latest upgrade of the > host and guests broke badly. > The host can not run guests with the latest kernels from Debian 8 and 9. If > we downgrade the kernel on > host or guest the problem is no longer present. > > To localize the root problem, I managed to launch a KVM guest on the command > line using the lastest > Debian live CD and the problem was the same. This is not a problem of > OpenNebula. > > I need help to collect more information about what is going wrong on the > guest and the host. > > Kind regards > Jose M Calhariz > I have made videos of a guest live cd from Debian trying to boot and failing. qemu-system-x86_64 -enable-kvm -machine pc-i440fx-2.1,accel=kvm,usb=off -m 8096 -device cirrus-vga,id=video0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -cpu host -msg timestamp=on -smp 4,sockets=4,cores=1,threads=1 -display vnc=:22 -cdrom ~cal/debian-9.5.0-amd64-xfce-CD-1.iso The most informative have 60MB. There is a recomended place to upload videos? If not, I can upload on my homepage at University. Kind regards Jose M Calhariz -- -- Quem ama purÃssima, dourada lhe parece. signature.asc Description: PGP signature
Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA
On 24/10/16 03:30, Ben Hutchings wrote: > On Sun, 2016-10-16 at 21:22 +0100, Jose M Calhariz wrote: >> Package: src:linux >> Version: 4.8~rc8-1~exp1 >> Severity: important >> >> Dear Maintainer, >> >>* What led up to the situation? >> >> Using a very recent Debian kernel 4.7 or 4.8. The vanilla 4.7.0 from >> kernel.org works. I simply boot the laptop. When the X11 is up and >> ready to input the user name, if I press any key it will shutdown. > [...] > > Is that a clean shutdown (services stopped, filesystems unmounted) or a > dirty shutdown (shuts off almost immediately, fsck reports an error on > the next boot)? > > What happens if you press a key earlier than that? > > Ben. > Yes, it seams to be a clean shutdown. User programs killed, services shutdown, nothing logged. If I press a key earlier, it is just ignored, as expected. Kind regards Jose M Calhariz signature.asc Description: OpenPGP digital signature
Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA
Is to tell that the new 4.9-rc works. Now I can login into the machine. During the weekend I will do a longer review of the kernel in search of regressions. Thank you. Kind regards Jose M Calhariz On 16/11/16 17:01, Santiago Vila wrote: > forcemerge 833016 841007 > thanks > > Hi. > > You will see that both bugs belong to the "src:linux" package, > so it's better not to file duplicates. To tell the BTS that > a certain version has the bug, we have a "found" command. > > I'm merging the bugs with this message. > > BTW: There is a 4.9-rc version in experimental, you might want to give > it a try and say here if there is any improvement. > > Thanks. signature.asc Description: OpenPGP digital signature
