Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon)
Here is the tail of dmesg after such an error. Best regards Tom Guder [ 1104.412089] radeon :02:00.0: ring 0 stalled for more than 10104msec [ 1104.412098] radeon :02:00.0: GPU lockup (waiting for 0x000664a0 last fence id 0x0006649f on ring 0) [ 1104.412102] radeon :02:00.0: failed to get a new IB (-35) [ 1104.900461] radeon :02:00.0: Saved 21357 dwords of commands on ring 0. [ 1104.900590] radeon :02:00.0: GPU softreset: 0x006C [ 1104.900592] radeon :02:00.0: GRBM_STATUS = 0xA0003028 [ 1104.900593] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1104.900594] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1104.900595] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1104.900706] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1104.900707] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1104.900708] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [ 1104.900710] radeon :02:00.0: R_00867C_CP_BUSY_STAT = 0x0002 [ 1104.900711] radeon :02:00.0: R_008680_CP_STAT = 0x80010243 [ 1104.900713] radeon :02:00.0: R_00D034_DMA_STATUS_REG = 0x44C83146 [ 1104.900714] radeon :02:00.0: R_00D834_DMA_STATUS_REG = 0x44C84246 [ 1104.900716] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 1104.900718] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x [ 1105.370049] radeon :02:00.0: GRBM_SOFT_RESET=0xDDFF [ 1105.370101] radeon :02:00.0: SRBM_SOFT_RESET=0x00100140 [ 1105.371247] radeon :02:00.0: GRBM_STATUS = 0x3028 [ 1105.371248] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1105.371249] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1105.371250] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1105.371361] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1105.371362] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1105.371363] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x [ 1105.371365] radeon :02:00.0: R_00867C_CP_BUSY_STAT = 0x [ 1105.371366] radeon :02:00.0: R_008680_CP_STAT = 0x [ 1105.371367] radeon :02:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 1105.371369] radeon :02:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [ 1105.371608] radeon :02:00.0: GPU reset succeeded, trying to resume [ 1105.402616] [drm] probing gen 2 caps for device 8086:e04 = 7a7903/e [ 1105.402619] [drm] PCIE gen 3 link speeds already enabled [ 1105.404456] [drm] PCIE GART of 1024M enabled (table at 0x00276000). [ 1105.404557] radeon :02:00.0: WB enabled [ 1105.404559] radeon :02:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8800b54c0c00 [ 1105.404560] radeon :02:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x8800b54c0c04 [ 1105.404561] radeon :02:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x8800b54c0c08 [ 1105.404561] radeon :02:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x8800b54c0c0c [ 1105.404562] radeon :02:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x8800b54c0c10 [ 1105.405169] radeon :02:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90011fb5a18 [ 1105.564971] [drm] ring test on 0 succeeded in 2 usecs [ 1105.564978] [drm] ring test on 1 succeeded in 1 usecs [ 1105.564984] [drm] ring test on 2 succeeded in 1 usecs [ 1105.564995] [drm] ring test on 3 succeeded in 5 usecs [ 1105.565005] [drm] ring test on 4 succeeded in 5 usecs [ 1105.740770] [drm] ring test on 5 succeeded in 2 usecs [ 1105.740776] [drm] UVD initialized successfully. [ 1115.740176] radeon :02:00.0: ring 0 stalled for more than 1msec [ 1115.740183] radeon :02:00.0: GPU lockup (waiting for 0x000665a7 last fence id 0x0006649f on ring 0) [ 1115.740187] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [ 1115.740192] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [ 1115.740195] radeon :02:00.0: ib ring test failed (-35). [ 1116.221093] radeon :02:00.0: GPU softreset: 0x0048 [ 1116.221095] radeon :02:00.0: GRBM_STATUS = 0xA0003028 [ 1116.221097] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1116.221098] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1116.221099] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1116.221210] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1116.221211] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1116.221212] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [ 1116.221214] radeon
Bug#773643: initramfs-tools: mkfs.* not added to initrd image (Warning: couldn't identify filesystem type for fsck hook, ignoring.)
Package: initramfs-tools Version: 0.118 Severity: important Dear Debian folks, since some time, the filesystem type of the LUKS encrypted root partition (/) is not detected. $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 Warning: couldn't identify filesystem type for fsck hook, ignoring. setupcon is missing. Please install the 'console-setup' package. $ mount […] /dev/mapper/luks-6fb2f31d-ca5f-4c02-b120-13fd929fcac1 on / type ext4 (rw,noatime,discard,errors=remount-ro,commit=600,data=ordered) […] Unfortunately, I do not know when started. Either due to a `initramfs-tool` upgrade or testing `dracut`, where I had to switch to using UUIDs. Thanks, Paul -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages initramfs-tools depends on: ii busybox1:1.22.0-14 ii cpio 2.11+dfsg-2+b1 ii klibc-utils2.0.4-2 ii kmod 18-3 ii module-init-tools 18-3 ii udev 215-8 ii util-linux 2.25.2-4 Versions of packages initramfs-tools recommends: ii busybox 1:1.22.0-14 Versions of packages initramfs-tools suggests: ii bash-completion 1:2.1-4 -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#766829:
The message is also displayed in kernel 3.18 from experimental. -- Thiago Bellini Ribeiro http://hackedbellini.org PGP: D70FD60E “Real knowledge is to know the extent of one's ignorance.” - Confucius -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKhO_r7ta8Kose1qyVH=WeebFV8bXWkVN2ANA576=2yv470...@mail.gmail.com
Bug#773646: Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback
Package: linux-image-3.16.0-0.bpo.4-amd64/wheezy-backports uptodate 3.16.7-ckt2-1~bpo70+1 Version: 3.16.7 After installing the Backport Package the system cannot boot with the new kernel. The System hangs and falls back to dracut console. It mentions that the root filesystem UID cannot not be found. The system itself has a boot disk (vda3) and the root is on (vda1). I checked the grub.cfg the Filesystem uid's are correct. Reboot to the original kernel 3.2.0 works though. During the installation of the Backport Kernel dracut warns that it can not find consolefonts, ... (the rest I can't remember, sadly not logged) Looks to me that some depencies are not in the package which are necessary when initramfs is replaced with dracut. I am using Debian GNU/Linux 7, Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/Linux -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5496c7ee.8000...@googlemail.com
Bug#773646: Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback
Control: reassign -1 src:linux 3.16.7-ckt2-1~bpo70+1 On Sun, 2014-12-21 at 14:15 +0100, Mario Kothe wrote: Package: linux-image-3.16.0-0.bpo.4-amd64/wheezy-backports uptodate 3.16.7-ckt2-1~bpo70+1 Version: 3.16.7 After installing the Backport Package the system cannot boot with the new kernel. The System hangs and falls back to dracut console. It mentions that the root filesystem UID cannot not be found. The system itself has a boot disk (vda3) and the root is on (vda1). I checked the grub.cfg the Filesystem uid's are correct. Reboot to the original kernel 3.2.0 works though. During the installation of the Backport Kernel dracut warns that it can not find consolefonts, ... (the rest I can't remember, sadly not logged) Looks to me that some depencies are not in the package which are necessary when initramfs is replaced with dracut. Presumably that would be a dracut bug. I am using Debian GNU/Linux 7, Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/Linux What happens if you install initramfs-tools from wheezy-backports? Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#773646: Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback
Processing control commands: reassign -1 src:linux 3.16.7-ckt2-1~bpo70+1 Bug #773646 [linux-image-3.16.0-0.bpo.4-amd64/wheezy-backports uptodate 3.16.7-ckt2-1~bpo70+1] Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback Warning: Unknown package 'linux-image-3.16.0-0.bpo.4-amd64/wheezy-backports' Warning: Unknown package 'uptodate' Warning: Unknown package '3.16.7-ckt2-1~bpo70+1' Bug reassigned from package 'linux-image-3.16.0-0.bpo.4-amd64/wheezy-backports uptodate 3.16.7-ckt2-1~bpo70+1' to 'src:linux'. Ignoring request to alter found versions of bug #773646 to the same values previously set Ignoring request to alter fixed versions of bug #773646 to the same values previously set Bug #773646 [src:linux] Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback Marked as found in versions linux/3.16.7-ckt2-1~bpo70+1. -- 773646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b773646.141916961717860.transcr...@bugs.debian.org
Bug#773646: Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback
On Sun, 2014-12-21 at 15:13 +0100, Mario Kothe wrote: I tried it with the initramfs-tools. Still no change. Error messsage is the same: dracut Warning: Could not boot. dracut Warning: /dev/disk/by-uuid/ does not exist Droping to debug shell. And yes it is a dracut bug. Here the install messages from installing initramfs-tools [...] Setting up initramfs-tools (0.115~bpo70+1) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: /boot/initrd.img-3.2.0-4-amd64 has been altered. update-initramfs: Cannot update. Override with -t option. root@nova:/etc# reboot Oh, well you need to tell initramfs-tools to rebuild the initramfs too: update-initramfs -u -t -k 3.16.0-0.bpo.4-amd64. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Processing of linux-2.6_2.6.32-48squeeze10_i386.changes
linux-2.6_2.6.32-48squeeze10_i386.changes uploaded successfully to ftp-master.debian.org along with the files: linux-2.6_2.6.32-48squeeze10.dsc linux-2.6_2.6.32-48squeeze10.diff.gz linux-doc-2.6.32_2.6.32-48squeeze10_all.deb linux-manual-2.6.32_2.6.32-48squeeze10_all.deb linux-patch-debian-2.6.32_2.6.32-48squeeze10_all.deb linux-source-2.6.32_2.6.32-48squeeze10_all.deb linux-support-2.6.32-5_2.6.32-48squeeze10_all.deb firmware-linux-free_2.6.32-48squeeze10_all.deb linux-base_2.6.32-48squeeze10_all.deb linux-image-2.6.32-5-486_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-486_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-686_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-686_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-686-bigmem_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-686-bigmem_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-amd64_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-amd64_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-common_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-openvz-686_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-openvz-686-dbg_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-openvz-686_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-common-openvz_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-all_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-all-i386_2.6.32-48squeeze10_i386.deb linux-libc-dev_2.6.32-48squeeze10_i386.deb linux-tools-2.6.32_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-vserver-686_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-vserver-686_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-vserver-686-bigmem_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-vserver-686-bigmem-dbg_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-common-vserver_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-xen-686_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-xen-686-dbg_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-xen-686_2.6.32-48squeeze10_i386.deb xen-linux-system-2.6.32-5-xen-686_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-common-xen_2.6.32-48squeeze10_i386.deb Greetings, Your Debian queue daemon (running on host coccia.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1y2kbi-0006a8...@coccia.debian.org
Processing of linux-2.6_2.6.32-48squeeze10_i386.changes
linux-2.6_2.6.32-48squeeze10_i386.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.32-48squeeze10.dsc linux-2.6_2.6.32-48squeeze10.diff.gz linux-doc-2.6.32_2.6.32-48squeeze10_all.deb linux-manual-2.6.32_2.6.32-48squeeze10_all.deb linux-patch-debian-2.6.32_2.6.32-48squeeze10_all.deb linux-source-2.6.32_2.6.32-48squeeze10_all.deb linux-support-2.6.32-5_2.6.32-48squeeze10_all.deb firmware-linux-free_2.6.32-48squeeze10_all.deb linux-base_2.6.32-48squeeze10_all.deb linux-image-2.6.32-5-486_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-486_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-686_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-686_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-686-bigmem_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-686-bigmem-dbg_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-686-bigmem_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-amd64_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-amd64_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-common_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-openvz-686_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-openvz-686-dbg_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-openvz-686_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-common-openvz_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-all_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-all-i386_2.6.32-48squeeze10_i386.deb linux-libc-dev_2.6.32-48squeeze10_i386.deb linux-tools-2.6.32_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-vserver-686_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-vserver-686_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-vserver-686-bigmem_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-vserver-686-bigmem-dbg_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-vserver-686-bigmem_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-common-vserver_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-xen-686_2.6.32-48squeeze10_i386.deb linux-image-2.6.32-5-xen-686-dbg_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-xen-686_2.6.32-48squeeze10_i386.deb xen-linux-system-2.6.32-5-xen-686_2.6.32-48squeeze10_i386.deb linux-headers-2.6.32-5-common-xen_2.6.32-48squeeze10_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1y2kcr-0001i5...@franck.debian.org
linux-2.6_2.6.32-48squeeze10_i386.changes ACCEPTED into squeeze-lts
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 21 Dec 2014 11:02:49 +0100 Source: linux-2.6 Binary: linux-tools-2.6.32 linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-5 linux-base linux-libc-dev linux-headers-2.6.32-5-all linux-headers-2.6.32-5-all-alpha linux-headers-2.6.32-5-common linux-image-2.6.32-5-alpha-generic linux-headers-2.6.32-5-alpha-generic linux-image-2.6.32-5-alpha-smp linux-headers-2.6.32-5-alpha-smp linux-image-2.6.32-5-alpha-legacy linux-headers-2.6.32-5-alpha-legacy linux-headers-2.6.32-5-all-amd64 linux-image-2.6.32-5-amd64 linux-headers-2.6.32-5-amd64 linux-image-2.6.32-5-amd64-dbg linux-headers-2.6.32-5-common-openvz linux-image-2.6.32-5-openvz-amd64 linux-headers-2.6.32-5-openvz-amd64 linux-image-2.6.32-5-openvz-amd64-dbg linux-headers-2.6.32-5-common-vserver linux-image-2.6.32-5-vserver-amd64 linux-headers-2.6.32-5-vserver-amd64 linux-image-2.6.32-5-vserver-amd64-dbg linux-headers-2.6.32-5-common-xen linux-image-2.6.32-5-xen-amd64 linux-headers-2.6.32-5-xen-amd64 linux-image-2.6.32-5-xen-amd64-dbg xen-linux-system-2.6.32-5-xen-amd64 linux-headers-2.6.32-5-all-armel linux-image-2.6.32-5-iop32x linux-headers-2.6.32-5-iop32x linux-image-2.6.32-5-ixp4xx linux-headers-2.6.32-5-ixp4xx linux-image-2.6.32-5-kirkwood linux-headers-2.6.32-5-kirkwood linux-image-2.6.32-5-orion5x linux-headers-2.6.32-5-orion5x linux-image-2.6.32-5-versatile linux-headers-2.6.32-5-versatile linux-headers-2.6.32-5-all-hppa linux-image-2.6.32-5-parisc linux-headers-2.6.32-5-parisc linux-image-2.6.32-5-parisc-smp linux-headers-2.6.32-5-parisc-smp linux-image-2.6.32-5-parisc64 linux-headers-2.6.32-5-parisc64 linux-image-2.6.32-5-parisc64-smp linux-headers-2.6.32-5-parisc64-smp linux-headers-2.6.32-5-all-i386 linux-image-2.6.32-5-486 linux-headers-2.6.32-5-486 linux-image-2.6.32-5-686 linux-headers-2.6.32-5-686 linux-image-2.6.32-5-686-bigmem linux-headers-2.6.32-5-686-bigmem linux-image-2.6.32-5-686-bigmem-dbg linux-image-2.6.32-5-openvz-686 linux-headers-2.6.32-5-openvz-686 linux-image-2.6.32-5-openvz-686-dbg linux-image-2.6.32-5-vserver-686 linux-headers-2.6.32-5-vserver-686 linux-image-2.6.32-5-vserver-686-bigmem linux-headers-2.6.32-5-vserver-686-bigmem linux-image-2.6.32-5-vserver-686-bigmem-dbg linux-image-2.6.32-5-xen-686 linux-headers-2.6.32-5-xen-686 linux-image-2.6.32-5-xen-686-dbg xen-linux-system-2.6.32-5-xen-686 linux-headers-2.6.32-5-all-ia64 linux-image-2.6.32-5-itanium linux-headers-2.6.32-5-itanium linux-image-2.6.32-5-mckinley linux-headers-2.6.32-5-mckinley linux-image-2.6.32-5-vserver-itanium linux-headers-2.6.32-5-vserver-itanium linux-image-2.6.32-5-vserver-mckinley linux-headers-2.6.32-5-vserver-mckinley linux-headers-2.6.32-5-all-m68k linux-image-2.6.32-5-amiga linux-headers-2.6.32-5-amiga linux-image-2.6.32-5-atari linux-headers-2.6.32-5-atari linux-image-2.6.32-5-bvme6000 linux-headers-2.6.32-5-bvme6000 linux-image-2.6.32-5-mac linux-headers-2.6.32-5-mac linux-image-2.6.32-5-mvme147 linux-headers-2.6.32-5-mvme147 linux-image-2.6.32-5-mvme16x linux-headers-2.6.32-5-mvme16x linux-headers-2.6.32-5-all-mips linux-image-2.6.32-5-r4k-ip22 linux-headers-2.6.32-5-r4k-ip22 linux-image-2.6.32-5-r5k-ip32 linux-headers-2.6.32-5-r5k-ip32 linux-image-2.6.32-5-sb1-bcm91250a linux-headers-2.6.32-5-sb1-bcm91250a linux-image-2.6.32-5-sb1a-bcm91480b linux-headers-2.6.32-5-sb1a-bcm91480b linux-image-2.6.32-5-4kc-malta linux-headers-2.6.32-5-4kc-malta linux-image-2.6.32-5-5kc-malta linux-headers-2.6.32-5-5kc-malta linux-headers-2.6.32-5-all-mipsel linux-image-2.6.32-5-r5k-cobalt linux-headers-2.6.32-5-r5k-cobalt linux-headers-2.6.32-5-all-powerpc linux-image-2.6.32-5-powerpc linux-headers-2.6.32-5-powerpc linux-image-2.6.32-5-powerpc-smp linux-headers-2.6.32-5-powerpc-smp linux-image-2.6.32-5-powerpc64 linux-headers-2.6.32-5-powerpc64 linux-image-2.6.32-5-vserver-powerpc linux-headers-2.6.32-5-vserver-powerpc linux-image-2.6.32-5-vserver-powerpc64 linux-headers-2.6.32-5-vserver-powerpc64 linux-headers-2.6.32-5-all-s390 linux-image-2.6.32-5-s390x linux-headers-2.6.32-5-s390x linux-image-2.6.32-5-s390x-tape linux-image-2.6.32-5-vserver-s390x linux-headers-2.6.32-5-vserver-s390x linux-headers-2.6.32-5-all-sh4 linux-image-2.6.32-5-sh7751r linux-headers-2.6.32-5-sh7751r linux-image-2.6.32-5-sh7785lcr linux-headers-2.6.32-5-sh7785lcr linux-headers-2.6.32-5-all-sparc linux-image-2.6.32-5-sparc64 linux-headers-2.6.32-5-sparc64 linux-image-2.6.32-5-sparc64-smp linux-headers-2.6.32-5-sparc64-smp linux-image-2.6.32-5-vserver-sparc64 linux-headers-2.6.32-5-vserver-sparc64 linux-headers-2.6.32-5-all-sparc64 Architecture: source all i386 Version: 2.6.32-48squeeze10 Distribution: squeeze-lts Urgency: medium Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Holger Levsen hol...@debian.org Description:
Bug#773661: linux-image-3.16-3-amd64: drm error messages on boot
Package: src:linux Version: 3.16.5-1 Severity: minor Dear Maintainer, On boot I have two errors reported by the kernel : [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun This is just cosmetic because boot process continues normally after the warnings. Thanks in advance. Best regards. Librement from France. -- Package-specific info: ** Version: Linux version 3.16-3-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-12) ) #1 SMP Debian 3.16.5-1 (2014-10-10) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16-3-amd64 root=UUID=d73ac13e-29f5-477b-9324-ff6d9aed054f ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [8.406848] ACPI: Power Button [PWRF] [8.408663] ACPI: AC Adapter [AC] (on-line) [8.431389] mei_me :00:16.0: irq 47 for MSI/MSI-X [8.434777] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input10 [8.458211] tpm_tis 00:01: 1.2 TPM (device-id 0xB, rev-id 16) [8.471499] wmi: Mapper loaded [8.482284] [drm] Initialized drm 1.1.0 20060810 [8.569473] ACPI: Battery Slot [BAT0] (battery present) [8.569561] ACPI: Battery Slot [BAT1] (battery absent) [8.671004] tpm_tis 00:01: TPM is disabled/deactivated (0x7) [8.848324] alg: No test for crc32 (crc32-pclmul) [8.852231] cfg80211: Calling CRDA to update world regulatory domain [8.946310] [drm] Memory usable by graphics device = 2048M [8.946316] [drm] Replacing VGA console driver [8.947461] Console: switching to colour dummy device 80x25 [8.985456] iTCO_vendor_support: vendor-support=0 [8.985993] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [8.986046] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460) [8.986208] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [9.123688] i915 :00:02.0: irq 48 for MSI/MSI-X [9.123711] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [9.123713] [drm] Driver supports precise vblank timestamp query. [9.152262] input: HP WMI hotkeys as /devices/virtual/input/input15 [9.152915] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [9.193511] fbcon: inteldrmfb (fb0) is primary device [9.402480] intel_rapl: RAPL domain dram detection failed [9.456700] ath: phy0: Enable LNA combining [9.457950] ath: EEPROM regdomain: 0x60 [9.457951] ath: EEPROM indicates we should expect a direct regpair map [9.457954] ath: Country alpha2 being used: 00 [9.457955] ath: Regpair used: 0x60 [9.467190] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.467191] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun [9.530129] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [9.530911] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [9.531257] ieee80211 phy0: Atheros AR9485 Rev:1 mem=0xc9001118, irq=19 [9.640942] psmouse serio4: synaptics: Touchpad model: 1, fw: 7.5, id: 0x1c0b1, caps: 0xd00033/0x64/0xa0400, board id: 1621, fw id: 730177 [9.687781] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input14 [9.913111] Console: switching to colour frame buffer device 170x48 [9.917204] i915 :00:02.0: fb0: inteldrmfb frame buffer device [9.917206] i915 :00:02.0: registered panic notifier [9.982649] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [9.982882] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input16 [9.983160] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [9.983802] snd_hda_intel :00:1b.0: irq 49 for MSI/MSI-X [ 10.109328] sound hdaudioC0D0: autoconfig: line_outs=1 (0xa/0x0/0x0/0x0/0x0) type:line [ 10.109336] sound hdaudioC0D0:speaker_outs=1 (0xd/0x0/0x0/0x0/0x0) [ 10.109339] sound hdaudioC0D0:hp_outs=1 (0xb/0x0/0x0/0x0/0x0) [ 10.109342] sound hdaudioC0D0:mono: mono_out=0x0 [ 10.109344] sound hdaudioC0D0:inputs: [ 10.109348] sound hdaudioC0D0: Mic=0xc [ 10.109351] sound hdaudioC0D0: Internal Mic=0x11 [ 10.109354] sound hdaudioC0D0: Line=0xf [ 10.298357] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/sound/card0/hdaudioC0D0/input17 [ 10.299367] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input18 [ 10.300662] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card0/input19 [ 10.300932] input: HDA Intel PCH Dock Line Out as /devices/pci:00/:00:1b.0/sound/card0/input20 [ 10.301128] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card0/input21 [ 10.301265] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input22 [ 10.301390] input: HDA
Bug#773646: Fwd: Re: Bug#773646: Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback
The install of initramfs-tools replaced the dracut, but in the repository the Version of the dracut ist as follows: Package: dracut Version: 020-2 Installed-Size: 668 Forwarded Message Subject: Re: Bug#773646: Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback Date: Sun, 21 Dec 2014 18:17:33 + From: Ben Hutchings b...@decadent.org.uk Reply-To: 773...@bugs.debian.org To: Mario Kothe mario.ko...@googlemail.com On Sun, 2014-12-21 at 19:04 +0100, Mario Kothe wrote: On 21.12.2014 16:03, Ben Hutchings wrote: On Sun, 2014-12-21 at 15:13 +0100, Mario Kothe wrote: I tried it with the initramfs-tools. Still no change. Error messsage is the same: dracut Warning: Could not boot. dracut Warning: /dev/disk/by-uuid/ does not exist Droping to debug shell. And yes it is a dracut bug. Here the install messages from installing initramfs-tools [...] Setting up initramfs-tools (0.115~bpo70+1) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: /boot/initrd.img-3.2.0-4-amd64 has been altered. update-initramfs: Cannot update. Override with -t option. root@nova:/etc# reboot Oh, well you need to tell initramfs-tools to rebuild the initramfs too: update-initramfs -u -t -k 3.16.0-0.bpo.4-amd64. Ben. Ok, totally forgot that part with the update-initramfs. It works now with kernel. Thank you for fast answers and replies. Please reply to the bug address (773...@bugs.debian.org) and state which version of dracut you are using. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: PGP signature
Re: Replacing aufs with overlayfs
Hi, intrigeri wrote (11 Dec 2014 13:13:43 GMT) : Ben Hutchings wrote (09 Dec 2014 19:55:10 GMT) : Please try the Linux 3.18 packages from experimental (they're not there yet, but should be soon) and check that overlayfs does what you need. Thanks. I'll test it for Tails' usecases (that use aufs a bit more than most other live systems, e.g. our incremental upgrades features uses it) once I find the time to. Here are the results of our preliminary investigations: 1. Due to overlayfs' stack depth limit of 2, until support more than one read-only lower layer is completed, overlayfs breaks live-boot's SquashFS stacking feature; Tails automatic upgrades rely on this feature. The current overlayfs maintainer says it is the top feature request, and has been working on it recently (https://www.mail-archive.com/linux-unionfs@vger.kernel.org/msg00079.html). The code lives in git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git (branch overlayfs-next, currently). Later on the same thread, there are also patches (https://www.mail-archive.com/linux-unionfs@vger.kernel.org/msg00088.html) to make the stack depth limit configurable at runtime, but it was deemed risky by the overlayfs maintainer without more work to check that the stack will be safe. So, our best bet right now seems to wait for the 1 read-only lower layer feature. 2. Whiteouts support *should* work when using SquashFS (for non-directories, using a char device; for directories, using a xattr to make them opaque). Not tested yet, though. We also rely on this feature for Tails automatic upgrades. Is it an option to get aufs back into the Debian kernel until #1 is completed and reaches mainline? (I could understand that you want to add a deadline if you make such a promise, of course :) Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/85wq5k208r@boum.org
Bug#773646: Fwd: Re: Bug#773646: Backports : linux-image-3.16.0-0.bpo.4-amd64 not booting dracut fallback
On Sun, 2014-12-21 at 19:58 +0100, Mario Kothe wrote: The install of initramfs-tools replaced the dracut, but in the repository the Version of the dracut ist as follows: Package: dracut Version: 020-2 Installed-Size: 668 That version is too old to satisfy the dependency; you must have had a newer version installed (from testing or unstable). Check for the last mention of dracut in /var/log/dpkg.log. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Re: Replacing aufs with overlayfs
On Sun, 2014-12-21 at 21:53 +0100, intrigeri wrote: Hi, intrigeri wrote (11 Dec 2014 13:13:43 GMT) : Ben Hutchings wrote (09 Dec 2014 19:55:10 GMT) : Please try the Linux 3.18 packages from experimental (they're not there yet, but should be soon) and check that overlayfs does what you need. Thanks. I'll test it for Tails' usecases (that use aufs a bit more than most other live systems, e.g. our incremental upgrades features uses it) once I find the time to. Here are the results of our preliminary investigations: 1. Due to overlayfs' stack depth limit of 2, until support more than one read-only lower layer is completed, overlayfs breaks live-boot's SquashFS stacking feature; Tails automatic upgrades rely on this feature. The current overlayfs maintainer says it is the top feature request, and has been working on it recently (https://www.mail-archive.com/linux-unionfs@vger.kernel.org/msg00079.html). The code lives in git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git (branch overlayfs-next, currently). Should we expect this to be merged in Linux 3.20? Later on the same thread, there are also patches (https://www.mail-archive.com/linux-unionfs@vger.kernel.org/msg00088.html) to make the stack depth limit configurable at runtime, but it was deemed risky by the overlayfs maintainer without more work to check that the stack will be safe. So, our best bet right now seems to wait for the 1 read-only lower layer feature. 2. Whiteouts support *should* work when using SquashFS (for non-directories, using a char device; for directories, using a xattr to make them opaque). Not tested yet, though. We also rely on this feature for Tails automatic upgrades. Is it an option to get aufs back into the Debian kernel until #1 is completed and reaches mainline? (I could understand that you want to add a deadline if you make such a promise, of course :) I would rather apply the overlayfs patches to support multiple lower layers. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
issues with experimental kernels on imx6 based boards.
I have some imx6 based boards which work as autobuilders for raspbian. I use btrfs for efficient snapshotting and have had some issues (crashes, weird filesystem errors) which I suspect are down to btrfs. As such i've been frequently upgradeing the kernel to the latest versions from experimental in the hope that the issues will be fixed upstream. There are a total of six boards. Five wandboard quads (one hosted at my flat, four hosted at bytemark), and one nitrogen6x, the wandboard quads are running a mostly wheezy system while the nitrogen6x is running a mostly jessie system. On all the systems the boot files and ext4 root filesystem is on a micro SD card while a hard drive is used for buildd related stuff (btrfs) and swap. The wandboards have a seperate ext2 boot partition while the nitrogen6x has /boot on the root partition. Currently there are (among others) the following kernels installed on the boards. linux-image-3.16-trunk-armmp version 3.16-1~exp1 linux-image-3.17-1-armmp version 3.17-1~exp1 linux-image-3.18.0-trunk-armmp version 3.18-1~exp1 linux-image-3.16-trunk-armmp seemed to work ok without any tweaking. linux-image-3.17-1-armmp seemed to work ok without any tweaking on the wandboard quads but it failed to boot with a timeout waiting for rootfs. I was able to get it to boot by doing lsmod | cut -d ' ' -f 1 /etc/initramfs-tools/modules (while running 3.16) and then rebuilding the initrd for 3.17, i'll try to investigate further whether this is reproducable with later versions of initramfs-tools and if-so what modules exactly are missing. linux-image-3.18.0-trunk-armmp, this failed on the nitrogen6x in the same way as 3.17, I haven't debugged that issue further yet. On the wandboard quad it booted but /dev was nearly empty and udev was failing to start, I tried upgrading udev first to the wheezy-backports version and then to the jessie version but while udev claimed to start successfully it still didn't seem to actually start managing /dev. Is anyone aware of any udev incompatibilities with 3.18? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54975d0d.1060...@p10link.net
Re: Replacing aufs with overlayfs
On Sun, Dec 21, 2014 at 09:53:24PM +0100, intrigeri wrote: Is it an option to get aufs back into the Debian kernel until #1 is completed and reaches mainline? (I could understand that you want to add a deadline if you make such a promise, of course :) no, there is no rush for the upcoming release, better work out the needed use case one by one with proper upstream. experimental and unstable (after release) are for development, use it! thanks for your update. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141221234441.GA7845@gluino
Bug#765363: fixed in 3.16.7
Looks like it's fixed in linux-image-3.16.0-0.bpo.4-amd64 3.16.7-ckt2-1~bpo70+1 . Sammy -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141222071607.ga8...@transtrend.com
