[Bug 768791] Re: isoinfo: Unable to find Joliet SVD (USB creator won't select ISO for creating boot USB)

[David Coe]

Ubuntu 21.04

This bug is still present :-(. Ubuntu ISOs appear in usb-creator-kde
source window OK (afik). Many others do not (debian-
live-10.9.0-amd64-kde.iso, devuan_beowulf_3.1.1_amd64_desktop-live.iso,
...).

Launching from the command line and selecting a problem ISO from the GUI
gives:

isoinfo: Unable to find Joliet SVD

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/768791

Title:
  isoinfo: Unable to find Joliet SVD (USB creator won't select ISO for
  creating boot USB)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/768791/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1906939] Re: kde frontend, ModuleNotFoundError: No module named 'sip'

[David Coe]

Hi Łukasz!

On 29/04/2021 08:52, Łukasz Zemczak wrote:
> Hello ivanto, or anyone else affected,
> 
> Accepted usb-creator into hirsute-proposed. The package will build now
> and be available at https://launchpad.net/ubuntu/+source/usb-
> creator/0.3.10 in a few hours, and then in the -proposed repository.
> 
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
> 
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, what testing has been
> performed on the package and change the tag from verification-needed-
> hirsute to verification-done-hirsute. If it does not fix the bug for
> you, please add a comment stating that, and change the tag to
> verification-failed-hirsute. In either case, without details of your
> testing we will not be able to proceed.
> 
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
> 
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
> 

Usb-creator-kde-0.3.10 updated from hirsute-proposed. Successfully 
writes usb drive. Many thanks.

-- 
David Coe

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906939

Title:
  kde frontend, ModuleNotFoundError: No module named 'sip'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1906939/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916278] Re: Arduino fails to start: undefined symbol: sp_get_port_usb_vid_pid

[David Coe]

Alas, the bug is still there in the just-released Kubuntu 21.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916278

Title:
  Arduino fails to start: undefined symbol: sp_get_port_usb_vid_pid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arduino/+bug/1916278/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter

[David Coe]

Hi Alex!

Herewith a summary of our accumulated results [1] for Surajee's IOMMU
patch using 20 msecs wait and logged retries on AMD's Ryzen:

Ryzen KernelColdWarm

4700U   5.11.0-116  1
3500U   5.11.7   5  6
2500U   5.8.0-455
5.12.0 RC3   5> 5
2400G   5.11.0-116  6
5.8.0-45 5  6
2200G   ? >10

Two points are clear:

1. there are differences between cold and warm boot, mostly marginal but
marked and very consistent with the quite new 4700U.

2. the choice of 5 as the maximum retry number is unfortunate. Mostly,
it guarantees all our Ryzens just fail the IOMMU write test!

The 2200G is a bit of a odd-ball and it's owner, understandably, wants a
more elegant solution than just upping the number of retries. For the
rest of us, a maximum of 6 or 7 would sort it.

Best regards and many thanks

David

[1] https://bugzilla.kernel.org/show_bug.cgi?id=201753

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917203

Title:
  AMD-Vi: Unable to read/write to IOMMU perf counter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917203/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter

[David Coe]

I've just tried Surajee's patch on Ubuntu's latest kernel 5.11.0-11 for
upcoming Hirsute and it consistently unlatches IOMMU after 6 x 20 msec
tries on my Ryzen 2400G. Mainline 5.12-rc2 gave identical results.

Paul Menzel too gets failure even after 10 x 20 msecs on a 2200G and
regards so long a delay as most unacceptable. Alexander Monakov's very
simple patch always works for me but I haven't seen data from other
people. Surajee has mentioned problems with it for some part of AMD's
product range and, as one of AMD's IOMMU experts down at Austen Texas,
he should know his onions :-).

I would be tempted to run with the patch (11 x 20 msecs), log the exit
count number and get some user feedback. Hopefully an improved patch
will emerge! AMD may have commercial as well as technical reasons not
leave it unaddressed.

Best regards

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917203

Title:
  AMD-Vi: Unable to read/write to IOMMU perf counter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917203/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter

[David Coe]

Hi Alex!

There are further results [1] for Suravee's patch on Ryzen 2500U
(BubuXP) and 2400G (myself). Both show a slight difference between cold
boot (retry 5 x 20 msecs = success) and warm boot (retry 6 x 20 msecs =
failure).

It would be worth (even slightly) increasing the number of retries
should you backport this commit <6778ff5b21bd8e78> to hirsute or breezy.

Regards

[1] https://bugzilla.kernel.org/show_bug.cgi?id=201753

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917203

Title:
  AMD-Vi: Unable to read/write to IOMMU perf counter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917203/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter

[David Coe]

Hi Alex!

A splendidly prompt piece of cherry-picking. Many thanks.

I've checked your test release on my Ryzen 2400G on current Ubuntu 20.10 and it 
still gives the diagostic:
  AMD-Vi: Unable to read/write to IOMMU perf counter

