[Touch-packages] [Bug 1898547] Re: neutron-linuxbridge-agent fails to start with iptables 1.8.5
I've tested this (s390x, groovy) and im able to launch an instance with the specific version of iptables mentioned above -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1898547 Title: neutron-linuxbridge-agent fails to start with iptables 1.8.5 Status in Ubuntu on IBM z Systems: Fix Committed Status in iptables package in Ubuntu: Fix Committed Status in neutron package in Ubuntu: Invalid Status in iptables source package in Groovy: Fix Committed Status in neutron source package in Groovy: Invalid Status in iptables source package in Hirsute: Fix Committed Status in neutron source package in Hirsute: Invalid Bug description: [Impact] With iptables 1.8.5 neutron-linuxbridge-agent fails to properly start. The log file shows many errors like: 2020-10-05 10:20:37.998 551 ERROR neutron.plugins.ml2.drivers.agent._common_agent ; Stdout: ; Stderr: iptables-restore: line 29 failed This can be demonstrated with a simple test case: iptables-restore
[Touch-packages] [Bug 1780885] [NEW] hangs at Building initial module for 4.15.0-23-generic (promptless password prompt)
Public bug reported: This bug may more specifically be with dkms, but assume most people will hit it this way sudo apt-get update ; sudo apt-get upgrade would hang at: Building initial module for 4.15.0-23-generic after a few seconds, keypresses/enter were not being registered, but there is a secret password prompt - i.e., at this point, when things appear to have hung, entering your password twice will continue the process. It may also be related to 'secure boot' but I am unsure. Similar issue and resolution found here: https://github.com/teejee2008/ukuu/issues/81 ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1780885 Title: hangs at Building initial module for 4.15.0-23-generic (promptless password prompt) Status in apt package in Ubuntu: New Bug description: This bug may more specifically be with dkms, but assume most people will hit it this way sudo apt-get update ; sudo apt-get upgrade would hang at: Building initial module for 4.15.0-23-generic after a few seconds, keypresses/enter were not being registered, but there is a secret password prompt - i.e., at this point, when things appear to have hung, entering your password twice will continue the process. It may also be related to 'secure boot' but I am unsure. Similar issue and resolution found here: https://github.com/teejee2008/ukuu/issues/81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1780885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780885] Re: hangs at Building initial module for 4.15.0-23-generic (promptless password prompt)
Further info: I am running bionic, upgraded from xenial -> zesty -> bionic, and have done previous apt-get upgrade's in bionic without running into this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1780885 Title: hangs at Building initial module for 4.15.0-23-generic (promptless password prompt) Status in apt package in Ubuntu: New Bug description: This bug may more specifically be with dkms, but assume most people will hit it this way sudo apt-get update ; sudo apt-get upgrade would hang at: Building initial module for 4.15.0-23-generic after a few seconds, keypresses/enter were not being registered, but there is a secret password prompt - i.e., at this point, when things appear to have hung, entering your password twice will continue the process. It may also be related to 'secure boot' but I am unsure. Similar issue and resolution found here: https://github.com/teejee2008/ukuu/issues/81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1780885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation
I'm seeing this installing 17.10 on s390x also. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1704929 Title: Repeating "can't open /dev/ttyX: No such device or address" messages during installation Status in Ubuntu on IBM z Systems: New Status in console-setup package in Ubuntu: New Status in console-setup source package in Xenial: New Status in console-setup source package in Zesty: New Status in console-setup source package in Artful: New Bug description: [Impact] console-setup continuously tries to open /dev/tty[1-6] on s390x, when such consoles do not exist on s390x. This can be seen on boot in the output from the initramfs, and during the installer. [Cuase] It seems to me that the postinst of the console-setup is incorrect for s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR, z/VM, KVM) [Solution] I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it to... "guess". Usually it should be slcp, but that depends on which consoles are configured/activated in the given KVM. [Testcase] On boot, scroll all the messages and makesure there are no error messages about inability to open /dev/tty* [Original Bug Report] During the installation (z/VM guest and KVM virtual machine) of Ubuntu Server 16.04.1 (and 16.04.2) repeating messages of the form: " Select and install software ... 10% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 20% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 30%... 40% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 50% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 60% can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 90% The system is going down NOW Sent SIGTERM to all processes Sent SIGKILL to all processes Requesting system reboot 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 00 Storage cleared - system reset. 00 zIPL .. " They start to occur when the software gets installed: "Select and install software ... 10% can't open /dev/tty4: No such device or address" And only stop with the final system reboot at the end of the installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673992] [NEW] init-premount/sysconfig_hardware does not online all DASDs in primary VG - drops to busybox initramfs prompt
Public bug reported:
Unsure if this is an initfs-tools issue, or s390-tools, or other?
Linux s4lpb 4.4.0-67-generic #88-Ubuntu SMP Wed Mar 8 16:39:07 UTC 2017
s390x s390x s390x GNU/Linux
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename: xenial
ii busybox-initramfs1:1.22.0-15ubuntu1
ii initramfs-tools 0.122ubuntu8.8
ii initramfs-tools-bin 0.122ubuntu8.8
ii initramfs-tools-core 0.122ubuntu8.8
ii libklibc 2.0.4-8ubuntu1.16.04.3
ii s390-tools 1.34.0-0ubuntu8.3
Brief description:
I have an s390x LPAR with multiple DASD disks in the 'system' VG -
kernel param specifies root=/dev/mapper/system-root. After preseeding,
and rebooting once, the system drops to BusyBox initramfs prompt, after
errors:
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... lvm
etad is not active yet, using direct activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
Refusing activation of partial LV system/root. Use '--activationmode partial'
to override.
lvmetad is not active yet, using direct activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
done.
Begin: Running /scripts/local-premount ... done.
Begin: Waiting for root file system ...
Begin: Running /scripts/local-block ... lvmetad is not active yet, using direc
t activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
Running vgchange -ay at this point just causes the same error - the DASD
disks still have not been brought online.
init-premount/sysconfig_hardware script brings the first disk in the VG
online - then /scripts/local-top/lvm2 tries to online the LV/VG. This
fails and causes the above error, as the DASD's have not been brought
online by init-premount. If the VG only contains one root disk then the
DASDS are brought online later, but in this situation to boot the system
I need all the PVs in the root LV to be brought online.
The preseed uses d-i partman to create LVM on the primary disk. Other
DASDs are added manually by a script using dasdfmt, fdasd, chzdev.
Validated workaround:
Create a script, e.g.
/usr/share/initramfs-tools/scripts/init-premout/online_all_dasds
containing:
echo 1 > /sys/bus/ccw/devices/${DASD_ID}/online
and then:
update-initramfs -u
All DASDS in the system VG are brought online by initramfs, allowing the lvm2
scripts in initramfs to work - I can then reboot the LPAR successfully.
** Affects: initramfs-tools
Importance: Undecided
Status: New
** Affects: s390-dasd (Ubuntu)
Importance: Undecided
Status: New
** Tags: s390x uosci
** Also affects: initramfs-tools
Importance: Undecided
Status: New
** Package changed: initramfs-tools (Ubuntu) => s390-dasd (Ubuntu)
** Tags added: s390x uosci
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1673992
Title:
init-premount/sysconfig_hardware does not online all DASDs in primary
VG - drops to busybox initramfs prompt
Status in initramfs-tools:
New
Status in s390-dasd package in Ubuntu:
New
Bug description:
Unsure if this is an initfs-tools issue, or s390-tools, or other?
Linux s4lpb 4.4.0-67-generic #88-Ubuntu SMP Wed Mar 8 16:39:07 UTC
2017 s390x s390x s390x GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial
iibusybox-initramfs1:1.22.0-15ubuntu1
iiinitramfs-tools 0.122ubuntu8.8
iiinitramfs-tools-bin 0.122ubuntu8.8
iiinitramfs-tools-core 0.122ubuntu8.8
iilibklibc 2.0.4-8ubuntu1.16.04.3
ii s390-tools 1.34.0-0ubuntu8.3
Brief description:
I have an s390x LPAR with multiple DASD disks in the 'system' VG -
kernel param specifies root=/dev/mapper/system-root. After preseeding,
and rebooting once, the system drops to BusyBox initramfs prompt,
after errors:
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... lvm
etad is not active yet, using direct activation during sysinit
Couldn't find device with uuid VudDPr-jSTm-ekaq-bWf7-xnVX-uFAd-lHUlfU.
Couldn't find device with uuid ySbAlW-I9M5-UV60-oHF3-uwAu-iXkH-H7zwPB.
Refusing activation of partial LV system/root. Use '--activationmode partial'
to override.
lvmetad is not active yet, using direct activation during sysinit
Couldn't find device with uuid VudDPr
[Touch-packages] [Bug 1654448] [NEW] XPS 13 9360, Realtek ALC3246, Headphone audio hiss
Public bug reported: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: New Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
