[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
Will new media be available w/ this fix in place? I ask because running "dkms status" or any dkms command presently triggers this bug for me, and the only way forward I can see to being able to fix that system is new media w/ a patched kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le
TL;DR: pass '-vga none' with -nographic, or redirect the screen somewhere! I ended up digging into this after it was mentioned by smoser. The bug is invalid because of a bad assumption in the QEMU inputs. smoser's workaround of usb=off removes USB as a workaround. The kernel, OpenFirmware, and QEMU are behaving correctly, but the original command-line hides the screen output. If you have both a supported* keyboard AND screen, then OpenFirmware/SLOF sets OF stdout to be the screen. This causes the OF output of 'No console specified using screen & keyboard' If you are missing either a keyboard OR screen, then OF sets stdout to be hvterm (serial). This causes the OF output of 'No console specified using hvterm' https://git.qemu.org/?p=SLOF.git;a=blob;f=board- qemu/slof/OF.fs;h=4e04b840d5e6ff6c39191939e1a4f70f3d169d5d;hb=HEAD#l215 Which devices are available depends on the QEMU commandline... Base QEMU defaults to '-vga std'. QEMU '-machine pseries' defaults to enabling USB. Re supported keyboards: The OpenFirmware/SLOF only seems to support USB keyboards at this time (virtio keyboard not supported). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563887 Title: qemu-system-ppc64 freezes on starting image on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1563887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332643] [NEW] pg_dump: Error message from server: SSL error: ccs received early
Public bug reported: See Debian bug #751093 Extra commit is needed on top of openssl_1.0.1f-1ubuntu2.3: https://git.openssl.org/gitweb/?p=openssl.git;a=commit;h=9beb75d3c4ce9a93ba07951e8595c09f07496ba8 Reproduction instructions 1. Take a large postgres DB (~200GiB here), 2. require hostssl in pg_hba to connect. 3. pg_dump over that hostssl connection. 4. fail out somewhere between 74MiB and 190GiB with: pg_dump: Error message from server: SSL error: ccs received early ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssl 1.0.1f-1ubuntu2.3 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Fri Jun 20 17:27:02 2014 InstallationDate: Installed on 2014-03-21 (91 days ago) InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 (20131016) ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: Upgraded to trusty on 2014-04-03 (78 days ago) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332643 Title: pg_dump: Error message from server: SSL error: ccs received early To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1332643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295819] [NEW] 12.04.4 on FAT32 USB key fails due to filename truncation
Public bug reported: Expect result: Installer should work Actual result: Installer fails to load /pool/main/l/linux-lts-saucy/block-modules-3.11.0-15-generic-di_3.11.0-15.25~precise1_amd64.udeb due to truncated filename. Reproduction Steps: 1. Get the Ubuntu 12.04.4 Server or alternate ISO 2. Run unetbootin 2.1. Format a USB key as FAT32 (required for EFI booting) 2.2. Mount USB key 2.3. Select the ISO in the lower box 2.4. Select the USB key 2.5. Let unetbootin install the ISO to the USB key 3. Examine the USB key filesystem 3.1. /pool/main/l/linux-lts-saucy/block-modules-3.11.0-15-generic-di_3.11.0-15.25~precise1_amd64.udeb should exist 3.2. Notice that the filename is truncated, has the extension of .ude. 3.3. Mostly files in the saucy module/kernel directories affected due to their length. 4. Boot the USB key 5. Select manual install or recover (anything that causes it to load the udeb kernel modules) 6. It will fail because it needs to load the above udeb. Suggested fix: a) Use shorter filenames on install media. b) support truncated filenames ** Affects: debian-installer (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/1295819 Title: 12.04.4 on FAT32 USB key fails due to filename truncation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1295819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
