[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
Maybe related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The KVP daemon fails to start on first boot due to being started before the hv_kvp device appears. Fix: Update the hv-kvp-daemon service file to start the daemon after device node appears. Regression Potential: The changes are only to the hv-kvp-daemon service file and adding a udev rule, so the worst case regression would be that the service does not start. In testing the service did start as expected. Test Case: See comment #15. --- Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
This is also happening on bare-metal machines as well! It starts to happen after installing the "linux-cloud-tools-generic- hwe-18.04" package. Also, Ubuntu 20.04 has the same problem. 20.04 slow boot stops for 1:30 min heree: --- A start job is running for /sys/dev…misc/vmbus!hv_kvp (13s / 1min 30s) --- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The KVP daemon fails to start on first boot due to being started before the hv_kvp device appears. Fix: Update the hv-kvp-daemon service file to start the daemon after device node appears. Regression Potential: The changes are only to the hv-kvp-daemon service file and adding a udev rule, so the worst case regression would be that the service does not start. In testing the service did start as expected. Test Case: See comment #15. --- Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
Terry, Ubuntu 18.04.4 with Kernel 5.3.0-40-generic, running on QEMU, takes more than 1:30 minutes to boot, it stops here for a while: --- [ *] A start job is running for sys-devi…\x21hv_kvp.device (51s / 1min 30s) --- I'm using the following image to build my QEMU VMs: http://uec-images.ubuntu.com/releases/18.04/release/ubuntu-18.04-server- cloudimg-amd64.img Cheers! Thiago -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The KVP daemon fails to start on first boot due to being started before the hv_kvp device appears. Fix: Update the hv-kvp-daemon service file to start the daemon after device node appears. Regression Potential: The changes are only to the hv-kvp-daemon service file and adding a udev rule, so the worst case regression would be that the service does not start. In testing the service did start as expected. Test Case: See comment #15. --- Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHel
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
I'm seeing this problem with Ubuntu 18.04.4 with HWE Kernel, fully upgraded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The KVP daemon fails to start on first boot due to being started before the hv_kvp device appears. Fix: Update the hv-kvp-daemon service file to start the daemon after device node appears. Regression Potential: The changes are only to the hv-kvp-daemon service file and adding a udev rule, so the worst case regression would be that the service does not start. In testing the service did start as expected. Test Case: See comment #15. --- Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 759725] Re: The kernel is no longer readable by non-root users
ROLL BACK THIS DAMN CHANGE!!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/759725 Title: The kernel is no longer readable by non-root users Status in linux package in Ubuntu: Won't Fix Bug description: The mode of the latest kernel has changed so it is no longer readable by non-root users: -rw-r--r-- 1 root root 4336016 2010-10-17 01:37 /boot/vmlinuz-2.6.35-22-generic -rw-r--r-- 1 root root 4336912 2010-11-24 12:46 /boot/vmlinuz-2.6.35-23-generic -rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic -rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic This prevents people from using this kernel to boot qemu virtual machines as non-root. Please change the mode back to make the kernel readable. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:240: no soundcards found... Architecture: amd64 ArecordDevices: arecord: device_list:240: no soundcards found... CRDA: Error: [Errno 2] No such file or directory Date: Wed Apr 13 13:05:01 2011 HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Red Hat KVM PciMultimedia: ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash RelatedPackageVersions: linux-restricted-modules-2.6.35-22-generic N/A linux-backports-modules-2.6.35-22-generic N/A linux-firmware 1.50 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.modalias: dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.0.0PC:cvnRedHat:ct1:cvr: dmi.product.name: KVM dmi.product.version: RHEL 6.0.0 PC dmi.sys.vendor: Red Hat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
I'll maintain the following repo: https://launchpad.net/~martinx/+archive/ubuntu/xrdp-hwe-18.04 ...until Ubuntu fixes it in an LTS version, maybe 20.04? That's okay... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Status in xrdp package in Ubuntu: Confirmed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-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/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
And here is the xrdp-0.9.9 and xorgxrdp-0.2.9 for Bionic HWE! https://launchpad.net/~martinx/+archive/ubuntu/xrdp-next Awesome Friday night! LOL -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Status in xrdp package in Ubuntu: Confirmed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-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/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
So, there is a need to rebuild xrdp against HWE 18.04. Maybe Ubuntu should provide a new binary package, let's say "xrdp- hwe-18.04" For now, I've recompiled the same xrdp from Ubuntu 18.04, on Ubuntu 18.04.2 and uploaded to my "XRP PPA", here: https://launchpad.net/~martinx/+archive/ubuntu/xrdp-hwe-18.04 To enjoy xrdp on Ubuntu 18.04 with HWE, just do: sudo add-apt-repository ppa:martinx/xrdp-hwe-18.04 sudo apt install xrdp xorgxrdp ;-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Status in xrdp package in Ubuntu: Confirmed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-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/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Ryan, If I remove the UEFI line (back to BIOS), the machine enters in Kernel Panic during the boot / commissioning. That was actually, the very test that I executed in first place (add UEFI to see)! Then, I came with this UEFI workaround, which is even better for me. Cheers! Thiago -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
@Ryan, The working XML file is attached here, with 2048 MB of RAM. NOTE: This XML was created using Virt-Manager, then, MaaS took it over after being "refreshed". Cheers! Thiago ** Attachment added: "vunft-1.xml" https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5229030/+files/vunft-1.xml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
I'm also facing this problem. My workaround is to compose VMs using Virt-Manager, Firmware = UEFI for the VM and then, refreshing the MaaS Pod. There is a need to install ovmf sudo apt install ovmf On MaaS Pod. Then, no more Kernel Panic! Details: https://discourse.maas.io/t/maas-2-5-bionic-pod-composing-guests-kernel- panic-no-init/302 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] Re: Missing "/sys/module/dummy/parameters/" subdir on dummy module
After chatting on IRC, #systemd channel, damjan explained this: https://github.com/systemd/systemd/blob/master/NEWS#L845 So, actually, the following file: cat /lib/modprobe.d/systemd.conf disables "extra" dummies, as follows: -- options bonding max_bonds=0 options dummy numdummies=0 -- Forcing us to explicitly create the dummy devices per demand (I believe, and I'll try it soon). I guess that it's really time to say goodbye to "ifupdown / /etc/network/interfaces" approach... Just for testing, after disabling the dummy line out from that file and rebooting it, I have the 12 dummies without my ugly workaround via /etc/rc.local! See, Jan-Dirk? I thought that I could blame systemd and I got my answer there! NOTE: I actually like systemd, okay? :-P It's just a new way of doing this (Netplan? systemd-networkd directly?), Jan, you can safely move to Ubuntu! ^_^ Cheers! ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Invalid Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] Re: Missing "/sys/module/dummy/parameters/" subdir on dummy module
Any news about this problem?! ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1226855] Re: Cannot use open-iscsi inside LXC container
Is this still a problem on Ubuntu 18.04? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1226855 Title: Cannot use open-iscsi inside LXC container Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Trying to use open-iscsi from within an LXC container, but the iscsi netlink socket does not support multiple namespaces, causing: "iscsid: sendmsg: bug? ctrl_fd 6" error and failure. Command attempted: iscsiadm -m node -p $ip:$port -T $target --login Results in: Exit code: 18 Stdout: 'Logging in to [iface: default, target: $target, portal: $ip,$port] (multiple)' Stderr: 'iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: $target, portal: $ip,$port]. iscsiadm: initiator reported error (18 - could not communicate to iscsid) iscsiadm: Could not log into all portals' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 17 14:38:08 2013 InstallationDate: Installed on 2013-01-15 (245 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-05-16 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147764/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147762/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147763/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147758/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147757/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147759/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147761/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147760/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147754/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147756/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147755/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] Re: Missing "/sys/module/dummy/parameters/" subdir on dummy module
apport information ** Tags added: apport-collected bionic uec-images ** Description changed: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.1 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + DistroRelease: Ubuntu 18.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + ProcEnviron: + TERM=screen + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 qxldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=26330e04-49ed-11e8-9cae-525400a53f07 ro + ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-22-generic N/A + linux-backports-modules-4.15.0-22-generic N/A + linux-firmware 1.173.1 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic uec-images + Uname: Linux 4.15.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: 1.10.2-1ubuntu1 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-bionic + dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-bionic + dmi.sys.vendor: QEMU ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1774731/+attachment/5147753/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-22-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root h
[Kernel-packages] [Bug 1774731] Re: Missing "/sys/module/dummy/parameters/" subdir on dummy module
I also asked a question about this here: https://askubuntu.com/questions/1042452/file-etc-modprobe-d-dummy-conf- ignored-on-ubuntu-18-04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Incomplete Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774731] [NEW] Missing "/sys/module/dummy/parameters/" subdir on dummy module
Public bug reported: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774731 Title: Missing "/sys/module/dummy/parameters/" subdir on dummy module Status in linux package in Ubuntu: Incomplete Bug description: Hello, On Ubuntu 18.04 (fully updated), the following configuration does not work: File /etc/modprobe.d/dummy.conf with: options dummy numdummies=12 File /etc/modules dummy The module "dummy" is loaded but, there is no 12 dummies NIC cards! The manual workaround is: --- rmmod dummy modprobe dummy numdummies=12 --- I talked on IRC and someone pointed that the dummy module is missing its "/sys/module/dummy/parameters/" subdir, so, I'm filling this bug report now. Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)
I'm also expecting this on Xenial ASAP! I'm using OpenStack with OVN, and the OpenFlow rules does not work with Kernel 4.4! And MTU does not work with 4.8! Very bad situation... :-( Also expecting the fix for: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742 ...in one shot! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)
Nice goldyfruit, thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe)
@goldyfruit, can you confirm if it also fixes the BUG: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742 ? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49, xenial-hwe) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
I also have a production environment running into network issues... Planning to downgrade the kernel to 4.4 series...=( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
I was experiencing issues with OpenStack deployed with Networking OVN and just saw this message in my dmesg: --- [ 12.241706] 8021q: adding VLAN 0 to HW filter on device eno2 [ 15.077293] eno2: Invalid MTU 9000 requested, hw max 68 --- And the IP of my eno2.600 VLAN is gone! So, the Instances can't ping each other because that is where my data path (GENEVE / VXLAN) tunnels are created on! How a bug like this ended up into an LTS release? :-( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: In Progress Status in linux-hwe source package in Yakkety: Confirmed Status in linux-hwe-edge source package in Yakkety: Confirmed Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...
Guys?!:-P -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO (and probably other modules as well) is built-in, make it modular... Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Won't Fix Status in linux source package in Yakkety: Confirmed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1389077] Re: [HP ProBook 4530s] Intel Powerclamp is Slowing CPU
I'm seeing this problem on Ubuntu 16.10. Not too frequent. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1389077 Title: [HP ProBook 4530s] Intel Powerclamp is Slowing CPU Status in linux package in Ubuntu: Confirmed Bug description: I upgraded from KUbuntu 14.04 to 14.10. Immediately, while playing minecraft with my daughter, I noticed the game was running very slowly. Even after closing the game, my web browsing slowed to a crawl. Looking at the processes in top, I noticed there were 4 tasks called kidle_inject running at 50% CPU each. After spending a long time figuring out what caused this, I found out this is caused by the Intel Powerclamp driver. I never did anything to enable this, and haven't observed this slowdown before the upgrade. I found the powerclamp driver in the /sys/class/thermal/cooling_device5 directory: root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat type intel_powerclamp root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat cur_state -1 root@bkat-HP-ProBook-4530s:/sys/class/thermal/cooling_device5# cat max_state 50 I tried to echo 0 to cur_state, but it still reported -1 when I catted the value. There seems to be no obvious way to disable this, and this should not have been enabled in the first place. 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 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bkat 2780 F pulseaudio CurrentDesktop: KDE Date: Mon Nov 3 23:16:04 2014 HibernationDevice: RESUME=UUID=35e1d874-a3bd-4227-acab-16f3e929d993 InstallationDate: Installed on 2012-04-22 (925 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Hewlett-Packard HP ProBook 4530s ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=743f1686-bfe7-4e32-911d-5371633ccec8 ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-11-03 (0 days ago) dmi.bios.date: 05/13/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.09 dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.1A dmi.chassis.asset.tag: CNU1284V1X dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.09:bd05/13/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4530s dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...
Guys, I'm marking this as "New", because this bug/improvement was not fixed on "4.8.0-11.12". Look: --- tmartins@blade:~$ lsb_release -ra No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety tmartins@blade:~$ grep VIRTIO /boot/config-4.8.0-26-generic CONFIG_VIRTIO_VSOCKETS=m CONFIG_VIRTIO_VSOCKETS_COMMON=m CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_DRM_VIRTIO_GPU=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_PCI_LEGACY=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_INPUT=m CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- See it? "CONFIG_VIRTIO_NET=y" and few others... Still not as modules... Cheers! Thiago ** Changed in: linux (Ubuntu Yakkety) Status: Fix Released => Confirmed ** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO (and probably other modules as well) is built-in, make it modular... Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Won't Fix Status in linux source package in Yakkety: Confirmed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...
I installed Linux 4.8 from "Ubuntu Kernel Team PPA" (ppa:canonical- kernel-team/ppa) on my Xenial, here is the result: -- grep VIRTIO /boot/config-4.8.0-25-generic CONFIG_VIRTIO_VSOCKETS=m CONFIG_VIRTIO_VSOCKETS_COMMON=m CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_DRM_VIRTIO_GPU=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_PCI_LEGACY=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_INPUT=m CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y -- Still not modular... :-( Any plans to make this available to Xenial via "linux-image-generic- lts-yakkety" ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO (and probably other modules as well) is built-in, make it modular... Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux source package in Yakkety: Fix Released Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10
You guys can ignore my latest message (#96). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1572801 Title: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: Ubuntu 16.04 64bit ISO number 20160420.1 unity version 7.4.0+16.04.20160415-0ubuntu1 Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10 Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 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 CasperVersion: 1.376 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 21 01:44:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1920x1080+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 'unityshell']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PLUS 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.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS 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: Thu Apr 21 01:37:17 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10
Right after booting my 16.04 (now 16.10), before even logging into Unity, I go to text console and log there... 32G of RAM being used! htop shows nothing... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1572801 Title: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: Ubuntu 16.04 64bit ISO number 20160420.1 unity version 7.4.0+16.04.20160415-0ubuntu1 Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10 Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 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 CasperVersion: 1.376 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 21 01:44:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1920x1080+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 'unityshell']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- cdrom-detect/try-usb=true noprompt SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PLUS 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.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS 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: Thu Apr 21 01:37:17 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
Anmar, I am 100% sure that it is not the browser, please guys, watch this: https://www.youtube.com/watch?v=BC287yYPfTA This BUG is not fixed. Or maybe, what I'm seeing here is a different bug. On Ubuntu 16.10, things looks a little bit better but, Chrome still flickers. Ubuntu 14.04 is fine. While 16.04 and 16.10 are just terrible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: *** Temporary workaround *** Install Kernel from the following location: - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ OR Perform the following: - $ apt-add-repository "deb http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety main" - $ echo -en "Package: *\nPin: release o=LP-PPA-canonical-kernel-team-ppa\nPin-Priority: -1\n" >> /etc/apt/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety - $ apt update - $ apt install linux-image-extra-4.6.0-6-generic linux-headers-4.6.0-6-generic linux-tools-4.6.0-6-generic ``` There was a typo in instructions (/etc/preferences.d should have been /etc/apt/preferences.d). As result you might have upgraded Linux META packages and therefor you won't receive proper upgrades of Xenial native Linux packages (hoping they will ever contain the fix). I suggest you move /etc/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety to /etc/apt/preferences.d/ and downgrade related packages: $ apt update $ apt install linux-headers-generic/xenial-updates linux-tools-generic/xenial-updates linux-image-generic/xenial-updates ``` *** Please inspect duplicate reports for more details: Bug #1522922 Bug #1535048 Bug #1552304 Bug #1555158 Bug #1561729 Bug #1565234 Bug #1568599 Bug #1573392 does not affect 4.4.0-8 affects 4.4.0-9 to 4.4.0-22 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.11.12 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tbonfort 1498 F pulseaudio CurrentDesktop: KDE Date: Tue Mar 8 09:57:12 2016 HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e InstallationDate: Installed on 2016-01-07 (61 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
I'm on 4.4.0-28-generic (Xenial), problem still here. A good website to test it, is TradingView: https://www.tradingview.com/chart/7ipqeH3N/ Google Chrome window flickers a lot! Especially if you really use the above website, by login in, clicking on its functions, pop-up windows and etc... Hardware is a Macbook Pro, end-2015. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: *** Temporary workaround *** Install Kernel from the following location: - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ OR Perform the following: - $ apt-add-repository "deb http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety main" - $ echo -en "Package: *\nPin: release o=LP-PPA-canonical-kernel-team-ppa\nPin-Priority: -1\n" >> /etc/apt/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety - $ apt update - $ apt install linux-image-extra-4.6.0-6-generic linux-headers-4.6.0-6-generic linux-tools-4.6.0-6-generic ``` There was a typo in instructions (/etc/preferences.d should have been /etc/apt/preferences.d). As result you might have upgraded Linux META packages and therefor you won't receive proper upgrades of Xenial native Linux packages (hoping they will ever contain the fix). I suggest you move /etc/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety to /etc/apt/preferences.d/ and downgrade related packages: $ apt update $ apt install linux-headers-generic/xenial-updates linux-tools-generic/xenial-updates linux-image-generic/xenial-updates ``` *** Please inspect duplicate reports for more details: Bug #1522922 Bug #1535048 Bug #1552304 Bug #1555158 Bug #1561729 Bug #1565234 Bug #1568599 Bug #1573392 does not affect 4.4.0-8 affects 4.4.0-9 to 4.4.0-22 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.11.12 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tbonfort 1498 F pulseaudio CurrentDesktop: KDE Date: Tue Mar 8 09:57:12 2016 HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e InstallationDate: Installed on 2016-01-07 (61 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...
Interesting... On Debian SID this is also not a module: --- thiago@debian-sid-1:~$ grep CONFIG_UNIX /boot/config-4.5.0-2-amd64 ... CONFIG_UNIX=y --- On 8 June 2016 at 14:43, Tim Gardner wrote: > Revert "UBUNTU: [Config] CONFIG_UNIX=m" > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1475078 > > Title: > VirtIO (and probably other modules as well) is built-in, make it > modular... > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO (and probably other modules as well) is built-in, make it modular... Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Won't Fix Status in linux source package in Yakkety: Fix Committed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
Still present on latest Xenial... :-( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1554613 Title: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: *** Temporary workaround *** Install Kernel from the following location: - http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ OR Perform the following: - $ apt-add-repository "deb http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu yakkety main" - $ echo -en "Package: *\nPin: release o=LP-PPA-canonical-kernel-team-ppa\nPin-Priority: -1\n" >> /etc/preferences.d/canonical-kernel-team-ubuntu-ppa-yakkety - $ apt update - $ apt install linux-image-extra-4.6.0-6-generic linux-headers-4.6.0-6-generic linux-tools-4.6.0-6-generic *** Please inspect duplicate reports for more details: Bug #1522922 Bug #1535048 Bug #1552304 Bug #1555158 Bug #1561729 Bug #1565234 Bug #1568599 Bug #1573392 does not affect 4.4.0-8 affects 4.4.0-9 to 4.4.0-22 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.11.12 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tbonfort 1498 F pulseaudio CurrentDesktop: KDE Date: Tue Mar 8 09:57:12 2016 HibernationDevice: RESUME=UUID=3248e0d7-0dac-4ccc-8982-b5ac5ce6ed5e InstallationDate: Installed on 2016-01-07 (61 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic root=UUID=757547b8-d0e4-4eb8-8afd-920b743f99a4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-8-generic N/A linux-backports-modules-4.4.0-8-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago) dmi.bios.date: 01/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1554613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...
Awesome!!! I'm curious, when Xenial receives the Yakkety kernel, will it be more modular too? I'm asking this because Xenial have a status of "Won't fix" but, since Canonical backports it, maybe it will benefit from this as well, am I right? Deploying Yakkety now to experiment it...:-) Thanks! Thiago -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO (and probably other modules as well) is built-in, make it modular... Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Won't Fix Status in linux source package in Yakkety: Fix Committed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1570195] Re: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices
Never mind, it is working now... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices Status in dpdk package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it up. https://help.ubuntu.com/16.04/serverguide/DPDK.html service openvswitch-switch stop service dpdk stop OVS DPDK Options (/etc/default/openvswitch-switch): -- DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist :00:03.0,:00:04.0' -- service dpdk start service openvswitch-switch start - Enable multi-queue on OVS+DPDK inside of the VM: ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00 * Multi-queue apparently works! ovs-vswitchd consumes more that 100% of CPU, meaning that it multi-queue is there... *** Where it fails? 1- Reboot the VM and try to run ethtool again (or go straight to 2 below): ethtool -L ens5 combined 4 2- Try to fire up ens4: ip link set dev ens4 up # FAIL! Both commands hangs, consuming 100% of guest's CPU... So, it looks like a Linux fault, because it is "allowing" the DPDK VirtIO App (a user land App), to interfere with kernel devices in a strange way... Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 14 00:35 seq crw-rw 1 root audio 116, 33 Apr 14 00:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Thu Apr 14 01:27:27 2016 HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de InstallationDate: Installed on 2016-04-07 (7 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160406) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=9911604e-353b-491f-a0a9-804724350592 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-wily dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-wily dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1570195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1570195] Re: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices
Just for the record, after upgrading DPDK (proposed repo), OpenvSwitch+DPDK isn't not starting up anymore when inside of a VM... I am double checking everything again... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices Status in dpdk package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it up. https://help.ubuntu.com/16.04/serverguide/DPDK.html service openvswitch-switch stop service dpdk stop OVS DPDK Options (/etc/default/openvswitch-switch): -- DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist :00:03.0,:00:04.0' -- service dpdk start service openvswitch-switch start - Enable multi-queue on OVS+DPDK inside of the VM: ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00 * Multi-queue apparently works! ovs-vswitchd consumes more that 100% of CPU, meaning that it multi-queue is there... *** Where it fails? 1- Reboot the VM and try to run ethtool again (or go straight to 2 below): ethtool -L ens5 combined 4 2- Try to fire up ens4: ip link set dev ens4 up # FAIL! Both commands hangs, consuming 100% of guest's CPU... So, it looks like a Linux fault, because it is "allowing" the DPDK VirtIO App (a user land App), to interfere with kernel devices in a strange way... Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 14 00:35 seq crw-rw 1 root audio 116, 33 Apr 14 00:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Thu Apr 14 01:27:27 2016 HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de InstallationDate: Installed on 2016-04-07 (7 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160406) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=9911604e-353b-491f-a0a9-804724350592 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-wily dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-wily dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/157019
[Kernel-packages] [Bug 1245081] Re: macbook keyboard layout maps the tilde key to something else
Still present on Xenial 16.04.
Workaround is good.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1245081
Title:
macbook keyboard layout maps the tilde key to something else
Status in linux package in Ubuntu:
Confirmed
Bug description:
1. install ubuntu on Macbook Air 6,2
2. press the key with the tilde ('~') written on it.
3. see that is prints '§' instead.
This is particularly annoying since the way to switch between windows uses
the tilde.
---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kms1491 F pulseaudio
/dev/snd/controlC1: kms1491 F pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=9e7b2d0e-6a44-4ad7-9725-f9a3f5f39c33
InstallationDate: Installed on 2013-10-25 (1 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac
(20131016.1)
MachineType: Apple Inc. MacBookAir6,2
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux 3.11.0.12.13
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic
root=UUID=079cbe6b-6488-4e57-85d3-c3e3e2fcbe40 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
RelatedPackageVersions:
linux-restricted-modules-3.11.0-12-generic N/A
linux-backports-modules-3.11.0-12-generic N/A
linux-firmware 1.116
Tags: saucy
Uname: Linux 3.11.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/12/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA61.88Z.0099.B01.1307121317
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-7DF21CB3ED6977E5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-7DF21CB3ED6977E5
dmi.modalias:
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B01.1307121317:bd07/12/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
dmi.product.name: MacBookAir6,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245081/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570195] [NEW] Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO
Public bug reported: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it up. https://help.ubuntu.com/16.04/serverguide/DPDK.html service openvswitch-switch stop service dpdk stop OVS DPDK Options (/etc/default/openvswitch-switch): -- DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist :00:03.0,:00:04.0' -- service dpdk start service openvswitch-switch start - Enable multi-queue on OVS+DPDK inside of the VM: ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00 * Multi-queue apparently works! ovs-vswitchd consumes more that 100% of CPU, meaning that it multi-queue is there... *** Where it fails? 1- Reboot the VM and try to run ethtool again (or go straight to 2 below): ethtool -L ens5 combined 4 2- Try to fire up ens4: ip link set dev ens4 up # FAIL! Both commands hangs, consuming 100% of guest's CPU... So, it looks like a Linux fault, because it is "allowing" the DPDK VirtIO App (a user land App), to interfere with kernel devices in a strange way... Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 14 00:35 seq crw-rw 1 root audio 116, 33 Apr 14 00:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Thu Apr 14 01:27:27 2016 HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de InstallationDate: Installed on 2016-04-07 (7 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160406) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=9911604e-353b-491f-a0a9-804724350592 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-wily dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-wily dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO Status in linux package in Ubuntu: New Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Et
[Kernel-packages] [Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...
So, no deal? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO (and probably other modules as well) is built-in, make it modular... Status in linux package in Ubuntu: Confirmed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561729] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe A FIFO underrun
Joseph, Earlier versions of Xenial, doesn't have this problem. Maybe with previous XOrg / Linux 4.3 combo... And also, maybe two or three Google Chrome previous versions? I think that it would be a good idea to give it a try, maybe a Xenial alpha. Best! Thiago -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1561729 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Bug description: Hey Guys, i am encountering some random screen flickering after i launched google-chrome. this persists even after closing chrome. it is like the screen wents black for a fracture of a second. when it happens dmesg reports: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe A FIFO underrun I am currently on Ubuntu 1604 Daily: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 PS: It is a Dell XPS 13 9530 with no external display attached. The internal display is an FHD one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561729] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe A FIFO underrun
However, I'm not seeing any DRM errors on dmesg / kern.log. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1561729 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Bug description: Hey Guys, i am encountering some random screen flickering after i launched google-chrome. this persists even after closing chrome. it is like the screen wents black for a fracture of a second. when it happens dmesg reports: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe A FIFO underrun I am currently on Ubuntu 1604 Daily: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 PS: It is a Dell XPS 13 9530 with no external display attached. The internal display is an FHD one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1561729] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe A FIFO underrun
Hey! I'm also facing this problem, I recorded a video about it: https://www.youtube.com/watch?v=l21WsKz3fZc I tried to move away from XOrg, by using GNOME+Wayland, but, problem persist, Wayland is faster, however, I can still see it flickering (faster). Problem with GNOME+Wayland is that it completely freezes my Macbook. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1561729 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Bug description: Hey Guys, i am encountering some random screen flickering after i launched google-chrome. this persists even after closing chrome. it is like the screen wents black for a fracture of a second. when it happens dmesg reports: [drm:intel_cpu_fifo_underrun_irq_handler [i915_bpo]] *ERROR* CPU pipe A FIFO underrun I am currently on Ubuntu 1604 Daily: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 PS: It is a Dell XPS 13 9530 with no external display attached. The internal display is an FHD one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
I'm seeing this BUG on most recent Xenial Beta release (updated today). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in os-prober package in Ubuntu: Confirmed Status in os-prober package in Debian: Fix Released Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108] attempt to access beyond end of device [ 576.834119] sda4: rw=16, want=3, limit=2 [ 576.834125] hfsplus: unable to find HFS+ superblock [ 576.837264] qnx4: no qnx4 filesystem (no root dir). [ 576.840408] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd
[Kernel-packages] [Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...
Any news about this guys? I'm on Linux 4.4.0-11-generic / Xenial and the kernel isn't modular yet! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO (and probably other modules as well) is built-in, make it modular... Status in linux package in Ubuntu: Confirmed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 262550] Re: WARNING: Intrepid might burn down MacBook Pro
Hey guys! Please, ignore my latest messages! After researching a little bit about this, I realized that by just installing: macfanctld and a few more, like: pommed / gpomme My Macbook is finally cooler on Ubuntu! Thanks! Thiago -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/262550 Title: WARNING: Intrepid might burn down MacBook Pro Status in Mactel Support: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Intrepid: Invalid Bug description: Binary package hint: linux-image-2.6.27-1-generic Testing Ubuntu 8.10 Alpha 4 64-Bit on a MacBook Pro rev. 3. Installing today's updates, the MacBook gets extremely hot and automatically goes into standby. This looks like an emergency standby caused by the EFI or something because it got overheated. Unless you put a metal plate or something under it, the fan runs on highest level at full power, which is not the usual. Is there a tool you can see the CPU temperature with? To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/262550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 262550] Re: WARNING: Intrepid might burn down MacBook Pro
Still a problem on Ubuntu 16.04 on a brand new Macbook Pro 2015. Under OS X, supercool, under Ubuntu, super hot! Even without running anything, just boot it, login and wait, it will become hot. This problem have what, 20 years? For God's sake! Time to fix this once for all, Ubuntu should keep a Macbook cool, just like OS X does, by default. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/262550 Title: WARNING: Intrepid might burn down MacBook Pro Status in Mactel Support: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Intrepid: Invalid Bug description: Binary package hint: linux-image-2.6.27-1-generic Testing Ubuntu 8.10 Alpha 4 64-Bit on a MacBook Pro rev. 3. Installing today's updates, the MacBook gets extremely hot and automatically goes into standby. This looks like an emergency standby caused by the EFI or something because it got overheated. Unless you put a metal plate or something under it, the fan runs on highest level at full power, which is not the usual. Is there a tool you can see the CPU temperature with? To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/262550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...
That's nice! How can I help? I would like to make sure that Linux 4.4 on Xenial have this bug fixed! I think I can help... Where is located the Ubuntu Linux package (its debian/ subdir)? Is it a Git repo used by git-buildpackage or something? :-) On 19 January 2016 at 08:30, Andy Whitcroft wrote: > ** Changed in: linux (Ubuntu) > Milestone: ubuntu-15.12 => ubuntu-16.01 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1475078 > > Title: > VirtIO (and probably other modules as well) is built-in, make it > modular... > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO (and probably other modules as well) is built-in, make it modular... Status in linux package in Ubuntu: Confirmed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475078] Re: VirtIO (and probably other modules as well) is built-in, make it modular...
Hey guys, Any plans to make Linux more modular for 16.04 ? I just installed it and modules are still built-in... --- ubuntu@xenial:~$ grep VIRTIO /boot/config-4.2.0-17-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_DRM_VIRTIO_GPU=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_PCI_LEGACY=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_INPUT=m CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- I would like to help testing this, to end up with 16.04 in shape! Lets do it?! Best, Thiago -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO (and probably other modules as well) is built-in, make it modular... Status in linux package in Ubuntu: Confirmed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1346917] Re: Using KSM on NUMA capable machines can cause KVM guest performance and stability issues
Why not go with Linux 3.19 ? You can just install it by running: sudo apt-get install linux-generic-lts-vivid It is by far, much more stable than Linux 3.13 (specially the network stack)... ;-) On 6 October 2015 at 11:36, Jim wrote: > This is NOT fixed by 3.13.0-33.58. It continues to persist even with > 3.13.0-65.106 (and 3.13.0-63.103). > > I have around 10 VMs running but ONE in particular disconnects from the > network every hour or so. > > I had this issue previously but it was initially gone on Ubuntu 14.04 > LTS but had come back recently - perhaps some kernel regression ? > > dmesg shows > > [42524.196629] kvm: zapping shadow pages for mmio generation wraparound > [42538.140013] br0: port 2(vnet0) entered learning state > [42538.268017] br1: port 2(vnet1) entered learning state > [42553.180008] br0: topology change detected, propagating > [42553.180015] br0: port 2(vnet0) entered forwarding state > [42553.308008] br1: topology change detected, propagating > [42553.308014] br1: port 2(vnet1) entered forwarding state > > (and NIC connection is gone) > > It's not clear if this is just co-incidence or if this is a pointer to > the issue. > > This VM is unusual in my VMs becuase it is the only one with 2 NIC > connections to br1 and br0. All the others connect to just br0. Those > others work OK. > > Happy to try suggestions to track this down. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1341195). > https://bugs.launchpad.net/bugs/1346917 > > Title: > Using KSM on NUMA capable machines can cause KVM guest performance and > stability issues > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1346917 Title: Using KSM on NUMA capable machines can cause KVM guest performance and stability issues Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: [Impact] When using KVM on NUMA machines, both Linux and Windows guests can exhibit very poor performance and potential crashes. Disabling KSM is a known workaround to fix this issue. [Fix] The following patch fixes the issue in our testing: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=64a9a34e22896dad430e21a28ad8cb00a756fefc This patch is present in v3.14-rc1 and onwards. [Test Case] General test case: 1) On a NUMA capable machine, setup the machine as a KVM hypervisor - lscpu should show more than 1 NUMA node 2) Install 4 KVM VMs 3) Run the following in another terminal to ensure that pages_shared and pages_sharing is increasing - watch 'tail /sys/kernel/mm/ksm/*' 4) In another terminal run a program that continually pings each node and alerts on high latencies What we've observed is that in Linux guests, the ping latencies can go into the ~2 second range for a few pings, then return back to the < 1ms range. (This is machine dependent.) In addition, occasionally when running this test with Windows guests we observe BSODs during this test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1473109] Re: uio_pci_generic is not available in trusty kernel package for ppc64el
Problem fixed on both "Linux 3.13.0-63-generic" and "Linux 3.16.0-48-generic" on Trusty. Thanks! ** Tags removed: trusty verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1473109 Title: uio_pci_generic is not available in trusty kernel package for ppc64el Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Bug description: [Impact] uio_pci_generic is not enabled in linux kernel package for ppc64el while other architectures have it enabled. This is useful for things like DPDK. [Test Case] modprobe uio_pci_generic [Fix] CONFIG_UIO_PCI_GENERIC=m for common ubuntu config -- Looking into git tree : ~/sources/pub/ubuntu.com/ubuntu-14.04-trusty$ git grep UIO_PCI_GENERIC debian.master/ debian.master/config/amd64/config.common.amd64:CONFIG_UIO_PCI_GENERIC=m debian.master/config/arm64/config.common.arm64:CONFIG_UIO_PCI_GENERIC=m debian.master/config/armhf/config.common.armhf:CONFIG_UIO_PCI_GENERIC=m debian.master/config/i386/config.common.i386:CONFIG_UIO_PCI_GENERIC=m debian.master/config/powerpc/config.common.powerpc:CONFIG_UIO_PCI_GENERIC=m debian.master/config/ppc64el/config.common.ppc64el:# CONFIG_UIO_PCI_GENERIC is not set I can't find a reason why it would be disabled only for ppc64el and I can see that utopic enables it for all architectures (common configuration). Can we have it enabled ? This module is used by dpdk (for example). Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475078] Re: VirtIO is built-in, make it modular...
Oh, BTW, I believe that the Linux Kernel configuration should be entirely modular, and not only the VirtIO related modules. ;-) ** Summary changed: - VirtIO is built-in, make it modular... + VirtIO (and probably other modules as well) is built-in, make it modular... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO (and probably other modules as well) is built-in, make it modular... Status in linux package in Ubuntu: Confirmed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475078] Re: VirtIO is built-in, make it modular...
YAY!! :-D That's why I love Launchpad! But, you meant "15.10", and not "15.07... Am I right? I hope to see the future package "linux-generic-lts-wily" for Trusty, in a modular fashion as well! Don't forget that! Thank you so much! Cheers! Thiago -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO is built-in, make it modular... Status in linux package in Ubuntu: Confirmed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475078] Re: VirtIO is built-in, make it modular...
Just for the record, I would give an use case example... For high performance virtualized environments, we're seeing new solutions popping out in the market, for example: * Netmap / VALE (mSwitch). But, since Ubuntu ships VirtIO as a buil-in module, It is not possible to use/evaluate Netmap (VirtIO version) with it. This is a show stopping for Ubuntu in a high performance virt-env... While Debian is fine. Ubuntu Kernel Team should definitively make its "linux-image" more modular, there is no doubt about this. OpenStack for Telcos (NFV subject) will definitively need Netmap / VALE, or DPDK, for example... So, Ubuntu should not do things that breaks future development of high speed virtual environments. Think forward, Linux is modular. No need to compile modules as built-in. Just my two Bitcents... :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO is built-in, make it modular... Status in linux package in Ubuntu: Confirmed Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475078/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475078] [NEW] VirtIO is built-in, make it modular...
Public bug reported: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-02-02 (163 days ago) dmi.bios.date: 10/09/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B11.1310091428 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B11.1310091428:bd10/09/2013:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1475078 Title: VirtIO is built-in, make it modular... Status in linux package in Ubuntu: New Bug description: Guys, Can Canonical ship Ubuntu with its Linux in a modular way? Honestly, don't understand why some modules are compiled as built-in, instead of modules, for example (NET/BLK/PCI/etc): --- ubuntu@vivid-1:~$ grep VIRTIO /boot/config-3.19.0-23-generic CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y CONFIG_VIRTIO_BALLOON=y CONFIG_VIRTIO_MMIO=y CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y --- While on Debian, it is all modular, as expected: --- debian@jessie-1:~# grep VIRTIO /boot/config-3.16.0-4-amd64 CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=m CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=m CONFIG_VIRTIO_CONSOLE=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m # CONFIG_VIRTIO_MMIO is not set --- I see no reason to load this modules in a non-virtualized environments. Thoughts!? Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmartins 3485 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 15 21:44:14 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-27 (261 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Apple Inc. MacBookAir4,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic.efi.signed root=UUID=f64e109d-bc06-43ec-8ca8-d10e4f915d2e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/
[Kernel-packages] [Bug 1399064] Re: bridges cannot have a mtu > 1500 by themselves
Also affects Linux 3.19 on Ubuntu Trusty (linux-generic-lts-vivid). It seems that the only way to create a bridge with MTU=9000 is by creating it on top of a dummy interface, with mtu 9000 already configured... Very annoying... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1399064 Title: bridges cannot have a mtu > 1500 by themselves Status in linux package in Ubuntu: Triaged Bug description: A linux bridge always adopts the smallest MTU of the enslaved devices. When no device are enslaved, it defaults to a MTU of 1500 and refuses to use a larger one. This is problematic when using bridges enslaving only virtual NICs (vnetX) like it's common with KVM guests. Steps to reproduce the problem 1) sudo ip link add br-test0 type bridge # create an empty bridge 2) sudo ip link set br-test0 mtu 9000# attempt to set MTU > 1500 3) ip link show dev br-test0 # confirm MTU Here, 2) returns "RTNETLINK answers: Invalid argument". One (cumbersome) way around this is: 4) sudo modprobe dummy 5) sudo ip link set dummy0 mtu 9000 master br-test0 Then the bridge's MTU can be changed from anywhere to 9000. This bug is especially annoying for the virtualization case because the KVM's tap driver will by default adopt the bridge's MTU on startup making it impossible (without the workaround) to use a large MTU on the guest VMs. Additional information: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy linux-image-3.13.0-41-generic iproute2 linux-image-3.13.0-41-generic: Installed: 3.13.0-41.70 Candidate: 3.13.0-41.70 Version table: *** 3.13.0-41.70 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status iproute2: Installed: 3.12.0-2 Candidate: 3.12.0-2 Version table: *** 3.12.0-2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-41-generic 3.13.0-41.70 ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 Uname: Linux 3.13.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simon 4594 F pulseaudio CurrentDesktop: Unity CurrentDmesg: dmesg: klogctl failed: Operation not permitted Date: Wed Dec 3 23:02:25 2014 HibernationDevice: RESUME=UUID=8e7a3220-158f-413b-81b2-55b236bb1f3f InstallationDate: Installed on 2014-01-26 (311 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) MachineType: LENOVO 2516CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-41-generic root=/dev/mapper/crypt-root ro quiet splash cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-root possible_cpus=4 nmi_watchdog=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-41-generic N/A linux-backports-modules-3.13.0-41-generic N/A linux-firmware 1.127.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1399064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1452868] Re: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19.
I am unable to replicate this problem. Closing it. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Package changed: linux (Ubuntu Vivid) => Ubuntu Vivid ** Changed in: Ubuntu Vivid Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in Ubuntu: Invalid Status in The Vivid Vervet: Invalid Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x
[Kernel-packages] [Bug 1452868] Re: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19.
Hello Chris, After a complete power cycle, Juno with Trusty + Linux 3.19 is working. Tenants have connectivity again. So far, the only error that I'm still seeing, is the following: --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' --- I'll clean up everything, bridges and Namespaces, to see if the problem persists. I saw this problem in a lab as well, I'll reset the databases and tenants to start over again, with Linux 3.19 from the beginning. If I do not manage to reproduce it until next Monday, I'll close this BUG as "not reproducible". Sorry about the buzz! Best, Thiago -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: New Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv
[Kernel-packages] [Bug 1452868] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393192/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 a
[Kernel-packages] [Bug 1452868] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393189/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad
[Kernel-packages] [Bug 1452868] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393188/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad de 48 89 df 48 89
[Kernel-packages] [Bug 1452868] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393187/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad de
[Kernel-packages] [Bug 1452868] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393184/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad de 48 89
[Kernel-packages] [Bug 1452868] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393186/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 2
[Kernel-packages] [Bug 1452868] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393196/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30
[Kernel-packages] [Bug 1452868] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393191/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad de 4
[Kernel-packages] [Bug 1452868] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393194/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad de 48 89 df 48
[Kernel-packages] [Bug 1452868] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393185/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad de 48 89 df 48 89 4
[Kernel-packages] [Bug 1452868] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393190/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad de 4
[Kernel-packages] [Bug 1452868] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393195/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad de 48 89 df
[Kernel-packages] [Bug 1452868] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1452868/+attachment/4393193/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Confirmed Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad de 4
[Kernel-packages] [Bug 1452868] Re: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19.
apport information ** Tags added: apport-collected ** Description changed: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad de 48 89 df 48 89 43 30 48 8b 43 48 ff 50 10 48 8b 43 48 <48> 8b 78 40 e8 d6 55 af c0 48 83 c4 08 5b 5d c3 66 66 66 66 66 [ 152.308375] RIP [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.308433] RSP [ 152.308504] ---[ end trace cc9561be41fd191a ]--- [ 217.847530] init: neutron-ovs-cleanup pre-start process (871) terminated with status 1 [ 217.913947] init: wait-for-state (neutron-dhcp-agentneutron-ovs-clean
[Kernel-packages] [Bug 1452868] Re: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno completely broken in Juno
lspci-vnvn.log ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452868/+attachment/4393166/+files/lspci-vnvn.log ** Summary changed: - "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno completely broken in Juno + "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno completely broken in Trusty + Linux 3.19. ** Summary changed: - "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno completely broken in Trusty + Linux 3.19. + "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452868 Title: "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19. Status in linux package in Ubuntu: Incomplete Bug description: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msg
[Kernel-packages] [Bug 1452868] [NEW] "ip link delete" returns "RTNETLINK answers: Operation not supported" - OpenStack Juno is completely broken in Trusty + Linux 3.19.
Public bug reported: Guys, I just upgraded my Trusty with "linux-generic-lts-vivid" that is available in proposed repository. OpenStack is completely broken now. I'm using it with VXLAN + OpenvSwitch. All Tenants are offline. I'm seeing the following error at Network Node (Neutron L3 Router): --- ==> /var/log/neutron/ovs-cleanup.log <== 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 86, in _execute 2015-05-07 13:30:57.384 881 TRACE neutron log_fail_as_error=log_fail_as_error) 2015-05-07 13:30:57.384 881 TRACE neutron File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 84, in execute 2015-05-07 13:30:57.384 881 TRACE neutron raise RuntimeError(m) 2015-05-07 13:30:57.384 881 TRACE neutron RuntimeError: 2015-05-07 13:30:57.384 881 TRACE neutron Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'link', 'delete', 'tap3da8f4fe-55'] 2015-05-07 13:30:57.384 881 TRACE neutron Exit code: 2 2015-05-07 13:30:57.384 881 TRACE neutron Stdout: '' 2015-05-07 13:30:57.384 881 TRACE neutron Stderr: 'RTNETLINK answers: Operation not supported\n' 2015-05-07 13:30:57.384 881 TRACE neutron --- It also doesn't work manually: --- root@network-1:~# ip link delete tap3da8f4fe-55 RTNETLINK answers: Operation not supported --- dmesg shows this: --- [ 152.307822] Modules linked in: vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch libcrc32c snd_hda_codec_generic iosf_mbi snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_controller ghash_clmulni_intel snd_hda_codec aesni_intel ppdev snd_hwdep snd_pcm aes_x86_64 qxl lrw snd_timer gf128mul snd ttm glue_helper drm_kms_helper soundcore i2c_piix4 ablk_helper drm serio_raw cryptd pvpanic 8250_fintek parport_pc mac_hid lp parport psmouse pata_acpi floppy [ 152.307893] CPU: 0 PID: 1067 Comm: ovs-vswitchd Not tainted 3.19.0-16-generic #16~14.04.2-Ubuntu [ 152.307901] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 152.307906] task: 880036aee220 ti: 880079eb4000 task.ti: 880079eb4000 [ 152.307912] RIP: 0010:[] [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.307923] RSP: 0018:880079eb79a8 EFLAGS: 00010296 [ 152.307929] RAX: 8025 RBX: 880079f04e40 RCX: 000181ec [ 152.307934] RDX: 000181ed RSI: ead860c0 RDI: 4000 [ 152.307938] RBP: 880079eb79b8 R08: 8800361834a0 R09: 000181ec [ 152.307943] R10: ead860c0 R11: 813a7f65 R12: 880079f04e40 [ 152.307948] R13: 880079e97100 R14: ffea R15: 880079e30180 [ 152.307955] FS: 7fc5f96a5980() GS:88007fc0() knlGS: [ 152.307961] CS: 0010 DS: ES: CR0: 80050033 [ 152.307966] CR2: 7f32854bd740 CR3: 7a032000 CR4: 000406f0 [ 152.307972] Stack: [ 152.307975] 880079eb7a30 880079eb7a30 880079eb79c8 c05f6380 [ 152.307984] 880079eb79f8 c05f6455 c05ff268 c0602040 [ 152.307992] 88007a700814 880079e97000 880079eb7aa8 816db0e5 [ 152.308003] Call Trace: [ 152.308012] [] ovs_dp_detach_port+0x30/0x40 [openvswitch] [ 152.308019] [] ovs_vport_cmd_del+0xc5/0x110 [openvswitch] [ 152.308034] [] genl_family_rcv_msg+0x1a5/0x3d0 [ 152.308040] [] ? genl_family_rcv_msg+0x3d0/0x3d0 [ 152.308046] [] genl_rcv_msg+0x91/0xd0 [ 152.308051] [] netlink_rcv_skb+0xc1/0xe0 [ 152.308056] [] genl_rcv+0x2c/0x40 [ 152.308060] [] netlink_unicast+0xf6/0x200 [ 152.308065] [] netlink_sendmsg+0x313/0x690 [ 152.308078] [] ? aa_sk_perm.isra.4+0x70/0x150 [ 152.308090] [] do_sock_sendmsg+0x8c/0x100 [ 152.308096] [] ? copy_msghdr_from_user+0x15e/0x1f0 [ 152.308103] [] ___sys_sendmsg+0x313/0x320 [ 152.308112] [] ? destroy_inode+0x3c/0x70 [ 152.308118] [] ? evict+0x117/0x190 [ 152.308122] [] ? dentry_free+0x5f/0xa0 [ 152.308127] [] ? __dentry_kill+0x154/0x1f0 [ 152.308132] [] ? dput+0xa5/0x170 [ 152.308138] [] ? mntput+0x24/0x40 [ 152.308143] [] __sys_sendmsg+0x42/0x80 [ 152.308148] [] SyS_sendmsg+0x12/0x20 [ 152.308156] [] system_call_fastpath+0x16/0x1b [ 152.308208] Code: 8b 57 30 48 85 c0 48 89 02 74 04 48 89 50 08 48 b8 00 02 20 00 00 00 ad de 48 89 df 48 89 43 30 48 8b 43 48 ff 50 10 48 8b 43 48 <48> 8b 78 40 e8 d6 55 af c0 48 83 c4 08 5b 5d c3 66 66 66 66 66 [ 152.308375] RIP [] ovs_vport_del+0x41/0x60 [openvswitch] [ 152.308433] RSP [ 152.308504] ---[ end trace cc9561be41fd191a ]--- [ 217.847530] init: neutron-ovs-cleanup pre-start process (871) terminated with status 1 [ 217.913947] init: wait-for-state (neutron-dhcp-agentneutron-ovs-cleanup) main process (862) killed by TERM signal --- Falling back to Linux 3.16. Info: root@network-1:~# cat /proc/version_signature > version.log root@network-1:~# cat version.log Ubuntu 3.19.0-16.16~14.04.2-generic 3.19.3
[Kernel-packages] [Bug 759725] Re: The kernel is no longer readable by non-root users
Any news on this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/759725 Title: The kernel is no longer readable by non-root users Status in hobbit-plugins package in Ubuntu: In Progress Status in linux package in Ubuntu: Won't Fix Bug description: The mode of the latest kernel has changed so it is no longer readable by non-root users: -rw-r--r-- 1 root root 4336016 2010-10-17 01:37 /boot/vmlinuz-2.6.35-22-generic -rw-r--r-- 1 root root 4336912 2010-11-24 12:46 /boot/vmlinuz-2.6.35-23-generic -rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic -rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic This prevents people from using this kernel to boot qemu virtual machines as non-root. Please change the mode back to make the kernel readable. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:240: no soundcards found... Architecture: amd64 ArecordDevices: arecord: device_list:240: no soundcards found... CRDA: Error: [Errno 2] No such file or directory Date: Wed Apr 13 13:05:01 2011 HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Red Hat KVM PciMultimedia: ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash RelatedPackageVersions: linux-restricted-modules-2.6.35-22-generic N/A linux-backports-modules-2.6.35-22-generic N/A linux-firmware 1.50 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.modalias: dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.0.0PC:cvnRedHat:ct1:cvr: dmi.product.name: KVM dmi.product.version: RHEL 6.0.0 PC dmi.sys.vendor: Red Hat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hobbit-plugins/+bug/759725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 997605] Re: Disabling IPv6 autoconfiguration in sysctl.conf doesn't affect boot process
Guys, This problem still persist on Ubuntu 14.04.1, as follows: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1345847 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/997605 Title: Disabling IPv6 autoconfiguration in sysctl.conf doesn't affect boot process Status in “linux” package in Ubuntu: Confirmed Bug description: When you put the following lines in sysctl.conf net.ipv6.conf.all.autoconf = 0 net.ipv6.conf.all.accept_ra = 0 the expeced result is to disable IPv6 autoconfiguration at bootup, but, actually, it does nothing, because sysctl.conf network settings are applied after network has been started. So what happens: 1. Network interfaces are started by /etc/init.d/networking 1a. IPv6 uses autocnfiguratin, because it is enabled at this point 2. Sysctl.conf settings are applied by /etc/init/procps.conf I don't know if there is an easy solution, because inverting order things are called could break something else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/997605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335691] Re: Server 14.04 does not set static IPv6 addresses on interfaces when auto-config options are turned off
Just a curiosity, take a look at my IPv6 problems with Trusty: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1345847 :-/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1335691 Title: Server 14.04 does not set static IPv6 addresses on interfaces when auto-config options are turned off Status in “linux” package in Ubuntu: Incomplete Bug description: On Ubuntu server 14.04 (upgraded from 13.10) I am trying to get rid of the IPv6 auto-config addresses and leave on my statically assigned ones. The system has two interfaces, a physical eth0 and vlan10. 1. privext 0 in /etc/network/interfaces When I set the "privext 0" option for both interfaces in /etc/network/interfaces, then vlan10 does not get the configured static IPv6 address. It only gets the IPv6 link local address. However, eth0 is configured as expected with just the given static address. Using "privext 0" on only one or the other, but not both, worked as expected. 2. net.ipv6.conf.*.use_tempaddr = 0 in /etc/sysctl.conf If I add both net.ipv6.conf.eth0.use_tempaddr = 0 and net.ipv6.conf.vlan10.use_tempaddr = 0 of /etc/sysctl.conf, then the situation is reversed. Vlan10 is configured as expected with just its given address and eth0 has only the link-local address. If I add only net.ipv6.conf.eth0.use_tempaddr = 0, then again eth0 only gets the link local address and not the assigned static. On using net.ipv6.conf.vlan10.use_tempaddr = 0, then everything ended up as expected - eth0 had the auto-config addresses plus its static address and vlan10 only had the static address. 1 + 2 kludging attempt: Unfortunately, combining net.ipv6.conf.vlan10.use_tempaddr = 0 in sysctl.conf and "privext 0" in /etc/network/interfaces for eth0, both of which worked as expected alone, did not work togther. The result was the same as setting net.ipv6.conf.*.use_tempaddr = 0 on bothg, as mentioned above. 3. net.ipv6.conf.*.use_tempaddr = 0 in /etc/sysctl.conf Using net.ipv6.conf.*.autoconf = 0 resulted in eth0 getting only it's static address as expected, but vlan10 was still given the autoconfig addresses. Using only net.ipv6.conf.vlan10.autoconf = 0 had no effect, the interface still go the auto-config addresses. Using only net.ipv6.conf.eth0.autoconf = 0 did work. 2 + 3 kludging attempt: What finally worked was the combination of net.ipv6.conf.vlan10.autoconf = 0 and net.ipv6.conf.vlan10.use_tempaddr = 0 Summary: So it looks like that of all thee three methods one can potentially use to get rid of IPv^ auto-config addresses, one simply doesn't work on vlan interfaces and the other two have weird transitive side effects when applied at the same time to a parent physical interface and a child vlan interface when one would expect them to be entirely independent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335691] Re: Server 14.04 does not set static IPv6 addresses on interfaces when auto-config options are turned off
Cory, You can run `apport-collect` on a headless server if you install the text browser called `w3m`. Take a look: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/997020 I did this myself and it works... BTW, I'm facing some IPv6 problems that I think it is related to this BUG, I'll post more info here this week. Best, Thiago -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1335691 Title: Server 14.04 does not set static IPv6 addresses on interfaces when auto-config options are turned off Status in “linux” package in Ubuntu: Incomplete Bug description: On Ubuntu server 14.04 (upgraded from 13.10) I am trying to get rid of the IPv6 auto-config addresses and leave on my statically assigned ones. The system has two interfaces, a physical eth0 and vlan10. 1. privext 0 in /etc/network/interfaces When I set the "privext 0" option for both interfaces in /etc/network/interfaces, then vlan10 does not get the configured static IPv6 address. It only gets the IPv6 link local address. However, eth0 is configured as expected with just the given static address. Using "privext 0" on only one or the other, but not both, worked as expected. 2. net.ipv6.conf.*.use_tempaddr = 0 in /etc/sysctl.conf If I add both net.ipv6.conf.eth0.use_tempaddr = 0 and net.ipv6.conf.vlan10.use_tempaddr = 0 of /etc/sysctl.conf, then the situation is reversed. Vlan10 is configured as expected with just its given address and eth0 has only the link-local address. If I add only net.ipv6.conf.eth0.use_tempaddr = 0, then again eth0 only gets the link local address and not the assigned static. On using net.ipv6.conf.vlan10.use_tempaddr = 0, then everything ended up as expected - eth0 had the auto-config addresses plus its static address and vlan10 only had the static address. 1 + 2 kludging attempt: Unfortunately, combining net.ipv6.conf.vlan10.use_tempaddr = 0 in sysctl.conf and "privext 0" in /etc/network/interfaces for eth0, both of which worked as expected alone, did not work togther. The result was the same as setting net.ipv6.conf.*.use_tempaddr = 0 on bothg, as mentioned above. 3. net.ipv6.conf.*.use_tempaddr = 0 in /etc/sysctl.conf Using net.ipv6.conf.*.autoconf = 0 resulted in eth0 getting only it's static address as expected, but vlan10 was still given the autoconfig addresses. Using only net.ipv6.conf.vlan10.autoconf = 0 had no effect, the interface still go the auto-config addresses. Using only net.ipv6.conf.eth0.autoconf = 0 did work. 2 + 3 kludging attempt: What finally worked was the combination of net.ipv6.conf.vlan10.autoconf = 0 and net.ipv6.conf.vlan10.use_tempaddr = 0 Summary: So it looks like that of all thee three methods one can potentially use to get rid of IPv^ auto-config addresses, one simply doesn't work on vlan interfaces and the other two have weird transitive side effects when applied at the same time to a parent physical interface and a child vlan interface when one would expect them to be entirely independent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1341195] Re: KVM guests getting slow by time
Hey guys! I'm pretty sure that the following patch will fix your problems: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346917 New kernel for Trusty: http://people.canonical.com/~arges/lp1346917/ My original BUG: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338277 Cheers! Thiago On 28 July 2014 15:43, wolfgang.m...@web.de wrote: > After updating a server 12.04. LTS including the new HWE stack support > I've got the same problems. > The guest (MS Server 2012R2) was running after startup for about 7 to 10 > min without problems, after this period the cpu utilisation for the kvm > process increases more an more, the guest became sluggish. > Most significant problem: file and printer services went slow but kept > working, SQL-Server applications have crashed. > Starting the previous kernel 3.11.0-26-generic was my workaround solving > the problem for the moment. > I > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1341195 > > Title: > KVM guests getting slow by time > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1341195/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1341195 Title: KVM guests getting slow by time Status in “linux” package in Ubuntu: Incomplete Bug description: There is a post with very similar symptoms on serverfault: http://serverfault.com/questions/609881/windows-server-2012-on-kvm-on- ubuntu-14-04-runs-well-for-a-while-and-then-slows/612084#612084 Basically all kind of KVM guests are getting slow by time, both windows or linux. The more running guests, it happens sooner. Switching back to Saucy kernel is a good workaround. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-kvm 2.0.0+dfsg-2ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Sat Jul 12 22:18:49 2014 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1341195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338277] Re: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD)
*** This bug is a duplicate of bug 1346917 *** https://bugs.launchpad.net/bugs/1346917 ** This bug has been marked a duplicate of bug 1346917 Using KSM on NUMA capable machines can cause KVM guest performance and stability issues -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0DFXXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0DFXXD:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338277] Re: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD)
Guys, The following patch http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=64a9a34e22896dad430e21a28ad8cb00a756fefc fixed the problem! -- Lab env: 1 R610 with 24G RAM 6 Windows 2008 R2 guests, 6G RAM each (min 4G - max 6G) ~17G of RAM memory being shared by KSM... YAY!!:-) * All Windows guests are stable for about ~17 hours * -- Accounting of RAM saved by KSM (ksmstat - shell script): https://gist.github.com/wankdanker/1206923 No signs of instability. Nice job!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0DFXXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0DFXXD:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sour
[Kernel-packages] [Bug 1338277] Re: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD)
Warner, I installed a new Dell R610 server ~6 hours ago, with Trusty's default kernel, to see Windows crashing again (and it crashed after ~3 hours of uptime - KSM=1). Now, I just installed (from: http://people.canonical.com/~arges/lp1346917/): -- linux-headers-3.13.0-33_3.13.0-33.58~lp1346917v201407220903_all.deb linux-image-3.13.0-33-generic_3.13.0-33.58~lp1346917v201407220903_amd64.deb linux-headers-3.13.0-33-generic_3.13.0-33.58~lp1346917v201407220903_amd64.deb linux-image-extra-3.13.0-33-generic_3.13.0-33.58~lp1346917v201407220903_amd64.deb -- I'll let it running this all night, if tomorrow morning the Windows guests are still alive (uptime higher than ~10 hours), I'll mark it as "duplicated of 1346917 / fixed". Thank you my friend! :-D -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0DFXXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc
[Kernel-packages] [Bug 1338277] Re: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD)
Okay, I'll try it today! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0DFXXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0DFXXD:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338277] Re: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD)
Hi Serge, At first, yes, I was trying with VirtIO. Later, I disabled VirtIO for Disk, didn't solve. Then, I disabled VirtIO for Net, didn't solve. Again, I disabled VirtIO for both Disk and Net, didn't solve. But, thinking on it again now, I did not tested it with a Windows 2008 R2 that did not touched VirtIO drivers, I mean, in all of my tests, I was using at least, the ballon RAM driver (and probable VirtIO Serial, or something like that). Next week, I'll try it with again, without any VirtIO, from the beginning, with KSM=1. Best, Thiago -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0DFXXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0DFXXD:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.v
[Kernel-packages] [Bug 1338277] Re: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD)
Just for the record... The Windows 2008 R2 (and Windows 7) guests are all 64-bit, with 4G of RAM each. I'm trying it using VirtIO for both Disk and Network, configured during Windows installation (the second Virtual CD Drive contains: http://alt.fedoraproject.org/pub/alt/virtio-win/latest/virtio- win-0.1-81.iso ) Even when IDLE, W2K8-R2 crashes and, for example, if you try to install it as a Secondary Active Directory of another Windows, then, it crashes more often... I'm using SPICE / QXL for guest video. Anyway, I tried it with almost all virtual hardware combinations, starting from VirtIO devices, to IDE and e1000, VGA and etc... Every time it crashes. Also, VirtIO for Network is very unstable, both Windows 7 and Windows 2008 crashes when using it with OpenvSwitch bridges, when using that "default NAT from libvirt", it works better, so, I'm using e1000 from now on. Disabling KSM make it far more stable but, as I said, VirtIO for Net is still unstable (it gives windows BSOD). If you guys want (Serge), I can give root access to 1 or 2 Dell R610 with Ubuntu 14.04 + Qemu 2.0, so, you guys will be able to catch this problem while it happens... Since this problem is hard to reproduce, I'm available to help debug this, just let me know. BTW, I'm planning to try it with new QEmu 2.1 ASAP and/or with new Linux 3.16, on different servers, to see which one becomes more stable... Honestly, I don't know where the problem is located, I mean, it this a Linux or QEmu BUG?! Cheers! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMA
[Kernel-packages] [Bug 1338277] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1338277/+attachment/4153183/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0DFXXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0DFXXD:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338277] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1338277/+attachment/4153186/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0DFXXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0DFXXD:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338277] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1338277/+attachment/4153189/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0DFXXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0DFXXD:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338277] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1338277/+attachment/4153185/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0DFXXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0DFXXD:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1338277] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1338277/+attachment/4153190/+files/WifiSyslog.txt ** Changed in: qemu (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0DFXXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0DFXXD:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net
[Kernel-packages] [Bug 1338277] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1338277/+attachment/4153188/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1338277 Title: Ubuntu 14.04 + QEmu 2.0 + KSM = 1, makes Windows 2008 R2 guests to crash (BSOD) Status in “linux” package in Ubuntu: Confirmed Status in “qemu” package in Ubuntu: Confirmed Bug description: Guys, I'm trying to run Windows 2008 as a QEmu guest on my Ubuntu 14.04 but, after lots of tests, I figured out that it doesn't work, QEmu makes Windows 2008 to crash, and it is not a Windows fault, I'm pretty sure that it is a QEmu bug. Lab environment (5 servers): 3 physical servers: Dell R610 2 physycal servers: IBM x3650 * Where Windows crash (5 servers tested) ? Ubuntu 14.04 + QEmu 2.0 + VirtIO 0.1-81 = Windows 2008 crash every hour - Installed with "apt-get install ubuntu-virt-server". * Where Windows do not crash (5 servers tested) ? Ubuntu 14.04 + Xen 4.4 + gplpv_Vista2008x64_1.0.1092.9 = Windows working smoothly - Installed with "apt-get install xen-system-amd64". So, after removing QEmu from my environment, and using Xen instead, all Windows guests are now running without any crash. What kind of information, can I provide for you guys, to deep debug this QEmu problem ? Plus, it is interesting to note that a lot of times, all Windows guests (on top of QEmu / KVM) crashes at the exactly the same time! So, it can not be a problem within each Windows guest, but at the Hypervisor itself! Something happen there, that affects almost all Windows guests simultaneously. Also, it worth to mention that this problem is probably affecting clouds based on OpenStack IceHouse, on top of Ubuntu + QEmu 2.0... Screenshots: http://i.imgur.com/vnJSTgg.png http://i.imgur.com/34nADWr.png NOTE: I'm using KSM (Kernel Samepage Merging) with QEmu, to save RAM. It seems that when with Xen (+QEmu / HVM), KSM is not used :'( , but it is enabled ( 1 > /sys/kernel/mm/ksm/run at Dom0's kernel). I did not tried to disable KSM to see if Windows becomes more stable on QEmu 2.0... Also, I did not run tests on this environment with Ubuntu 12.04.4 (or 12.04.4 with Ubuntu Cloud Archives, to get newer versions of QEmu (but not 2.0) for old LTS). CURIOSITY: On older hardware, like Dell R1950, and at my old Intel Desktop Core i7, I'm running Windows 2008 and 7, on Ubuntu 14.04 with QEmu 2.0 without any crash... I really like to figure out why QEmu is crashing Windows guests on Dell R610 and on IBM x3650... Attaching the VM's configuration files on next posts... Best, Thiago --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 15 08:32 seq crw-rw 1 root audio 116, 33 Jul 15 08:32 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-06-23 (22 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: Error: [Errno 2] No such file or directory MachineType: Dell Inc. PowerEdge R610 Package: qemu PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=6a76ba24-a056-468d-b620-84a49c71d873 ro ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 6.4.0 dmi.board.name: 0DFXXD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr6.4.0:bd07/23/2013:svnDellInc.:pnPowerEdgeR610:pvr:rvnDellInc.:rn0DFXXD:rvrA00:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