It's to be expected! The little crew engaged with testing Suravee
Suthikulpanit's patch [1] are finding that the 2400G (that's me) needs
120 msec for power-gating and the 2200G (that's Paul Menzel] needs >200
msecs. Suravee's RFC v3 provides 5 x 20 msecs delay which just isn't
enough for these lesser Ryzen's :-).

If you change Suravee's patch line

   for (retry = 5; retry; retry--) {
to
   for (retry = 25; retry; retry--) {

all will be well (imho). The maximum delay is indeed outrageous but only
that really necessary to enable IOMMU is actually used. Eventually a
proper solution will be found (in firmware or silicon) but (unlike at
present) the many users of entry-level Ryzen CPU's will not have their
IOMMU crippled during linux boot-up.

Incidentally, if you do rebuild your (very kind) test-release with the
above change (please, please), could you also include the deb package
for linux-tools for the same kernel. Things like the command "perf stat
-a -e amd_iommu/mem_trans_total/ test" (used to test IOMMU performance
in user-space) are tied to the running kernel-version and will then
work.

Best regards and again many thanks

David

[1] https://bugzilla.kernel.org/show_bug.cgi?id=201753

** Bug watch added: Linux Kernel Bug Tracker #201753
   https://bugzilla.kernel.org/show_bug.cgi?id=201753

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917203

Title:
  AMD-Vi: Unable to read/write to IOMMU perf counter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917203/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1916278] [NEW] Arduino fails to start: undefined symbol: sp_get_port_usb_vid_pid

[David Coe]

Same problem here on the alpha Hirsute Hippo :-). Suspect package 
liblistserialsj1 needs attention.

Download version 1.8.13 direct from Arduino. That works fine!

-- 
David Coe

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916278

Title:
  Arduino fails to start: undefined symbol: sp_get_port_usb_vid_pid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arduino/+bug/1916278/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870845] [NEW] Boot diagnostic: Initramfs unpacking failed: Decoding failed

[David Coe]

Public bug reported:

AMD 2400G dual-booting Eoan and Focal (beta) gives both unpacking and
IOMMU diagnostics. Earlier CPUs (eg AMD FX-8350) only show the initramfs
unpacking failure. Neither failure appears fatal!

Booting Eoan, boot screen diagnostic ...

 AMD-Vi: Unable to read/write to IOMMU perf counter

dmesg diagnostic ...

[0.226916] PCI: CLS 64 bytes, default 64
[0.226954] Trying to unpack rootfs image as initramfs...
[0.354744] Initramfs unpacking failed: Decoding failed
[0.354754] fbcon: Taking over console
[0.363736] Freeing initrd memory: 75116K
[0.363852] pci :00:00.2: AMD-Vi: Unable to read/write to IOMMU perf 
counter.
[0.363964] pci :00:00.2: can't derive routing for PCI INT A
[0.363965] pci :00:00.2: PCI INT A: not connected

Booting Focal, boot screen is clean

dmesg diagnostic ...

[0.223341] PCI: CLS 64 bytes, default 64
[0.223389] Trying to unpack rootfs image as initramfs...
[0.360518] Initramfs unpacking failed: Decoding failed
[0.369668] Freeing initrd memory: 78244K
[0.369778] pci :00:00.2: AMD-Vi: Unable to read/write to IOMMU perf 
counter.
[0.369879] pci :00:00.2: can't derive routing for PCI INT A
[0.369880] pci :00:00.2: PCI INT A: not connected

There is a lot of comment (and inconclusive workarounds) in
 on the
unpacking issue. The diagnostic can be removed by changing lz4 to gzip
in /etc/initramfs-tools/initramfs.conf and rerunning update-initramfs
-u.

I can't find guidance on the IOMMU problem - it's just concealed by grub
configured not to take over the fbcon console and (presumably) affects
the VGA port.

Both may require upstream attention (with the kernel) rather than with
with the grub code or configuration. Could you route as appropriate? My
thanks!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: grub-efi-amd64-signed 1.137+2.04-1ubuntu22
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Apr  4 22:46:04 2020
InstallationDate: Installed on 2020-04-03 (1 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
SourcePackage: grub2-signed
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub2-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870845

Title:
  Boot diagnostic: Initramfs unpacking failed: Decoding failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1870845/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1870301] Re: Ubiquity crashes just before completion. Installation does work, however.

[David Coe]

Good morning, Jean-Baptiste!

I've just tried (re)installing the Kubuntu Focal beta on my two Asus 
machines with spare SSD partitions (an old M5A99FX Pro R2.0 and a more 
recent Prime B350-Plus). The latter is the one I had problems with 
Ubiquity crashing.

This time, both installations finished without issues and I'm ploughing 
through configuration of the applications, servers and file-store. So 
far, so good. It's a really nice distribution - hats off to you guys and 
the Plasma folk.

The only difference I can think of is that I did not reformat the 
original target drive (it was pre-formatted ext4 but empty). This time 
around I ticked both format boxes! I've have kept the log files from 
yesterday (there is no /var/log/installer) and will keep looking for 
what went wrong.

Best regards and many thanks.

David Coe

On 02/04/2020 10:33, Jean-Baptiste Lallement wrote:
> Thanks for your report.
>
> Is there any log file in /var/log/installer ? It'd be useful to
> understand what happened. Thanks.
>
> ** Changed in: ubiquity (Ubuntu)
> Status: New => Incomplete
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870301

Title:
  Ubiquity crashes just before completion. Installation does work,
  however.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1870301/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870301] [NEW] Ubiquity crashes just before completion. Installation does work, however.

[David Coe]

Public bug reported:

Ubiquity diagnostics (from beta Live ISO) say something like "packages
may not be correctly installed and may need reinstalling". Post-
installation reboot (as normal) gives a working system but installation
log files (of course) are gone.

Sorry not to be more specific. May try a repeat installation in a few
days time.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Apr  2 09:40:21 2020
InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=04a4096c-2ddf-48c7-9c94-58b83ab1ed43 ro quiet splash vt.handoff=7
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870301

Title:
  Ubiquity crashes just before completion. Installation does work,
  however.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1870301/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs