[Kernel-packages] [Bug 1420544] Re: [SRU] Ubuntu instances on GCE should use NOOP scheduler
** Changed in: linux (Ubuntu) Assignee: Ben Howard (utlemming) => (unassigned) -- 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/1420544 Title: [SRU] Ubuntu instances on GCE should use NOOP scheduler Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in systemd source package in Trusty: Fix Released Bug description: [IMPACT] By default, the Ubuntu kernel uses deadline. Google has identified that Cloud Workloads running on Ubuntu perform better using NOOP as the default scheduler. Google has requested that Google Cloud Compute (GCE) instances use NOOP as the default. [FIX] Add udev rule for GCE devices to use NOOP by default. [VALIDATION] 1. Boot Ubuntu instance on Google GCE 2. Confirm that the scheduler is deadline: $ cat /sys/block/sda/queue/scheduler noop [deadline] cfq 3. Install proposed udev package 4. Reboot 5. Confirm that schedule is now noop $ cat /sys/block/sda/queue/scheduler [noop] deadline cfq [RISK] This patch will affect currently running instances and on reboot they should see better performance. However, there is a risk that some users will experience a performance hit. [ORIGINAL REPORT] Per Google's request, Ubuntu instances should use NOOP as the default scheduler. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420544/+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 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
** Package changed: linux (Ubuntu) => cloud-init (Ubuntu) -- 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/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in cloud-init package in Ubuntu: Confirmed Bug description: On Azure, cloud-init relies on the system-uuid as based by SMBIOS a unique ID for a cloud instance. If this ID ever changes, then cloud- init will attempt to reprovision the VM. This recent kernel patch in the Ubuntu kernel corrects the endianness for some SMBIOS fields, but also has the effect causing cloud-init to think that the system-uuid has changed: http://kernel.ubuntu.com/git/ubuntu/ubuntu- trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1551419/+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 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
Raising to critical as this breaks Azure users. ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- 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/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in linux package in Ubuntu: Confirmed Bug description: On Azure, cloud-init relies on the system-uuid as based by SMBIOS a unique ID for a cloud instance. If this ID ever changes, then cloud- init will attempt to reprovision the VM. This recent kernel patch in the Ubuntu kernel corrects the endianness for some SMBIOS fields, but also has the effect causing cloud-init to think that the system-uuid has changed: http://kernel.ubuntu.com/git/ubuntu/ubuntu- trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551419/+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 1551419] Re: Fix UUID endianness patch breaks cloud-init on Azure
Stephen, can you please tell us what the affected kernel versions are? -- 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/1551419 Title: Fix UUID endianness patch breaks cloud-init on Azure Status in linux package in Ubuntu: Confirmed Bug description: On Azure, cloud-init relies on the system-uuid as based by SMBIOS a unique ID for a cloud instance. If this ID ever changes, then cloud- init will attempt to reprovision the VM. This recent kernel patch in the Ubuntu kernel corrects the endianness for some SMBIOS fields, but also has the effect causing cloud-init to think that the system-uuid has changed: http://kernel.ubuntu.com/git/ubuntu/ubuntu- trusty.git/commit/drivers/firmware?id=3ec24c55be6c543797ba3ee9a227a5631aef607e The impact is that cloud-init attempts to reprovision the VM, often causing the customer to lose access to their VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551419/+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 1544798] Re: high load with on 4.2.x+ kernels for Intel Mobile processors
Dropping this bug. After upgrading to Xenial, I found that the 4.4 kernel from the archives has reasonable load. The issue is only seen with mainline kernels. ** Changed in: linux (Ubuntu) Status: Triaged => 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/1544798 Title: high load with on 4.2.x+ kernels for Intel Mobile processors Status in linux package in Ubuntu: Invalid Bug description: Running the mainline kernel builds, I'm seeing high load averages for my Intel Mobile processor. When I revert back to the 4.2 kernel, the load goes back down. (Reason for using the 4.5 kernel is because the Intel i915 Graphics driver crashes/freezes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1544798/+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 1544798] Re: high load with on 4.2.x+ kernels for Intel Mobile processors
The 4.2.0-x kernels are being installed via apt. Where the 4.2.x was installed from the mainline kernel ppa. The last 4.2.x kernel that I tested was at http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.4-wily/ -- 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/1544798 Title: high load with on 4.2.x+ kernels for Intel Mobile processors Status in linux package in Ubuntu: Triaged Bug description: Running the mainline kernel builds, I'm seeing high load averages for my Intel Mobile processor. When I revert back to the 4.2 kernel, the load goes back down. (Reason for using the 4.5 kernel is because the Intel i915 Graphics driver crashes/freezes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1544798/+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 1544798] Re: high load with on 4.2.x+ kernels for Intel Mobile processors
Actually, for the 4.2.0-x kernels, the load is fine; it is with 4.2.x-wily kernels where I saw the high load. I tested the 4.2.4-wily kernel and hit the issue, but did not test the others as they were marked as "unstable." -- 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/1544798 Title: high load with on 4.2.x+ kernels for Intel Mobile processors Status in linux package in Ubuntu: Triaged Bug description: Running the mainline kernel builds, I'm seeing high load averages for my Intel Mobile processor. When I revert back to the 4.2 kernel, the load goes back down. (Reason for using the 4.5 kernel is because the Intel i915 Graphics driver crashes/freezes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1544798/+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 1544798] Re: high load with on 4.2.x+ kernels for Intel Mobile processors
After testing every kernel under the sun, I found that 4.2.0.x kernels appear to the last ones with normal idle load. I tested all the 4.2, 4.3 and 4.4 kernels marked "-wily" and found that they all had the increased load. I didn't test any of hte unstable ones. The load averages are, however, more pronounced on 4.3 than 4.2. For example, I'm seeing 1.4 to 2.2 for the 4.2 kernel, and then it jumps for to 2.1 to 2.6 for the 4.(3,4,5) kernels. ** Summary changed: - high load with 4.4 and 4.5 kernels for Intel Mobile processors + high load with on 4.2.x+ kernels for Intel Mobile processors -- 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/1544798 Title: high load with on 4.2.x+ kernels for Intel Mobile processors Status in linux package in Ubuntu: Triaged Bug description: Running the mainline kernel builds, I'm seeing high load averages for my Intel Mobile processor. When I revert back to the 4.2 kernel, the load goes back down. (Reason for using the 4.5 kernel is because the Intel i915 Graphics driver crashes/freezes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1544798/+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 1544798] Re: high load with 4.4 and 4.5 kernels for Intel Mobile processors
CPU details $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 61 model name : Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz stepping: 4 microcode : 0x1d cpu MHz : 1198.804 cache size : 4096 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 20 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt dtherm ida arat pln pts bugs: bogomips: 2793.50 clflush size: 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: -- 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/1544798 Title: high load with 4.4 and 4.5 kernels for Intel Mobile processors Status in linux package in Ubuntu: Incomplete Bug description: Running the mainline kernel builds, I'm seeing high load averages for my Intel Mobile processor. When I revert back to the 4.2 kernel, the load goes back down. (Reason for using the 4.5 kernel is because the Intel i915 Graphics driver crashes/freezes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1544798/+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 1544798] Re: high load with 4.4 and 4.5 kernels for Intel Mobile processors
Load average is: 1.25, 1.34, 1.41 running Thunderbird, IRC and chrome. Under 4.2, those averages drop between 0.15 and 0.4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1544798 Title: high load with 4.4 and 4.5 kernels for Intel Mobile processors Status in linux package in Ubuntu: Incomplete Bug description: Running the mainline kernel builds, I'm seeing high load averages for my Intel Mobile processor. When I revert back to the 4.2 kernel, the load goes back down. (Reason for using the 4.5 kernel is because the Intel i915 Graphics driver crashes/freezes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1544798/+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 1544798] [NEW] high load with 4.4 and 4.5 kernels for Intel Mobile processors
Public bug reported: Running the mainline kernel builds, I'm seeing high load averages for my Intel Mobile processor. When I revert back to the 4.2 kernel, the load goes back down. (Reason for using the 4.5 kernel is because the Intel i915 Graphics driver crashes/freezes). ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: kernel-da-key xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1544798 Title: high load with 4.4 and 4.5 kernels for Intel Mobile processors Status in linux package in Ubuntu: Incomplete Bug description: Running the mainline kernel builds, I'm seeing high load averages for my Intel Mobile processor. When I revert back to the 4.2 kernel, the load goes back down. (Reason for using the 4.5 kernel is because the Intel i915 Graphics driver crashes/freezes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1544798/+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 1538379] [NEW] zfs dkms module attempts to build before spl
Public bug reported: This looks like Bug #1491729: Steps to Repo: 1. Start clean Wily instance 2. Run "sudo apt-get install zfs-dkms" $ sudo apt-get install zfs-dkms Selecting previously unselected package libisl13:amd64. (Reading database ... 62785 files and directories currently installed.) Preparing to unpack .../libisl13_0.14-2_amd64.deb ... Unpacking libisl13:amd64 (0.14-2) ... Selecting previously unselected package libmpc3:amd64. Preparing to unpack .../libmpc3_1.0.3-1_amd64.deb ... Unpacking libmpc3:amd64 (1.0.3-1) ... Selecting previously unselected package cpp-5. Preparing to unpack .../cpp-5_5.2.1-22ubuntu2_amd64.deb ... Unpacking cpp-5 (5.2.1-22ubuntu2) ... Selecting previously unselected package cpp. Preparing to unpack .../cpp_4%3a5.2.1-3ubuntu1_amd64.deb ... Unpacking cpp (4:5.2.1-3ubuntu1) ... Selecting previously unselected package libcc1-0:amd64. Preparing to unpack .../libcc1-0_5.2.1-22ubuntu2_amd64.deb ... Unpacking libcc1-0:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package binutils. Preparing to unpack .../binutils_2.25.1-6ubuntu2_amd64.deb ... Unpacking binutils (2.25.1-6ubuntu2) ... Selecting previously unselected package libgomp1:amd64. Preparing to unpack .../libgomp1_5.2.1-22ubuntu2_amd64.deb ... Unpacking libgomp1:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package libitm1:amd64. Preparing to unpack .../libitm1_5.2.1-22ubuntu2_amd64.deb ... Unpacking libitm1:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package libatomic1:amd64. Preparing to unpack .../libatomic1_5.2.1-22ubuntu2_amd64.deb ... Unpacking libatomic1:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package libasan2:amd64. Preparing to unpack .../libasan2_5.2.1-22ubuntu2_amd64.deb ... Unpacking libasan2:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package liblsan0:amd64. Preparing to unpack .../liblsan0_5.2.1-22ubuntu2_amd64.deb ... Unpacking liblsan0:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package libtsan0:amd64. Preparing to unpack .../libtsan0_5.2.1-22ubuntu2_amd64.deb ... Unpacking libtsan0:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package libubsan0:amd64. Preparing to unpack .../libubsan0_5.2.1-22ubuntu2_amd64.deb ... Unpacking libubsan0:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package libcilkrts5:amd64. Preparing to unpack .../libcilkrts5_5.2.1-22ubuntu2_amd64.deb ... Unpacking libcilkrts5:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package libmpx0:amd64. Preparing to unpack .../libmpx0_5.2.1-22ubuntu2_amd64.deb ... Unpacking libmpx0:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package libquadmath0:amd64. Preparing to unpack .../libquadmath0_5.2.1-22ubuntu2_amd64.deb ... Unpacking libquadmath0:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package libgcc-5-dev:amd64. Preparing to unpack .../libgcc-5-dev_5.2.1-22ubuntu2_amd64.deb ... Unpacking libgcc-5-dev:amd64 (5.2.1-22ubuntu2) ... Selecting previously unselected package gcc-5. Preparing to unpack .../gcc-5_5.2.1-22ubuntu2_amd64.deb ... Unpacking gcc-5 (5.2.1-22ubuntu2) ... Selecting previously unselected package gcc. Preparing to unpack .../gcc_4%3a5.2.1-3ubuntu1_amd64.deb ... Unpacking gcc (4:5.2.1-3ubuntu1) ... Selecting previously unselected package make. Preparing to unpack .../make_4.0-8.2_amd64.deb ... Unpacking make (4.0-8.2) ... Selecting previously unselected package dkms. Preparing to unpack .../dkms_2.2.0.3-2ubuntu6.1_all.deb ... Unpacking dkms (2.2.0.3-2ubuntu6.1) ... Selecting previously unselected package spl-dkms. Preparing to unpack .../spl-dkms_0.6.4.2-0ubuntu1_amd64.deb ... Unpacking spl-dkms (0.6.4.2-0ubuntu1) ... Processing triggers for man-db (2.7.4-1) ... Setting up libisl13:amd64 (0.14-2) ... Setting up libmpc3:amd64 (1.0.3-1) ... Setting up cpp-5 (5.2.1-22ubuntu2) ... Setting up cpp (4:5.2.1-3ubuntu1) ... Setting up libcc1-0:amd64 (5.2.1-22ubuntu2) ... Setting up binutils (2.25.1-6ubuntu2) ... Setting up libgomp1:amd64 (5.2.1-22ubuntu2) ... Setting up libitm1:amd64 (5.2.1-22ubuntu2) ... Setting up libatomic1:amd64 (5.2.1-22ubuntu2) ... Setting up libasan2:amd64 (5.2.1-22ubuntu2) ... Setting up liblsan0:amd64 (5.2.1-22ubuntu2) ... Setting up libtsan0:amd64 (5.2.1-22ubuntu2) ... Setting up libubsan0:amd64 (5.2.1-22ubuntu2) ... Setting up libcilkrts5:amd64 (5.2.1-22ubuntu2) ... Setting up libmpx0:amd64 (5.2.1-22ubuntu2) ... Setting up libquadmath0:amd64 (5.2.1-22ubuntu2) ... Setting up libgcc-5-dev:amd64 (5.2.1-22ubuntu2) ... Setting up gcc-5 (5.2.1-22ubuntu2) ... Setting up gcc (4:5.2.1-3ubuntu1) ... Setting up make (4.0-8.2) ... Setting up dkms (2.2.0.3-2ubuntu6.1) ... Setting up spl-dkms (0.6.4.2-0ubuntu1) ... Loading new spl-0.6.4.2 DKMS files... First Installation: checking all kernels... Building only for 4.2.0-25-generic Building initial module for 4.2.0-25-generic configure: error: in `/var/lib/dkms/spl/0.6.4.2/build': configure: error: C compiler cannot
[Kernel-packages] [Bug 613022] Re: ssh daemon hangs after publickey packet sent
Closing this out as crufty. If this is seen again, please reopen. ** Changed in: openssh (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/613022 Title: ssh daemon hangs after publickey packet sent Status in cloud-init package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in openssh package in Ubuntu: Invalid Bug description: A launched ec2 instance in ap-southeast-1 region is unreachable via ssh. $ ssh -vvv ec2-175-41-171-225.ap-southeast-1.compute.amazonaws.com shows progress up to : debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering public key: smoser@brickies debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply Then nothing for minutes before session is killed (manually). In a 'good' connection, the following would be next: debug2: we sent a publickey packet, wait for reply debug1: Authentications that can continue: publickey I'll attach full 'ssh -vvv' logs good and bad connection. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: openssh-server 1:5.5p1-4ubuntu3 ProcVersionSignature: User Name 2.6.35-14.19-virtual 2.6.35 Uname: Linux 2.6.35-14-virtual x86_64 Architecture: amd64 Date: Tue Aug 3 14:45:25 2010 Ec2AMI: ami-9fc4bbcd Ec2AMIManifest: ubuntu-images-testing-ap-southeast-1/ubuntu-maverick-daily-amd64-server-20100803.1.manifest.xml Ec2AvailabilityZone: ap-southeast-1a Ec2InstanceType: m1.large Ec2Kernel: aki-11d5aa43 Ec2Ramdisk: unavailable ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/613022/+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 1477171] Re: Enable intel_pstate by default on Trusty EC2 AMIs
** Project changed: ubuntu-on-ec2 = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1477171 Title: Enable intel_pstate by default on Trusty EC2 AMIs Status in linux-meta package in Ubuntu: New Bug description: Please can the intel_pstate driver be enabled by default on the Ubuntu EC2 AMIs. On instances with support for C-states and P-States [1] there is a notable performance impact and lack of support for higher clock frequencies available due to the use of the acpi-cpufreq driver. For example on a c4.8xlarge the default frequency is limited to 2.9GHz when 3.2GHz is supported by the chip [2]. Some additional analysis is available here [3] and re-enabling it by default has been discussed [4] but this request is specifically for the EC2 AMIs. [1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/processor_state_control.html [2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/c4-instances.html [3] http://www.deplication.net/2015/07/c-states-and-p-states-with-ubuntu-1404.html [4] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647 AMI: ami-47a23a30 (eu-west-1) $ lsb_release -d Description:Ubuntu 14.04.2 LTS $ uname -a Linux ip-172-31-8-218 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Default configuration (c4.8xl): $ sudo cpupower frequency-info analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.20 GHz - 2.90 GHz available frequency steps: 2.90 GHz, 2.90 GHz, 2.80 GHz, 2.70 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.20 GHz and 2.90 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.20 GHz (asserted by call to hardware). cpufreq stats: 2.90 GHz:70.40%, 2.90 GHz:0.00%, 2.80 GHz:0.00%, 2.70 GHz:0.00%, 2.50 GHz:0.00%, 2.40 GHz:0.00%, 2.30 GHz:0.00%, 2.20 GHz:0.00%, 2.00 GHz:0.00%, 1.90 GHz:0.00%, 1.80 GHz:0.00%, 1.70 GHz:0.00%, 1.60 GHz:0.09%, 1.40 GHz:0.00%, 1.30 GHz:0.00%, 1.20 GHz:29.51% (5) boost state support: Supported: yes Active: yes With intel_pstate enabled (c4.8xl): $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 1.20 GHz - 3.50 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.20 GHz and 3.50 GHz. The governor performance may decide which speed to use within this range. current CPU frequency is 3.20 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1477171/+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 1411294] Re: kernel panic during MAAS fastpath install of Vivid images
I am manually hand-holding a build through for the latest kernel CVE. Image builds and promotion are in the works. ETA tomorrow morning. -- 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/1411294 Title: kernel panic during MAAS fastpath install of Vivid images Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in cloud-initramfs-tools source package in Trusty: Fix Released Status in linux source package in Trusty: Invalid Status in cloud-initramfs-tools source package in Utopic: Fix Released Status in linux source package in Utopic: New Bug description: [Impact] overlayfs support doesn't work with kernels 3.18 which will, for example, break MAAS commissioning/deploying using trusty+hwe-v (when it exists). [Test Case] Create custom trusty image using the vivid kernel and attempt to commission a node with MAAS using that image. [Regression Potential] If the kernel detection code is buggy, it could regress functionality on older kernels (e.g. 3.13/3.16). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1411294/+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 1311070] Re: hyper-v:IP Injection on Ubuntu 13.10 guest during Failover and Test Failover is corrupting the existing entries
This bug is a targeted at 13.10, which reached EOL on 17 July 2014 and is therefore invalid. If this bug exists on 14.04 or later, please refile. ** 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/1311070 Title: hyper-v:IP Injection on Ubuntu 13.10 guest during Failover and Test Failover is corrupting the existing entries Status in linux package in Ubuntu: Invalid Bug description: [HyperV Replica :: http://technet.microsoft.com/en-us/library/jj134172.aspx] [Guest IP Injection :: http://blogs.technet.com/b/virtualization/archive/2012/05/29/inject-ip-address-into-the-vm-during-failover.aspx] hv_set_ifconfig script is corrupting the last entry inside /etc/network/interfaces. It is creating 2 entries for eth1 Leading to failure of IP Injection. 1) Create Ubuntu 13.10 virtual machine. 2) Attach network adapters 'Network Adapter' and 'Adapter2' on primary and configured via DHCP. cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet dhcp 3) Enable Replication. 4) Set Failover IP settings on second adapter (Adapter2) Set-VMNetworkAdapterFailoverConfiguration -ComputerName $computerName -VMName $vmname -IPv4Address 192.168.100.10 -IPv4SubnetMask 255.255.0.0 -IPv4PreferredDNSServer 192.168.100.101 -IPv4AlternateDNSServer 192.168.100.102 -IPv4DefaultGateway 192.168.100.1 -VMNetworkAdapterName 'Adapter2' 5) Do Failover cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp iface eth1 inet dhcp # The following stanza(s) added by hv_set_ifconfig auto eth1 iface eth1 inet static address 192.168.100.10 netmask 255.255.0.0 gateway 192.168.100.1 dns-nameservers 192.168.100.101 192.168.100.102 #End of hv_set_ifconfig stanzas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311070/+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 1447751] [NEW] CPU: 0 PID: 2802 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:1256 assert_plane.constprop.87+0x7b/0x90 [i915]()
Public bug reported: [ 396.209024] [ cut here ] [ 396.209071] WARNING: CPU: 0 PID: 2802 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:1256 assert_plane.constprop.87+0x7b/0x90 [i915]() [ 396.209072] plane A assertion failure (expected on, current off) [ 396.209103] Modules linked in: veth xt_conntrack ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) ip6table_filter ip6_tables binfmt_misc vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp iptable_filter ip_tables x_tables bridge stp llc joydev intel_rapl snd_hda_codec_realtek iosf_mbi snd_hda_codec_generic x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp hid_logitech_hidpp coretemp snd_hda_intel kvm_intel snd_soc_rt5640 snd_hda_controller snd_soc_rl6231 kvm snd_soc_core snd_hda_codec snd_compress snd_hwdep snd_pcm_dmaengine dm_multipath scsi_dh snd_pcm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_seq_midi snd_seq_midi_event [ 396.209130] snd_rawmidi aesni_intel i915 aes_x86_64 lrw gf128mul drm_kms_helper glue_helper snd_seq ablk_helper cryptd snd_seq_device snd_timer drm snd i2c_algo_bit mei_me lpc_ich mei soundcore mac_hid nuvoton_cir dw_dmac rc_core 8250_dw i2c_hid dw_dmac_core i2c_designware_platform video i2c_designware_core snd_soc_sst_acpi spi_pxa2xx_platform hid_generic parport_pc ppdev lp parport autofs4 hid_logitech_dj usbhid hid btrfs xor raid6_pq e1000e ptp pps_core ahci libahci sdhci_acpi sdhci [last unloaded: vmw_vmci] [ 396.209134] CPU: 0 PID: 2802 Comm: Xorg Tainted: G OE 3.19.0-15-generic #15-Ubuntu [ 396.209135] Hardware name: /D54250WYK, BIOS WYLPT10H.86A.0035.2015.0126.1814 01/26/2015 [ 396.209138] c0758e10 8803fbd0b728 817c2205 8afa8afa [ 396.209140] 8803fbd0b778 8803fbd0b768 8107595a [ 396.209142] 8800c87ec000 8800c9417000 8800c9417000 [ 396.209143] Call Trace: [ 396.209152] [817c2205] dump_stack+0x45/0x57 [ 396.209156] [8107595a] warn_slowpath_common+0x8a/0xc0 [ 396.209159] [810759d6] warn_slowpath_fmt+0x46/0x50 [ 396.209188] [c06f552b] assert_plane.constprop.87+0x7b/0x90 [i915] [ 396.209213] [c06fd6a1] hsw_disable_ips+0x41/0x190 [i915] [ 396.209235] [c06fda68] intel_crtc_disable_planes+0x48/0x140 [i915] [ 396.209255] [c06fe7cf] haswell_crtc_disable+0x4f/0x3c0 [i915] [ 396.209281] [c06ff769] __intel_set_mode+0xa59/0xc80 [i915] [ 396.209309] [c070633b] intel_crtc_set_config+0xbfb/0xf70 [i915] [ 396.209331] [c05c9e36] drm_mode_set_config_internal+0x66/0x100 [drm] [ 396.209343] [c0675d18] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] [ 396.209354] [c0677d89] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x80 [drm_kms_helper] [ 396.209365] [c0677e02] drm_fb_helper_set_par+0x22/0x50 [drm_kms_helper] [ 396.209391] [c071229a] intel_fbdev_set_par+0x1a/0x60 [i915] [ 396.209395] [814339da] fb_set_var+0x18a/0x410 [ 396.209426] [c03e6aad] ? btrfs_get_token_32+0x5d/0x120 [btrfs] [ 396.209430] [8142a409] fbcon_blank+0x229/0x300 [ 396.209456] [c03f12a3] ? free_extent_buffer+0x53/0xb0 [btrfs] [ 396.209461] [814ba03a] do_unblank_screen+0xba/0x1f0 [ 396.209467] [814b0faa] vt_ioctl+0x13ea/0x1460 [ 396.209472] [814a2df1] tty_ioctl+0x411/0xcb0 [ 396.209477] [8119cf21] ? kzfree+0x31/0x40 [ 396.209482] [811d476e] ? kfree+0x13e/0x150 [ 396.209485] [8120b4ca] ? dput+0x2a/0x1c0 [ 396.209488] [81207b40] do_vfs_ioctl+0x2e0/0x4e0 [ 396.209492] [811f514e] ? fput+0xe/0x10 [ 396.209496] [81092d0c] ? task_work_run+0xbc/0xf0 [ 396.209498] [81207dc1] SyS_ioctl+0x81/0xa0 [ 396.209503] [817c934d] system_call_fastpath+0x16/0x1b [ 396.209504] ---[ end trace fe3c0fa6d5597c72 ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Package changed: ubuntu = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1447751 Title: CPU: 0 PID: 2802 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:1256 assert_plane.constprop.87+0x7b/0x90 [i915]() Status in linux package in Ubuntu: Incomplete Bug description: [ 396.209024] [ cut here ] [ 396.209071] WARNING: CPU: 0 PID: 2802 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:1256 assert_plane.constprop.87+0x7b/0x90 [i915]() [ 396.209072] plane A assertion failure (expected on, current off) [ 396.209103] Modules linked in:
[Kernel-packages] [Bug 1420544] Re: [SRU] Ubuntu instances on GCE should use NOOP scheduler
Confirmed -proposed. Marking as validation-done. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1420544 Title: [SRU] Ubuntu instances on GCE should use NOOP scheduler Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Trusty: Fix Committed Bug description: [IMPACT] By default, the Ubuntu kernel uses deadline. Google has identified that Cloud Workloads running on Ubuntu perform better using NOOP as the default scheduler. Google has requested that Google Cloud Compute (GCE) instances use NOOP as the default. [FIX] Add udev rule for GCE devices to use NOOP by default. [VALIDATION] 1. Boot Ubuntu instance on Google GCE 2. Confirm that the scheduler is deadline: $ cat /sys/block/sda/queue/scheduler noop [deadline] cfq 3. Install proposed udev package 4. Reboot 5. Confirm that schedule is now noop $ cat /sys/block/sda/queue/scheduler [noop] deadline cfq [RISK] This patch will affect currently running instances and on reboot they should see better performance. However, there is a risk that some users will experience a performance hit. [ORIGINAL REPORT] Per Google's request, Ubuntu instances should use NOOP as the default scheduler. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420544/+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 1420544] Re: [SRU] Ubuntu instances on GCE should use NOOP scheduler
** Summary changed: - Ubuntu instances on GCE should use NOOP scheduler + [SRU] Ubuntu instances on GCE should use NOOP scheduler -- 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/1420544 Title: [SRU] Ubuntu instances on GCE should use NOOP scheduler Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Trusty: In Progress Bug description: Per Google's request, Ubuntu instances should use NOOP as the default scheduler. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420544/+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 1420544] Re: [SRU] Ubuntu instances on GCE should use NOOP scheduler
Sorry about missing the SRU info. Added. -- 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/1420544 Title: [SRU] Ubuntu instances on GCE should use NOOP scheduler Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Trusty: In Progress Bug description: [IMPACT] By default, the Ubuntu kernel uses deadline. Google has identified that Cloud Workloads running on Ubuntu perform better using NOOP as the default scheduler. Google has requested that Google Cloud Compute (GCE) instances use NOOP as the default. [FIX] Add udev rule for GCE devices to use NOOP by default. [VALIDATION] 1. Boot Ubuntu instance on Google GCE 2. Confirm that the scheduler is deadline: $ cat /sys/block/sda/queue/scheduler noop [deadline] cfq 3. Install proposed udev package 4. Reboot 5. Confirm that schedule is now noop $ cat /sys/block/sda/queue/scheduler [noop] deadline cfq [RISK] This patch will affect currently running instances and on reboot they should see better performance. However, there is a risk that some users will experience a performance hit. [ORIGINAL REPORT] Per Google's request, Ubuntu instances should use NOOP as the default scheduler. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420544/+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 1400947] Re: Upstream bugfixes for hv_vmbus
For the Microsoft Azure images, we are going to switch images over to the HWE Kernel for precise, which has the fixes. We will provide instructions for existing users on how to upgrade to the HWE kernel. HWE kernel for Microsoft Azure is currently undergoing QA. -- 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/1400947 Title: Upstream bugfixes for hv_vmbus Status in linux package in Ubuntu: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux source package in Utopic: Fix Released Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux source package in Vivid: Fix Released Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Bug description: Please take these upstream patches for the Hyper-V VMBus driver. In some cases we are seeing crashes due to these bugs on Hyper-V and Azure. commit 72c6b71c245dac8f371167d97ef471b367d0b66b Author: K. Y. Srinivasan k...@microsoft.com Date: Wed Aug 27 16:25:34 2014 -0700 Drivers: hv: vmbus: Cleanup vmbus_establish_gpadl() commit b29ef3546aecb253a5552b198cef23750d56e1e4 Author: K. Y. Srinivasan k...@microsoft.com Date: Thu Aug 28 18:29:52 2014 -0700 Drivers: hv: vmbus: Cleanup hv_post_message() commit 98d731bb064a9d1817a6ca9bf8b97051334a7cfe Author: K. Y. Srinivasan k...@microsoft.com Date: Wed Aug 27 16:25:33 2014 -0700 Drivers: hv: vmbus: Cleanup vmbus_close_internal() commit 45d727cee9e200f5b351528b9fb063b69cf702c8 Author: K. Y. Srinivasan k...@microsoft.com Date: Wed Aug 27 16:25:35 2014 -0700 Drivers: hv: vmbus: Fix a bug in vmbus_open() commit 66be653083057358724d56d817e870e53fb81ca7 Author: K. Y. Srinivasan k...@microsoft.com Date: Wed Aug 27 16:25:32 2014 -0700 Drivers: hv: vmbus: Cleanup vmbus_teardown_gpadl() commit fdeebcc62279119dbeafbc1a2e39e773839025fd Author: K. Y. Srinivasan k...@microsoft.com Date: Wed Aug 27 16:25:31 2014 -0700 Drivers: hv: vmbus: Cleanup vmbus_post_msg() === break-fix: - 72c6b71c245dac8f371167d97ef471b367d0b66b break-fix: - b29ef3546aecb253a5552b198cef23750d56e1e4 break-fix: - 98d731bb064a9d1817a6ca9bf8b97051334a7cfe break-fix: - 45d727cee9e200f5b351528b9fb063b69cf702c8 break-fix: - 66be653083057358724d56d817e870e53fb81ca7 break-fix: - fdeebcc62279119dbeafbc1a2e39e773839025fd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400947/+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 1415580] Re: add nvme to -virtual kernel
Here is what the devices look like: ben@nvmetest2:~$ sudo udevadm info /dev/nvme0 P: /devices/pci:00/:00:04.0/misc/nvme0 N: nvme0 E: DEVNAME=/dev/nvme0 E: DEVPATH=/devices/pci:00/:00:04.0/misc/nvme0 E: MAJOR=10 E: MINOR=57 E: SUBSYSTEM=misc ben@nvmetest2:~$ sudo udevadm info /dev/nvme0n1 P: /devices/pci:00/:00:04.0/block/nvme0n1 N: nvme0n1 E: DEVNAME=/dev/nvme0n1 E: DEVPATH=/devices/pci:00/:00:04.0/block/nvme0n1 E: DEVTYPE=disk E: MAJOR=259 E: MINOR=0 E: SUBSYSTEM=block E: USEC_INITIALIZED=87744 -- 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/1415580 Title: add nvme to -virtual kernel Status in linux package in Ubuntu: Confirmed Bug description: GCE has requested that the nvme kernel module be added to the GCE images. Please add nvme to the -virtual kernel series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415580/+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 1415580] [NEW] add nvme to -virtual kernel
Public bug reported: GCE has requested that the nvme kernel module be added to the GCE images. Please add nvme to the -virtual kernel series. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Andy Whitcroft (apw) Status: Confirmed ** Package changed: ubuntu = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1415580 Title: add nvme to -virtual kernel Status in linux package in Ubuntu: Confirmed Bug description: GCE has requested that the nvme kernel module be added to the GCE images. Please add nvme to the -virtual kernel series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1415580/+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 1390604] Re: Outbound TCP Throughput drops to zero for several drivers
Fix is confirmed by a Canonical partner.
--
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/1390604
Title:
Outbound TCP Throughput drops to zero for several drivers
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Utopic:
Fix Committed
Status in linux source package in Vivid:
Fix Released
Bug description:
There is a bug with TCP in kernel 3.16+ described as:
Some drivers are unable to perform TX completions in a bound time.
They instead call skb_orphan()
Problem is skb_fclone_busy() has to detect this case, otherwise
we block TCP retransmits and can freeze unlucky tcp sessions on
mostly idle hosts.
A patch for this has been submitted upstream:
https://patchwork.ozlabs.org/patch/405110/
The Google engineer that submitted that patch also adds the following:
Backported patch for 3.16 or 3.17 kernel is much simpler :
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index 4e4932b5079b..a8794367cd20 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -2082,7 +2082,8 @@ static bool skb_still_in_host_queue(const struct sock
*sk,
const struct sk_buff *fclone = skb + 1;
if (unlikely(skb-fclone == SKB_FCLONE_ORIG
-fclone-fclone == SKB_FCLONE_CLONE)) {
+fclone-fclone == SKB_FCLONE_CLONE
+fclone-sk == sk)) {
NET_INC_STATS_BH(sock_net(sk),
LINUX_MIB_TCPSPURIOUS_RTX_HOSTQUEUES);
return true;
I do not believe that this problem affects any release prior to 14.10, and I
don't know which version of the patch you may need, but have included both.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390604/+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 1304001] Re: xen:balloon errors in 14.04 beta
I think that this is a verification-failed. Upgrading the kernel in -proposed does not fix the issue: ubuntu@ip-10-11-165-53:~$ uname -a Linux ip-10-11-165-53 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-11-165-53:~$ dpkg-query --show linux-image-virtual linux-image-virtual 3.13.0.37.44 ubuntu@ip-10-11-165-53:~$ dmesg | grep xen [0.00] xen: PV spinlocks enabled [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.440123] xen:balloon: Initialising balloon driver [0.444026] xen_balloon: Initialising balloon driver [0.452023] xen:balloon: Cannot add additional memory (-17) [0.492062] Switched to clocksource xen [0.515406] xen: -- pirq=16 - irq=8 (gsi=8) [0.515446] xen: -- pirq=17 - irq=12 (gsi=12) [0.515470] xen: -- pirq=18 - irq=1 (gsi=1) [0.515497] xen: -- pirq=19 - irq=6 (gsi=6) [0.515530] xen: -- pirq=20 - irq=4 (gsi=4) [0.778201] xen: -- pirq=21 - irq=28 (gsi=28) [0.778253] xen:grant_table: Grant tables using version 1 layout [0.917639] xen_netfront: Initialising Xen virtual ethernet driver [1.006714] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.456083] xen:balloon: Cannot add additional memory (-17) [6.460080] xen:balloon: Cannot add additional memory (-17) [ 14.476110] xen:balloon: Cannot add additional memory (-17) [ 30.492059] xen:balloon: Cannot add additional memory (-17) [ 62.556156] xen:balloon: Cannot add additional memory (-17) [ 94.620107] xen:balloon: Cannot add additional memory (-17) ** Tags removed: verification-needed-trusty ** Tags added: verification-failed -- 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/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] The following errors may occur on HVM instances on EC2: xen:balloon: reserve_additional_memory: add_memory() failed: -17 [Test Case] Boot Ubuntu Trusty 3.13 series HVM instances and check dmesg for this error message. [Fix] A minimal fix for this bug can be found here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3dcf63677d4eb7fdfc13290c8558c301d2588fe8 This allows the ballooning to be cancelled if adding new memory failed which means that the error message is printed once instead of repeatedly. There should still be effort to root cause this issue and determine how to avoid the ballooning errors in the first place. I still think this patch should be applied to alleviate symptoms until root cause is discovered. -- Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory:
[Kernel-packages] [Bug 1350373] Re: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest
Raising the severity due to the impact on EC2. ** Changed in: linux (Ubuntu Trusty) Importance: Medium = High -- 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/1350373 Title: Kernel BUG in paravirt_enter_lazy_mmu when running as a Xen PV guest Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Triaged Bug description: Xen PV guests may crash during boot in paravirt_enter_lazy_mmu() while expanding the grant table (usually when requested by blkfront, when booting). See an example trace below. This is caused by calling functions that are unsafe in atomic context. The fix (which has been submitted to 3.16) is available here (also attached): https://git.kernel.org/cgit/linux/kernel/git/xen/tip.git/commit/?h=stable /for-linus-3.16id=b7dd0e350e0bd4c0fddcc9b8958342700b00b168 The fix is applicable to all kernel since 2.6.39 but only appears to trigger with the 3.13 kernel in 14.04. [2.577876] [ cut here ] [2.577896] kernel BUG at /build/buildd/linux-3.13.0/arch/x86/kernel/paravirt.c:239! [2.577910] invalid opcode: [#1] SMP [2.577922] Modules linked in: [2.577933] CPU: 0 PID: 1 Comm: init Not tainted 3.13.0-24-generic #46-Ubuntu [2.577946] task: ec058000 ti: ec09 task.ti: ec09 [2.577955] EIP: 0061:[c1645ebc] EFLAGS: 00010002 CPU: 0 [2.577973] EIP is at enter_lazy.part.1+0x3/0x5 [2.577982] EAX: 0001 EBX: ec0cc000 ECX: 00581980 EDX: [2.577992] ESI: edc0 EDI: edc0 EBP: ec091a50 ESP: ec091a50 [2.578001] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069 [2.578014] CR0: 8005003b CR2: bfca2fa4 CR3: 2c392000 CR4: 2660 [2.578027] Stack: [2.578032] ec091a58 c1046564 ec091ab4 c1146fd3 fa83b2da edc00fff edc01000 c1a93018 [2.578052] edc00fff c193ce80 edc01000 [2.578076] ed3ef588 ed3ef588 c1b87b70 ec091ad0 edc01000 c1b65310 1000 [2.578096] Call Trace: [2.578111] [c1046564] paravirt_enter_lazy_mmu+0x24/0x30 [2.578127] [c1146fd3] apply_to_page_range+0x1a3/0x310 [2.578141] [c1008eb8] arch_gnttab_map_status+0x38/0x60 [2.578152] [c1008d70] ? map_pte_fn+0x70/0x70 [2.578166] [c13ab020] gnttab_map_frames_v2+0xb0/0x100 [2.578182] [c13ab205] gnttab_map+0x95/0x120 [2.578198] [c12c7ff0] ? blk_update_request+0x190/0x340 [2.578209] [c13ab363] get_free_entries+0xd3/0x280 [2.578221] [c13ab5d3] gnttab_alloc_grant_references+0x13/0x30 [2.578238] [c1424be5] do_blkif_request+0x535/0x6f0 [2.578253] [c16523dc] ? _raw_spin_unlock_irqrestore+0x1c/0x40 [2.578269] [c12c57ee] __blk_run_queue+0x2e/0x40 [2.578280] [c12c5825] blk_start_queue+0x25/0x40 [2.578291] [c1424dbe] kick_pending_request_queues+0x1e/0x30 [2.578304] [c142546f] blkif_interrupt+0x69f/0x740 [2.578318] [c100654f] ? xen_set_pte_at+0xbf/0xf0 [2.578335] [c10a5ba5] handle_irq_event_percpu+0x35/0x1a0 [2.578351] [c12f136a] ? radix_tree_lookup+0xa/0x10 [2.578364] [c10a5d41] handle_irq_event+0x31/0x50 [2.578376] [c10a8036] handle_edge_irq+0x66/0x110 [2.578389] [c13ac246] __xen_evtchn_do_upcall+0x1c6/0x2c0 [2.578402] [c13ae100] xen_evtchn_do_upcall+0x20/0x40 [2.578415] [c165a087] xen_do_upcall+0x7/0xc [2.578427] [c1001227] ? xen_hypercall_xen_version+0x7/0x20 [2.578441] [c10083cf] ? xen_force_evtchn_callback+0xf/0x20 [2.578454] [c1008c50] check_events+0x8/0xc [2.578464] [c1008c47] ? xen_restore_fl_direct_reloc+0x4/0x4 [2.578480] [c1006373] ? xen_batched_set_pte+0xb3/0x160 [2.578493] [c10064b8] xen_set_pte_at+0x28/0xf0 [2.578505] [c10048e6] ? __raw_callee_save_xen_pte_val+0x6/0x8 [2.578521] [c11447a8] copy_pte_range+0x258/0x4c0 [2.578534] [c1146d27] copy_page_range+0x1d7/0x2e0 [2.578549] [c105462e] dup_mm+0x28e/0x4f0 [2.578561] [c1055866] copy_process.part.33+0xfa6/0x10d0 [2.578574] [c1055b41] do_fork+0xc1/0x2c0 [2.578591] [c1067996] ? SyS_rt_sigprocmask+0x76/0xa0 [2.578604] [c1055e05] SyS_clone+0x25/0x30 [2.578615] [c1659b4d] sysenter_do_call+0x12/0x28 [2.578626] Code: c4 1c 5b 5e 5f 5d c3 55 89 e5 f3 0f b8 c0 90 5d c3 55 ba a0 2c aa c1 89 e5 b9 25 00 00 00 57 31 c0 89 d7 f3 ab 5f 5d c3 55 89 e5 0f 0b 55 89 e5 66 66 66 66 90 0f 0b 8b 15 28 d9 91 c1 55 89 e5 [2.578745] EIP: [c1645ebc] enter_lazy.part.1+0x3/0x5 SS:ESP 0069:ec091a50 [2.578765] ---[ end trace ab5b5344be71ca3d ]--- [2.578775] Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1350522] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4167018/+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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887]
[Kernel-packages] [Bug 1350522] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4167019/+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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887]
[Kernel-packages] [Bug 1350522] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4167016/+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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887]
[Kernel-packages] [Bug 1350522] Re: EC2 kernel crash due to vmalloc
apport information ** Description changed: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu. DistroRelease: Ubuntu 14.10 Ec2AMI: ami-c571d8d8 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: sa-east-1b Ec2InstanceType: m3.medium Ec2Kernel: aki-5553f448 Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package:
[Kernel-packages] [Bug 1350522] Re: EC2 kernel crash due to vmalloc
* It would be useful to correlate Xen hypervisor versions. On each launch with warnings we need to grep 'Xen version' in dmesg. Xen 4.2, w/ Amazon patches. * Can you add the following to kernel cmdline options to get additional debug information: initcall_debug debug ignore_loglevel LOGLEVEL=8 Added in the latest set of logs * If you see this problem in an instance, if you reboot does the same problem occur? Multiple reboots yields the same issue, but at different points -- 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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2
[Kernel-packages] [Bug 1350522] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4167020/+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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887]
[Kernel-packages] [Bug 1350522] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4167015/+files/Dependencies.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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887]
[Kernel-packages] [Bug 1350522] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4167017/+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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887]
[Kernel-packages] [Bug 1350522] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4167021/+files/WifiSyslog.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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887]
[Kernel-packages] [Bug 1350375] Re: DomU crach on xen 3.2 due to NMI call
$ git log -S xen_enable_nmi --source --all commit ea9f9274bf4337ba7cbab241c780487651642d63 refs/tags/v3.16-rc6 Author: David Vrabel david.vra...@citrix.com Date: Mon Jun 16 13:07:00 2014 +0200 x86/xen: no need to explicitly register an NMI callback Remove xen_enable_nmi() to fix a 64-bit guest crash when registering the NMI callback on Xen 3.1 and earlier. It's not needed since the NMI callback is set by a set_trap_table hypercall (in xen_load_idt() or xen_write_idt_entry()). It's also broken since it only set the current VCPU's callback. Signed-off-by: David Vrabel david.vra...@citrix.com Reported-by: Vitaly Kuznetsov vkuzn...@redhat.com Tested-by: Vitaly Kuznetsov vkuzn...@redhat.com ** Package changed: ubuntu = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1350375 Title: DomU crach on xen 3.2 due to NMI call Status in “linux” package in Ubuntu: Confirmed Bug description: Request from Amazon: Our engineering team has reported that the kernel in 14.04 LTS is making a call to NMI which in turn causes DomU instances to crash under Xen 3.2. This affects only a particular range of kernel versions from 3.12.25 to 3.15.6, and the kernel in 14.04 seems to be 3.14.x. There is already a patch in the mainstream kernel version to apply that would address the situation. The probability of a DomU crash with the current ubuntu 14.04 kernel on a Dom0 running Xen 3.2 is always. Our customers sometimes run on instance types that route them to 3.2 Xen so this does not impact all customers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350375/+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 1350522] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4166184/+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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu.
[Kernel-packages] [Bug 1350522] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4166185/+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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu.
[Kernel-packages] [Bug 1350522] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4166183/+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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu.
[Kernel-packages] [Bug 1350522] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4166181/+files/Dependencies.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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu.
[Kernel-packages] [Bug 1350522] Re: EC2 kernel crash due to vmalloc
apport information ** Tags added: apport-collected ec2-images third-party-packages utopic ** Description changed: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jul 30 20:19 seq + crw-rw 1 root audio 116, 33 Jul 30 20:19 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.4-0ubuntu2 + 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 + CurrentDmesg: + [ 42.901579] systemd-logind[1378]: New seat seat0. + [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu. + DistroRelease: Ubuntu 14.10 + Ec2AMI: ami-c571d8d8 + Ec2AMIManifest: (unknown) + Ec2AvailabilityZone: sa-east-1b + Ec2InstanceType: m3.medium + Ec2Kernel: aki-5553f448 + Ec2Ramdisk: unavailable + IwConfig: Error: [Errno 2] No such file or directory + Lspci: + + Lsusb: Error: command ['lsusb'] failed with
[Kernel-packages] [Bug 1350522] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4166188/+files/WifiSyslog.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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu.
[Kernel-packages] [Bug 1350522] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4166186/+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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu. DistroRelease: Ubuntu
[Kernel-packages] [Bug 1350522] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1350522/+attachment/4166187/+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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu. DistroRelease:
[Kernel-packages] [Bug 1350522] Re: EC2 kernel crash due to vmalloc
Another stack trace from another instance: 20:34:16 [2.425540] systemd-udevd[95]: starting version 204 20:34:16 [2.576097] [ cut here ] 20:34:16 [2.576111] WARNING: CPU: 0 PID: 98 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 20:34:16 [2.576115] Modules linked in: 20:34:16 [2.576120] CPU: 0 PID: 98 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 20:34:16 [2.576123] 0009 88000316fb98 81755538 20:34:16 [2.576128] 88000316fbd0 8106bb0d 88000400df68 0001 20:34:16 [2.576132] 880003393900 c01ed000 88000316fbe0 20:34:16 [2.576136] Call Trace: 20:34:16 [2.576147] [81755538] dump_stack+0x45/0x56 20:34:16 [2.576152] [8106bb0d] warn_slowpath_common+0x7d/0xa0 20:34:16 [2.576156] [8106bbea] warn_slowpath_null+0x1a/0x20 20:34:16 [2.576159] [81197c31] vmap_page_range_noflush+0x2d1/0x370 20:34:16 [2.576163] [81197cfe] map_vm_area+0x2e/0x40 20:34:16 [2.576167] [8119a058] __vmalloc_node_range+0x188/0x280 20:34:16 [2.576175] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 20:34:16 [2.576178] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 20:34:16 [2.576183] [8104f294] module_alloc+0x74/0xd0 20:34:16 [2.576187] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 20:34:16 [2.576190] [810e92b4] module_alloc_update_bounds+0x14/0x70 20:34:16 [2.576194] [810e9a6c] layout_and_allocate+0x74c/0xc70 20:34:16 [2.576198] [810ea063] load_module+0xd3/0x1b70 20:34:16 [2.576202] [811cfeb1] ? vfs_read+0xf1/0x170 20:34:16 [2.576206] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 20:34:16 [2.576209] [810ebc76] SyS_finit_module+0x86/0xb0 20:34:16 [2.576217] [8175de7f] tracesys+0xe1/0xe6 20:34:16 [2.576220] ---[ end trace 0f39a359bc0e983c ]--- 20:34:16 [2.576223] vmalloc: allocation failure, allocated 20480 of 24576 bytes 20:34:16 [2.576226] systemd-udevd: page allocation failure: order:0, mode:0xd2 20:34:16 [2.576229] CPU: 0 PID: 98 Comm: systemd-udevd Tainted: GW 3.16.0-6-generic #11-Ubuntu 20:34:16 [2.576232] 81a88bc0 88000316fc08 81755538 00d2 20:34:16 [2.576236] 88000316fc90 811642bf 81a88bc0 88000316fc28 20:34:16 [2.576239] 3fff0018 88000316fca0 88000316fc40 0163 20:34:16 [2.576246] Call Trace: 20:34:16 [2.576249] [81755538] dump_stack+0x45/0x56 20:34:16 [2.576254] [811642bf] warn_alloc_failed+0xdf/0x130 20:34:16 [2.576257] [8119a118] __vmalloc_node_range+0x248/0x280 20:34:16 [2.576261] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 20:34:16 [2.576264] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 20:34:16 [2.576267] [8104f294] module_alloc+0x74/0xd0 20:34:16 [2.576271] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 20:34:16 [2.576274] [810e92b4] module_alloc_update_bounds+0x14/0x70 20:34:16 [2.576278] [810e9a6c] layout_and_allocate+0x74c/0xc70 20:34:16 [2.576281] [810ea063] load_module+0xd3/0x1b70 20:34:16 [2.576287] [811cfeb1] ? vfs_read+0xf1/0x170 20:34:16 [2.576290] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 20:34:16 [2.576294] [810ebc76] SyS_finit_module+0x86/0xb0 20:34:16 [2.576298] [8175de7f] tracesys+0xe1/0xe6 20:34:16 [2.576300] Mem-Info: 20:34:16 [2.576302] Node 0 DMA per-cpu: 20:34:16 [2.576304] CPU0: hi:0, btch: 1 usd: 0 20:34:16 [2.576306] Node 0 DMA32 per-cpu: 20:34:16 [2.576311] CPU0: hi: 186, btch: 31 usd: 125 20:34:16 [2.576315] active_anon:630 inactive_anon:13 isolated_anon:0 20:34:16 [2.576315] active_file:975 inactive_file:4521 isolated_file:0 20:34:16 [2.576315] unevictable:0 dirty:0 writeback:0 unstable:0 20:34:16 [2.576315] free:943953 slab_reclaimable:1610 slab_unreclaimable:1090 20:34:16 [2.576315] mapped:836 shmem:19 pagetables:285 bounce:0 20:34:16 [2.576315] free_cma:16384 20:34:16 [2.576325] Node 0 DMA free:15852kB min:32kB low:40kB high:48kB active_anon:24kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15996kB managed:15912kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:12kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes 20:34:16 [2.576338] lowmem_reserve[]: 0 3730 3730 3730 20:34:16
[Kernel-packages] [Bug 1350522] Re: EC2 kernel crash due to vmalloc
I am seeing this happen in about 5% of the launches on EC2. -- 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/1350522 Title: EC2 kernel crash due to vmalloc Status in “linux” package in Ubuntu: Confirmed Bug description: During Alpha-2 automated testing, I saw the following in a log: 19:35:02 [2.475810] systemd-udevd[95]: starting version 204 19:35:02 [2.547049] [ cut here ] 19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at /build/buildd/linux-3.16.0/mm/vmalloc.c:128 vmap_page_range_noflush+0x2d1/0x370() 19:35:02 [2.547069] Modules linked in: 19:35:02 [2.547073] CPU: 0 PID: 97 Comm: systemd-udevd Not tainted 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547077] 0009 880002defb98 81755538 19:35:02 [2.547082] 880002defbd0 8106bb0d 88000400ec88 0001 19:35:02 [2.547086] 880002fcfb00 c0391000 880002defbe0 19:35:02 [2.547090] Call Trace: 19:35:02 [2.547096] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547101] [8106bb0d] warn_slowpath_common+0x7d/0xa0 19:35:02 [2.547104] [8106bbea] warn_slowpath_null+0x1a/0x20 19:35:02 [2.547108] [81197c31] vmap_page_range_noflush+0x2d1/0x370 19:35:02 [2.547112] [81197cfe] map_vm_area+0x2e/0x40 19:35:02 [2.547115] [8119a058] __vmalloc_node_range+0x188/0x280 19:35:02 [2.547120] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547124] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547129] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547132] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547135] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547146] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547149] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547154] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547157] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547161] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547167] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547169] ---[ end trace 8a5de7fc66e75fe4 ]--- 19:35:02 [2.547172] vmalloc: allocation failure, allocated 20480 of 24576 bytes 19:35:02 [2.547175] systemd-udevd: page allocation failure: order:0, mode:0xd2 19:35:02 [2.547180] CPU: 0 PID: 97 Comm: systemd-udevd Tainted: G W 3.16.0-6-generic #11-Ubuntu 19:35:02 [2.547183] 81a88bc0 880002defc08 81755538 00d2 19:35:02 [2.547187] 880002defc90 811642bf 81a88bc0 880002defc28 19:35:02 [2.547191] 3fff0018 880002defca0 880002defc40 0163 19:35:02 [2.547195] Call Trace: 19:35:02 [2.547197] [81755538] dump_stack+0x45/0x56 19:35:02 [2.547202] [811642bf] warn_alloc_failed+0xdf/0x130 19:35:02 [2.547207] [8119a118] __vmalloc_node_range+0x248/0x280 19:35:02 [2.547210] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547214] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547217] [8104f294] module_alloc+0x74/0xd0 19:35:02 [2.547220] [810e92b4] ? module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547224] [810e92b4] module_alloc_update_bounds+0x14/0x70 19:35:02 [2.547229] [810e9a6c] layout_and_allocate+0x74c/0xc70 19:35:02 [2.547232] [810ea063] load_module+0xd3/0x1b70 19:35:02 [2.547235] [811cfeb1] ? vfs_read+0xf1/0x170 19:35:02 [2.547238] [810e7aa1] ? copy_module_from_fd.isra.46+0x121/0x180 19:35:02 [2.547242] [810ebc76] SyS_finit_module+0x86/0xb0 19:35:02 [2.547246] [8175de7f] tracesys+0xe1/0xe6 19:35:02 [2.547248] Mem-Info: --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 30 20:19 seq crw-rw 1 root audio 116, 33 Jul 30 20:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.4-0ubuntu2 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 CurrentDmesg: [ 42.901579] systemd-logind[1378]: New seat seat0. [ 42.932887] systemd-logind[1378]: New session 1 of user ubuntu. DistroRelease: Ubuntu 14.10 Ec2AMI: ami-c571d8d8 Ec2AMIManifest: (unknown)
[Kernel-packages] [Bug 1101636] Re: LICENSE.aic94xx-seq in linux-firmware - is this firmware distributable?
Marking as verification done. I've confirmed that the problematic firmware is missing. ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1101636 Title: LICENSE.aic94xx-seq in linux-firmware - is this firmware distributable? Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-firmware” source package in Precise: Fix Committed Status in “linux-firmware” source package in Trusty: Fix Released Bug description: For this specific license it appears that this License is rather restrictive. In clause two it appears that this package cannot be distributed. I think this is a bug right? :) The Fedora Core 18 counterpart looks like: http://pkgs.fedoraproject.org/cgit/aic94xx- firmware.git/tree/LICENSE.aic94xx?h=f18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1101636/+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 1317695] Re: hyper-v: Unable to copy and boot Generation 2 Ubuntu 14.04 VHDs
To highlight jleung's comments, what is going on is that generation 2 VM's require UEFI to boot, inform the UEFI boot manager of the OS (via registration of values in the NVRAM). The Ubuntu installer does this at installation time. What jlaeung's describing is converting to removal mode. I suspect that VM's should be installed w/ removal mode by default to support cloning operations. We currently do this on the Ubuntu 14.04 LTS UEFI cloud images. -- 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/1317695 Title: hyper-v: Unable to copy and boot Generation 2 Ubuntu 14.04 VHDs Status in “linux” package in Ubuntu: Confirmed Bug description: After creating a Generation 2 virtual machine, we are unable to shutdown the VM, copy the VHD and create a new Generation 2 virtual machine out of the VHD. It seems that once the copy out operation has occurred, the UEFI boot entry is not available on the file-system. This hinders scenarios where customers routinely copy VHDs to create new virtual machines. Root cause unknown as of now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317695/+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 1311070] Re: hyper-v:IP Injection on Ubuntu 13.10 guest during Failover and Test Failover is corrupting the existing entries
Marked several bugs as duplicates. Please do not file multiple bugs for the same issue, as it add confusion to the issue at hand. -- 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/1311070 Title: hyper-v:IP Injection on Ubuntu 13.10 guest during Failover and Test Failover is corrupting the existing entries Status in “linux” package in Ubuntu: Confirmed Bug description: [HyperV Replica :: http://technet.microsoft.com/en-us/library/jj134172.aspx] [Guest IP Injection :: http://blogs.technet.com/b/virtualization/archive/2012/05/29/inject-ip-address-into-the-vm-during-failover.aspx] hv_set_ifconfig script is corrupting the last entry inside /etc/network/interfaces. It is creating 2 entries for eth1 Leading to failure of IP Injection. 1) Create Ubuntu 13.10 virtual machine. 2) Attach network adapters 'Network Adapter' and 'Adapter2' on primary and configured via DHCP. cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet dhcp 3) Enable Replication. 4) Set Failover IP settings on second adapter (Adapter2) Set-VMNetworkAdapterFailoverConfiguration -ComputerName $computerName -VMName $vmname -IPv4Address 192.168.100.10 -IPv4SubnetMask 255.255.0.0 -IPv4PreferredDNSServer 192.168.100.101 -IPv4AlternateDNSServer 192.168.100.102 -IPv4DefaultGateway 192.168.100.1 -VMNetworkAdapterName 'Adapter2' 5) Do Failover cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp iface eth1 inet dhcp # The following stanza(s) added by hv_set_ifconfig auto eth1 iface eth1 inet static address 192.168.100.10 netmask 255.255.0.0 gateway 192.168.100.1 dns-nameservers 192.168.100.101 192.168.100.102 #End of hv_set_ifconfig stanzas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311070/+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 1311055] Re: hyper-v: DNS Server settings are not getting injected inside Ubuntu 13.10 during Failover and Test-Failover
*** This bug is a duplicate of bug 1311070 *** https://bugs.launchpad.net/bugs/1311070 Marking this as a duplicate. This issue is the same issue as bug #1311070, namely that the IP injection scripts are not working properly. Therefore, I have marked this as a duplicate. ** This bug has been marked a duplicate of bug 1311070 hyper-v:IP Injection on Ubuntu 13.10 guest during Failover and Test Failover is corrupting the existing entries -- 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/1311055 Title: hyper-v: DNS Server settings are not getting injected inside Ubuntu 13.10 during Failover and Test-Failover Status in “linux” package in Ubuntu: Confirmed Bug description: [HyperV Replica :: http://technet.microsoft.com/en-us/library/jj134172.aspx] [Guest IP Injection :: http://blogs.technet.com/b/virtualization/archive/2012/05/29/inject-ip-address-into-the-vm-during-failover.aspx] DNS server settigns are not getting injected inside Ubuntu 13-10 for a network adapter that is attached to an external network before Failover and is configured using static Guest IP injection during Failover. The settings are updated correctly inside /etc/network/interfaces. The DNS server entries updated to specified values after next reboot. 1 Create anUbuntu-13.10 VM with external network attached to it. 2 Check DNS entries cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver X.Y.Z.W nameserver X.Y.Z.K search dummy.fake.com 3 Enable Replication. 4 Set Failover IPv4 (static IP) settings. Set-VMNetworkAdapterFailoverConfiguration -ComputerName bharatl-test1 -VMName lol -IPv4Address 192.168.100.10 -IPv4SubnetMask 255.255.255.0 -IPv4PreferredDNSServer 192.168.100.101 -IPv4DefaultGateway 192.168.100.1 -VMNetworkAdapterName 'Network Adapter' 5 Do Failover. 6 Check DNS settings. cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver X.Y.Z.W nameserver X.Y.Z.K search dummy.fake.com 7 Reboot the Guest. 8 Check DNS settings # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.100.101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311055/+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 1311071] Re: hyper-v: IP Injection setting are not correctly populated inside Ubuntu 13.10 guest during Failover and Test Failover when using more than one interfaces for IP Inj
*** This bug is a duplicate of bug 1311070 *** https://bugs.launchpad.net/bugs/1311070 Marking this as a duplicate. This issue is the same issue as bug #1311070, namely that the IP injection scripts are not working properly. Therefore, I have marked this as a duplicate. ** This bug has been marked a duplicate of bug 1311070 hyper-v:IP Injection on Ubuntu 13.10 guest during Failover and Test Failover is corrupting the existing entries -- 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/1311071 Title: hyper-v: IP Injection setting are not correctly populated inside Ubuntu 13.10 guest during Failover and Test Failover when using more than one interfaces for IP Injection Status in “linux” package in Ubuntu: Confirmed Bug description: [HyperV Replica :: http://technet.microsoft.com/en-us/library/jj134172.aspx] [Guest IP Injection :: http://blogs.technet.com/b/virtualization/archive/2012/05/29/inject-ip-address-into-the-vm-during-failover.aspx] After failover only the Injected IP settings of the last interface is retained inside /etc/network/interfaces Repro Steps: 1) Create Ubuntu 13.10 virtual machine. 2) Enable Replication. 3) Attach two network adapters on recovery. 'Network Adapter' and 'Adapter2' 4) Assign Failover IP settings to both these adapters. Set-VMNetworkAdapterFailoverConfiguration -ComputerName $computerName -VMName $vmname -IPv4Address 192.168.100.10 -IPv4SubnetMask 255.255.0.0 -IPv4PreferredDNSServer 192.168.100.101 -IPv4AlternateDNSServer 192.168.100.102 -IPv4DefaultGateway 192.168.100.1 -VMNetworkAdapterName 'Network Adapter' Set-VMNetworkAdapterFailoverConfiguration -ComputerName $computerName -VMName $vmname -IPv4Address 192.168.100.20 -IPv4SubnetMask 255.255.255.0 -IPv4PreferredDNSServer 192.168.100.201 -IPv4AlternateDNSServer 192.168.100.202 -IPv4DefaultGateway 192.168.100.2 -VMNetworkAdapterName 'Adapter2' 5) Do Failover. Check contents of eth0 cat /var/lib/hyperv/ifcfg-eth0 HWADDR=00:15:5D:38:4E:30 DEVICE=eth0 BOOTPROTO=none IPADDR0=192.168.100.10 NETMASK0=255.255.0.0 GATEWAY=192.168.100.1 DNS1=192.168.100.101 DNS2=192.168.100.102 Check contents of eth1 # cat /var/lib/hyperv/ifcfg-eth1 HWADDR=00:15:5D:38:4E:31 DEVICE=eth1 BOOTPROTO=none IPADDR0=192.168.100.20 NETMASK0=255.255.255.0 GATEWAY=192.168.100.2 DNS1=192.168.100.201 DNS2=192.168.100.202 6) Look into contents of /etc/network/interfaces # cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 # The following stanza(s) added by hv_set_ifconfig auto eth1 iface eth1 inet static address 192.168.100.20 netmask 255.255.255.0 gateway 192.168.100.2 dns-nameservers 192.168.100.201 192.168.100.202 #End of hv_set_ifconfig stanzas 7) Only IP settings for the last interface i.e., eth1 in our case are intact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311071/+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 1311048] Re: hyper-v: hv_set_ifconfig is not parsing netmask setting on Ubuntu-13.10
*** This bug is a duplicate of bug 1311070 *** https://bugs.launchpad.net/bugs/1311070 Marking this as a duplicate. This issue is the same issue as bug #1311070, namely that the IP injection scripts are not working properly. Therefore, I have marked this as a duplicate. ** This bug has been marked a duplicate of bug 1311070 hyper-v:IP Injection on Ubuntu 13.10 guest during Failover and Test Failover is corrupting the existing entries -- 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/1311048 Title: hyper-v: hv_set_ifconfig is not parsing netmask setting on Ubuntu-13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Netmask is not set correctly by hv_set_ifconfig of Ubuntu 13.10 during Failover and Test-Failover. hv_set_ifconfig is not parsing the /var/lib/hyperv/ifcfg-ethX file correctly and ignoring the netmask field. Error Line if NETMASK+suffix in kvp.keys(): output += [\tnetmask + kvp[NETMASK+suffix]] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311048/+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 1304001] [NEW] xen:balloon errors in 14.04 beta
Public bug reported: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux-meta” package in Ubuntu: New Bug description: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [
[Kernel-packages] [Bug 1301019] Re: hyper-v: ifdown command not working due to bad ifstate
@apw the python script is assuming that the NIC is configured via /etc/network/interfaces. Over a year ago we changed Cloud Images from using /etc/network/interfaces with the primary configuration to using /etc/network/interfaces.d/INT.cfg and using /etc/network/interface to source them. Bare metal installations I have confirmed that our version of hv_set_ifconfig does not handle this change. Bare metal installations from media should be using /etc/network/interfaces, so the installed script should continue to work just fine. ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Ben Howard (utlemming) -- 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/1301019 Title: hyper-v: ifdown command not working due to bad ifstate Status in “linux” package in Ubuntu: Confirmed Bug description: It appears that ifdown command is not working because “/run/network/ifstate does not contain eth0=eth0. This in turn causes hyper-v's script hv_set_ifconfig.sh to fail as follows: root@ubuntu:~# ./hv_set_ifconfig.sh /var/lib/hyperv/ifcfg-eth0 ifdown: interface eth0 not configured RTNETLINK answers: File exists Failed to bring up eth0. It appears that something is wrong with your core networking files for trusty. Please could you help fix? Thanks, Abhishek To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301019/+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 1271669] Re: move drivers/misc/vmw_vmci/vmw_vmci.ko from linux-image-extra to linux-image-virtual
** Description changed: - drivers/misc/vmw_vmci/vmw_vmci.ko is currently in linux-image-extra. Due - to a sync of open-vm-tools and an open MIR on open-vm-tools, this module - is needed in the regular kernel + drivers/misc/vmw_vmci/vmw_vmci.ko, + net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko are + currently in linux-image-extra. Due to a sync of open-vm-tools and an + open MIR on open-vm-tools, these modules are needed in the regular + kernel. Bug #1220950 open-vm-tools ** Summary changed: - move drivers/misc/vmw_vmci/vmw_vmci.ko from linux-image-extra to linux-image-virtual + move vmware modules (vmci, vsock, vxnet) from linux-image-extra to linux-image-virtual -- 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/1271669 Title: move vmware modules (vmci, vsock, vxnet3) from linux-image-extra to linux-image-virtual Status in “linux” package in Ubuntu: In Progress Bug description: drivers/misc/vmw_vmci/vmw_vmci.ko, net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko are currently in linux-image-extra. Due to a sync of open-vm-tools and an open MIR on open-vm-tools, these modules are needed in the regular kernel. Bug #1220950 open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271669/+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 1271669] Re: Move vmware related modules from extras into main kernel package
Once these modules are enabled in the kernel, we should disable the modules in open-vm-tools DKMS package. The only module that should be built via the DKMS package is vmhgfs. ** Also affects: open-vm-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: open-vm-tools (Ubuntu) Assignee: (unassigned) = Robert Jennings (rcj) ** Changed in: open-vm-tools (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Milestone: None = ubuntu-14.04 ** Changed in: open-vm-tools (Ubuntu) Milestone: None = ubuntu-14.04 ** Changed in: open-vm-tools (Ubuntu) Status: New = In Progress -- 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/1271669 Title: Move vmware related modules from extras into main kernel package Status in “linux” package in Ubuntu: In Progress Status in “open-vm-tools” package in Ubuntu: In Progress Bug description: drivers/misc/vmw_vmci/vmw_vmci.ko, net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko are currently in linux-image-extra. Due to a sync of open-vm-tools and an open MIR on open-vm-tools, these modules are needed in the regular kernel. Bug #1220950 open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271669/+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 1271669] Re: move vmware modules (vmci, vsock, vxnet3) from linux-image-extra to linux-image-virtual
Please make sure that vmxnet3 is included, not vmxnet ** Summary changed: - move vmware modules (vmci, vsock, vxnet) from linux-image-extra to linux-image-virtual + move vmware modules (vmci, vsock, vxnet3) from linux-image-extra to linux-image-virtual -- 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/1271669 Title: move vmware modules (vmci, vsock, vxnet3) from linux-image-extra to linux-image-virtual Status in “linux” package in Ubuntu: In Progress Bug description: drivers/misc/vmw_vmci/vmw_vmci.ko, net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko are currently in linux-image-extra. Due to a sync of open-vm-tools and an open MIR on open-vm-tools, these modules are needed in the regular kernel. Bug #1220950 open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271669/+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 1258631] Re: instances fails to register GPT partition entries on virtio devices
The messages: [ 0.627017] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 0.628500] GPT:4194303 != 20971519 [ 0.629167] GPT:Alternate GPT header not at the end of the disk. [ 0.630291] GPT:4194303 != 20971519 [ 0.630951] GPT: Use GNU Parted to correct GPT errors. [ 0.632002] vda: vda1 Are expected. This image was built as a 2GB volume and then expanded to 10GB on OpenStack. When you reboot, the message goes away and the grow- rootfs fixes the problem. Also, you'll notice that the physical layout has partition 127 and 128 at the begining of the drive, before partition one. I would argue that this message is a red herring. -- 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/1258631 Title: instances fails to register GPT partition entries on virtio devices Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: In Progress Bug description: When booting via KVM and using the VirtIO interface, GPT partition entries are not shown properly. ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print Model: Virtio Block Device (virtblk) Disk /dev/vda: 10.7GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start EndSize File system Name Flags 127 1049kB 2097kB 1049kB BIOS boot partition bios_grub 128 2097kB 89.1MB 87.0MB fat32 EFI System boot 1 89.1MB 10.7GB 10.6GB ext4 Linux filesystem Booting with -hda disk.img [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5 [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.644685] sda: sda1 sda127 sda128 [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk Booting with -drive if=virtio,file=disk.img or -drive if=scsi,file=disk.img: [2.411933] brd: module loaded [2.422616] loop: module loaded [2.442178] vda: vda1 [2.49] scsi0 : ata_piix [2.456868] scsi1 : ata_piix ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu6 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Fri Dec 6 18:49:57 2013 Ec2AMI: ami-0632 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0548 Ec2Ramdisk: ari-0548 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic root=LABEL=cloudimg-rootfs console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.3 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258631/+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 1258631] Re: instances fails to register GPT partition entries on virtio devices
Joseph, This problem does happen with the latest upstream kernel as well. ubuntu@gpt-test-4:~$ uname -a Linux gpt-test-4 3.13.0-031300rc3-generic #201312061335 SMP Fri Dec 6 18:37:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ubuntu@gpt-test-4:~$ dmesg | grep vda [1.039698] vda: vda1 [1.879747] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null) [2.544984] EXT4-fs (vda1): re-mounted. Opts: (null) And testing the 3.8 line in Saucy: ubuntu@gpt-test-4:~$ uname -a Linux gpt-test-4 3.8.13-03081311-generic #201310151335 SMP Tue Oct 15 17:36:06 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ubuntu@gpt-test-4:~$ dmesg | grep vda [0.789770] vda: vda1 [1.618881] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null) [2.226267] EXT4-fs (vda1): re-mounted. Opts: (null) So this appears to be a long-running issue. -- 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/1258631 Title: instances fails to register GPT partition entries on virtio devices Status in “linux” package in Ubuntu: Confirmed Bug description: When booting via KVM and using the VirtIO interface, GPT partition entries are not shown properly. ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print Model: Virtio Block Device (virtblk) Disk /dev/vda: 10.7GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start EndSize File system Name Flags 127 1049kB 2097kB 1049kB BIOS boot partition bios_grub 128 2097kB 89.1MB 87.0MB fat32 EFI System boot 1 89.1MB 10.7GB 10.6GB ext4 Linux filesystem Booting with -hda disk.img [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5 [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.644685] sda: sda1 sda127 sda128 [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk Booting with -drive if=virtio,file=disk.img or -drive if=scsi,file=disk.img: [2.411933] brd: module loaded [2.422616] loop: module loaded [2.442178] vda: vda1 [2.49] scsi0 : ata_piix [2.456868] scsi1 : ata_piix ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu6 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Fri Dec 6 18:49:57 2013 Ec2AMI: ami-0632 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0548 Ec2Ramdisk: ari-0548 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic root=LABEL=cloudimg-rootfs console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.3 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258631/+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 1258631] Re: instances fails to register GPT partition entries on virtio devices
** Package changed: systemd (Ubuntu) = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1258631 Title: instances fails to register GPT partition entries on virtio devices Status in “linux” package in Ubuntu: New Bug description: When booting via KVM and using the VirtIO interface, GPT partition entries are not shown properly. ubuntu@gpt-test-4:~$ sudo parted /dev/vda -s -- print Model: Virtio Block Device (virtblk) Disk /dev/vda: 10.7GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start EndSize File system Name Flags 127 1049kB 2097kB 1049kB BIOS boot partition bios_grub 128 2097kB 89.1MB 87.0MB fat32 EFI System boot 1 89.1MB 10.7GB 10.6GB ext4 Linux filesystem Booting with -hda disk.img [2.612975] sr 1:0:0:0: Attached scsi generic sg1 type 5 [2.617252] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.644685] sda: sda1 sda127 sda128 [2.664314] sd 0:0:0:0: [sda] Attached SCSI disk Booting with -drive if=virtio,file=disk.img or -drive if=scsi,file=disk.img: [2.411933] brd: module loaded [2.422616] loop: module loaded [2.442178] vda: vda1 [2.49] scsi0 : ata_piix [2.456868] scsi1 : ata_piix ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu6 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Fri Dec 6 18:49:57 2013 Ec2AMI: ami-0632 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0548 Ec2Ramdisk: ari-0548 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-5-generic root=LABEL=cloudimg-rootfs console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnOpenStackFoundation:pnOpenStackNova:pvr2013.1.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.1.3 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258631/+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 1235025] Re: Ubuntu 13.10 missing daemon initialization scripts for hv_vss_daemon.
Marking as fix released. Fix went out with 13.10.
** Changed in: hv-kvp-daemon-init (Ubuntu)
Status: Fix Committed = Fix Released
--
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/1235025
Title:
Ubuntu 13.10 missing daemon initialization scripts for hv_vss_daemon.
Status in “hv-kvp-daemon-init” package in Ubuntu:
Fix Released
Status in “linux” package in Ubuntu:
Invalid
Bug description:
Hi,
It appears that Ubuntu 13.10 does not include a script to initialize
the hv_vss_daemon. The script should be just the same as the one for
hv_kvp_daemon.
The hv_kvp_daemon init script hv-kvp-daemon-init is just a symbolic
link to /lib/init/upstart-job
Creating a new symbolic link titled hv-vss-daemon-init that would
start the daemon /usr/sbin/hv_vss_daemon_{version number} should solve
the problem.
Thanks,
Abhishek
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hv-kvp-daemon-init/+bug/1235025/+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 1078106] Re: [MIR] hv-kvp-daemon-init
** Changed in: linux (Ubuntu) Status: Fix Committed = Fix Released -- 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/1078106 Title: [MIR] hv-kvp-daemon-init Status in “hv-kvp-daemon-init” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux-backports-modules-3.2.0” package in Ubuntu: Invalid Status in “linux-backports-modules-3.5.0” package in Ubuntu: Invalid Status in “hv-kvp-daemon-init” source package in Precise: Fix Released Status in “linux” source package in Precise: Invalid Status in “linux-backports-modules-3.2.0” source package in Precise: Fix Released Status in “linux-backports-modules-3.5.0” source package in Precise: Invalid Status in “hv-kvp-daemon-init” source package in Quantal: Fix Released Status in “linux” source package in Quantal: Invalid Status in “linux-backports-modules-3.2.0” source package in Quantal: Invalid Status in “linux-backports-modules-3.5.0” source package in Quantal: Fix Released Bug description: [Availability]: The hv-kvp-daemon-init has been in Universe since Precise [Rationale]: The hv-kvp-daemon-init is provided in the linux-tools package. However, there is no init script to start the daemon. This daemon is required in order to facilitate communication between Hyper-V hypervisors and the kernel. This package is a build requirement for the 13.04 Cloud Images for Windows Azure. Per policy, only pacakges from main are allowed on Cloud Images. [Security]: This init script packaging does not expose any services. Rather, it simply starts a daemon from the the linux-tools package. [Quality assurance]: Due to the rather simplistic nature of the hv_kvp_daemon package, it will be easily maintained. [Dependencies]: linux-tools, which is in main already. [Maintenance]: The maintaince of this package is realatively simple due to the packge being only an upstart job. This package will be maintained and tracked by the Canonical Cloud Ecosystems team. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hv-kvp-daemon-init/+bug/1078106/+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 1235025] Re: Ubuntu 13.10 missing daemon initialization scripts for hv_vss_daemon.
** Changed in: hv-kvp-daemon-init (Ubuntu)
Status: New = Fix Committed
--
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/1235025
Title:
Ubuntu 13.10 missing daemon initialization scripts for hv_vss_daemon.
Status in “hv-kvp-daemon-init” package in Ubuntu:
Fix Committed
Status in “linux” package in Ubuntu:
Invalid
Bug description:
Hi,
It appears that Ubuntu 13.10 does not include a script to initialize
the hv_vss_daemon. The script should be just the same as the one for
hv_kvp_daemon.
The hv_kvp_daemon init script hv-kvp-daemon-init is just a symbolic
link to /lib/init/upstart-job
Creating a new symbolic link titled hv-vss-daemon-init that would
start the daemon /usr/sbin/hv_vss_daemon_{version number} should solve
the problem.
Thanks,
Abhishek
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hv-kvp-daemon-init/+bug/1235025/+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 1235025] Re: Ubuntu 13.10 missing daemon initialization scripts for hv_vss_daemon.
** Changed in: hv-kvp-daemon-init (Ubuntu)
Importance: High = Critical
--
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/1235025
Title:
Ubuntu 13.10 missing daemon initialization scripts for hv_vss_daemon.
Status in “hv-kvp-daemon-init” package in Ubuntu:
New
Status in “linux” package in Ubuntu:
Invalid
Bug description:
Hi,
It appears that Ubuntu 13.10 does not include a script to initialize
the hv_vss_daemon. The script should be just the same as the one for
hv_kvp_daemon.
The hv_kvp_daemon init script hv-kvp-daemon-init is just a symbolic
link to /lib/init/upstart-job
Creating a new symbolic link titled hv-vss-daemon-init that would
start the daemon /usr/sbin/hv_vss_daemon_{version number} should solve
the problem.
Thanks,
Abhishek
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hv-kvp-daemon-init/+bug/1235025/+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 1235025] Re: Ubuntu 13.10 missing daemon initialization scripts for hv_vss_daemon.
Fixed the existing scripts. Just need a review and upload.
** Branch linked: lp:~utlemming/ubuntu/saucy/hv-kvp-daemon-
init/lp1235025
** Changed in: hv-kvp-daemon-init (Ubuntu)
Importance: Undecided = High
** Changed in: hv-kvp-daemon-init (Ubuntu)
Assignee: (unassigned) = Ben Howard (utlemming)
--
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/1235025
Title:
Ubuntu 13.10 missing daemon initialization scripts for hv_vss_daemon.
Status in “hv-kvp-daemon-init” package in Ubuntu:
New
Status in “linux” package in Ubuntu:
Invalid
Bug description:
Hi,
It appears that Ubuntu 13.10 does not include a script to initialize
the hv_vss_daemon. The script should be just the same as the one for
hv_kvp_daemon.
The hv_kvp_daemon init script hv-kvp-daemon-init is just a symbolic
link to /lib/init/upstart-job
Creating a new symbolic link titled hv-vss-daemon-init that would
start the daemon /usr/sbin/hv_vss_daemon_{version number} should solve
the problem.
Thanks,
Abhishek
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hv-kvp-daemon-init/+bug/1235025/+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 1233376] [NEW] hv_kvp_daemon is missing from linux-extras
Public bug reported:
ver=$(uname -r)
/sbin/hv_kvp_daemon_${ver$-*} is missing from linux-tools on 13.10.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 30 18:18 seq
crw-rw 1 root audio 116, 33 Sep 30 18:18 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.12.5-0ubuntu1
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:
CurrentDmesg:
[ 1546.435641] systemd-udevd[2477]: starting version 204
[ 8567.655927] init: hv-kvp-daemon-init main process (9295) terminated with
status 2
DistroRelease: Ubuntu 13.10
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
MarkForUpload: True
Package: linux-tools 3.11.0.9.11
PackageArchitecture: amd64
PciMultimedia:
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic
root=UUID=3343792a-da3d-4534-aa85-a0b1bcd70ffe ro console=tty1 console=ttyS0
earlyprintk=ttyS0 rootdelay=300
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
RelatedPackageVersions:
linux-restricted-modules-3.11.0-9-generic N/A
linux-backports-modules-3.11.0-9-generic N/A
linux-firmware1.115
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy uec-images
Uname: Linux 3.11.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 4426-8856-8314-6101-2634-9501-21
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation
** Affects: linux (Ubuntu)
Importance: High
Status: New
** Tags: apport-collected saucy uec-images
** Package changed: ubuntu = linux-meta (Ubuntu)
** Tags added: apport-collected saucy uec-images
** Description changed:
ver=$(uname -r)
/sbin/hv_kvp_daemon_${ver$-*} is missing from linux-tools on 13.10.
+ ---
+ AlsaDevices:
+ total 0
+ crw-rw 1 root audio 116, 1 Sep 30 18:18 seq
+ crw-rw 1 root audio 116, 33 Sep 30 18:18 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.12.5-0ubuntu1
+ 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:
+ CurrentDmesg:
+ [ 1546.435641] systemd-udevd[2477]: starting version 204
+ [ 8567.655927] init: hv-kvp-daemon-init main process (9295) terminated with
status 2
+ DistroRelease: Ubuntu 13.10
+ IwConfig:
+ eth0 no wireless extensions.
+
+ lono wireless extensions.
+ Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
+ MachineType: Microsoft Corporation Virtual Machine
+ MarkForUpload: True
+ Package: linux-tools 3.11.0.9.11
+ PackageArchitecture: amd64
+ PciMultimedia:
+
+ ProcFB: 0 hyperv_fb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic
root=UUID=3343792a-da3d-4534-aa85-a0b1bcd70ffe ro console=tty1 console=ttyS0
earlyprintk=ttyS0 rootdelay=300
+ ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
+ RelatedPackageVersions:
+ linux-restricted-modules-3.11.0-9-generic N/A
+ linux-backports-modules-3.11.0-9-generic N/A
+ linux-firmware1.115
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags: saucy uec-images
+ Uname: Linux 3.11.0-9-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+
+ dmi.bios.date: 05/23/2012
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 090006
+ dmi.board.name: Virtual Machine
+ dmi.board.vendor: Microsoft Corporation
+ dmi.board.version: 7.0
+ dmi.chassis.asset.tag: 4426-8856-8314-6101-2634-9501-21
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Microsoft Corporation
+ dmi.chassis.version: 7.0
+ dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
+ dmi.product.name: Virtual Machine
+ dmi.product.version: 7.0
+ dmi.sys.vendor: Microsoft Corporation
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
[Kernel-packages] [Bug 1233376] Dependencies.txt
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1233376/+attachment/3851891/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1233376
Title:
hv_kvp_daemon is missing from linux-extras
Status in “linux” package in Ubuntu:
New
Bug description:
ver=$(uname -r)
/sbin/hv_kvp_daemon_${ver$-*} is missing from linux-tools on 13.10.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 30 18:18 seq
crw-rw 1 root audio 116, 33 Sep 30 18:18 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.12.5-0ubuntu1
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:
CurrentDmesg:
[ 1546.435641] systemd-udevd[2477]: starting version 204
[ 8567.655927] init: hv-kvp-daemon-init main process (9295) terminated with
status 2
DistroRelease: Ubuntu 13.10
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
MarkForUpload: True
Package: linux-tools 3.11.0.9.11
PackageArchitecture: amd64
PciMultimedia:
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic
root=UUID=3343792a-da3d-4534-aa85-a0b1bcd70ffe ro console=tty1 console=ttyS0
earlyprintk=ttyS0 rootdelay=300
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
RelatedPackageVersions:
linux-restricted-modules-3.11.0-9-generic N/A
linux-backports-modules-3.11.0-9-generic N/A
linux-firmware1.115
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy uec-images
Uname: Linux 3.11.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 4426-8856-8314-6101-2634-9501-21
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
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/1233376/+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 1233376] ProcEnviron.txt
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1233376/+attachment/3851894/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1233376
Title:
hv_kvp_daemon is missing from linux-extras
Status in “linux” package in Ubuntu:
New
Bug description:
ver=$(uname -r)
/sbin/hv_kvp_daemon_${ver$-*} is missing from linux-tools on 13.10.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 30 18:18 seq
crw-rw 1 root audio 116, 33 Sep 30 18:18 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.12.5-0ubuntu1
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:
CurrentDmesg:
[ 1546.435641] systemd-udevd[2477]: starting version 204
[ 8567.655927] init: hv-kvp-daemon-init main process (9295) terminated with
status 2
DistroRelease: Ubuntu 13.10
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
MarkForUpload: True
Package: linux-tools 3.11.0.9.11
PackageArchitecture: amd64
PciMultimedia:
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic
root=UUID=3343792a-da3d-4534-aa85-a0b1bcd70ffe ro console=tty1 console=ttyS0
earlyprintk=ttyS0 rootdelay=300
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
RelatedPackageVersions:
linux-restricted-modules-3.11.0-9-generic N/A
linux-backports-modules-3.11.0-9-generic N/A
linux-firmware1.115
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy uec-images
Uname: Linux 3.11.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 4426-8856-8314-6101-2634-9501-21
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
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/1233376/+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 1233376] CRDA.txt
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1233376/+attachment/3851890/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1233376
Title:
hv_kvp_daemon is missing from linux-extras
Status in “linux” package in Ubuntu:
New
Bug description:
ver=$(uname -r)
/sbin/hv_kvp_daemon_${ver$-*} is missing from linux-tools on 13.10.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 30 18:18 seq
crw-rw 1 root audio 116, 33 Sep 30 18:18 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.12.5-0ubuntu1
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:
CurrentDmesg:
[ 1546.435641] systemd-udevd[2477]: starting version 204
[ 8567.655927] init: hv-kvp-daemon-init main process (9295) terminated with
status 2
DistroRelease: Ubuntu 13.10
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
MarkForUpload: True
Package: linux-tools 3.11.0.9.11
PackageArchitecture: amd64
PciMultimedia:
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic
root=UUID=3343792a-da3d-4534-aa85-a0b1bcd70ffe ro console=tty1 console=ttyS0
earlyprintk=ttyS0 rootdelay=300
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
RelatedPackageVersions:
linux-restricted-modules-3.11.0-9-generic N/A
linux-backports-modules-3.11.0-9-generic N/A
linux-firmware1.115
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy uec-images
Uname: Linux 3.11.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 4426-8856-8314-6101-2634-9501-21
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
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/1233376/+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 1233376] ProcCpuinfo.txt
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1233376/+attachment/3851893/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1233376
Title:
hv_kvp_daemon is missing from linux-extras
Status in “linux” package in Ubuntu:
New
Bug description:
ver=$(uname -r)
/sbin/hv_kvp_daemon_${ver$-*} is missing from linux-tools on 13.10.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 30 18:18 seq
crw-rw 1 root audio 116, 33 Sep 30 18:18 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.12.5-0ubuntu1
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:
CurrentDmesg:
[ 1546.435641] systemd-udevd[2477]: starting version 204
[ 8567.655927] init: hv-kvp-daemon-init main process (9295) terminated with
status 2
DistroRelease: Ubuntu 13.10
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
MarkForUpload: True
Package: linux-tools 3.11.0.9.11
PackageArchitecture: amd64
PciMultimedia:
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic
root=UUID=3343792a-da3d-4534-aa85-a0b1bcd70ffe ro console=tty1 console=ttyS0
earlyprintk=ttyS0 rootdelay=300
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
RelatedPackageVersions:
linux-restricted-modules-3.11.0-9-generic N/A
linux-backports-modules-3.11.0-9-generic N/A
linux-firmware1.115
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy uec-images
Uname: Linux 3.11.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 4426-8856-8314-6101-2634-9501-21
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
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/1233376/+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 1233376] Lspci.txt
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1233376/+attachment/3851892/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1233376
Title:
hv_kvp_daemon is missing from linux-extras
Status in “linux” package in Ubuntu:
New
Bug description:
ver=$(uname -r)
/sbin/hv_kvp_daemon_${ver$-*} is missing from linux-tools on 13.10.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 30 18:18 seq
crw-rw 1 root audio 116, 33 Sep 30 18:18 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.12.5-0ubuntu1
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:
CurrentDmesg:
[ 1546.435641] systemd-udevd[2477]: starting version 204
[ 8567.655927] init: hv-kvp-daemon-init main process (9295) terminated with
status 2
DistroRelease: Ubuntu 13.10
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
MarkForUpload: True
Package: linux-tools 3.11.0.9.11
PackageArchitecture: amd64
PciMultimedia:
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic
root=UUID=3343792a-da3d-4534-aa85-a0b1bcd70ffe ro console=tty1 console=ttyS0
earlyprintk=ttyS0 rootdelay=300
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
RelatedPackageVersions:
linux-restricted-modules-3.11.0-9-generic N/A
linux-backports-modules-3.11.0-9-generic N/A
linux-firmware1.115
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy uec-images
Uname: Linux 3.11.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 4426-8856-8314-6101-2634-9501-21
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
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/1233376/+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 1233376] UdevLog.txt
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1233376/+attachment/3851898/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1233376
Title:
hv_kvp_daemon is missing from linux-extras
Status in “linux” package in Ubuntu:
New
Bug description:
ver=$(uname -r)
/sbin/hv_kvp_daemon_${ver$-*} is missing from linux-tools on 13.10.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 30 18:18 seq
crw-rw 1 root audio 116, 33 Sep 30 18:18 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.12.5-0ubuntu1
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:
CurrentDmesg:
[ 1546.435641] systemd-udevd[2477]: starting version 204
[ 8567.655927] init: hv-kvp-daemon-init main process (9295) terminated with
status 2
DistroRelease: Ubuntu 13.10
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
MarkForUpload: True
Package: linux-tools 3.11.0.9.11
PackageArchitecture: amd64
PciMultimedia:
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic
root=UUID=3343792a-da3d-4534-aa85-a0b1bcd70ffe ro console=tty1 console=ttyS0
earlyprintk=ttyS0 rootdelay=300
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
RelatedPackageVersions:
linux-restricted-modules-3.11.0-9-generic N/A
linux-backports-modules-3.11.0-9-generic N/A
linux-firmware1.115
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy uec-images
Uname: Linux 3.11.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 4426-8856-8314-6101-2634-9501-21
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
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/1233376/+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 1233376] WifiSyslog.txt
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1233376/+attachment/3851899/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1233376
Title:
hv_kvp_daemon is missing from linux-extras
Status in “linux” package in Ubuntu:
New
Bug description:
ver=$(uname -r)
/sbin/hv_kvp_daemon_${ver$-*} is missing from linux-tools on 13.10.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 30 18:18 seq
crw-rw 1 root audio 116, 33 Sep 30 18:18 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.12.5-0ubuntu1
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:
CurrentDmesg:
[ 1546.435641] systemd-udevd[2477]: starting version 204
[ 8567.655927] init: hv-kvp-daemon-init main process (9295) terminated with
status 2
DistroRelease: Ubuntu 13.10
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
MarkForUpload: True
Package: linux-tools 3.11.0.9.11
PackageArchitecture: amd64
PciMultimedia:
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic
root=UUID=3343792a-da3d-4534-aa85-a0b1bcd70ffe ro console=tty1 console=ttyS0
earlyprintk=ttyS0 rootdelay=300
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
RelatedPackageVersions:
linux-restricted-modules-3.11.0-9-generic N/A
linux-backports-modules-3.11.0-9-generic N/A
linux-firmware1.115
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy uec-images
Uname: Linux 3.11.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 4426-8856-8314-6101-2634-9501-21
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
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/1233376/+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 1233376] ProcInterrupts.txt
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1233376/+attachment/3851895/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1233376
Title:
hv_kvp_daemon is missing from linux-extras
Status in “linux” package in Ubuntu:
New
Bug description:
ver=$(uname -r)
/sbin/hv_kvp_daemon_${ver$-*} is missing from linux-tools on 13.10.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 30 18:18 seq
crw-rw 1 root audio 116, 33 Sep 30 18:18 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.12.5-0ubuntu1
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:
CurrentDmesg:
[ 1546.435641] systemd-udevd[2477]: starting version 204
[ 8567.655927] init: hv-kvp-daemon-init main process (9295) terminated with
status 2
DistroRelease: Ubuntu 13.10
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
MarkForUpload: True
Package: linux-tools 3.11.0.9.11
PackageArchitecture: amd64
PciMultimedia:
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic
root=UUID=3343792a-da3d-4534-aa85-a0b1bcd70ffe ro console=tty1 console=ttyS0
earlyprintk=ttyS0 rootdelay=300
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
RelatedPackageVersions:
linux-restricted-modules-3.11.0-9-generic N/A
linux-backports-modules-3.11.0-9-generic N/A
linux-firmware1.115
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy uec-images
Uname: Linux 3.11.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 4426-8856-8314-6101-2634-9501-21
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
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/1233376/+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 1233376] ProcModules.txt
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1233376/+attachment/3851896/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1233376
Title:
hv_kvp_daemon is missing from linux-extras
Status in “linux” package in Ubuntu:
New
Bug description:
ver=$(uname -r)
/sbin/hv_kvp_daemon_${ver$-*} is missing from linux-tools on 13.10.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Sep 30 18:18 seq
crw-rw 1 root audio 116, 33 Sep 30 18:18 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.12.5-0ubuntu1
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:
CurrentDmesg:
[ 1546.435641] systemd-udevd[2477]: starting version 204
[ 8567.655927] init: hv-kvp-daemon-init main process (9295) terminated with
status 2
DistroRelease: Ubuntu 13.10
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: Microsoft Corporation Virtual Machine
MarkForUpload: True
Package: linux-tools 3.11.0.9.11
PackageArchitecture: amd64
PciMultimedia:
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic
root=UUID=3343792a-da3d-4534-aa85-a0b1bcd70ffe ro console=tty1 console=ttyS0
earlyprintk=ttyS0 rootdelay=300
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
RelatedPackageVersions:
linux-restricted-modules-3.11.0-9-generic N/A
linux-backports-modules-3.11.0-9-generic N/A
linux-firmware1.115
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy uec-images
Uname: Linux 3.11.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 4426-8856-8314-6101-2634-9501-21
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
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/1233376/+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 1223499] Re: Enable TRIM support in Ubuntu for Hyper-V
tested new proposed kernel, and it works: utlemming@utl-0917-s3a:~$ cat /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_2/host3/target3:0:1/3:0:1:0/scsi_disk/3:0:1:0/thin_provisioning 1 utlemming@utl-0917-s3a:~$ cat /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_1/host2/target2:0:0/2:0:0:0/scsi_disk/2:0:0:0/provisioning_mode unmap utlemming@utl-0917-s3a:~$ cat /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_2/host3/target3:0:1/3:0:1:0/scsi_disk/3:0:1:0/provisioning_mode unmap utlemming@utl-0917-s3a:~$ uname -a Linux utl-0917-s3a 3.11.0-8-generic #14~lp1223499v201309131830 SMP Fri Sep 13 17:31:57 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- 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/1223499 Title: Enable TRIM support in Ubuntu for Hyper-V Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Fix Released Bug description: Microsoft has asked for us to enable unmap support Hyper-V targets. The current kernels for 12.04 and later do not correctly identify the devices as being capable of supporting unmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223499/+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 1223499] Re: Enable TRIM support in Ubuntu for Hyper-V
Microsoft reports that the proposed fix does work from the hypervisor level. ** Package changed: ubuntu = linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1223499 Title: Enable TRIM support in Ubuntu for Hyper-V Status in “linux-meta” package in Ubuntu: Confirmed Status in “linux-meta” source package in Saucy: Confirmed Bug description: Microsoft has asked for us to enable unmap support Hyper-V targets. The current kernels for 12.04 and later do not correctly identify the devices as being capable of supporting unmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1223499/+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 1193172] Re: Populating Hyper-V MSR for Ubuntu 13.10
Raising priority. MS has indicated this is a critical need for 13.10. ** Changed in: linux (Ubuntu) Importance: Medium = High -- 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/1193172 Title: Populating Hyper-V MSR for Ubuntu 13.10 Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Confirmed Bug description: For new distribution releases the Hyper-V team is trying to better populate the Hyper-V guest ID. Our specific goal is to identify any given distribution and its release version. With this intent we worked with SUSE to include a patch in their upcoming SLES 11 SP3 release. The patch is available in the following issue: https://bugzilla.novell.com/show_bug.cgi?id=814005 In case you cannot access the bug then the entire patch is as follows: --- linux-3.9-rc5-master.orig/drivers/hv/hv.c +++ linux-3.9-rc5-master/drivers/hv/hv.c @@ -134,6 +134,8 @@ int hv_init(void) int max_leaf; union hv_x64_msr_hypercall_contents hypercall_msr; void *virtaddr = NULL; + __u8 d1 = 0x10; /* SuSE */ + __u16 d2 = 0x0; /* -d of a.b.c-d */ memset(hv_context.synic_event_page, 0, sizeof(void *) * NR_CPUS); memset(hv_context.synic_message_page, 0, @@ -148,7 +150,7 @@ int hv_init(void) /* * Write our OS ID. */ - hv_context.guestid = generate_guest_id(0, LINUX_VERSION_CODE, 0); + hv_context.guestid = generate_guest_id(d1, LINUX_VERSION_CODE, d2); wrmsrl(HV_X64_MSR_GUEST_OS_ID, hv_context.guestid); /* See if the hypercall page is already set */ We request you to include the same patch for Ubuntu 13.10 with the below modifications: 1. In place of __u8 d1 = 0x10; /* SuSE */ we would request you to add the following line: __u8 d1 = 0x80; /* Canonical */ 2. In place of __u16 d2 = 0x0; /* -d of a.b.c-d */ we would request you to add the correct ‘-d’ of the Linux kernel version for Ubuntu 13.10 __u16 d2 = 0x0; /* -d of a.b.c-d */ For Ubuntu 13.10, I noticed that uname –r returns “3.9.0-6-generic”. We would like to populate d2 with 6. It would be best if you guys could automate the process of populating that string. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1193172/+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 1202700] Re: saucy kernel 300 second hang before root mounted rw on azure
To clarify, this is a boot regression from 13.04 to 13.10. On previous versions it takes a few seconds (~15 to ~20) to boot completely. -- 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/1202700 Title: saucy kernel 300 second hang before root mounted rw on azure Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: on azure saucy images (b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy- 13_10-amd64-server-20130718-en-us-30GB in 'US East' location). I get a 300 second timeout before / is mounted RW. See attached dmesg for full dmesg. snippet here. [6.974849] scsi3 : storvsc_host_t [6.977249] scsi 3:0:1:0: Direct-Access Msft Virtual Disk 1.0 PQ: 0 ANSI: 4 [6.981087] sda: sda1 [6.983419] sd 3:0:1:0: Attached scsi generic sg2 type 0 [6.986119] sd 3:0:1:0: [sdb] 41943040 512-byte logical blocks: (21.4 GB/20.0 GiB) [6.989874] sd 3:0:1:0: [sdb] Write Protect is off [6.992325] sd 3:0:1:0: [sdb] Mode Sense: 0f 00 00 00 [6.992353] sd 2:0:0:0: [sda] Attached SCSI disk [6.995243] sd 3:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6.999603] scsi4 : storvsc_host_t [7.002527] scsi scan: INQUIRY result too short (5), using 36 [7.006224] scsi scan: INQUIRY result too short (5), using 36 [7.009942] sdb: sdb1 [7.011837] scsi5 : storvsc_host_t [7.015888] scsi scan: INQUIRY result too short (5), using 36 [7.019459] sd 3:0:1:0: [sdb] Attached SCSI disk [7.022017] scsi scan: INQUIRY result too short (5), using 36 [ 303.184698] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 305.379387] EXT4-fs (sda1): re-mounted. Opts: discard --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 18 14:08 seq crw-rw 1 root audio 116, 33 Jul 18 14:08 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.11-0ubuntu1 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: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 356.806779] init: cloud-config main process (1126) terminated with status 1 DistroRelease: Ubuntu 13.10 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine MarkForUpload: True Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=19f8b960-2ffd-4241-befd-fc605380cba6 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 ProcVersionSignature: User Name 3.10.0-3.12-generic 3.10.1 RelatedPackageVersions: linux-restricted-modules-3.10.0-3-generic N/A linux-backports-modules-3.10.0-3-generic N/A linux-firmware1.112 RfKill: Error: [Errno 2] No such file or directory Tags: saucy uec-images Uname: Linux 3.10.0-3-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev video dmi.bios.date: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 2175-9033-8610-7819-8007-6304-66 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine 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/1202700/+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
