Bug#993227: gramps: Error installing the PostgreSQL addon into Gramps
Package: gramps Version: 5.1.3-1 Severity: minor X-Debbugs-Cc: jsmith+debb...@alum.mit.edu Dear Maintainer, * What led up to the situation? Trying to install the PostgreSQL addon for Gramps * What exactly did you do (or not do) that was effective (or ineffective)? Ran the Gramps Plugin manager, chose install for postgreSQL * What was the outcome of this action? "The following addon had errors: PostGreSQL" * What outcome did you expect instead? Installation of the addon -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gramps depends on: ii gir1.2-gtk-3.03.24.30-2 ii librsvg2-22.50.3+dfsg-1 ii python3 3.9.2-3 ii python3-bsddb36.2.9-1 ii python3-gi3.40.1-2 ii python3-gi-cairo 3.40.1-2 ii xdg-utils 1.1.3-4.1 Versions of packages gramps recommends: ii gir1.2-geocodeglib-1.0 3.26.2-2 ii gir1.2-gexiv2-0.10 0.12.1-1 ii gir1.2-osmgpsmap-1.01.2.0-1 ii graphviz2.42.2-5 ii python3-icu 2.5-1+b2 Versions of packages gramps suggests: ii fonts-freefont-ttf20120503-10 ii gir1.2-goocanvas-2.0 2.0.4-1+b1 ii gir1.2-gtkspell3-3.0 3.0.10-1 ii python3-numpy 1:1.19.5-1 ii python3-pil 8.1.2+dfsg-0.3 ii rcs 5.10.0-1 PostgreSQL installed: ii postgresql13+225 all ii postgresql-13 13.4-2 amd64 ii postgresql-client 13+225 all ii postgresql-client-13 13.4-2 amd64 ii postgresql-client-common 225 all ii postgresql-common 225 all ii postgresql-contrib13+225 all ii postgresql-doc13+225 all ii postgresql-doc-13 13.4-2 all ii postgresql-filedump 13.1-1 amd64 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gramps depends on: ii gir1.2-gtk-3.03.24.30-2 ii librsvg2-22.50.3+dfsg-1 ii python3 3.9.2-3 ii python3-bsddb36.2.9-1 ii python3-gi3.40.1-2 ii python3-gi-cairo 3.40.1-2 ii xdg-utils 1.1.3-4.1 Versions of packages gramps recommends: ii gir1.2-geocodeglib-1.0 3.26.2-2 ii gir1.2-gexiv2-0.10 0.12.1-1 ii gir1.2-osmgpsmap-1.01.2.0-1 ii graphviz2.42.2-5 ii python3-icu 2.5-1+b2 Versions of packages gramps suggests: ii fonts-freefont-ttf20120503-10 ii gir1.2-goocanvas-2.0 2.0.4-1+b1 ii gir1.2-gtkspell3-3.0 3.0.10-1 ii python3-numpy 1:1.19.5-1 ii python3-pil 8.1.2+dfsg-0.3 ii rcs 5.10.0-1 PostgreSQL installed: -- no debconf information -- no debconf information
Bug#947801: linux-image-5.3.0-3-amd64: b44 module unable to dma to address
Package: src:linux Version: 5.3.15-1 Severity: normal Dear Maintainer, * What led up to the situation? Had been having lockup with swiotlb getting overloaded, added iommu=force, intel_iommu=on, swiotlb=noforce to fix. Have reduced the swiotlb lockup, but now get a freeze on system with the b44 DMA below * What exactly did you do (or not do) that was effective (or ineffective)? Attempting to figure out b44 parametrs to get DMA to work, searched with google on how to overcome DMA issues * What was the outcome of this action? no luck * What outcome did you expect instead? Reduce DMA issues, stop freezes of system -- Package-specific info: ** Version: Linux version 5.3.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 20191130 (Debian 9.2.1-21)) #1 SMP Debian 5.3.15-1 (2019-12-07) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-3-amd64 root=UUID=f0a976b0-b2fa-418b-bdf5-d1666e3c05fb ro iommu=force intel_iommu=on swiotlb=noforce quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 321.030640] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 325.970842] swiotlb_map: 681 callbacks suppressed [ 325.970851] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 325.978046] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 325.985252] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 325.992504] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 325.999757] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 326.007003] b44 :03:00.0: Cannot do DMA to address 0xc3e7e002 [ 326.014247] b44 :03:00.0: Cannot do DMA to address 0xc3e7b002 [ 326.021437] b44 :03:00.0: Cannot do DMA to address 0xc3e79002 [ 326.028655] b44 :03:00.0: Cannot do DMA to address 0xc3e7d002 [ 326.035878] b44 :03:00.0: Cannot do DMA to address 0xc3e7e802 [ 330.976083] swiotlb_map: 681 callbacks suppressed [ 330.976092] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 330.983295] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 330.990535] b44 :03:00.0: Cannot do DMA to address 0xc3e7e002 [ 330.997751] b44 :03:00.0: Cannot do DMA to address 0xc3e7b002 [ 331.005015] b44 :03:00.0: Cannot do DMA to address 0xc3e79002 [ 331.012209] b44 :03:00.0: Cannot do DMA to address 0xc3e7d002 [ 331.019415] b44 :03:00.0: Cannot do DMA to address 0xc3e7e802 [ 331.026683] b44 :03:00.0: Cannot do DMA to address 0xc3e7c802 [ 331.033945] b44 :03:00.0: Cannot do DMA to address 0xc3e7c802 [ 331.041102] b44 :03:00.0: Cannot do DMA to address 0xc3e7e802 [ 335.981437] swiotlb_map: 681 callbacks suppressed [ 335.981446] b44 :03:00.0: Cannot do DMA to address 0xc3e7d002 [ 335.988568] b44 :03:00.0: Cannot do DMA to address 0xc3e7e802 [ 335.995770] b44 :03:00.0: Cannot do DMA to address 0xc3e7c802 [ 336.010229] b44 :03:00.0: Cannot do DMA to address 0xc3e7c802 [ 336.017460] b44 :03:00.0: Cannot do DMA to address 0xc3e7e802 [ 336.024678] b44 :03:00.0: Cannot do DMA to address 0xc3e7d002 [ 336.031882] b44 :03:00.0: Cannot do DMA to address 0xc3e79002 [ 336.039114] b44 :03:00.0: Cannot do DMA to address 0xc3e7b002 [ 336.046375] b44 :03:00.0: Cannot do DMA to address 0xc3e7e002 [ 336.053610] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 340.986518] swiotlb_map: 680 callbacks suppressed [ 340.986527] b44 :03:00.0: Cannot do DMA to address 0xc3e7d002 [ 340.993788] b44 :03:00.0: Cannot do DMA to address 0xc3e79002 [ 341.000963] b44 :03:00.0: Cannot do DMA to address 0xc3e7b002 [ 341.008251] b44 :03:00.0: Cannot do DMA to address 0xc3e7e002 [ 341.015466] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 341.022652] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 341.029887] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 341.037124] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 341.044388] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 341.051624] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 345.991870] swiotlb_map: 681 callbacks suppressed [ 345.991880] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 345.999000] b44 :03:00.0: Cannot do DMA to address 0xc3e78002 [ 346.006239] b44 :03:00.0: Cannot do DMA to address 0xc3e7f802 [ 346.013465] b44 :03:00.0: Cannot do DMA to address 0xc3e7c002 [ 346.020694] b44 :03:00.0: Cannot do DMA to address 0xc3e7e002 [ 346.027896] b44 :03:00.0: Cannot do DMA to address 0xc3e7b002 [ 346.035155] b44 :03:00.0: Cannot do
