[Bug 1828712] Re: I/O errors when trying to loop mount an image
@brian-murray thanks for the suggestion. Have done you suggest but apport-cli on the system with the GUI does not seem to allow an existing bug to be updated with the info, so rather than generating a new bug report am copying the file generated by apport-cli --save below. ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Fri May 17 10:50:14 2019 Dependencies: adduser 3.116ubuntu1 apt 1.6.10 apt-utils 1.6.10 busybox-initramfs 1:1.27.2-2ubuntu3.2 ca-certificates 20180409 coreutils 8.28-1ubuntu1 cpio 2.12+dfsg-6 debconf 1.5.66 debconf-i18n 1.5.66 dmsetup 2:1.02.145-4.1ubuntu3 dpkg 1.19.0.5ubuntu2.1 fdisk 2.31.1-0.4ubuntu3.3 gcc-8-base 8.3.0-6ubuntu1~18.04 gettext-base 0.19.8.1-6ubuntu0.3 gpgv 2.2.4-1ubuntu1.2 grub-common 2.02-2ubuntu8.13 grub-gfxpayload-lists 0.7 grub-pc 2.02-2ubuntu8.13 grub-pc-bin 2.02-2ubuntu8.13 grub2-common 2.02-2ubuntu8.13 init-system-helpers 1.51 initramfs-tools 0.130ubuntu3.7 initramfs-tools-bin 0.130ubuntu3.7 initramfs-tools-core 0.130ubuntu3.7 klibc-utils 2.0.4-9ubuntu2 kmod 24-1ubuntu3.2 libacl1 2.2.52-3build1 libapt-inst2.0 1.6.10 libapt-pkg5.0 1.6.10 libattr1 1:2.4.47-2build1 libaudit-common 1:2.8.2-1ubuntu1 libaudit1 1:2.8.2-1ubuntu1 libblkid1 2.31.1-0.4ubuntu3.3 libbz2-1.0 1.0.6-8.1 libc6 2.27-3ubuntu1 libcap-ng0 0.7.7-3.1 libdb5.3 5.3.28-13.1ubuntu1 libdevmapper1.02.1 2:1.02.145-4.1ubuntu3 libfdisk1 2.31.1-0.4ubuntu3.3 libffi6 3.2.1-8 libfreetype6 2.8.1-2ubuntu2 libfuse2 2.9.7-1ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04 libgcrypt20 1.8.1-4ubuntu1.1 libgmp10 2:6.1.2+dfsg-2 libgnutls30 3.5.18-1ubuntu1 libgpg-error0 1.27-6 libgpm2 1.20.7-5 libhogweed4 3.4-1 libidn2-0 2.0.4-1.1build2 libklibc 2.0.4-9ubuntu2 libkmod2 24-1ubuntu3.2 liblocale-gettext-perl 1.07-3build2 liblz4-1 0.0~r131-2ubuntu3 liblzma5 5.2.2-1.3 libmount1 2.31.1-0.4ubuntu3.3 libncurses5 6.1-1ubuntu1.18.04 libncursesw5 6.1-1ubuntu1.18.04 libnettle6 3.4-1 libp11-kit0 0.23.9-2 libpam-modules 1.1.8-3.6ubuntu2.18.04.1 libpam-modules-bin 1.1.8-3.6ubuntu2.18.04.1 libpam0g 1.1.8-3.6ubuntu2.18.04.1 libpcre3 2:8.39-9 libpng16-16 1.6.34-1ubuntu0.18.04.2 libprocps6 2:3.3.12-3ubuntu1.1 libseccomp2 2.3.1-2.1ubuntu4.1 libselinux1 2.7-2build2 libsemanage-common 2.7-2build2 libsemanage1 2.7-2build2 libsepol1 2.7-1 libsmartcols1 2.31.1-0.4ubuntu3.3 libssl1.1 1.1.0g-2ubuntu4.3 libstdc++6 8.3.0-6ubuntu1~18.04 libsystemd0 237-3ubuntu10.21 libtasn1-6 4.13-2 libtext-charwidth-perl 0.04-7.1 libtext-iconv-perl 1.7-5build6 libtext-wrapi18n-perl 0.06-7.1 libtinfo5 6.1-1ubuntu1.18.04 libudev1 237-3ubuntu10.21 libunistring2 0.9.9-0ubuntu2 libuuid1 2.31.1-0.4ubuntu3.3 libzstd1 1.3.3+dfsg-2ubuntu1 linux-base 4.5ubuntu1 linux-modules-4.18.0-18-generic 4.18.0-18.19~18.04.1 lsb-base 9.20170808ubuntu1 openssl 1.1.0g-2ubuntu4.3 os-prober 1.74ubuntu1 passwd 1:4.5-1ubuntu2 perl-base 5.26.1-6ubuntu0.3 procps 2:3.3.12-3ubuntu1.1 psmisc 23.1-1ubuntu0.1 sensible-utils 0.0.12 tar 1.29b-2ubuntu0.1 ubuntu-keyring 2018.09.18.1~18.04.0 ucf 3.0038 udev 237-3ubuntu10.21 update-motd 3.6-0ubuntu1 util-linux 2.31.1-0.4ubuntu3.3 uuid-runtime 2.31.1-0.4ubuntu3.3 zlib1g 1:1.2.11.dfsg-0ubuntu2 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-10-25 (1299 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: linux-image-4.18.0-18-generic 4.18.0-18.19~18.04.1 PackageArchitecture: amd64 ProcCpuinfoMinimal: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i7-2860QM CPU @ 2.50GHz stepping : 7 cpu MHz: 2494.338 cache size : 8192 KB physical id: 0 siblings : 1 core id: 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu: yes fpu_exception : yes cpuid level: 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx hypervisor lahf_lm pti bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf bogomips : 4988.67 clflush size : 64 cache_alignment: 64 address sizes : 36 bits physical, 48 bits virtual power management: ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash TERM=ansi LANGUAGE=en_GB:en XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 SourcePackage: linux-signed-hwe Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-02-08 (97 days ago) _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828712 Title: I/O errors when trying t
[Bug 1828712] Re: I/O errors when trying to loop mount an image
Sorry I cannot run apport-collect as the machine has no GUI. I have tried the command on the console and via ssh but the resulting text-mode screen seems to prevent me entering my email address to log in. I also tried apport-cli but it had the same problem with the same authentication screen. As for logs, I did include the relevant syslog entries in the original report, if that helps. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828712 Title: I/O errors when trying to loop mount an image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828712] Re: I/O errors when trying to loop mount an image
Setting package to linux kernel as advised for a filesystem issue. Ran apport-collect -p linux 1828712 per the instructions but I don't know that it worked as machine has no GUI. ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828712 Title: I/O errors when trying to loop mount an image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828712] [NEW] I/O errors when trying to loop mount an image
Public bug reported: Command sudo mount -t vfat flop1 /mnt/flop1 fails. The image is readable but the log shows many I/O errors such as May 12 07:57:24 us64a kernel: [69801.335823] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.337707] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.339521] FAT-fs (loop0): unable to read boot sector May 12 07:57:24 us64a kernel: [69801.342063] print_req_error: I/O error, dev loop0, sector 0 May 12 07:57:24 us64a kernel: [69801.343891] Buffer I/O error on dev loop0, logical block 0, async page read May 12 07:57:24 us64a kernel: [69801.345974] print_req_error: I/O error, dev loop0, sector 1 May 12 07:57:24 us64a kernel: [69801.347832] Buffer I/O error on dev loop0, logical block 1, async page read May 12 07:57:24 us64a kernel: [69801.349928] print_req_error: I/O error, dev loop0, sector 2 May 12 07:57:24 us64a kernel: [69801.351818] Buffer I/O error on dev loop0, logical block 2, async page read May 12 07:57:24 us64a kernel: [69801.356103] print_req_error: I/O error, dev loop0, sector 3 May 12 07:57:24 us64a kernel: [69801.356109] Buffer I/O error on dev loop0, logical block 3, async page read May 12 07:57:24 us64a kernel: [69801.356117] print_req_error: I/O error, dev loop0, sector 4 May 12 07:57:24 us64a kernel: [69801.356119] Buffer I/O error on dev loop0, logical block 4, async page read May 12 07:57:24 us64a kernel: [69801.356122] print_req_error: I/O error, dev loop0, sector 5 May 12 07:57:24 us64a kernel: [69801.356125] Buffer I/O error on dev loop0, logical block 5, async page read May 12 07:57:24 us64a kernel: [69801.356128] print_req_error: I/O error, dev loop0, sector 6 May 12 07:57:24 us64a kernel: [69801.356130] Buffer I/O error on dev loop0, logical block 6, async page read May 12 07:57:24 us64a kernel: [69801.356134] print_req_error: I/O error, dev loop0, sector 7 May 12 07:57:24 us64a kernel: [69801.356136] Buffer I/O error on dev loop0, logical block 7, async page read May 12 07:57:24 us64a kernel: [69801.356260] Buffer I/O error on dev loop0, logical block 0, async page read May 12 07:57:24 us64a kernel: [69801.356263] Buffer I/O error on dev loop0, logical block 1, async page read The command, understandably, reports "can't read superblock on /dev/loop0". The problem happens even on newly created images. Here's a sample set of commands and responses: $ mkfs.msdos -C flop1 1440 $ ls -l -rwxrwxrwx 1 root root 1474560 May 10 18:49 flop1 $ hd flop1 <--- output looks reasonable including 55 aa and two FATs ---> $ sudo mkdir /mnt/flop1 $ sudo mount -o loop flop1 /mnt/flop1 mount: /mnt/flop1: can't read superblock on /dev/loop0. $ losetup -f /dev/loop0 $ I see plenty of reports of similar on different websites but without resolution, including one on Launchpad but where the OP stopped responding so it did not get resolved. I don't know when this problem started to occur on this machine. If it's relevant, this is running under VirtualBox which reports itself as Version 5.2.26 r128414 (Qt5.6.2) with their 'host extensions' enabled. However, mounting a floppy image previously worked on this virtual machine. I have rebooted with /forcefsck to check the root (and only) filesystem. I have upgraded to the latest LTS Ubuntu, as below, but the problem persists. System info: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic Linux us64a 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:22:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The machine is command-line only, i.e. no windowing. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828712 Title: I/O errors when trying to loop mount an image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1828712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 508901] Re: update-grub sets wrong root argument
HOLY COW This bug was reported in 2010 AND STILL HAS NOT BEEN FIXED ! Totally unacceptable. To make sure we have a common understanding. I have linux on partition sda9 and "other" version of linux on partitions sda8, sdb8, and sdb9. The menu entries for ALL the "other" linuxes all specify the sda8 partition is the root partition, which is wrong for the sdb8 and sdb9 partitions. The bug applies if one is specifying the root using UUID or device name. I have inserted the following line into 30_os-prober as a Bug-Work- Around. The BWA only works because I am specifing root with a device name and not a UUID. A different BWA would be required for those using UUID. Fixing this should not be a major undertaking. I cannot fathom why in some much time it has not been addressed. LPARAMS=`echo $LPARAMS | sed "s:root=/dev/[A-Za-z0-9]* :root=$LROOT :"` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/508901 Title: update-grub sets wrong root argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/508901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757328] [NEW] package systemd 237-3ubuntu 4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Description:Ubuntu 17.10 Release:17.10 systemd: Installed: 237-3ubuntu4 Candidate: 237-3ubuntu4 Expected updating with `do-release-upgrade -d` to succeed, however failed during the install of the systemd package. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: systemd 237-3ubuntu4 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Function not implemented Date: Wed Mar 21 04:10:47 2018 Dmesg: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcInterrupts: ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: sort: cannot read: /proc/modules: No such file or directory RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.2.25 SourcePackage: systemd Title: package systemd 237-3ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2018-03-21 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful third-party-packages uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757328 Title: package systemd 237-3ubuntu 4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1757328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit st
Same issue occurs with 17.10 -> 18.04 on WSL -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748659 Title: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752524] Re: package bash 4.3-14ubuntu1.2 fa iled to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped
*** This bug is a duplicate of bug 1725333 *** https://bugs.launchpad.net/bugs/1725333 ** This bug has been marked a duplicate of bug 1725333 do-release-upgrade broke WSL -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752524 Title: package bash 4.3-14ubuntu1.2 fa iled to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1752524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752524] [NEW] package bash 4.3-14ubuntu1.2 fa iled to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped
Public bug reported: 16.04 -> 17.10 release upgrade within Windows Subsystem for Linux ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bash 4.3-14ubuntu1.2 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Mar 1 08:45:25 2018 Dmesg: ErrorMessage: subprocess new pre-installation script was killed by signal (Aborted), core dumped RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.2.25 SourcePackage: bash Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to xenial on 2018-03-01 (0 days ago) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package uec-images xenial ** Description changed: - 16.04 -> 17.10 release upgrade within Windows Subsystem for Linux using - the Ubuntu image + 16.04 -> 17.10 release upgrade within Windows Subsystem for Linux ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bash 4.3-14ubuntu1.2 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Mar 1 08:45:25 2018 Dmesg: - + ErrorMessage: subprocess new pre-installation script was killed by signal (Aborted), core dumped RelatedPackageVersions: - dpkg 1.18.24ubuntu1 - apt 1.2.25 + dpkg 1.18.24ubuntu1 + apt 1.2.25 SourcePackage: bash Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to xenial on 2018-03-01 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752524 Title: package bash 4.3-14ubuntu1.2 fa iled to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1752524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564269] Re: 12.04 -> 14.04 upgrade fails in apache2
I ran into this issue. And it looks my fault for not using a2enmod. ls -l /etc/apache2/mods-enabled/proxy.load lrwxrwxrwx 1 root root 38 Nov 11 2014 proxy.load -> /etc/apache2/mods-available/proxy.load This breaks apache2.postinst: target=$(readlink "$link") || true ... if [ ! -e "/etc/apache2/mods-enabled/$target" ] ; then Replacing the symlink targets with relative paths also works around the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564269 Title: 12.04 -> 14.04 upgrade fails in apache2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1564269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1407521] Re: C compiler bcc struct passing fails
Attached a short program which can be compiled in order to see the problem. Compile with bcc -ansi -S struct_pass.c Then scroll down the resulting assembly file struct_pass.s to get past the comments. On my system the errant code began at line 235. ** Attachment added: "Source code struct_pass.c to help show the bug" https://bugs.launchpad.net/ubuntu/+source/linux86/+bug/1407521/+attachment/4292104/+files/struct_pass.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407521 Title: C compiler bcc struct passing fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux86/+bug/1407521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1407521] [NEW] C compiler bcc struct passing fails
Public bug reported: C compiler bcc copies structs and returns structs correctly but fails to pass them to functions. From checking it turns out that the generated code calls _memcpy with the wrong parameters. For example, this is the generated assembly which should pass a 6-byte struct to a function. ! Debug: list struct composite original = [S+$14-$C] (used reg = ) add sp,*-6 mov ax,sp <--- presumably the target address mov ax,*6 <--- gets overwritten by the size of the struct pushax <--- push the size of the struct lea bx,-$A[bp] pushbx <--- push the source address pushax <--- should be the target address call_memcpy add sp,*6 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bcc 0.16.17-3.1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 Date: Sun Jan 4 22:58:22 2015 ProcEnviron: SHELL=/bin/bash TERM=ansi PATH=(custom, user) LANG=en_GB.utf8 XDG_RUNTIME_DIR= SourcePackage: linux86 UpgradeStatus: Upgraded to trusty on 2014-06-20 (198 days ago) ** Affects: linux86 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407521 Title: C compiler bcc struct passing fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux86/+bug/1407521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1238321] Re: after upgrade to 0.27 transcoded files no longer have audio
I have the same problem in 0.27 with missing audio after transcoding. But sometimes I can transcode and audio still works. I think I've narrowed it down to the scenarios below. WORKING AUDIO - 1. mythtranscode with lossless mpeg2 and honor cutlist 2. mythtranscode with mpeg4 and NO cutlist output from avplay for transcoded file with audio working (mpeg2 trimmed by cutlist) james@tvserver:/var/lib/mythtv/livetv$ avplay cutmpeg2.nuv avplay version 0.8.8-4:0.8.8-0ubuntu0.12.04.1, Copyright (c) 2003-2013 the Libav developers built on Oct 22 2013 12:31:55 with gcc 4.6.3 [mpeg @ 0x7f0428c0] max_analyze_duration reached Input #0, mpeg, from 'cutmpeg2.nuv': Duration: 00:00:59.95, start: 0.310533, bitrate: 2869 kb/s Stream #0.0[0x1e0]: Video: mpeg2video (Main), yuv420p, 704x480 [PAR 10:11 DAR 4:3], 15000 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0.1[0x80]: Audio: ac3, 48000 Hz, stereo, s16, 192 kb/s 1.10 A-V: -0.010 s:0.0 aq= 320KB vq= 3986KB sq=0B f=0/0 f=0/0 = Note the audio stream above just says "stereo". MISSING AUDIO - 1. mythtranscode with mpeg4 and honor cutlist Output from avplay for transcoded file with no audio (mpeg4 trimmed by cutlist) james@tvserver:/var/lib/mythtv/livetv$ avplay cutmpeg4.nuv avplay version 0.8.8-4:0.8.8-0ubuntu0.12.04.1, Copyright (c) 2003-2013 the Libav developers built on Oct 22 2013 12:31:55 with gcc 4.6.3 [nuv @ 0x7fb2c8c0] max_analyze_duration reached [nuv @ 0x7fb2c8c0] Estimating duration from bitrate, this may be inaccurate Input #0, nuv, from 'cutmpeg4.nuv': Duration: 00:03:57.05, start: 0.033000, bitrate: 1411 kb/s Stream #0.0: Video: mpeg4, yuv420p, 1056x720, PAR 10:11 DAR 4:3, 30.30 fps, 29.97 tbr, 1k tbn, 1k tbc Stream #0.1: Audio: mp3, 48000 Hz, 2 channels, s16, 1411 kb/s 0.00 A-V: -1.969 s:0.0 aq=0KB vq=15370KB sq=0B f=0/0 f=0/0 = I can't seem to get avplay to admit that there is no audio. But nothing comes out. The only difference between this output and one where audio works is the "max_analyze_duration reached" message and that the audio stream says it is "2 channels". mythtranscode output when using mpeg4 and honor cutlist james@tvserver:/var/lib/mythtv/livetv$ mythtranscode -i 2223_20131117010600.mpg -o cutmpeg4.nuv -p "High Quality" --honorcutlist 2013-11-16 20:13:12.990782 C mythtranscode version: fixes/0.27 [v0.27-75-g45459f9] www.mythtv.org 2013-11-16 20:13:12.990795 C Qt version: compile: 4.8.1, runtime: 4.8.1 2013-11-16 20:13:12.990802 N Enabled verbose msgs: general 2013-11-16 20:13:12.990809 N Setting Log Level to LOG_INFO 2013-11-16 20:13:13.001482 I Added logging to the console 2013-11-16 20:13:13.002141 I Setup Interrupt handler 2013-11-16 20:13:13.002154 I Setup Terminated handler 2013-11-16 20:13:13.002165 I Setup Segmentation fault handler 2013-11-16 20:13:13.002175 I Setup Aborted handler 2013-11-16 20:13:13.002185 I Setup Bus error handler 2013-11-16 20:13:13.002196 I Setup Floating point exception handler 2013-11-16 20:13:13.002206 I Setup Illegal instruction handler 2013-11-16 20:13:13.002221 I Setup Real-time signal 0 handler 2013-11-16 20:13:13.002265 N Using runtime prefix = /usr 2013-11-16 20:13:13.002278 N Using configuration directory = /home/james/.mythtv 2013-11-16 20:13:13.002357 I Assumed character encoding: en_US.UTF-8 2013-11-16 20:13:13.002766 N Empty LocalHostName. 2013-11-16 20:13:13.002775 I Using localhost value of tvserver 2013-11-16 20:13:13.002817 I Testing network connectivity to '192.168.1.4' 2013-11-16 20:13:13.004212 I Starting process manager 2013-11-16 20:13:13.004186 I Starting IO manager (read) 2013-11-16 20:13:13.004240 I Starting process signal handler 2013-11-16 20:13:13.004376 I Starting IO manager (write) 2013-11-16 20:13:13.103557 I New Client: (#1) 2013-11-16 20:13:13.118989 N Setting QT default locale to EN_US 2013-11-16 20:13:13.119076 I Current locale EN_US 2013-11-16 20:13:13.119127 N Reading locale defaults from /usr/share/mythtv//locales/en_us.xml 2013-11-16 20:13:13.126350 I Loading en_us translation for module mythfrontend 2013-11-16 20:13:13.128557 N Transcoding from 2223_20131117010600.mpg to cutmpeg4.nuv 2013-11-16 20:13:13.157261 I AFD: codec AC3 has 2 channels 2013-11-16 20:13:13.157620 I AFD: Opened codec 0x18aa000, id(AC3) type(Audio) 2013-11-16 20:13:13.160513 I AFD: Opened codec 0x18a95a0, id(MPEG2VIDEO) type(Video) 2013-11-16 20:13:13.160687 N AudioPlayer: Enabling Audio 2013-11-16 20:13:13.172275 I Honoring the cutlist while transcoding 2013-11-16 20:13:13.173138 I Cutlist: 0-2353,4150-11802 2013-11-16 20:13:13.173149 I Original Length: 11802 frames 2013-11-16 20:13:13.173154 I New Length : 1797 frames 2013-11-16 20:13:13.186324 I Resizing from 704x480 to 1056x720 2
[Bug 1092883] Re: Disk report of Unhandled error code
The issue occurred again. Will try to make some sense of it. Whatever is causing the initial failure of access to one of the disks, when the error occurs the kernel or driver subsystem seems to go into an infinite loop (or a number of infinite loops - see below). Even if the disk is pulled from the machine (SATA, hot swap) the kernel continues to emit the error messages and does not recognise removal of the device. After the kernel reports: Jan 29 22:17:15 s01 kernel: [772716.664170] ata9.00: disabled Jan 29 22:17:15 s01 kernel: [772716.664176] ata9: EH complete it then starts what seem to be a number of loops - possibly because there are different disk requests outstanding (but that is just a guess) - each reporting: Jan 29 22:17:15 s01 kernel: [772716.664204] sd 8:0:0:0: [sdg] Unhandled error code Jan 29 22:17:15 s01 kernel: [772716.664207] sd 8:0:0:0: [sdg] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Here are some examples of lines that were reported thousands of times (about 70 reports per second) until the machine was rebooted. Jan 29 22:17:15 s01 kernel: [772716.664331] end_request: I/O error, dev sdg, sector 4096 Jan 29 22:17:15 s01 kernel: [772716.672247] end_request: I/O error, dev sdg, sector 3388584944 Both of the above were always to the same sector. Jan 29 22:17:15 s01 kernel: [772716.685014] EXT2-fs (sdg2): error: read_block_bitmap: Cannot read block bitmap - block_group = 12926, block_bitmap = 423572606 This was always the same block_bitmap number. HTH, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
Updated to latest kernel. At the time I downloaded it the latest was slightly after the one Joseph pointed me to so used the latest one. The stanza it added to menu.lst was title Ubuntu 12.04.1 LTS, kernel 3.8.0-030800rc2-generic root(hd0,2) kernel /boot/vmlinuz-3.8.0-030800rc2-generic root=LABEL=s01-root ro initrd /boot/initrd.img-3.8.0-030800rc2-generic quiet Unfortunately - the machine behaved oddly on the updated kernel. Even keyboard input was garbled. Had to use power button to reboot. So was unable to verify whether the problem exists on the new kernel. Sorry. As directed have added the tag kernel-unable-to-test-upstream. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
Will try to test the upstream kernel and then report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
Not sure if it is related but the following has happened since recent upgrade to kernel 3.2.0-35-generic-pae. Once it happens the machine has long pauses between certain operations (GUI updates like alt-tab, responding to command-line commands like lsb_release -a, and file accesses such as directory reads) as if it waits for something and times out before responding. Again, is it possible that disk errors are not being properly understood by the kernel or drivers? Jan 2 16:05:26 s01 kernel: [ 3600.304094] INFO: task flush-8:32:3521 blocked for more than 120 seconds. Jan 2 16:05:26 s01 kernel: [ 3600.304098] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 2 16:05:26 s01 kernel: [ 3600.304102] flush-8:32 D 0 3521 2 0x Jan 2 16:05:26 s01 kernel: [ 3600.304109] cf53bba8 0046 f6b59658 c88340b8 c180b020 c1931e00 c1931e00 Jan 2 16:05:26 s01 kernel: [ 3600.304119] 989c16d8 0327 f7bbae00 e0e88000 c180b020 00164400 0282 0006 Jan 2 16:05:26 s01 kernel: [ 3600.304128] 0010 e0872200 f6b59658 cf53bb94 f6b59658 0010 cf53bbb0 0246 Jan 2 16:05:26 s01 kernel: [ 3600.304138] Call Trace: Jan 2 16:05:26 s01 kernel: [ 3600.304148] [] schedule+0x35/0x50 Jan 2 16:05:26 s01 kernel: [ 3600.304153] [] io_schedule+0x78/0xb0 Jan 2 16:05:26 s01 kernel: [ 3600.304158] [] get_request_wait+0xbd/0x190 Jan 2 16:05:26 s01 kernel: [ 3600.304165] [] ? cfq_merge+0x63/0x90 Jan 2 16:05:26 s01 kernel: [ 3600.304171] [] ? add_wait_queue+0x50/0x50 Jan 2 16:05:26 s01 kernel: [ 3600.304175] [] blk_queue_bio+0x62/0x2e0 Jan 2 16:05:26 s01 kernel: [ 3600.304190] [] generic_make_request.part.47+0x59/0x90 Jan 2 16:05:26 s01 kernel: [ 3600.304194] [] generic_make_request+0x57/0x60 Jan 2 16:05:26 s01 kernel: [ 3600.304198] [] submit_bio+0x6f/0x100 Jan 2 16:05:26 s01 kernel: [ 3600.304203] [] ? bio_alloc_bioset+0x40/0xc0 Jan 2 16:05:26 s01 kernel: [ 3600.304208] [] submit_bh+0xd1/0x100 Jan 2 16:05:26 s01 kernel: [ 3600.304212] [] __block_write_full_page+0x22b/0x390 Jan 2 16:05:26 s01 kernel: [ 3600.304216] [] ? blkdev_get_blocks+0xe0/0xe0 Jan 2 16:05:26 s01 kernel: [ 3600.304220] [] block_write_full_page_endio+0xa1/0xe0 Jan 2 16:05:26 s01 kernel: [ 3600.304224] [] ? end_buffer_async_read+0x110/0x110 Jan 2 16:05:26 s01 kernel: [ 3600.304228] [] ? blkdev_get_blocks+0xe0/0xe0 Jan 2 16:05:26 s01 kernel: [ 3600.304233] [] ? vt8237_force_hpet_resume+0x40/0x70 Jan 2 16:05:26 s01 kernel: [ 3600.304237] [] block_write_full_page+0x17/0x20 Jan 2 16:05:26 s01 kernel: [ 3600.304241] [] ? end_buffer_async_read+0x110/0x110 Jan 2 16:05:26 s01 kernel: [ 3600.304245] [] blkdev_writepage+0x14/0x20 Jan 2 16:05:26 s01 kernel: [ 3600.304249] [] __writepage+0x10/0x40 Jan 2 16:05:26 s01 kernel: [ 3600.304253] [] write_cache_pages+0x193/0x3f0 Jan 2 16:05:26 s01 kernel: [ 3600.304258] [] ? set_page_dirty_lock+0x50/0x50 Jan 2 16:05:26 s01 kernel: [ 3600.304262] [] generic_writepages+0x3c/0x60 Jan 2 16:05:26 s01 kernel: [ 3600.304266] [] do_writepages+0x22/0x40 Jan 2 16:05:26 s01 kernel: [ 3600.304271] [] writeback_single_inode+0x129/0x390 Jan 2 16:05:26 s01 kernel: [ 3600.304275] [] writeback_sb_inodes+0x159/0x1f0 Jan 2 16:05:26 s01 kernel: [ 3600.304279] [] __writeback_inodes_wb+0x74/0xa0 Jan 2 16:05:26 s01 kernel: [ 3600.304283] [] wb_writeback+0x22b/0x2d0 Jan 2 16:05:26 s01 kernel: [ 3600.304287] [] ? global_dirty_limits+0x2a/0x120 Jan 2 16:05:26 s01 kernel: [ 3600.304291] [] wb_do_writeback+0x137/0x160 Jan 2 16:05:26 s01 kernel: [ 3600.304297] [] ? lock_timer_base.isra.30+0x2b/0x50 Jan 2 16:05:26 s01 kernel: [ 3600.304301] [] bdi_writeback_thread+0x75/0x240 Jan 2 16:05:26 s01 kernel: [ 3600.304305] [] ? wb_do_writeback+0x160/0x160 Jan 2 16:05:26 s01 kernel: [ 3600.304309] [] kthread+0x6d/0x80 Jan 2 16:05:26 s01 kernel: [ 3600.304313] [] ? flush_kthread_worker+0x80/0x80 Jan 2 16:05:26 s01 kernel: [ 3600.304318] [] kernel_thread_helper+0x6/0x10 and a few minutes later: Jan 2 16:07:54 s01 udevd[2955]: timeout 'udisks-part-id /dev/sdc1' Jan 2 16:07:55 s01 udevd[2955]: timeout: killing 'udisks-part-id /dev/sdc1' [3537] Jan 2 16:07:55 s01 udevd[2955]: 'udisks-part-id /dev/sdc1' [3537] terminated by signal 9 (Killed) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
This shouldn't have been closed as a disk issue. The bug report wasn't for the disk error but that Linux didn't handle the error! That handling could be as simple as reporting what was wrong but if Linux doesn't recognise the error code it can never know if it is handling it correctly. ** Changed in: linux (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] [NEW] Disk report of Unhandled error code
Public bug reported:
Repeated message such as
Dec 21 10:56:03 s01 kernel: [12597.472089] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.472093] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.472098] sd 8:0:0:0: [sde] CDB: Read(10): 28
00 6e b6 92 00 00 02 00 00
Dec 21 10:56:03 s01 kernel: [12597.472113] end_request: I/O error, dev sde,
sector 1857458688
Once this occurs it is reported a number of times per second apparently
on a continuous basis. The sector number does increase but I'm not sure
whether the disk driver is really trying to access the disk.
To show the above log entries in context here are a few lines before
them and a few after.
Dec 21 10:55:03 s01 kernel: [12537.438622] ata9.00: exception Emask 0x10 SAct
0x1 SErr 0x8 action 0xe frozen
Dec 21 10:55:03 s01 kernel: [12537.438628] ata9.00: irq_stat 0x00100010, PHY
RDY changed
Dec 21 10:55:03 s01 kernel: [12537.438633] ata9: SError: { 10B8B }
Dec 21 10:55:03 s01 kernel: [12537.438638] ata9.00: failed command: READ FPDMA
QUEUED
Dec 21 10:55:03 s01 kernel: [12537.438646] ata9.00: cmd
60/00:00:00:92:b6/02:00:6e:00:00/40 tag 0 ncq 262144 in
Dec 21 10:55:03 s01 kernel: [12537.438648] res
f2/36:00:00:00:00/00:00:00:01:f2/00 Emask 0x12 (ATA bus error)
Dec 21 10:55:03 s01 kernel: [12537.438652] ata9.00: status: { Busy }
Dec 21 10:55:03 s01 kernel: [12537.438655] ata9.00: error: { IDNF ABRT }
Dec 21 10:55:03 s01 kernel: [12537.438662] ata9: hard resetting link
Dec 21 10:55:13 s01 kernel: [12547.444041] ata9: softreset failed (timeout)
Dec 21 10:55:13 s01 kernel: [12547.444048] ata9: hard resetting link
Dec 21 10:55:23 s01 kernel: [12557.456048] ata9: softreset failed (timeout)
Dec 21 10:55:23 s01 kernel: [12557.456055] ata9: hard resetting link
Dec 21 10:55:58 s01 kernel: [12592.460049] ata9: softreset failed (timeout)
Dec 21 10:55:58 s01 kernel: [12592.460057] ata9: limiting SATA link speed to
1.5 Gbps
Dec 21 10:55:58 s01 kernel: [12592.460061] ata9: hard resetting link
Dec 21 10:56:03 s01 kernel: [12597.472038] ata9: softreset failed (timeout)
Dec 21 10:56:03 s01 kernel: [12597.472046] ata9: reset failed, giving up
Dec 21 10:56:03 s01 kernel: [12597.472050] ata9.00: disabled
Dec 21 10:56:03 s01 kernel: [12597.472064] ata9: EH complete
Dec 21 10:56:03 s01 kernel: [12597.472089] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.472093] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.472098] sd 8:0:0:0: [sde] CDB: Read(10): 28
00 6e b6 92 00 00 02 00 00
Dec 21 10:56:03 s01 kernel: [12597.472113] end_request: I/O error, dev sde,
sector 1857458688
Dec 21 10:56:03 s01 kernel: [12597.472250] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.472254] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.472258] sd 8:0:0:0: [sde] CDB: Read(10): 28
00 6e b6 92 00 00 00 08 00
Dec 21 10:56:03 s01 kernel: [12597.472271] end_request: I/O error, dev sde,
sector 1857458688
Dec 21 10:56:03 s01 kernel: [12597.472378] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.472381] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.472386] sd 8:0:0:0: [sde] CDB: Read(10): 28
00 6e b6 92 08 00 00 08 00
Dec 21 10:56:03 s01 kernel: [12597.472398] end_request: I/O error, dev sde,
sector 1857458696
Dec 21 10:56:03 s01 kernel: [12597.473888] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.473891] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.473896] sd 8:0:0:0: [sde] CDB: Read(10): 28
00 6e b6 92 10 00 00 08 00
Dec 21 10:56:03 s01 kernel: [12597.473910] end_request: I/O error, dev sde,
sector 1857458704
Dec 21 10:56:03 s01 kernel: [12597.473953] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.473957] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.473962] sd 8:0:0:0: [sde] CDB: Read(10): 28
00 6e b6 92 18 00 00 08 00
Dec 21 10:56:03 s01 kernel: [12597.473976] end_request: I/O error, dev sde,
sector 1857458712
Dec 21 10:56:03 s01 kernel: [12597.474014] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.474017] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.474022] sd 8:0:0:0: [sde] CDB: Read(10): 28
00 6e b6 92 20 00 00 08 00
Dec 21 10:56:03 s01 kernel: [12597.474035] end_request: I/O error, dev sde,
sector 1857458720
Dec 21 10:56:03 s01 kernel: [12597.474073] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.474087] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.474091] sd 8:0:0
[Bug 734883] Re: iPod won't mount
i am having the same problem with a current 160GB ipod. I'm pretty new to linux, can someone point me towards some instructions on how to downgrade the kernel so I can get my ipod mounted? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/734883 Title: iPod won't mount -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366606] Re: DVB-T PCI card not working in 9.04
This is still a problem for me. I have tried booting with kernel 2.6.27-14-generic and the DVB problem goes away and I can record again BUT this impacts playback. Audio is fine but any file played back has choppy video as if the system plays back only one frame in two or three. This renders the machine almost useless. I can either record or I can play back but not both unless I reboot between recording and playing back. Does anyone know how to get back to the Ubuntu 8.10 scenario which worked OK? James -- DVB-T PCI card not working in 9.04 https://bugs.launchpad.net/bugs/366606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 399120] Re: NFS mounts cause mythtv-common to fail to install
Sorry - I never got round to following up your previous email. As I mentioned earlier this was a transient issue and was not causing me a problem. Well done for finding a fix, though. 2009/9/11 Mario Limonciello : > I made a best guess at how to fix this in mythtv-trunk-022 bzr #163, > hopefully that does it right. > > ** Changed in: mythtv (Ubuntu) > Status: Incomplete => Fix Committed > > -- > NFS mounts cause mythtv-common to fail to install > https://bugs.launchpad.net/bugs/399120 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “mythtv” package in Ubuntu: Fix Committed > > Bug description: > Binary package hint: update-manager > > Carrying out a dist upgrade > > ProblemType: Package > Architecture: i386 > DistroRelease: Ubuntu 8.10 > ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process > /usr/bin/dpkg returned an error code (1) > > Package: update-manager 1:0.93.34 > PackageArchitecture: all > SourcePackage: update-manager > Title: package update-manager 1:0.93.34 failed to install/upgrade: > ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg > returned an error code (1) > Uname: Linux 2.6.24-24-generic i686 > -- James Harris james.harri...@googlemail.com -- NFS mounts cause mythtv-common to fail to install https://bugs.launchpad.net/bugs/399120 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366606] Re: DVB-T PCI card not working in 9.04
I have the same problem. All was OK (with all packages updated) under Ubuntu 8.10. Since the upgrade to 9.04 the problem occurs. It is trying to access a Nebula DigiTV PCI card with a Zarlink mt352 chip and driver. -- DVB-T PCI card not working in 9.04 https://bugs.launchpad.net/bugs/366606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368215] Re: Nebula DigiTV DVB-T (PCI) no longer works
Same issue. Why did I upgrade...? Any time the machine tries to record it gets ret of -6 as follows. Sep 9 01:21:06 hfx1 kernel: [ 277.606234] mt352_read_register: readreg error (reg=137, ret==-6) Sep 9 01:21:06 hfx1 kernel: [ 277.606869] mt352_read_register: readreg error (reg=138, ret==-6) Sep 9 01:21:06 hfx1 kernel: [ 277.647684] mt352_write() to reg 51 failed (err = -6)! Sep 9 01:21:06 hfx1 kernel: [ 277.648629] mt352_write() to reg 5d failed (err = -6)! Sep 9 01:21:06 hfx1 kernel: [ 277.699342] mt352_read_register: readreg error (reg=0, ret==-6) Sep 9 01:21:06 hfx1 kernel: [ 277.739990] mt352_read_register: readreg error (reg=0, ret==-6) Sep 9 01:21:06 hfx1 kernel: [ 277.742616] mt352_read_register: readreg error (reg=20, ret==-6) Sep 9 01:21:06 hfx1 kernel: [ 277.743249] mt352_read_register: readreg error (reg=21, ret==-6) etc etc -- Nebula DigiTV DVB-T (PCI) no longer works https://bugs.launchpad.net/bugs/368215 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 399120] Re: package update-manager 1:0.93.34 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)
Yes, the machine being upgraded had NFS mounts. Apart from the error message and a bit of retrying everything seems to have upgraded properly. Is there a way I can check whether the mythtv- common post-installation script has run successfully? Other than that as far as I am concerned this is no longer an issue and doesn't need to be kept open unless you want to do something to address it. I cannot imagine why the NFS mounts caused the local machine upgrade to fail. But it seems to have been a minor and transient issue. -- package update-manager 1:0.93.34 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/399120 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 399120] Re: package update-manager 1:0.93.34 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/28996403/Dependencies.txt ** Attachment added: "VarLogDistupgradeAptlog.gz" http://launchpadlibrarian.net/28996404/VarLogDistupgradeAptlog.gz ** Attachment added: "VarLogDistupgradeApttermlog.gz" http://launchpadlibrarian.net/28996405/VarLogDistupgradeApttermlog.gz ** Attachment added: "VarLogDistupgradeMainlog.gz" http://launchpadlibrarian.net/28996406/VarLogDistupgradeMainlog.gz ** Attachment added: "VarLogDistupgradeTermlog.gz" http://launchpadlibrarian.net/28996407/VarLogDistupgradeTermlog.gz -- package update-manager 1:0.93.34 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/399120 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 399120] [NEW] package update-manager 1:0.93.34 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)
Public bug reported: Binary package hint: update-manager Carrying out a dist upgrade ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 8.10 ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) Package: update-manager 1:0.93.34 PackageArchitecture: all SourcePackage: update-manager Title: package update-manager 1:0.93.34 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) Uname: Linux 2.6.24-24-generic i686 ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package -- package update-manager 1:0.93.34 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1) https://bugs.launchpad.net/bugs/399120 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
