[Touch-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Dave Chiluk (chiluk) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Dave Chiluk (chiluk) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: In Progress Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscripti
[Touch-packages] [Bug 1996550] [NEW] Bionic: system update killed networking (sort of)
Public bug reported: Filing for a friend: I have several Ubuntu servers that all just quit working at the same time. By “quit working” I mean they take forever to boot and applications do not work on them correctly until after about 30 minutes (and the applications have been restarted). Nov 14 16:27:08 help systemd[1]: Started OpenBSD Secure Shell server. Nov 14 16:27:08 help whoopsie[775]: [16:27:08] Using lock path: /var/lock/whoopsie/lock Nov 14 16:27:09 help whoopsie[775]: [16:27:09] Could not get the Network Manager state: Nov 14 16:27:09 help whoopsie[775]: [16:27:09] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager has not provided by any .service files Nov 14 16:27:09 help networkd-dispatcher[684]: WARNING: systemd-networkd is not running, output will be incomplete. Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=2, name='eth0', type='ether', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help systemd[1]: Started Dispatcher daemon for systemd-networkd. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => systemd (Ubuntu) ** Description changed: Filing for a friend: - I have several UBNT servers that all just quit working at the same time. - By “quitworking” I mean they take forever to boot and applications to do - not work on them correctly. + I have several Ubuntu servers that all just quit working at the same + time. By “quit working” I mean they take forever to boot and + applications do not work on them correctly until after about 30 minutes + (and the applications have been restarted). Nov 14 16:27:08 help systemd[1]: Started OpenBSD Secure Shell server. Nov 14 16:27:08 help whoopsie[775]: [16:27:08] Using lock path: /var/lock/whoopsie/lock Nov 14 16:27:09 help whoopsie[775]: [16:27:09] Could not get the Network Manager state: Nov 14 16:27:09 help whoopsie[775]: [16:27:09] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager has not provided by any .service files Nov 14 16:27:09 help networkd-dispatcher[684]: WARNING: systemd-networkd is not running, output will be incomplete. Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=2, name='eth0', type='ether', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operati
[Touch-packages] [Bug 1996550] Re: Bionic: system update killed networking (sort of)
After restoring to a functional backup we discovered that updating from cloud-init 22.2-0ubuntu1~18.04.3 is the cause of the problem. ** Package changed: systemd (Ubuntu) => cloud-init (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1996550 Title: Bionic: system update killed networking (sort of) Status in cloud-init package in Ubuntu: New Status in cloud-init source package in Bionic: New Bug description: Filing for a friend: I have several Ubuntu servers that all just quit working at the same time. By “quit working” I mean they take forever to boot and applications do not work on them correctly until after about 30 minutes (and the applications have been restarted). Nov 14 16:27:08 help systemd[1]: Started OpenBSD Secure Shell server. Nov 14 16:27:08 help whoopsie[775]: [16:27:08] Using lock path: /var/lock/whoopsie/lock Nov 14 16:27:09 help whoopsie[775]: [16:27:09] Could not get the Network Manager state: Nov 14 16:27:09 help whoopsie[775]: [16:27:09] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager has not provided by any .service files Nov 14 16:27:09 help networkd-dispatcher[684]: WARNING: systemd-networkd is not running, output will be incomplete. Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=2, name='eth0', type='ether', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help systemd[1]: Started Dispatcher daemon for systemd-networkd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1996550/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
Observed on bionic:linux-aws-5.4 5.4.0-1055.58~18.04.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+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 1943441] Re: lxc: lxc-test-parse-config-file failure
Also observed with impish linux-aws 5.13.0-1000.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1943441 Title: lxc: lxc-test-parse-config-file failure Status in lxc package in Ubuntu: In Progress Bug description: I'm getting the following error with the lxc kernel autotest on impish: 08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match 08:46:04 DEBUG| 08:46:04 DEBUG| parse_config_file.c: 382: main: lxc.selinux.context 08:46:06 INFO | ERRORubuntu_lxc.lxc-test-parse-config-file ubuntu_lxc.lxc-test-parse-config-filetimestamp=1631090766localtime=Sep 08 08:46:06Command failed, rc=1, Command returned non-zero exit status * Command: /tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file Exit status: 1 Duration: 0.0550210475922 stderr: parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match parse_config_file.c: 382: main: lxc.selinux.context I haven't investigated very much, but it looks like a (mis)configuration change / issue. Does it ring any bell? Otherwise I'll investigate more. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1943441/+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 1944712] [NEW] systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1
Public bug reported: This is a scripted bug report about ADT failures while running systemd tests for linux-aws-5.4/5.4.0-1057.60~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/s/systemd/20210923_022411_52338@/log.gz ** Affects: linux-aws-5.4 (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1944712 Title: systemd/237-3ubuntu10.52 ADT test failure with linux- aws-5.4/5.4.0-1057.60~18.04.1 Status in linux-aws-5.4 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-aws-5.4/5.4.0-1057.60~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/s/systemd/20210923_022411_52338@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1944712/+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 1944712] Re: systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1
timedatedPASS hostnamedPASS localed-locale PASS localed-x11-keymap PASS logind PASS unit-config PASS storage PASS networkd-test.py PASS build-login PASS boot-and-servicesPASS udev PASS root-unittests PASS upstream FAIL timed out boot-smoke PASS systemd-fsckdSKIP exit status 77 and marked as skippable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1944712 Title: systemd/237-3ubuntu10.52 ADT test failure with linux- aws-5.4/5.4.0-1057.60~18.04.1 Status in linux-aws-5.4 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-aws-5.4/5.4.0-1057.60~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/s/systemd/20210923_022411_52338@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1944712/+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 1446906] Re: lxc container with postfix, permission denied on mailq
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Vivid) Status: New => In Progress ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Wily) Status: New => In Progress ** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1446906 Title: lxc container with postfix, permission denied on mailq Status in linux package in Ubuntu: Fix Committed Status in lxc package in Ubuntu: Confirmed Status in linux source package in Vivid: In Progress Status in lxc source package in Vivid: New Status in linux source package in Wily: In Progress Status in lxc source package in Wily: New Status in linux source package in Xenial: Fix Committed Status in lxc source package in Xenial: Confirmed Bug description: [Impact] * Users may encounter situations where they use applications, confined by AppArmor, that hit EACESS failures when attempting to operate on AF_UNIX stream sockets. * These failures typically occur when the confined applications attempts to read from an AF_UNIX stream socket when the other end of the socket has already been closed. * AppArmor is mistakenly denying the socket operations due to the socket shutdown operation making the sun_path no longer being available for AppArmor mediation after the socket is shutdown. [Test Case] The expected test case is: $ sudo apt-get install postfix # installing in 'local only' config is fine $ cat > bug-profile << EOF profile bug-profile flags=(attach_disconnected) { network, file, } EOF $ sudo apparmor_parser -r bug.profile $ aa-exec -p bug-profile -- mailq Mail queue is empty A failed test case will see the mailq command exit with an error: $ aa-exec -p bug-profile -- mailq postqueue: warning: close: Permission denied and these denials will be found in the syslog: Jan 25 16:56:29 sec-vivid-amd64 kernel: [ 241.096168] audit: type=1400 audit(1453762589.727:29): apparmor="DENIED" operation="file_perm" profile="bug-profile" name="public/showq" pid=4923 comm="postqueue" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Jan 25 16:56:29 sec-vivid-amd64 kernel: [ 241.096175] audit: type=1400 audit(1453762589.727:30): apparmor="DENIED" operation="file_perm" profile="bug-profile" name="public/showq" pid=4923 comm="postqueue" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [Regression Potential] * The changes are local to the path-based AF_UNIX stream socket mediation code so that limits the regression potential to some degree. * John Johansen authored the patch and I reviewed it. It is small and there's no obvious areas of concern to me regarding potential regressions. [Other Info] * None at this time [Original bug report] Hello, on three Vivid host, all of them up-to-date, I have the problem described here: https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1390223 That bug report shows the problem was fixed, but it is not (at least on current Vivid) ii linux-image-generic 3.19.0.15.14 amd64 Generic Linux kernel image ii lxc 1.1.2-0ubuntu3 amd64 Linux Containers userspace tools ii apparmor2.9.1-0ubuntu9 amd64 User-space parser utility for AppArmor Reproducible with: $ sudo lxc-create -n test -t ubuntu $ sudo lxc-start -n test (inside container) $ sudo apt-get install postfix $ mailq postqueue: warning: close: Permission denied dmesg shows: [82140.386109] audit: type=1400 audit(1429661150.086:17067): apparmor="DENIED" operation="file_perm" profile="lxc-container-default" name="public/showq" pid=27742 comm="postqueue" requested_mask="r" denied_mask="
[Touch-packages] [Bug 1446906] Re: lxc container with postfix, permission denied on mailq
** Changed in: linux (Ubuntu Vivid) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1446906 Title: lxc container with postfix, permission denied on mailq Status in linux package in Ubuntu: Fix Committed Status in lxc package in Ubuntu: Confirmed Status in linux source package in Vivid: Fix Committed Status in lxc source package in Vivid: New Status in linux source package in Wily: Fix Committed Status in lxc source package in Wily: New Status in linux source package in Xenial: Fix Committed Status in lxc source package in Xenial: Confirmed Bug description: [Impact] * Users may encounter situations where they use applications, confined by AppArmor, that hit EACESS failures when attempting to operate on AF_UNIX stream sockets. * These failures typically occur when the confined applications attempts to read from an AF_UNIX stream socket when the other end of the socket has already been closed. * AppArmor is mistakenly denying the socket operations due to the socket shutdown operation making the sun_path no longer being available for AppArmor mediation after the socket is shutdown. [Test Case] The expected test case is: $ sudo apt-get install postfix # installing in 'local only' config is fine $ cat > bug-profile << EOF profile bug-profile flags=(attach_disconnected) { network, file, } EOF $ sudo apparmor_parser -r bug.profile $ aa-exec -p bug-profile -- mailq Mail queue is empty A failed test case will see the mailq command exit with an error: $ aa-exec -p bug-profile -- mailq postqueue: warning: close: Permission denied and these denials will be found in the syslog: Jan 25 16:56:29 sec-vivid-amd64 kernel: [ 241.096168] audit: type=1400 audit(1453762589.727:29): apparmor="DENIED" operation="file_perm" profile="bug-profile" name="public/showq" pid=4923 comm="postqueue" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Jan 25 16:56:29 sec-vivid-amd64 kernel: [ 241.096175] audit: type=1400 audit(1453762589.727:30): apparmor="DENIED" operation="file_perm" profile="bug-profile" name="public/showq" pid=4923 comm="postqueue" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [Regression Potential] * The changes are local to the path-based AF_UNIX stream socket mediation code so that limits the regression potential to some degree. * John Johansen authored the patch and I reviewed it. It is small and there's no obvious areas of concern to me regarding potential regressions. [Other Info] * None at this time [Original bug report] Hello, on three Vivid host, all of them up-to-date, I have the problem described here: https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1390223 That bug report shows the problem was fixed, but it is not (at least on current Vivid) ii linux-image-generic 3.19.0.15.14 amd64 Generic Linux kernel image ii lxc 1.1.2-0ubuntu3 amd64 Linux Containers userspace tools ii apparmor2.9.1-0ubuntu9 amd64 User-space parser utility for AppArmor Reproducible with: $ sudo lxc-create -n test -t ubuntu $ sudo lxc-start -n test (inside container) $ sudo apt-get install postfix $ mailq postqueue: warning: close: Permission denied dmesg shows: [82140.386109] audit: type=1400 audit(1429661150.086:17067): apparmor="DENIED" operation="file_perm" profile="lxc-container-default" name="public/showq" pid=27742 comm="postqueue" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zoolook1913 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=aa25401d-0553-43dc-b7c8-c530fe245fb6 InstallationDate: Installed on 2015-02-27 (53 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 20150 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 Tags: vivid Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-29 (24 days ago) UserGroups: adm docker libvirtd lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 12
[Touch-packages] [Bug 1463836] Re: 4.0 kernel build failure on ppc64el
Here is a build log with V=1. Search for 'Error: missing operand'. ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1463836/+attachment/4412794/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1463836 Title: 4.0 kernel build failure on ppc64el Status in binutils package in Ubuntu: New Bug description: We have uploaded our first 4.0 based Wily kernel to the archive but are unfortunately seeing the following build failure which we believe is related to our wily toolchain: https://launchpadlibrarian.net/208665203/buildlog_ubuntu-wily- ppc64el.linux_4.0.0-1.1_BUILDING.txt.gz /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S: Assembler messages: /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S:188: Error: missing operand /build/buildd/linux-4.0.0/scripts/Makefile.build:294: recipe for target 'arch/powerpc/kernel/swsusp_asm64.o' failed make[3]: *** [arch/powerpc/kernel/swsusp_asm64.o] Error 1 /build/buildd/linux-4.0.0/Makefile:957: recipe for target 'arch/powerpc/kernel' failed make[2]: *** [arch/powerpc/kernel] Error 2 We do not believe this is due to a kernel change as the code in question has not changed in years. Additionally, we had 4.0 based test builds successfully passing in our PPA (ppa:canonical-kernel- team/ppa). The last successful test build in our PPA was from May 21 (the logs are still there if needed). We were also unable to reproduce by cross-compiling. As added information, our wily kernel git repo can be seen at: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/wily Let us know if any additional information is required to debug this. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: binutils 2.25-8ubuntu1 ProcVersionSignature: Ubuntu 4.0.0-1.1-generic 4.0.5 Uname: Linux 4.0.0-1-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 10 06:16:10 2015 Dependencies: gcc-5-base 5.1.1-9ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.1.1-9ubuntu2 multiarch-support 2.21-0ubuntu4 zlib1g 1:1.2.8.dfsg-2ubuntu1 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-17 (449 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317) SourcePackage: binutils UpgradeStatus: Upgraded to wily on 2015-05-28 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1463836/+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 1463836] Re: 4.0 kernel build failure on ppc64el
Plus the intermediate temp file created using the '-save-temps' flag to GCC ** Attachment added: "swsusp_asm64.s" https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1463836/+attachment/4412803/+files/swsusp_asm64.s -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1463836 Title: 4.0 kernel build failure on ppc64el Status in binutils package in Ubuntu: New Bug description: We have uploaded our first 4.0 based Wily kernel to the archive but are unfortunately seeing the following build failure which we believe is related to our wily toolchain: https://launchpadlibrarian.net/208665203/buildlog_ubuntu-wily- ppc64el.linux_4.0.0-1.1_BUILDING.txt.gz /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S: Assembler messages: /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S:188: Error: missing operand /build/buildd/linux-4.0.0/scripts/Makefile.build:294: recipe for target 'arch/powerpc/kernel/swsusp_asm64.o' failed make[3]: *** [arch/powerpc/kernel/swsusp_asm64.o] Error 1 /build/buildd/linux-4.0.0/Makefile:957: recipe for target 'arch/powerpc/kernel' failed make[2]: *** [arch/powerpc/kernel] Error 2 We do not believe this is due to a kernel change as the code in question has not changed in years. Additionally, we had 4.0 based test builds successfully passing in our PPA (ppa:canonical-kernel- team/ppa). The last successful test build in our PPA was from May 21 (the logs are still there if needed). We were also unable to reproduce by cross-compiling. As added information, our wily kernel git repo can be seen at: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/wily Let us know if any additional information is required to debug this. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: binutils 2.25-8ubuntu1 ProcVersionSignature: Ubuntu 4.0.0-1.1-generic 4.0.5 Uname: Linux 4.0.0-1-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 10 06:16:10 2015 Dependencies: gcc-5-base 5.1.1-9ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.1.1-9ubuntu2 multiarch-support 2.21-0ubuntu4 zlib1g 1:1.2.8.dfsg-2ubuntu1 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-17 (449 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317) SourcePackage: binutils UpgradeStatus: Upgraded to wily on 2015-05-28 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1463836/+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 1602737] Re: PCI RoCE Interface could not be renamed from default name with link file
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1602737 Title: PCI RoCE Interface could not be renamed from default name with link file Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in linux source package in Xenial: Fix Released Status in systemd source package in Xenial: New Status in linux source package in Yakkety: Fix Released Status in systemd source package in Yakkety: New Bug description: == Comment: #0 - Helmut Grauer - 2016-07-13 09:05:27 == Try to rename PCI Roce Interface with .link file root@s35lp02:/etc/systemd/network# cat 10-net.link [Match] Path=pci-:00:00.0* MACAddress=82:01:14:07:85:70 [Link] Name=hug0 root@s35lp02:/etc/systemd/network# do a reboot and journalctl show old interface name for RoCE PCI Interface Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: frag:0 - size:1522 prefix:0 stride:1536 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing port Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: frag:0 - size:1522 prefix:0 stride:1536 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing port Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from eth0 Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from eth1 Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed from eth3 Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from eth2 Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system using the ext4 subsystem Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with ordered data mode. Opts: (null) udevadm test show the following output oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0 calling: test version 229 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. === trie on-disk === tool version: 229 file size: 6841701 bytes header size 80 bytes strings1755245 bytes nodes 5086376 bytes Load module index timestamp of '/etc/systemd/network' changed Skipping overridden file: /usr/lib/systemd/network/99-default.link. Skipping overridden file: /usr/lib/systemd/network/10-net.link. Skipping overridden file: /lib/systemd/network/99-default.link. Skipping overridden file: /lib/systemd/network/10-net.link. Parsed configuration file /etc/systemd/network/99-default.link Parsed configuration file /lib/systemd/network/90-mac-for-usb.link Parsed configuration file /etc/systemd/network/11-net.link Parsed configuration file /etc/systemd/network/10-net.link Created link configuration context. timestamp of '/etc/udev/rules.d' changed Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules Reading rules file: /lib/udev/rules.d/40-z90crypt.rules Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules Reading rules file: /lib/udev/rules.d/50-firmware.rules Reading rules file: /lib/udev/rules.d/50-udev-default.rules Reading rules file: /lib/udev/rules.d/55-dm.rules Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules Reading rules file: /lib/udev/rules.d/56-lvm.rules Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules Reading rules file: /lib/udev/rules.d/59-dasd.rules Reading rules file: /lib/udev/rules.d/60-block.rules Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules Reading rules file: /lib/udev/rules.d/60-crda.rules Reading rules file: /lib/udev/rules.d/60-drm.rules Reading rules file: /lib/udev/rules.d/60-evdev.rules Reading rules file: /lib/udev/rules.d/60
[Touch-packages] [Bug 1611078] Re: Support snaps inside of lxd containers
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1611078 Title: Support snaps inside of lxd containers Status in lxd: Unknown Status in Snappy: Fix Committed Status in apparmor package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Committed Status in lxd package in Ubuntu: Fix Committed Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1611078/+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 1616107] Re: Kernel oops + system freeze on network-bridge shutdown
https://lists.ubuntu.com/archives/kernel-team/2016-December/081252.html ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1616107 Title: Kernel oops + system freeze on network-bridge shutdown Status in bridge-utils package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in bridge-utils source package in Xenial: Invalid Status in linux source package in Xenial: In Progress Status in bridge-utils source package in Yakkety: Invalid Bug description: A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver. This error does not appear in Ubuntu 14.04 however. The error is reproducible whenever issuing the commands "shutdown", "service networking stop" or "brctl delbr br0". Manually creating the bridge and subsequently bringing it down results in the same error. /var/log/kern.log: [...] Aug 23 15:09:46 base1 kernel: [ 617.996677] device ens1f0 left promiscuous mode Aug 23 15:09:46 base1 kernel: [ 617.996699] br0: port 1(ens1f0) entered disabled state Aug 23 15:09:46 base1 kernel: [ 617.996730] BUG: unable to handle kernel NULL pointer dereference at 00d2 Aug 23 15:09:46 base1 kernel: [ 618.008306] IP: [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.020549] PGD 10374c0067 PUD 1033927067 PMD 0 Aug 23 15:09:46 base1 kernel: [ 618.032773] Oops: 0002 [#1] SMP Aug 23 15:09:46 base1 kernel: [ 618.044434] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio libcrc32c wmi fjes Aug 23 15:09:46 base1 kernel: [ 618.058563] CPU: 3 PID: 4049 Comm: brctl Not tainted 4.4.0-34-generic #53-Ubuntu Aug 23 15:09:46 base1 kernel: [ 618.058564] Hardware name: HP ProLiant DL120 Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016 Aug 23 15:09:46 base1 kernel: [ 618.058574] task: 881030676040 ti: 8810341e4000 task.ti: 8810341e4000 Aug 23 15:09:46 base1 kernel: [ 618.058576] RIP: 0010:[] [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058754] RSP: 0018:8810341e7d68 EFLAGS: 00010206 Aug 23 15:09:46 base1 kernel: [ 618.058769] RAX: RBX: RCX: Aug 23 15:09:46 base1 kernel: [ 618.058774] RDX: 881038470848 RSI: RDI: Aug 23 15:09:46 base1 kernel: [ 618.058775] RBP: 8810341e7d78 R08: R09: 8170d949 Aug 23 15:09:46 base1 kernel: [ 618.058776] R10: ead61340 R11: 8810329d2c00 R12: 00c0 Aug 23 15:09:46 base1 kernel: [ 618.058777] R13: 881030044000 R14: 881038470840 R15: Aug 23 15:09:46 base1 kernel: [ 618.058782] FS: 7f9aebc94700() GS:88107fcc() knlGS: Aug 23 15:09:46 base1 kernel: [ 618.058789] CS: 0010 DS: ES: CR0: 80050033 Aug 23 15:09:46 base1 kernel: [ 618.058790] CR2: 00d2 CR3: 00102fe83000 CR4: 001406e0 Aug 23 15:09:46 base1 kernel: [ 618.058802] Stack: Aug 23 15:09:46 base1 kernel: [ 618.058806] 8810356a4c00 8810341e7d98 c0489258 Aug 23 15:09:46 base1 kernel: [ 618.058822] 8810356a4c00 881038470840 8810341e7dc0 c0479bd8 Aug 23 15:09:46 base1 kernel: [ 618.058825] 881038470838 881038470848 88103847 8810341e7df8 Aug 23 15:09:46 base1 kernel: [ 618.058827] Call Trace: Aug 23 15:09:46 base1 kernel: [ 618.058863] [] nbp_vlan_flush+0x28/0x65 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058870] [] del_nbp+0x98/0x130 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058889] [] br_dev_delete+0x42/0xb0 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058895] [] br_del_bridge+0x4a/0x70 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058911] [] br_ioctl_deviceless_stub+0x153
[Touch-packages] [Bug 1653489] Re: [LTCTest][OPAL][FW860.20] Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu 16.04.1 is dropping to (initramfs)
But ipr.ko is already included. There must be some other missing boot essential module. ~/ubuntu/ubuntu-yakkety$ git grep ipr debian.master/control.d/generic.inclusion-list debian.master/control.d/generic.inclusion-list:drivers/scsi/ipr.ko -- 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/1653489 Title: [LTCTest][OPAL][FW860.20] Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu 16.04.1 is dropping to (initramfs) Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: @kernel-team Please move ipr module from image-extra to image package. ---Problem Description--- Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu 16.04.1 is dropping to (initramfs) Contact Information = pavsu...@in.ibm.com ---uname output--- Linux (none) 4.8.0-27-generic #29~16.04.1-Ubuntu SMP Fri Nov 4 17:24:37 UTC 2016 ppc64le GNU/Linux ---Additional Hardware Info--- root@powerkvm3-lp1:~# lspci :00:00.0 PCI bridge: IBM Device 03dc :01:00.0 RAID bus controller: IBM Obsidian-E PCI-E SCSI controller (rev 01) 0001:00:00.0 PCI bridge: IBM Device 03dc 0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0001:03:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0001:03:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0001:03:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01) 0001:05:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01) 0004:00:00.0 PCI bridge: IBM Device 03dc 0004:01:00.0 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre Channel Host Adapter (rev 10) 0004:01:00.1 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre Channel Host Adapter (rev 10) 0005:00:00.0 PCI bridge: IBM Device 03dc 0005:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:02:01.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:02:08.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:02:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:02:10.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:02:11.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller (rev 02) 0005:09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0005:09:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0005:09:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0005:09:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0005:0f:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) 0005:0f:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) 0040:00:00.0 PCI bridge: IBM Device 03dc 0044:00:00.0 PCI bridge: IBM Device 03dc 0044:01:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0044:01:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0044:01:00.2 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0044:01:00.3 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0044:01:00.4 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator (Lancer) (rev 10) 0044:01:00.5 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator (Lancer) (rev 10) 0045:00:00.0 PCI bridge: IBM Device 03dc 0045:01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0045:01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0045:01:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0045:01:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) Machine Type = P8 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 16.04
[Touch-packages] [Bug 1660832] Re: unix domain socket cross permission check failing with nested namespaces
** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1660832 Title: unix domain socket cross permission check failing with nested namespaces Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: New Status in linux source package in Yakkety: Fix Committed Status in apparmor source package in Zesty: New Status in linux source package in Zesty: In Progress Bug description: When using nested namespaces policy within the nested namespace is trying to cross validate with policy outside of the namespace that is not visible to it. This results the access being denied and with no way to add a rule to policy that would allow it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1660832/+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 1661030] Re: regession tests failing after stackprofile test is run
** Also affects: apparmor (Ubuntu Zesty) Importance: High Assignee: John Johansen (jjohansen) Status: Incomplete ** Also affects: apparmor (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: apparmor (Ubuntu Yakkety) Status: New => Fix Committed ** Changed in: apparmor (Ubuntu Zesty) Status: Incomplete => Fix Committed ** Changed in: apparmor (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1661030 Title: regession tests failing after stackprofile test is run Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Fix Committed Status in apparmor source package in Zesty: Fix Released Bug description: from source, I'm running the tests and the makefile fails at the end with: running stackprofile Makefile:303: recipe for target 'tests' failed make: *** [tests] Error 1 No idea why that is happening. It's breaking on our kernel team regression tests runs, so can this be investigated? The source was fetched using "apt-get source apparmor". A full run is below: king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make USE_SYSTEM=1 tests running aa_exec running access xfail: ACCESS file rx (r) xfail: ACCESS file rwx (r) xfail: ACCESS file r (wx) xfail: ACCESS file rx (wx) xfail: ACCESS file rwx (wx) xfail: ACCESS dir rwx (r) xfail: ACCESS dir r (wx) xfail: ACCESS dir rx (wx) xfail: ACCESS dir rwx (wx) running at_secure running introspect running capabilities (ptrace) (sethostname) (setdomainname) (setpriority) (setscheduler) (reboot) (chroot) (mlockall) (net_raw) (ioperm) (iopl) running changeprofile running onexec running changehat running changehat_fork running changehat_misc *** A 'Killed' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12503 Killed $testexec "$@" > $outfile 2>&1 *** A 'Killed' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12537 Killed $testexec "$@" > $outfile 2>&1 running chdir running clone running coredump *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12803 Segmentation fault (core dumped) $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12833 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12869 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12905 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 12941 Segmentation fault $testexec "$@" > $outfile 2>&1 XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement) running deleted running environ Fatal Error (environ): Unable to run test sub-executable running exec running exec_qual running fchdir running fd_inheritance running fork running i18n running link running link_subset running mkdir running mmap running mount using mount rules ... running mult_mount running named_pipe running namespaces running net_raw running open running openat running pipe running pivot_root running ptrace using ptrace v6 tests ... running pwrite running query_label Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked as expected pass but known problem (xpass) xpass: QUERY file (all base perms #1) Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked as expected pass but known problem (xpass) xpass: QUERY file (all base perms #2) running regex running rename running readdir running rw running socketpa
[Touch-packages] [Bug 1660762] Re: [Regression] Interface configuration not restored after driver unbind/bind (generic)
** Changed in: ifupdown (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1660762 Title: [Regression] Interface configuration not restored after driver unbind/bind (generic) Status in ifupdown package in Ubuntu: Invalid Bug description: ---Problem Description--- Interface configuration not restored after driver unbind/bind root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0 enP28p96s0f0: flags=4163 mtu 1500 inet 10.10.10.11 netmask 255.255.255.0 broadcast 10.10.10.255 inet6 fe80::290:faff:fe7a:5840 prefixlen 64 scopeid 0x20 ether 00:90:fa:7a:58:40 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 13 bytes 1046 (1.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@ltciofvtr-s824-lp8:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto ibmveth2 iface ibmveth2 inet static address 9.47.68.120 netmask 255.255.240.0 network 9.47.64.0 broadcast 9.47.79.255 gateway 9.47.79.254 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 9.12.18.2 dns-search pok.stglabs.ibm.com auto enP28p96s0f0 iface enP28p96s0f0 inet static address 10.10.10.11 netmask 255.255.255.0 root@ltciofvtr-s824-lp8:~# ethtool -i enP28p96s0f0 driver: be2net version: 11.1.0.0 firmware-version: 10.2.252.1913 expansion-rom-version: bus-info: 001c:60:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: no supports-priv-flags: yes root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/unbind root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net 001c:60:00.1 001c:60:00.2 001c:60:00.3 bind module new_id remove_id uevent unbind root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/bind root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net 001c:60:00.0 001c:60:00.1 001c:60:00.2 001c:60:00.3 bind module new_id remove_id uevent unbind root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0 enP28p96s0f0: flags=4098 mtu 1500 ether 00:90:fa:7a:58:40 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0 ifup: interface enP28p96s0f0 already configured root@ltciofvtr-s824-lp8:~# ifdown enP28p96s0f0 RTNETLINK answers: Cannot assign requested address root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0 root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0 enP28p96s0f0: flags=4163 mtu 1500 inet 10.10.10.11 netmask 255.255.255.0 broadcast 10.10.10.255 inet6 fe80::290:faff:fe7a:5840 prefixlen 64 scopeid 0x20 ether 00:90:fa:7a:58:40 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 16 bytes 1344 (1.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ---uname output--- Linux ltciofvtr-s824-lp8 4.9.0-12-generic #13-Ubuntu SMP Tue Jan 10 12:52:39 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = IBM,8286-42A LPAR ---Steps to Reproduce--- # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/unbind # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/bind == Comment - Vaishnavi Bhat Hi, To bind a device to a driver, the device must first not be controlled by any other driver. Can you check for 'driver' in the below before you bind ? $ tree /sys//bus/pci/devices/001c:60:00.0 Thank you. == Comment - Murilo Fossa Vicentini Just adding some information, this is not a driver specific issue, this was also seen with tg3 and i40e adapters . This behavior is a regression when compared to Ubuntu 16.04 where the interfaces where properly reconfigured upon bind with the information set in /etc/network/interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1660762/+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 1673350] Re: dm-queue-length module is not included in installer/initramfs
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed -- 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/1673350 Title: dm-queue-length module is not included in installer/initramfs Status in hw-detect package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Committed Status in multipath-tools package in Ubuntu: Triaged Status in hw-detect source package in Xenial: New Status in initramfs-tools source package in Xenial: New Status in linux source package in Xenial: In Progress Status in multipath-tools source package in Xenial: New Status in hw-detect source package in Yakkety: New Status in initramfs-tools source package in Yakkety: New Status in linux source package in Yakkety: New Status in multipath-tools source package in Yakkety: New Bug description: [Impact] Multipath users using EMC XtremIO storage as boot device or at install time may run into this issue. With the module unavailable the device is more often than not unavailable. Any users changing path selector to 'queue-length' with other storage devices may also be affected. [Test case] 1) Install on multipath system using EMC XtremIO storage / OR: a) Start d-i install on qemu with multipath enabled b) exit to d-i menu c) modify /etc/multipath.conf to define path selector as 'queue-length' for the local qemu device. d) restart multipathd if necessary. 2) Try to complete the install, setting up storage as multipath and using the multipath device as boot disk. 3) Reboot to disk. In a success case, the install should complete successfully without requiring manual configuration from the user to support the multipath storage past the normal detection of multipath and partitioning. In a failure case, the install may not complete, or rebooting may fail or lead to a system booted on a single path of the multipath device (ie. / on /dev/sda2 rather than /dev/mpatha2). [Regression Potential] The inclusion of a new multipath path selector driver should not cause any regressions, but any failure to detect, configure or boot on multipath devices following this change on XtremIO hardware or otherwise would constitute a regression potentially caused by this change. --- ---Problem Description--- dm-queue-length module is not included in installer/initramfs On Ubuntu, multipath devices using the 'queue-length' path selector are non-functional on both the installer and initramfs environments; because the 'dm-queue-length' kernel module is not included in them. The multipath-modules.udeb (src:linux) does not include it in the installer, nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs. One example is the EMC XtremIO storage, which has 'queue-length' defined as its path selector in the default multipath configuration, at least on 16.04. Other products may be affected if they are manually configured to use that path selector (e.g., via /etc/multipath.conf), and the mere switch of that might render the system _unbootable_ if booting from multipath, since the initramfs is affected. More recently this and another storage changed default path selectors out of 'queue-length', however, it's virtually possible for any storage system to be affected, with the described manual configuration change. So, this change is also desired on for the next stable release, 17.04, and later. Patches are provided for 16.04 and 17.04. Error logs in LP comment #6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+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 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
UBUNTU: SAUCE: Disable default console blanking interval I'll also send this upstream to get some opinions. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: kbd (Ubuntu Zesty) Importance: Medium Assignee: Robie Basak (racb) Status: Triaged ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Assignee: Tim Gardner (timg-tpi) Status: Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Committed Status in kbd source package in Zesty: Triaged Status in linux source package in Zesty: Fix Committed Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+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 1555264] Re: Ubuntu16.04 netboot installation fails with illegal instruction error
This does not appear to be a kernel problem. ** Package changed: linux (Ubuntu) => wget (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1555264 Title: Ubuntu16.04 netboot installation fails with illegal instruction error Status in wget package in Ubuntu: New Bug description: Problem Description Tried installing ubuntu16.04 using netboot method and it fails with error 'Illegal instruction' > Tried installing ubuntu16.04 using netboot method - yupg1 guest. > Added DHCP entry in KTE for the yupg1 guest. > Able to select Langauage and Location from installer menu. > It prompts for 'configure network window' as below ??? [!] Configure the network ??? ? ? ? Please enter the hostname for this system.? ? ? ? The hostname is a single word that identifies your system to the ? ? network. If you don't know what your hostname should be, consult your ? ? network administrator. If you are setting up your own home network, ? ? you can make something up here. ? ? ? ? Hostname: ? ? ? ? yupg1 ? ? ? ?? ? ? ? > After selecting continue button, it thows message as 'Illegal instruction' Illegal instruction > Unable to proceed further and it continously throws above message Host Details: --- KVM BUILD LEVEL: GA3 SP1 build 55 == Comment: #8 - Vaishnavi Bhat - == When I started the installation and reached the point to enter the hostname, the installation hanged with 'Illegal instruction'. At this point I could not collect any debug logs. I tried installation with multipath enabled and could reach a point where I could collect the debug logs. I did not see ''Illegal instruction' on my console this time but it was recorded in the logs. Mar 8 16:40:09 main-menu[209]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored) Mar 8 16:40:09 main-menu[209]: INFO: Menu item 'network-preseed' selected Mar 8 16:40:09 kernel: [ 43.752359] wget[1357]: unhandled signal 4 at 3159de5c nip 3159de5c lr 3159de48 code 30001 Mar 8 16:40:09 kernel: [ 43.754753] wget[1362]: unhandled signal 4 at 369fde5c nip 369fde5c lr 369fde48 code 30001 Mar 8 16:40:16 main-menu[209]: (process:1340): expr: warning: '^.*\[[:a-fA-F0-9]*\]': using '^' as the first character Mar 8 16:40:16 main-menu[209]: (process:1340): of a basic regular expression is not portable; it is ignored Mar 8 16:40:16 main-menu[209]: (process:1340): Illegal instruction Mar 8 16:40:16 main-menu[209]: (process:1340): Illegal instruction Mar 8 16:40:16 main-menu[209]: WARNING **: Configuring 'network-preseed' failed with error code 1 Mar 8 16:40:16 main-menu[209]: WARNING **: Menu item 'network-preseed' failed. Mar 8 16:40:20 main-menu[209]: INFO: Modifying debconf priority limit from 'high' to 'medium' Mar 8 16:40:20 debconf: Setting debconf/priority to medium Mar 8 16:40:20 main-menu[209]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored) Mar 8 16:40:28 main-menu[209]: INFO: Menu item 'di-utils-shell' selected Mar 8 16:41:56 main-menu[209]: DEBUG: resolver (libc6-udeb): package doesn't exist (ignored) Mar 8 16:42:08 main-menu[209]: INFO: Menu item 'save-logs' selected == Comment: #9 - INDIRA P. JOGA - == Hi, I am able to recreate the issue on 2 different host machines with 2 different networks Raykvm - Travis3En network on host Yupkvm - Austin network on host. Tried installing ubunu16.04 using netboot on both kvm hosts and it failed with same error 'Illegal Instruction" Regards, Indira == Comment: #10 - Richard M. Scheller - == I was able to get to a shell in the installer so that I could look for broken binaries that might cause a SIGILL. I found that /usr/bin/wget is incorrectly linked as a shared object instead of an executable. I verified from the installer command line that "wget" does, in fact, die with SIGILL: /usr/bin # ./
[Touch-packages] [Bug 1379535] Re: policy namespace stacking
** Also affects: apparmor (Ubuntu Xenial) Importance: Critical Assignee: Tyler Hicks (tyhicks) Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Critical Status: Triaged ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1379535 Title: policy namespace stacking Status in AppArmor: In Progress Status in apparmor package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Committed Status in apparmor source package in Xenial: In Progress Status in linux source package in Xenial: Fix Committed Bug description: Tracking bug for supporting stacked policy namesapaces (ie, different profiles on host, container, container in a container, etc) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1379535/+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 1579135] Re: AppArmor profile reloading causes an intermittent kernel BUG
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1579135 Title: AppArmor profile reloading causes an intermittent kernel BUG Status in apparmor package in Ubuntu: Incomplete Status in linux package in Ubuntu: Fix Committed Status in apparmor source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Incomplete Status in linux source package in Yakkety: Fix Committed Bug description: First, a bit of background: I've built a go binary of the upstream snappy integration tests, and built them into a snap so that we can easily keep them up to date, and call them from other test suites. I'm running through the tests in qemu on a current 16 image (built yesteray), and hitting this most of the time with the homeInterface Suite tests in particular. The networkInterfaceSuite tests also seem to produce a similar problem: sudo snap connect home-consumer:home ubuntu-core:home [/] Connect home-consumer:home to ubuntu-core:home home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable sudo snap disconnect home-consumer:home ubuntu-core:home [ 519.416354] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 519.417327] IP: [] profile_cmp+0x2f/0x180 [ 519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 [ 519.418574] Oops: [#1] SMP [ 519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 nls_iso8859_1 usb_storage ahci libahci squashfs [ 519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 4.4.0-21-generic #37-Ubuntu [ 519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 88001b58c000 [ 519.425385] RIP: 0010:[] [] profile_cmp+0x2f/0x180 [ 519.426242] RSP: 0018:88001b58fcb0 EFLAGS: 00010086 [ 519.426791] RAX: RBX: 88001b1b1400 RCX: 0006 [ 519.427628] RDX: RSI: RDI: 0009 [ 519.428405] RBP: 88001b58fcc0 R08: 000a R09: 0274 [ 519.429127] R10: 88001f236890 R11: 0274 R12: [ 519.429956] R13: 000b R14: R15: 88001abff950 [ 519.430957] FS: 7f0c1609b740() GS:88001fc0() knlGS: [ 519.432256] CS: 0010 DS: ES: CR0: 80050033 [ 519.433030] CR2: 0038 CR3: 1b14b000 CR4: 06f0 [ 519.433868] Stack: [ 519.434204] 000c 88001abff9b0 88001b58fd08 8138a0c3 [ 519.435355] 00011f2b9450 880c 88001abff950 88001b1b1760 [ 519.436480] 88001f236848 88001abff900 88001f236840 88001b58fd98 [ 519.437609] Call Trace: [ 519.438007] [] aa_vec_unique+0x163/0x240 [ 519.438709] [] __aa_labelset_update_subtree+0x687/0x820 [ 519.439537] [] aa_replace_profiles+0x59b/0xb70 [ 519.440268] [] ? __kmalloc+0x22e/0x250 [ 519.440944] [] policy_update+0x9f/0x1f0 [ 519.441617] [] profile_replace+0x13/0x20 [ 519.442299] [] __vfs_write+0x18/0x40 [ 519.443032] [] vfs_write+0xa9/0x1a0 [ 519.443721] [] ? do_sys_open+0x1bf/0x2a0 [ 519.16] [] SyS_write+0x55/0xc0 [ 519.445042] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 [ 519.451336] RIP [] profile_cmp+0x2f/0x180 [ 519.452088] RSP [ 519.452570] CR2: 0038 [ 519.453032] ---[ end trace 65ff12ee2e7c26af ]--- The details of this test can be found at: https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer Will follow up with more details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+subscriptions -- Mailing list: https://launc
[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Commit 02da2d72174c61988eb4456b53f405e3ebdebce4 merged in v4.7 ** Also affects: e2fsprogs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: e2fsprogs (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: e2fsprogs (Ubuntu Yakkety) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: Incomplete ** Also affects: e2fsprogs (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: e2fsprogs (Ubuntu Trusty) Status: New => Invalid ** Changed in: e2fsprogs (Ubuntu Vivid) Status: New => Invalid ** Changed in: e2fsprogs (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Yakkety) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Vivid) Status: New => In Progress ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: In Progress Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: In Progress Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: In Progress Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+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 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
https://lists.ubuntu.com/archives/kernel-team/2016-September/079897.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: In Progress Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: In Progress Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: In Progress Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+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 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Test kernel at http://people.canonical.com/~rtg/lsattr-lp1619918/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: In Progress Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: In Progress Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: In Progress Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+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 1625100] Re: systemd test failure with linux 4.8.0-11.12: scsi_debug missing in ppc64el, systemd-tmpfiles crash
CONFIG_SCSI_DEBUG is now enabled for all arches in Ubuntu-4.8.0-12.13 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1625100 Title: systemd test failure with linux 4.8.0-11.12: scsi_debug missing in ppc64el, systemd-tmpfiles crash Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/amd64/s/systemd/20160918_093714@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/ppc64el/s/systemd/20160918_231904@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625100/+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 1602737] Re: PCI RoCE Interface could not be renamed from default name with link file
linux 4.8.0-11.12 ** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1602737 Title: PCI RoCE Interface could not be renamed from default name with link file Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in linux source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Yakkety: Fix Released Status in systemd source package in Yakkety: New Bug description: == Comment: #0 - Helmut Grauer - 2016-07-13 09:05:27 == Try to rename PCI Roce Interface with .link file root@s35lp02:/etc/systemd/network# cat 10-net.link [Match] Path=pci-:00:00.0* MACAddress=82:01:14:07:85:70 [Link] Name=hug0 root@s35lp02:/etc/systemd/network# do a reboot and journalctl show old interface name for RoCE PCI Interface Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: frag:0 - size:1522 prefix:0 stride:1536 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing port Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: frag:0 - size:1522 prefix:0 stride:1536 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing port Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from eth0 Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from eth1 Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed from eth3 Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from eth2 Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system using the ext4 subsystem Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with ordered data mode. Opts: (null) udevadm test show the following output oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0 calling: test version 229 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. === trie on-disk === tool version: 229 file size: 6841701 bytes header size 80 bytes strings1755245 bytes nodes 5086376 bytes Load module index timestamp of '/etc/systemd/network' changed Skipping overridden file: /usr/lib/systemd/network/99-default.link. Skipping overridden file: /usr/lib/systemd/network/10-net.link. Skipping overridden file: /lib/systemd/network/99-default.link. Skipping overridden file: /lib/systemd/network/10-net.link. Parsed configuration file /etc/systemd/network/99-default.link Parsed configuration file /lib/systemd/network/90-mac-for-usb.link Parsed configuration file /etc/systemd/network/11-net.link Parsed configuration file /etc/systemd/network/10-net.link Created link configuration context. timestamp of '/etc/udev/rules.d' changed Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules Reading rules file: /lib/udev/rules.d/40-z90crypt.rules Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules Reading rules file: /lib/udev/rules.d/50-firmware.rules Reading rules file: /lib/udev/rules.d/50-udev-default.rules Reading rules file: /lib/udev/rules.d/55-dm.rules Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules Reading rules file: /lib/udev/rules.d/56-lvm.rules Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules Reading rules file: /lib/udev/rules.d/59-dasd.rules Reading rules file: /lib/udev/rules.d/60-block.rules Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules Reading rules file: /lib/udev/rules.d/60-crda.rules Reading rules file: /lib/udev/rules.d/60-drm.rules Reading rules file: /lib/udev/rules.d/60-evdev.rules Reading rules file: /
[Touch-packages] [Bug 1626394] Re: 4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test)
** Also affects: linux (Ubuntu Yakkety) Importance: Critical Assignee: Tim Gardner (timg-tpi) Status: Confirmed ** Also affects: systemd (Ubuntu Yakkety) Importance: Undecided Assignee: Martin Pitt (pitti) Status: Won't Fix ** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1626394 Title: 4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test) Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Won't Fix Status in linux source package in Yakkety: Fix Committed Status in systemd source package in Yakkety: Won't Fix Bug description: Since the kernel upgrade from 4.4 to 4.8 in yakkety, systemd's TEST-08-ISSUE-2730 upstream test now consistently fails with: + timeout --foreground 180 /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel /boot/vmlinuz-4.8.0-14-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.4jlHRw/rootdisk.img -append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no ' warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5] [1.491760] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [1.492153] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-14-generic #15-Ubuntu [1.492153] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [1.492153] 0086 35700369 a8b59c24 97201dd45000 [1.492153] 97201e9afea0 a8987431 0010 97201e9afeb0 [1.492153] 97201e9afe48 35700369 97201e9afe58 97201e9afeb8 [1.492153] Call Trace: [1.492153] [] ? dump_stack+0x5c/0x78 [1.492153] [] ? panic+0xe4/0x226 [1.492153] [] ? mount_block_root+0x284/0x2c0 [1.492153] [] ? set_debug_rodata+0xc/0xc [1.492153] [] ? prepare_namespace+0x12b/0x180 [1.492153] [] ? kernel_init_freeable+0x1dd/0x1ed [1.492153] [] ? kernel_init+0xa/0x100 [1.492153] [] ? ret_from_fork+0x1f/0x40 [1.492153] [] ? rest_init+0x80/0x80 [1.492153] Kernel Offset: 0x2780 from 0x8100 (relocation range: 0x8000-0xbfff) [1.492153] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) qemu-system-x86_64: terminating on signal 15 from pid 8784 This only happens on amd64, i386 and ppc64el are fine. http://autopkgtest.ubuntu.com/packages/systemd/yakkety/amd64 I'll investigate more details, filing this for getting a reference for the britney hint. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626394/+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 1556228] Re: HP Notebook Probook 440 G3 HDA Intel PCH horrible sounds while booting
** Also affects: alsa-driver (Ubuntu Xenial) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1556228 Title: HP Notebook Probook 440 G3 HDA Intel PCH horrible sounds while booting Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in alsa-driver source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: At first there was no native recognition of my sound driver (see this [ https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1525554 ] a lot of others a experiencing this problem) so there was a workaround to fix that, the notebook has sound output now, but ever since i got these horrible scratching noises while booting, which i dont have booting windows, which is kinda surprising while one could take it for a bios or hardware problem. basic workaround for fixing missing sound driver was adding two lines to the /etc/modprobe.d/alsa-base.conf options snd-hda-intel single_cmd=1 options snd-hda-intel probe_mask=1 with these lines a was able to get sound, but i then have these crazy noises while booting. the following are some lines from the terminal which might help: 'lsb_release -rd' Ubuntu 15.10 cat /proc/asound/version Advanced Linux Sound Architecture Driver Version k4.2.0-30-generic. uname -a Linux 15 4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux lspci -v | grep -A7 -i "audio" 00:1f.3 Multimedia audio controller: Intel Corporation Device 9d70 (rev 21) Subsystem: Hewlett-Packard Company Device 8100 Flags: bus master, fast devsel, latency 64, IRQ 16 Memory at c132 (64-bit, non-prefetchable) [size=16K] Memory at c131 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel lsmod | grep snd snd_hda_codec_hdmi 49152 1 snd_hda_intel 36864 2 snd_hda_codec 135168 2 snd_hda_codec_hdmi,snd_hda_intel snd_hda_core 65536 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel snd_hwdep 16384 1 snd_hda_codec snd_pcm 106496 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_rawmidi 32768 1 snd_seq_midi snd_seq 69632 2 snd_seq_midi_event,snd_seq_midi snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 32768 2 snd_pcm,snd_seq snd 81920 13 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device soundcore 16384 1 snd cat /proc/asound/cards 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xc132 irq 129 even adding the right driver and module into /etc/modules (like snd- hda-intel model=PCH index=0) did not work, like i found in this thread ( https://wiki.ubuntuusers.de/Soundkarten_konfigurieren/ ) sorry for the german thread. i dont know what to add anymore. feel free to ask. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1613 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=80c72696-84ee-47f5-8764-86ed7ccd8bf2 InstallationDate: Installed on 2016-02-18 (22 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: HP HP ProBook 440 G3 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=9c79ccaf-65c6-40d6-a2a8-16d77841af74 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 RelatedPackageVersions: linux-restricted-modules-4.2.0-30-generic N/A linux-backports-modules-4.2.0-30-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/25/2016 dmi.bios.vendor: HP dmi.bios.version: N78 Ver. 01.07 dmi.board.name: 8100 dmi.board.vendor: HP dmi.board.version: KBC Version 40.03 dmi.chassis.asset.tag: 5CD5514XK5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN78Ver.01.07:bd01/2
[Touch-packages] [Bug 1558275] Re: wrong/missing permissions for device file /dev/prandom (prng.ko)
** Also affects: s390-tools (Ubuntu Xenial) Importance: Wishlist Assignee: Dimitri John Ledkov (xnox) Status: Invalid ** Also affects: linux (Ubuntu Xenial) Importance: Wishlist Assignee: Dimitri John Ledkov (xnox) Status: Triaged ** Also affects: systemd (Ubuntu Xenial) Importance: Wishlist Assignee: Dimitri John Ledkov (xnox) Status: Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: Dimitri John Ledkov (xnox) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1558275 Title: wrong/missing permissions for device file /dev/prandom (prng.ko) Status in linux package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in s390-tools source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Bug description: The access rights for /dev/prandom are set to 0600. The prandom file is created upon loading the prng module. Expectation: The access rights are set to 0644. Details = root@s83lp22:~# modinfo prng filename: /lib/modules/4.4.0-13-generic/kernel/arch/s390/crypto/prng.ko description:s390 PRNG interface author: IBM Corporation license:GPL srcversion: B48774F4AEBAE6DB4983C98 alias: cpu:type:*:feature:*0003* depends: intree: Y vermagic: 4.4.0-13-generic SMP mod_unload modversions parm: mode:int parm: prng_mode:PRNG mode: 0 - auto, 1 - TDES, 2 - SHA512 parm: chunksize:int parm: prng_chunk_size:PRNG read chunk size in bytes parm: reseed_limit:int parm: prng_reseed_limit:PRNG reseed limit Contact Information = christian.r...@de.ibm.com ---uname output--- Linux s83lp22 4.4.0-13-generic #29-Ubuntu SMP Fri Mar 11 19:30:41 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = Manufacturer: IBM Type: 2964 Model: 702 N96 ---Steps to Reproduce--- 1) modprobe prng 2) ls -l /dev/prandom This is a s390x issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1558275/+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 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable
Here is a rough example for how to support 3rd party modules in a secure boot environment. Note that you have to have Xenial linux 4.4.0-22.38 or better. https://docs.google.com/document/d /1Z1_jR3MmxuvqolQH4PORkJCgENkb2Tlw4FVA-sHqdMw -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574732 Title: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable Status in shim: New Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am running Ubuntu 16.04 since at least four months, always with the nvidia proprietary drivers (installed from the repository). I used nvidia-361 for a while with no issues (and i need it for steam gaming). However, an update installed on my machine yesterday breaks the nvidia drivers. I tried purging the driver, rebooting and reinstalling and i tried a newer version for the ubuntu-drivers ppa. Nothing helps: With the nvidia driver installed, i get a low- resolution login screen, but cannot login due to missing 3d acceleration. Running on nouveau works fine. This seems very strange to since everything worked until this afternoon. Yesterday, i was happily playing games on steam, installed some updates and now, my graphics are broken. $ lspci | grep NVIDIA 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 25 17:45:12 2016 DistUpgraded: 2016-03-11 21:34:38,175 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Palit Microsystems Inc. GM107 [GeForce GTX 750] [1569:1381] InstallationDate: Installed on 2016-01-05 (110 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=ed669b2d-c3af-4570-9eb7-2978557208ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-03-11 (44 days ago) dmi.bios.date: 05/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: H97 Performance dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 17:44:29 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/shim/+bug/1574732/+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.l
[Touch-packages] [Bug 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable
That is the goal. I'm surprised that you didn't get a dialog on upgrade that requested a decision on secure boot mode. You might if you remove and reinstall the nVidia driver. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574732 Title: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable Status in shim: New Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am running Ubuntu 16.04 since at least four months, always with the nvidia proprietary drivers (installed from the repository). I used nvidia-361 for a while with no issues (and i need it for steam gaming). However, an update installed on my machine yesterday breaks the nvidia drivers. I tried purging the driver, rebooting and reinstalling and i tried a newer version for the ubuntu-drivers ppa. Nothing helps: With the nvidia driver installed, i get a low- resolution login screen, but cannot login due to missing 3d acceleration. Running on nouveau works fine. This seems very strange to since everything worked until this afternoon. Yesterday, i was happily playing games on steam, installed some updates and now, my graphics are broken. $ lspci | grep NVIDIA 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 25 17:45:12 2016 DistUpgraded: 2016-03-11 21:34:38,175 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Palit Microsystems Inc. GM107 [GeForce GTX 750] [1569:1381] InstallationDate: Installed on 2016-01-05 (110 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=ed669b2d-c3af-4570-9eb7-2978557208ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-03-11 (44 days ago) dmi.bios.date: 05/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: H97 Performance dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 17:44:29 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/shim/+bug/1574732/+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 1580922] Re: Upgrade libseccomp from 2.2.3 ->2.3.1
** Package changed: linux (Ubuntu) => libseccomp (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1580922 Title: Upgrade libseccomp from 2.2.3 ->2.3.1 Status in libseccomp package in Ubuntu: New Bug description: == Comment: #1 - Heinz-Werner Seeck - 2016-05-11 05:09:09 == Please upgrade package libseccomp. The new version 2.3.1 is available on github https://github.com/seccomp/libseccomp/releases == Comment: #2 - Heinz-Werner Seeck - 2016-05-11 05:10:59 == ?Version 2.3.0 - February 29, 2016 ?Added support for the s390 and s390x architectures ?Added support for the ppc, ppc64, and ppc64le architectures ?Update the internal syscall tables to match the Linux 4.5-rcX releases ?Filter generation for both multiplexed and direct socket syscalls on x86 ?Support for the musl libc implementation ?Additions to the API to enable runtime version checking of the library ?Enable the use of seccomp() instead of prctl() on supported systems ?Added additional tests to the regression test suite ?Version 2.3.1 - April 20, 2016 ?Fixed a problem with 32-bit x86 socket syscalls on some systems ?Fixed problems with ipc syscalls on 32-bit x86 ?Fixed problems with socket and ipc syscalls on s390 and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1580922/+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 1567107] Re: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs
** Also affects: linux (Ubuntu Xenial) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Package changed: linux (Ubuntu Xenial) => initramfs-tools (Ubuntu Xenial) ** Changed in: initramfs-tools (Ubuntu Xenial) Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) -- 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/1567107 Title: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: In Progress Bug description: Because Generation 2 virtual machines in Hyper-V are presented with a minimal set of EFI hardware, the kernel module "hyperv_keyboard" must be present to interact with the console keyboard. On systems with disk encryption, the user will be prompted for the key to decrypt the disk, but cannot enter the password because no keyboard driver is present. This issue appears to exist in all Ubuntu releases that support EFI and are therefore eligible to be used as Generation 2 VMs, most recently tried with the April 5 ISO of the day for 16.04 (pre- release). This module *is* present when the grub menu is presented and later when the kernel is fully loaded. FYI, if some mechanism requires a mouse or touch, the hid_hyperv module will also be needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1567107/+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 1567107] Re: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs
** Changed in: initramfs-tools (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1567107 Title: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Xenial: Fix Committed Bug description: Because Generation 2 virtual machines in Hyper-V are presented with a minimal set of EFI hardware, the kernel module "hyperv_keyboard" must be present to interact with the console keyboard. On systems with disk encryption, the user will be prompted for the key to decrypt the disk, but cannot enter the password because no keyboard driver is present. This issue appears to exist in all Ubuntu releases that support EFI and are therefore eligible to be used as Generation 2 VMs, most recently tried with the April 5 ISO of the day for 16.04 (pre- release). This module *is* present when the grub menu is presented and later when the kernel is fully loaded. FYI, if some mechanism requires a mouse or touch, the hid_hyperv module will also be needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1567107/+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 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
** Also affects: initramfs-tools (Ubuntu Utopic) Importance: High Status: Invalid ** Also affects: linux (Ubuntu Utopic) Importance: High Assignee: Stefan Bader (smb) Status: Fix Released ** Changed in: linux (Ubuntu Utopic) Status: Fix Released => Fix Committed -- 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/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in “initramfs-tools” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Committed Status in “initramfs-tools” source package in Saucy: Invalid Status in “linux” source package in Saucy: Fix Released Status in “initramfs-tools” source package in Trusty: Invalid Status in “linux” source package in Trusty: Fix Released Status in “initramfs-tools” source package in Utopic: Invalid Status in “linux” source package in Utopic: Fix Committed Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is "Select Language". The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See "Server 13.10 Install Hangs", http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+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 1389201] Re: Error calling EVIOCSKEYCODE on device node: Invalid argument
This doesn't seem like a kernel issue. ** Package changed: linux (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1389201 Title: Error calling EVIOCSKEYCODE on device node: Invalid argument Status in “systemd” package in Ubuntu: Confirmed Bug description: In dmesg I can see these two error lines [7.375599] systemd-udevd[508]: Error calling EVIOCSKEYCODE on device node '/dev/input/event10' (scan code 0xc022d, key code 418): Invalid argument [7.375605] systemd-udevd[508]: Error calling EVIOCSKEYCODE on device node '/dev/input/event10' (scan code 0xc022e, key code 419): Invalid argument res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error) No idea what these two mean and how we can fix this. Any clues? ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael-heuberger 2178 F pulseaudio /dev/snd/controlC2: michael-heuberger 2178 F pulseaudio /dev/snd/controlC0: michael-heuberger 2178 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 5 00:55:34 2014 HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028 InstallationDate: Installed on 2014-10-31 (4 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1389201/+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 1357103] Re: apparmor denied a golang build inside a container
** Changed in: linux (Ubuntu) Assignee: (unassigned) => John Johansen (jjohansen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1357103 Title: apparmor denied a golang build inside a container Status in “apparmor” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Status in “lxc” package in Ubuntu: New Bug description: First, the error, while building a package inside a precise container: (...) make[1]: Entering directory `/home/ubuntu/deb/landscape-server-13.09.3~bzr544' GOPATH=/home/ubuntu/deb/landscape-server-13.09.3~bzr544/src/landscape/go /usr/bin/go install launchpad.net/gocheck github.com/lib/pq github.com/glacjay/goini GOPATH=/home/ubuntu/deb/landscape-server-13.09.3~bzr544/src/landscape/go /usr/bin/go install launchpad.net/landscape/cmd/packagesearch launchpad.net/landscape/cmd/license-audit launchpad.net/landscape/cmd/valid-license-audit # launchpad.net/landscape/cmd/license-audit /usr/lib/go/pkg/tool/linux_amd64/6g: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Permission denied make[1]: *** [install] Error 2 make[1]: Leaving directory `/home/ubuntu/deb/landscape-server-13.09.3~bzr544' make: *** [install] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 In dmesg: [226141.740150] type=1400 audit(1408053388.352:106): apparmor="DENIED" operation="file_mmap" profile="lxc-container-default" name="landscape/cmd/valid-license-audit/" pid=389 comm="6g" requested_mask="mr" denied_mask="mr" fsuid=1000 ouid=0 The host is trusty, running 3.13.0-32-lowlatency #57 My /var/lib/lxc is btrfs: /dev/mapper/ubuntu--vg-containers on /var/lib/lxc type btrfs (rw) Filesystem Size Used Avail Use% Mounted on /dev/mapper/ubuntu--vg-containers 50G 15G 35G 30% /var/lib/lxc How I created the precise container: lxc-create -n andreas-test -t ubuntu -- -S /home/andreas/.ssh/id_rsa.pub -r precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1357103/+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 1314653] Re: sysvinit: default cpufreq governor to powersave for intel-pstate driver
Not gonna do this for Trusty ** Changed in: sysvinit (Ubuntu Trusty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1314653 Title: sysvinit: default cpufreq governor to powersave for intel-pstate driver Status in “sysvinit” package in Ubuntu: Fix Released Status in “sysvinit” source package in Trusty: Won't Fix Status in “sysvinit” source package in Utopic: Fix Released Bug description: When defaulting to the intel-pstate driver, there are only a couple of cpufreq governors available, none of which are handled in the /etc/init.d/ondemand script. Since this driver is meant to be used for power saving, it seems wrong to leave the system in the kernel default configured "performance" governor after boot, so I think it is pertinent to set this to "powersave" if it is the only suitable non-power hungry governor available. How to reproduce: 1. enable the intel_pstate driver on a recent Intel machine (Sandybridge or above) edit /etc/default/grub, modify the following: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=enable" and run: sudo update-grub and reboot. 2. login 3. wait at least 60 seconds for /etc/init.d/ondemand to complete check out the default cpufreq governor, you will see it is still set to the boot default of "performance": cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor With the attached fix the system will boot into a less aggressive cpufreq governor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1314653/+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