[Kernel-packages] [Bug 1565841] Re: Provide zfcpdump-infrastructure with Ubuntu 16.04
--- Comment From heinz-werner_se...@de.ibm.com 2016-04-15 02:59 EDT--- Changed TargetMilestone from 16.04 -> 16.10. Will not make GA of 16.04 ** Tags removed: targetmilestone-inin1604 ** Tags added: targetmilestone-inin1610 -- 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/1565841 Title: Provide zfcpdump-infrastructure with Ubuntu 16.04 Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in s390-tools package in Ubuntu: New Status in linux source package in Xenial: New Status in s390-tools source package in Xenial: New Status in linux source package in y-series: New Status in s390-tools source package in y-series: New Bug description: == Comment: #0 - Heinz-Werner Seeck - 2016-04-04 10:59:10 == Please provide the zfcpdump infrastructure to Ubuntu 16.04 , to enhance RAS capabilities and better Service enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1565841/+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 788259] Re: Bluetooth Can't Connect to Devices After Suspend
Closing that outdated report as EOL has been reached long time ago ** Changed in: bluez (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/788259 Title: Bluetooth Can't Connect to Devices After Suspend Status in bluez package in Ubuntu: Invalid Bug description: Binary package hint: bluez I'm running Ubuntu 10.04 on a Macbook 5.5. I was using the Macbook's builtin Bluetooth, which working fine, even with suspend. However, this recently got fried, so I was forced to start using a Targus USB Bluetooth adapter. The adapter works fine after a fresh reboot. However, Bluetooth becomes unusable after suspend. Before suspend, I can use the "Bluetooth Preferences" dialog to detect and pair to bluetooth devices, but after suspend, it shows the devices I had previously paired with, but doesn't detect them or provide a way to reconnect. The only solution I've found is to remove the pairing, set my device back into pairing mode, and repair, which is very frustrating. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: bluetooth 4.60-0ubuntu8 Uname: Linux 2.6.32-020632-generic x86_64 NonfreeKernelModules: nvidia wl Architecture: amd64 Date: Wed May 25 13:37:42 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) InterestingModules: bnep btusb MachineType: Apple Inc. MacBookPro5,5 PackageArchitecture: all ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-020632-generic root=UUID=b3f45a1c-0d35-43ce-bb7e-32400f29bd9e ro vga=792 splash quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: bluez dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP55.88Z.00AC.B03.0906151708 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F2268AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8: dmi.product.name: MacBookPro5,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: USB BD Address: 00:19:0E:09:17:4D ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:6948 acl:23 sco:0 events:757 errors:0 TX bytes:1346514 acl:1405 sco:0 commands:43 errors:0 rfkill: 5: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/788259/+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 1570754] [NEW] Graphics freeze after 6 - 48 hours, applications carry on working
Public bug reported: We're testing Intel Compute Stick (http://www.cnet.com/products/intel- compute-stick/specs/) with Ubuntu 14.04 for our google chrome based digital signage solution. Unfortunately, the graphics freeze after a random period of time which I've noticed to be anything from 6 to 48 hours. With the graphics frozen, the only thing I can do is move the mouse pointer and everything else is stuck. I've set up SSH server on it and after logging into the device I can see that all the applications are still running as expected. I doubt that it has anything to do with a faulty device as I was able to reproduce it on 7 different compute sticks. Kernel: 3.16.0-69-generic (but have also reproduced on 3.16.0-45-generic and 3.16.0-70-generic) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-69-generic 3.16.0-69.89~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-69.89~14.04.1-generic 3.16.7-ckt25 Uname: Linux 3.16.0-69-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Apr 15 10:32:40 2016 InstallationDate: Installed on 2016-03-23 (22 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" Linuxium - Beta Intel Z3735F (20150811) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - Graphics freeze after 6 - 48, applications carry on working + Graphics freeze after 6 - 48 hours, applications carry on working -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1570754 Title: Graphics freeze after 6 - 48 hours, applications carry on working Status in linux-lts-utopic package in Ubuntu: New Bug description: We're testing Intel Compute Stick (http://www.cnet.com/products/intel- compute-stick/specs/) with Ubuntu 14.04 for our google chrome based digital signage solution. Unfortunately, the graphics freeze after a random period of time which I've noticed to be anything from 6 to 48 hours. With the graphics frozen, the only thing I can do is move the mouse pointer and everything else is stuck. I've set up SSH server on it and after logging into the device I can see that all the applications are still running as expected. I doubt that it has anything to do with a faulty device as I was able to reproduce it on 7 different compute sticks. Kernel: 3.16.0-69-generic (but have also reproduced on 3.16.0-45-generic and 3.16.0-70-generic) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-69-generic 3.16.0-69.89~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-69.89~14.04.1-generic 3.16.7-ckt25 Uname: Linux 3.16.0-69-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Apr 15 10:32:40 2016 InstallationDate: Installed on 2016-03-23 (22 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" Linuxium - Beta Intel Z3735F (20150811) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1570754/+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 1570441] Re: Kernel Panic in Ubuntu 16.04 netboot installer
Ugh, looking this morning there is a whole bulk of patches referring to be
fixes for the initial
1f12e32f4cd5 ("x86/topology: Create logical package id")
* commit ee6825c80e870fff1a370c718ec77022ade0889b
x86/topology: Fix AMD core count
* commit ed6069be7204541c1da532ad8bbf892e34513552
xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op
* commit 3e8db2246b434c6b18a6a9f09904038bddcf76c7
x86/topology: Use total_cpus not nr_cpu_ids for logical packages
* commit 63d1e995be455ae9196270eb4b789de21afd42ed
x86/topology: Fix Intel HT disable
* commit b5d5f27d938fb6fc8d3202704e699d2694a02da6
x86/topology: Fix logical package mapping
--
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/1570441
Title:
Kernel Panic in Ubuntu 16.04 netboot installer
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
Hello,
we are working with the Ubuntu 16.04 developer preview. Yesterday we
observed a kernel panic of the installer kernel on one of our machines.
The machine is of type
Supermicro X10DRH LN4/X10DRH-CLN4, BIOS s1.0b 12/01/2015
We are installing the machine via PXEboot with the netboot installer
system using the following kernel/initrd:
dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/initrd.gz
dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/linux
When using this version the kernel crashes (see attached log file). We
have also tried the version 447 instead of 446. This version shows
the same effect.
Some time ago we worked with the installer version 441. This release
worked as expected.
Someone out there knows what has changed? It seems that the kernel has a
problem with the harddisk IO system. In our machine the mpt3sas disk
controller is required to get access to the harddisks.
If I should test some new stuff please let me know. Or if I can help you
in some other way to solve this issue contact me.
Thank you for your help
Dr. Johann Pfefferl
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570441/+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 1531768] Re: [arm64] locks up a few minutes after booting
Meh, of course this came back. Only not a few minutes after booting any more, but two days. ** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed ** Summary changed: - [arm64] locks up a few minutes after booting + [arm64] locks up some time after booting -- 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/1531768 Title: [arm64] locks up some time after booting Status in linux package in Ubuntu: Confirmed Bug description: I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I want to use for armhf autopkgtesting in LXD). I started with wily as that has lxd available (it's not yet available in trusty nor the PPA for arm64). However, pretty much any LXD task that I do (I haven't tried much else) on this machine takes unbearably long. A simple "lxc profile set default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes. I see tons of [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0 [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds. in dmesg (the attached apport info has the complete dmesg). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 09:18 seq crw-rw 1 root audio 116, 33 Jan 7 09:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Jan 7 09:24:01 2016 IwConfig: eth0 no wireless extensions. lono wireless extensions. lxcbr0no wireless extensions. Lspci: 00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008] Subsystem: Red Hat, Inc Device [1af4:1100] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic root=LABEL=cloudimg-rootfs earlyprintk RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531768/+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 1570441] Re: Kernel Panic in Ubuntu 16.04 netboot installer
But then 1f12e32f4cd5 ("x86/topology: Create logical package id") is a
4.6-rc1 change which is not in the 4.4.x used in Xenial.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1570441
Title:
Kernel Panic in Ubuntu 16.04 netboot installer
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
Hello,
we are working with the Ubuntu 16.04 developer preview. Yesterday we
observed a kernel panic of the installer kernel on one of our machines.
The machine is of type
Supermicro X10DRH LN4/X10DRH-CLN4, BIOS s1.0b 12/01/2015
We are installing the machine via PXEboot with the netboot installer
system using the following kernel/initrd:
dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/initrd.gz
dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/linux
When using this version the kernel crashes (see attached log file). We
have also tried the version 447 instead of 446. This version shows
the same effect.
Some time ago we worked with the installer version 441. This release
worked as expected.
Someone out there knows what has changed? It seems that the kernel has a
problem with the harddisk IO system. In our machine the mpt3sas disk
controller is required to get access to the harddisks.
If I should test some new stuff please let me know. Or if I can help you
in some other way to solve this issue contact me.
Thank you for your help
Dr. Johann Pfefferl
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570441/+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 994931] Re: Altering use_tempaddr drops all IPv6 addresses
Ping. The test kernel seems to fix this. Could it be pushed to Trusty? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/994931 Title: Altering use_tempaddr drops all IPv6 addresses Status in Linux: Invalid Status in linux package in Ubuntu: Confirmed Status in linux source package in Precise: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: Invalid Bug description: $ uname -a Linux expvr-alnilam 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 UTC 2012 i686 i686 i386 GNU/Linux $ sysctl net.ipv6.conf.eth2.use_tempaddr net.ipv6.conf.eth2.use_tempaddr = 2 # (as per the default /etc/sysctl.d/10-ipv6-privacy.conf in 12.04) # Add a static IPv6 address: $ sudo ip addr add 2001:470:9321:f003::1122/64 dev eth2 # Verify that it has been set up, and that a temporary address and a SLAAC address also exist: $ ip -6 addr list dev eth2 4: eth2: mtu 1500 qlen 1000 inet6 2001:470:9321:f003:74e3:aa2b:7ee5:c002/64 scope global temporary dynamic valid_lft 86393sec preferred_lft 14393sec inet6 2001:470:9321:f003:6c97:24ff:fe3f:263b/64 scope global dynamic valid_lft 86393sec preferred_lft 14393sec inet6 2001:470:9321:f003::1122/64 scope global valid_lft forever preferred_lft forever inet6 fe80::6c97:24ff:fe3f:263b/64 scope link valid_lft forever preferred_lft forever # Disable RFC 4941 temporary addresses: $ sudo sysctl net.ipv6.conf.eth2.use_tempaddr=0 net.ipv6.conf.eth2.use_tempaddr = 0 $ ip -6 addr list dev eth2 4: eth2: mtu 1500 qlen 1000 inet6 fe80::6c97:24ff:fe3f:263b/64 scope link tentative valid_lft forever preferred_lft forever I.e. on setting use_tempaddr=0, _all_ IPv6 addresses are removed, including statically-configured and non-temporary SLAAC-configured addresses. (The link-local address reappears quickly but the 'tentative' flag indicates that it has been newly re-added. The SLAAC address reappears after a slightly longer interval as the kernel continues to undergo SLAAC, but the static address is gone forever unless manually reinstated.) The same happens if use_tempaddr is changed from 0 back to 2. The expected outcome is that only temporary addresses are affected by a change to use_tempaddr. --- AcpiTables: AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 May 5 03:53 seq crw-rw---T 1 root audio 116, 33 May 5 03:53 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 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: DistroRelease: Ubuntu 12.04 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory Lsusb: Error: [Errno 2] No such file or directory Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen.linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=b16ffd9c-a54a-4dd3-a839-16c382ea8787 ro console=hvc0 ProcModules: lp 17455 0 - Live 0x parport 40930 1 lp, Live 0x xenfs 17877 1 - Live 0x ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic-pae N/A linux-backports-modules-3.2.0-24-generic-pae N/A linux-firmware1.79 RfKill: Error: [Errno 2] No such file or directory Tags: precise Uname: Linux 3.2.0-24-generic-pae i686 UpgradeStatus: Upgraded to precise on 2012-05-05 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/994931/+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 1564475] Comment bridged from LTC Bugzilla
--- Comment From thorsten.di...@de.ibm.com 2016-04-15 05:15 EDT--- (In reply to comment #25) > @thorsten > > If I understand correctly cio_ignore command needs to be on the running > instance that is about to crash, rather than on the re-exec kernel. Thus it @Dimitri, that's not correct. The LPAR kdump would also work fine, if the zipl.conf has NO cio_ignore statement, just the KDUMP_CMDLINE_APPEND= statement. > needs to be computed and added to e.g. /etc/zipl.conf. At the moment we do > not generate/update /etc/zipl.conf in an automated way, but the more I think > about it the better it sounds to e.g. able to specify all crashdump > parameters, computed cio_ignore, correct root= argument, and generate menu > items for every installed ubuntu kernel (rather than just the last one), and > recovery stanzas too. I'll open a wishlist bug about that. That sounds reasonable. > BTW, does it make sense to compute and use `cio_ignore -k -u` generated > command line by default? on one hand kernel will use less memory, on the > other hand `lszdev` will be quite empty and one will have a harder time to > discover additional devices one can bring online. Exactly, that is the conflict. From performance point of view, it is appreciable to have cio_ignore enabled, since an LPAR boot with thousands of devices takes a little bit longer. For our Test LPARs with many shared resources we prefer and recommend to have cio_ignore enabled. In a resonably set up customer environment the disadvantage of the more inconvenient device handling is more relevant than the benfits of cio_ignore. Feel free to hear other opinions on that topic, e.g. from your z Systems experts Frank and Christian ;-) But for the KDUMP_CMDLINE_APPEND= statement is does NOT harm, and I recommend to add this automatically upon every restart of kdump-tools.service > I have, for now, added things to https://wiki.ubuntu.com/S390X -> feel free > to edit and/or improve that. And I will open a new bug report to get those > updates into the Ubuntu Server Guide. That reads good and is sufficient to close this bug. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1564475 Title: 128M is not enough for kdump on s390 LPARs Status in Ubuntu on IBM z Systems: Fix Released Status in makedumpfile package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in zipl-installer package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Invalid Status in s390-tools source package in Xenial: Fix Released Status in zipl-installer source package in Xenial: Fix Released Bug description: == Comment: #0 - Michael Holzheu - 2016-03-31 10:59:26 == With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt"). On z/VM guests 128M seems to be sufficient. One reason on our test LPAR is that a lot of devices are attached (see attachment "lscss_lpar.txt") which are not required for kdump but consume a lot of memory because the s390 CIO layer allocates data structures in the kernel for those devices. We can disable the devices by using the "cio_ignore=" kernel parameter in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD 0.0.e934 for /var/crash, we added the following line to disable the devices: KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1 cio_ignore=all,!condev,!0.0.e934" For more information on the "cio_ignore=" kernel parameter see: https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO Even with "cio_ignore=" we still get out-of-memory with "crashkernel=128M". With "crashkernel=196M" and "cio_ignore=" we are able to create a dump on our LPAR. We currently do not know why kdump with "cio_ignore=" on LPAR consumes more memory than on z/VM guests. == Comment: #1 - Michael Holzheu - 2016-03-31 11:03:15 == Kernel messages of kdump out-of-memory crash on LPAR with many devices without cio_ignore parameter and 128M crashkernel memory. == Comment: #2 - Michael Holzheu - 2016-03-31 11:04:10 == Output of lscss showing all attached (not online) devices on the LPAR. == Comment: #3 - Michael Holzheu - 2016-03-31 11:07:35 == To solve this issue our recommendation is: 1) Increase "crashkernel=" default to 196M on Ubuntu for s390. 2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used to decrease memory consumption for kdump on systems with many devices that are not required for kdump. The most user friendly solution would be to automatically determine the required kdump devices and set the correct "cio_ignore=" kernel parameter. But this is not trivial, because it can be difficult to find out the required devices for stacked setups like LVM or for network dump. To ma
[Kernel-packages] [Bug 1570195] Re: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO
Repro: OVS-DPDK starting up seems fine initializing my non-blacklisted card DPDK_OPTS are '--dpdk -c 0x6 -n 4 --pci-blacklist :00:03.0 -m 2048' Allowing PMDs on two CPUs consuming 2G of huge pages Before adding Ports config is done with ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=2 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0x6 Port is added like: ovs-vsctl add-port ovsdpdkbr0 dpdk0 -- set Interface dpdk0 type=dpdk Two PMDs are seen dpif_netdev|INFO|Created 2 pmd threads on numa node 0 bridge|INFO|bridge ovsdpdkbr0: added interface dpdk0 on port 1 dpif_netdev(pmd12)|INFO|Core 2 processing port 'dpdk0' dpif_netdev(pmd13)|INFO|Core 1 processing port 'dpdk0' PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 26062 root 10 -10 2816828 105612 16328 R 99.9 1.7 1:09.46 pmd12 26061 root 10 -10 2816828 105612 16328 R 99.9 1.7 1:09.42 pmd13 Now I should be in a similar state as you are. I know the assumption so far was that the reboot (which resets the #queues on the device) might be involved. But I first wanted to try what changing queues without reboot would do. Even setting it down from 4 to 3 (remember I only use 2 actively) goes into the block. ethtool -L eth1 combined 3 => I can see a hang of the ethtool program Good thing: at least it seems we can remove the reboot out of our thinking. Just changing #queues with (?OVS?)DPDK attached seems to be very unhappy. Please note the discussion that could be related: http://dpdk.org/ml/archives/dev/2016-April/037443.html For confirmation @Thiago - does for you also the ethtool program hang, or the full guest? Next steps: - gather debug data on hanging ethtool - check what happens if we ethtool after we stopped OVS-DPDK (match upstream discussion) - check what happens if we have testpmd enabled instead of openvswitch-dpdk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO Status in dpdk package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it up. https://help.ubuntu.com/16.04/serverguide/DPDK.html service openvswitch-switch stop service dpdk stop OVS DPDK Options (/etc/default/openvswitch-switch): -- DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist :00:03.0,:00:04.0' -- service dpdk start service openvswitch-switch start - Enable multi-queue on OVS+DPDK inside of the VM: ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00 * Multi-queue apparently works! ovs-vswitchd consumes more that 100% of CPU, meaning that it multi-queue is there... *** Where it fails? 1- Reboot the VM and try to run ethtool again (or go straight to 2 below): ethtool -L ens5 combined 4 2- Try to fire up ens4: ip link set dev ens4 up # FAIL! Both commands hangs, consuming 100% of guest's CPU... So, it looks like a Linux fault, because it is "allowing" the DPDK VirtIO App (a user land App), to interfere with kernel devices in a strange way... Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 14 00:35 seq crw-rw 1 root audio 116, 33 Apr 14 00:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or di
[Kernel-packages] [Bug 1564807] Re: nfs causes guest system to get stuck
suspending and resuming the guest os does not trigger this problem. Only when doing it for the host os. -- 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/1564807 Title: nfs causes guest system to get stuck Status in linux package in Ubuntu: Incomplete Bug description: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders. This is syslog on the guest, from waking up until vagrant halt --force is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564807/+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 1564807] Re: nfs causes guest system to get stuck
I have tested these versions: linux-image-3.19.0-56-generic linux-image-3.16.0-67-generic linux-image-3.13.0-85-generic The initial report is wrong. It does not make the entire guest OS hang, only processes that touch the nfs mount hangs (like ls /vagrant). It can easily be recreated with this Vagrantfile: Vagrant.configure(2) do |config| config.vm.box = "ubuntu/trusty64" config.vm.network "private_network", ip: "192.168.33.10" config.vm.synced_folder ".", "/vagrant", type: "nfs" end 1. vagrant up 2. vagrant ssh # ls /vagrant works 3. suspend the host machine 4. resume the host machine 5. in the vagrant ssh terminal ls /vagrant hangs At least one other (the commenter) has the problem: http://stackoverflow.com/questions/35645041/after-suspend-guest-os- hangs-when-using-vagrant-with-nfs ** Description changed: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, - the entire guest OS will be unusable. This does not happen when using - the normal virtualbox shared folders. + every process that tried to access the nfs share will hang. This does + not happen when using the normal virtualbox shared folders. - It's not only the nfs shared folder that is unusable, the entire OS is - hanging. Even syslog does not seem to see much action. This is syslog on - the guest, from waking up until vagrant halt is completed. + This is syslog on the guest, from waking up until vagrant halt --force + is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. - - When I try to ssh to the guest system I the motd and last login: ..., but nothing more, it just hangs. - If I was already logged in the guest system through ssh then that session is unresponsive (after pressing enter). - - How can this be fixed? - How should I debug it? -- 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/1564807 Title: nfs causes guest system to get stuck Status in linux package in Ubuntu: Incomplete Bug description: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders. This is syslog on the guest, from waking up until vagrant halt --force is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564807/+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 1564807] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1564807/+attachment/4637516/+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/1564807 Title: nfs causes guest system to get stuck Status in linux package in Ubuntu: Confirmed Bug description: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders. This is syslog on the guest, from waking up until vagrant halt --force is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 09:07 seq crw-rw 1 root audio 116, 33 Apr 15 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=6872cb1e-3766-4ff3-9de5-11ffd99c3fc9 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.13.0-85-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564807/+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 1564807] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1564807/+attachment/4637514/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1564807 Title: nfs causes guest system to get stuck Status in linux package in Ubuntu: Confirmed Bug description: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders. This is syslog on the guest, from waking up until vagrant halt --force is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 09:07 seq crw-rw 1 root audio 116, 33 Apr 15 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=6872cb1e-3766-4ff3-9de5-11ffd99c3fc9 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.13.0-85-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564807/+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 1564807] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1564807/+attachment/4637520/+files/UdevLog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1564807 Title: nfs causes guest system to get stuck Status in linux package in Ubuntu: Confirmed Bug description: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders. This is syslog on the guest, from waking up until vagrant halt --force is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 09:07 seq crw-rw 1 root audio 116, 33 Apr 15 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=6872cb1e-3766-4ff3-9de5-11ffd99c3fc9 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.13.0-85-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564807/+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 1564807] Re: nfs causes guest system to get stuck
apport information ** Tags added: apport-collected trusty uec-images ** Description changed: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders. This is syslog on the guest, from waking up until vagrant halt --force is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Apr 15 09:07 seq + crw-rw 1 root audio 116, 33 Apr 15 09:07 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.19 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 14.04 + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 + MachineType: innotek GmbH VirtualBox + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=6872cb1e-3766-4ff3-9de5-11ffd99c3fc9 ro console=tty1 console=ttyS0 + ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-85-generic N/A + linux-backports-modules-3.13.0-85-generic N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty uec-images + Uname: Linux 3.13.0-85-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 12/01/2006 + dmi.bios.vendor: innotek GmbH + dmi.bios.version: VirtualBox + dmi.board.name: VirtualBox + dmi.board.vendor: Oracle Corporation + dmi.board.version: 1.2 + dmi.chassis.type: 1 + dmi.chassis.vendor: Oracle Corporation + dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: + dmi.product.name: VirtualBox + dmi.product.version: 1.2 + dmi.sys.vendor: innotek GmbH ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1564807/+attachment/4637513/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1564807 Title: nfs causes guest system to get stuck Status in linux package in Ubuntu: Confirmed Bug description: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders. This is syslog on the guest, from waking up until vagrant halt --force is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 09:07 seq crw-rw 1 root audio 116, 33 Apr 15 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 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 fi
[Kernel-packages] [Bug 1564807] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1564807/+attachment/4637515/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1564807 Title: nfs causes guest system to get stuck Status in linux package in Ubuntu: Confirmed Bug description: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders. This is syslog on the guest, from waking up until vagrant halt --force is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 09:07 seq crw-rw 1 root audio 116, 33 Apr 15 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=6872cb1e-3766-4ff3-9de5-11ffd99c3fc9 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.13.0-85-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564807/+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 1564807] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1564807/+attachment/4637519/+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/1564807 Title: nfs causes guest system to get stuck Status in linux package in Ubuntu: Confirmed Bug description: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders. This is syslog on the guest, from waking up until vagrant halt --force is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 09:07 seq crw-rw 1 root audio 116, 33 Apr 15 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=6872cb1e-3766-4ff3-9de5-11ffd99c3fc9 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.13.0-85-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564807/+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 1564807] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1564807/+attachment/4637518/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1564807 Title: nfs causes guest system to get stuck Status in linux package in Ubuntu: Confirmed Bug description: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders. This is syslog on the guest, from waking up until vagrant halt --force is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 09:07 seq crw-rw 1 root audio 116, 33 Apr 15 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=6872cb1e-3766-4ff3-9de5-11ffd99c3fc9 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.13.0-85-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564807/+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 1564807] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1564807/+attachment/4637517/+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/1564807 Title: nfs causes guest system to get stuck Status in linux package in Ubuntu: Confirmed Bug description: Host OS Ubuntu 15.10 Guest OS Ubuntu 14.10 Using Vagrant with nfs and Virtualbox and static ip on the private network. It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders. This is syslog on the guest, from waking up until vagrant halt --force is completed. Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com";] exiting on signal 15. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 09:07 seq crw-rw 1 root audio 116, 33 Apr 15 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=6872cb1e-3766-4ff3-9de5-11ffd99c3fc9 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 RelatedPackageVersions: linux-restricted-modules-3.13.0-85-generic N/A linux-backports-modules-3.13.0-85-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.13.0-85-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570195] Re: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO
Appears running: F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 4 0 26330 26263 20 0 7588 980 - R+ pts/2 33:52 \_ ethtool -L eth1 combined 3 All that touches it seems to get affected, so e.g. a ltrace/strace get stuck as well. Meanwhile the log on virsh console of the guest goes towards soft lockups: [ 568.394870] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ethtool:26330] [ 575.418868] INFO: rcu_sched self-detected stall on CPU [ 575.419674] 0-...: (14999 ticks this GP) idle=66d/141/0 softirq=21127/21127 fqs=14994 [ 575.420779] (t=15000 jiffies g=11093 c=11092 q=9690) More Info in the journal: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ethtool:26330] Modules linked in: openvswitch nf_defrag_ipv6 nf_conntrack isofs ppdev kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul parport_pc parport joydev serio_raw iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear psmouse aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd floppy CPU: 0 PID: 26330 Comm: ethtool Not tainted 4.4.0-18-generic #34-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 task: 8801b747d280 ti: 8800ba58c000 task.ti: 8800ba58c000 RIP: 0010:[] [] virtnet_send_command+0xf3/0x150 RSP: 0018:8800ba58fb60 EFLAGS: 0246 RAX: RBX: 8800bba62840 RCX: 8801b64a9000 RDX: c010 RSI: 8800ba58fb64 RDI: 8800bba6c400 RBP: 8800ba58fbf8 R08: 0004 R09: 8801b9001b00 R10: 8801b671b080 R11: 0246 R12: 0002 R13: 8800ba58fb88 R14: R15: 0004 FS: 7fb57d56c700() GS:8801bfc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fb57cd7b680 CR3: ba85a000 CR4: 001406f0 Stack: 8800ba58fc28 ea0002ee9882 00020940 ea0002ee9882 00010942 8800ba58fb68 8800ba58fc10 8800ba58fb88 Call Trace: [] virtnet_set_queues+0x9a/0x100 [] virtnet_set_channels+0x52/0xa0 [] ethtool_set_channels+0xfc/0x140 [] dev_ethtool+0x40d/0x1d70 [] ? page_add_file_rmap+0x25/0x60 [] ? __rtnl_unlock+0x15/0x20 [] ? netdev_run_todo+0x61/0x320 [] ? unlock_page+0x69/0x70 [] dev_ioctl+0x182/0x580 [] ? handle_mm_fault+0xe44/0x1820 [] sock_do_ioctl+0x42/0x50 [] sock_ioctl+0x1d2/0x290 [] do_vfs_ioctl+0x29f/0x490 [] ? __do_page_fault+0x1b4/0x400 [] SyS_ioctl+0x79/0x90 [] entry_SYSCALL_64_fastpath+0x16/0x71 Code: 44 89 e2 4c 89 6c c5 b0 e8 3b dc ec ff 48 8b 7b 08 e8 f2 db ec ff 84 c0 75 11 eb 24 48 8b 7b 08 e8 d3 d6 ec ff 84 c0 75 17 f3 90 <48> 8b 7b 08 48 8d b5 6c ff ff ff e8 4d e0 ec ff 48 85 c0 74 dc Sometimes there is this on top [] ? virtnet_send_command+0x103/0x150 Need to check if there is a loop in virtnet_set_queues that could call virtnet_send_command infinitely. Being stuck in the kernel explains why signals and traces can't attach. Note - we are already on todays: Linux guest-virtio-dpdk 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:01:02 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux I seem to be able to work on old ssh sessions, but new sessions get stuck as well - need to prepare more next time :-) Next Steps: - analyze code pointed out by hangs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO Status in dpdk package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install
[Kernel-packages] [Bug 1570775] [NEW] makekdump should re-exec with cio_ignore on s390x
Public bug reported: As per https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19 We should re-exec with cio_ignore lines. As per report there, it should result in lowered required crashdump setting. Hypothetically, one should be able to test this imperially by lowering crashdump memory settings until kdump does not succeed anymore. And then generated and append `cio_ignore -k -u` to the KDUMP_CMDLINE_APPEND= and see that kdump starts working again with a lower memory usage. Once this is developed / verified / tested, we should probably SRU this back to xenial. ** Affects: makedumpfile (Ubuntu) Importance: Undecided Status: New ** Tags: s390x ** Tags added: s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1570775 Title: makekdump should re-exec with cio_ignore on s390x Status in makedumpfile package in Ubuntu: New Bug description: As per https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19 We should re-exec with cio_ignore lines. As per report there, it should result in lowered required crashdump setting. Hypothetically, one should be able to test this imperially by lowering crashdump memory settings until kdump does not succeed anymore. And then generated and append `cio_ignore -k -u` to the KDUMP_CMDLINE_APPEND= and see that kdump starts working again with a lower memory usage. Once this is developed / verified / tested, we should probably SRU this back to xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1570775/+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 1564475] Re: 128M is not enough for kdump on s390 LPARs
I see, thanks a lot!. Opened https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1570775 to generate and use cio_ignore in kdump. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1564475 Title: 128M is not enough for kdump on s390 LPARs Status in Ubuntu on IBM z Systems: Fix Released Status in makedumpfile package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in zipl-installer package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Invalid Status in s390-tools source package in Xenial: Fix Released Status in zipl-installer source package in Xenial: Fix Released Bug description: == Comment: #0 - Michael Holzheu - 2016-03-31 10:59:26 == With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt"). On z/VM guests 128M seems to be sufficient. One reason on our test LPAR is that a lot of devices are attached (see attachment "lscss_lpar.txt") which are not required for kdump but consume a lot of memory because the s390 CIO layer allocates data structures in the kernel for those devices. We can disable the devices by using the "cio_ignore=" kernel parameter in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD 0.0.e934 for /var/crash, we added the following line to disable the devices: KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1 cio_ignore=all,!condev,!0.0.e934" For more information on the "cio_ignore=" kernel parameter see: https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO Even with "cio_ignore=" we still get out-of-memory with "crashkernel=128M". With "crashkernel=196M" and "cio_ignore=" we are able to create a dump on our LPAR. We currently do not know why kdump with "cio_ignore=" on LPAR consumes more memory than on z/VM guests. == Comment: #1 - Michael Holzheu - 2016-03-31 11:03:15 == Kernel messages of kdump out-of-memory crash on LPAR with many devices without cio_ignore parameter and 128M crashkernel memory. == Comment: #2 - Michael Holzheu - 2016-03-31 11:04:10 == Output of lscss showing all attached (not online) devices on the LPAR. == Comment: #3 - Michael Holzheu - 2016-03-31 11:07:35 == To solve this issue our recommendation is: 1) Increase "crashkernel=" default to 196M on Ubuntu for s390. 2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used to decrease memory consumption for kdump on systems with many devices that are not required for kdump. The most user friendly solution would be to automatically determine the required kdump devices and set the correct "cio_ignore=" kernel parameter. But this is not trivial, because it can be difficult to find out the required devices for stacked setups like LVM or for network dump. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1564475/+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 1570780] [NEW] External Monitor makes System with Ubuntu 15.10 and Intel Graphics freeze
Public bug reported: A Lenovo ThinkPad L460 with Intel Graphics freezes, if an external Monitor is connected via the docking station. Please tell me if any information to solve this issue is needed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic 4.2.0-35.40 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: knut 1724 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 15 11:56:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=3ed9dcc5-0917-4be8-a2df-82cc2f5f36ef InstallationDate: Installed on 2016-04-06 (9 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FVS01500 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic root=UUID=b6aaa9e7-c690-41f8-a56b-dc0043e4cc20 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R08ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FVS01500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR08ET35W(1.09):bd02/04/2016:svnLENOVO:pn20FVS01500:pvrThinkPadL460:rvnLENOVO:rn20FVS01500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FVS01500 dmi.product.version: ThinkPad L460 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1570780 Title: External Monitor makes System with Ubuntu 15.10 and Intel Graphics freeze Status in linux package in Ubuntu: New Bug description: A Lenovo ThinkPad L460 with Intel Graphics freezes, if an external Monitor is connected via the docking station. Please tell me if any information to solve this issue is needed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic 4.2.0-35.40 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: knut 1724 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 15 11:56:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=3ed9dcc5-0917-4be8-a2df-82cc2f5f36ef InstallationDate: Installed on 2016-04-06 (9 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FVS01500 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic root=UUID=b6aaa9e7-c690-41f8-a56b-dc0043e4cc20 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R08ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FVS01500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR08ET35W(1.09):bd02/04/2016:svnLENOVO:pn20FVS01500:pvrThinkPadL460:rvnLENOVO:rn20FVS01500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FVS01500 dmi.product.version: ThinkPad L460 dmi.sys.vendor: LENOVO To manage notificatio
[Kernel-packages] [Bug 1570775] Re: makekdump should re-exec with cio_ignore on s390x
** Changed in: makedumpfile (Ubuntu) Status: New => Confirmed ** Changed in: makedumpfile (Ubuntu) Importance: Undecided => Medium ** Changed in: makedumpfile (Ubuntu) Assignee: (unassigned) => Louis Bouchard (louis-bouchard) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1570775 Title: makekdump should re-exec with cio_ignore on s390x Status in makedumpfile package in Ubuntu: Confirmed Bug description: As per https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19 We should re-exec with cio_ignore lines. As per report there, it should result in lowered required crashdump setting. Hypothetically, one should be able to test this imperially by lowering crashdump memory settings until kdump does not succeed anymore. And then generated and append `cio_ignore -k -u` to the KDUMP_CMDLINE_APPEND= and see that kdump starts working again with a lower memory usage. Once this is developed / verified / tested, we should probably SRU this back to xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1570775/+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 1570780] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570780 Title: External Monitor makes System with Ubuntu 15.10 and Intel Graphics freeze Status in linux package in Ubuntu: Confirmed Bug description: A Lenovo ThinkPad L460 with Intel Graphics freezes, if an external Monitor is connected via the docking station. Please tell me if any information to solve this issue is needed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic 4.2.0-35.40 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: knut 1724 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 15 11:56:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=3ed9dcc5-0917-4be8-a2df-82cc2f5f36ef InstallationDate: Installed on 2016-04-06 (9 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FVS01500 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic root=UUID=b6aaa9e7-c690-41f8-a56b-dc0043e4cc20 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R08ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FVS01500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR08ET35W(1.09):bd02/04/2016:svnLENOVO:pn20FVS01500:pvrThinkPadL460:rvnLENOVO:rn20FVS01500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FVS01500 dmi.product.version: ThinkPad L460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570780/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp
confirm fix from post #5, ubuntu 16.04 beta 2 Ubuntu Gnome. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Confirmed Status in pulseaudio source package in Vivid: Confirmed Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1438510/+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 1570802] [NEW] ATI Radeon not working: from no rendering to system freeze
Public bug reported: Release: Ubuntu 16.04 LTS (pre-release daily build) Hardware: Dell Inspiron 15 5000 Series (Intel(R)) - 5559, hybrid graphics: Intel integrated + AMD Radeon(TM) R5 M335 4GB DDR3 GPU. I can't get the GPU to work properly. Examples: glxgears not showing output or crashing, blender causing the system to freeze. What I've tried: 1] with the default configuration (integrated Intel card activated by default), glxgears works fine. 2] DRI_PRIME=1 glxgears: THe windows gets drawn, but no content is rendered 3] Output from xrandr --listproviders: Providers: number : 3 Provider 0: id: 0x66 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 2 name:Intel Provider 1: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:HAINAN @ pci::01:00.0 Provider 2: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:HAINAN @ pci::01:00.0 So I change with: xrandr --setprovideroffloadsink 0x3f 0x66 4] DRI_PRIME=1 glxgears now gives: radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeonsi: Failed to create a context. radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeonsi: Failed to create a context. X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 30 Current serial number in output stream: 32 "Apport" for this bug was run after going back to "xrandr --setprovideroffloadsink 0x66 0x3f". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 [modified: boot/vmlinuz-4.4.0-18-generic] ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicola 1402 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 15 11:55:17 2016 HibernationDevice: RESUME=UUID=449a6774-7719-42e0-ad0d-0941778d2be5 InstallationDate: Installed on 2016-04-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160414) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:07dc Intel Corp. Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=1505ea58-b580-4f52-b408-26294cb50da1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.6 dmi.board.name: 0664DJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.6:bd09/16/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0664DJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570802 Title: ATI Radeon not
[Kernel-packages] [Bug 1570195] Re: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO
I tested to change a device touched (initialized) by DPDK, but not yet on an Openvswitch bridge (no port added). That hangs stalls as well, so it is not required to add it to openvswitch-dpdk. Next step was to exclude openvswitch completely, therefor I ran testpmd against those ports. /usr/bin/testpmd --pci-blacklist :00:03.0 --socket-mem 2048 -- --interactive --total-num-mbufs=2048 After the test I ran ethtool and boom, hangs again. Test gets simpler and simpler. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO Status in dpdk package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it up. https://help.ubuntu.com/16.04/serverguide/DPDK.html service openvswitch-switch stop service dpdk stop OVS DPDK Options (/etc/default/openvswitch-switch): -- DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist :00:03.0,:00:04.0' -- service dpdk start service openvswitch-switch start - Enable multi-queue on OVS+DPDK inside of the VM: ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00 * Multi-queue apparently works! ovs-vswitchd consumes more that 100% of CPU, meaning that it multi-queue is there... *** Where it fails? 1- Reboot the VM and try to run ethtool again (or go straight to 2 below): ethtool -L ens5 combined 4 2- Try to fire up ens4: ip link set dev ens4 up # FAIL! Both commands hangs, consuming 100% of guest's CPU... So, it looks like a Linux fault, because it is "allowing" the DPDK VirtIO App (a user land App), to interfere with kernel devices in a strange way... Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 14 00:35 seq crw-rw 1 root audio 116, 33 Apr 14 00:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Thu Apr 14 01:27:27 2016 HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de InstallationDate: Installed on 2016-04-07 (7 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160406) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=9911604e-353b-491f-a0a9-804724350592 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-wily dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/
[Kernel-packages] [Bug 1570195] Re: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO
I confirmed that before running testpmd I can change the number of used queues just fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO Status in dpdk package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it up. https://help.ubuntu.com/16.04/serverguide/DPDK.html service openvswitch-switch stop service dpdk stop OVS DPDK Options (/etc/default/openvswitch-switch): -- DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist :00:03.0,:00:04.0' -- service dpdk start service openvswitch-switch start - Enable multi-queue on OVS+DPDK inside of the VM: ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00 * Multi-queue apparently works! ovs-vswitchd consumes more that 100% of CPU, meaning that it multi-queue is there... *** Where it fails? 1- Reboot the VM and try to run ethtool again (or go straight to 2 below): ethtool -L ens5 combined 4 2- Try to fire up ens4: ip link set dev ens4 up # FAIL! Both commands hangs, consuming 100% of guest's CPU... So, it looks like a Linux fault, because it is "allowing" the DPDK VirtIO App (a user land App), to interfere with kernel devices in a strange way... Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 14 00:35 seq crw-rw 1 root audio 116, 33 Apr 14 00:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Thu Apr 14 01:27:27 2016 HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de InstallationDate: Installed on 2016-04-07 (7 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160406) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=9911604e-353b-491f-a0a9-804724350592 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-wily dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-wily dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1570195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1570802] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570802 Title: ATI Radeon not working: from no rendering to system freeze Status in linux package in Ubuntu: Confirmed Bug description: Release: Ubuntu 16.04 LTS (pre-release daily build) Hardware: Dell Inspiron 15 5000 Series (Intel(R)) - 5559, hybrid graphics: Intel integrated + AMD Radeon(TM) R5 M335 4GB DDR3 GPU. I can't get the GPU to work properly. Examples: glxgears not showing output or crashing, blender causing the system to freeze. What I've tried: 1] with the default configuration (integrated Intel card activated by default), glxgears works fine. 2] DRI_PRIME=1 glxgears: THe windows gets drawn, but no content is rendered 3] Output from xrandr --listproviders: Providers: number : 3 Provider 0: id: 0x66 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 2 name:Intel Provider 1: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:HAINAN @ pci::01:00.0 Provider 2: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:HAINAN @ pci::01:00.0 So I change with: xrandr --setprovideroffloadsink 0x3f 0x66 4] DRI_PRIME=1 glxgears now gives: radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeonsi: Failed to create a context. radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeonsi: Failed to create a context. X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 30 Current serial number in output stream: 32 "Apport" for this bug was run after going back to "xrandr --setprovideroffloadsink 0x66 0x3f". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 [modified: boot/vmlinuz-4.4.0-18-generic] ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicola 1402 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 15 11:55:17 2016 HibernationDevice: RESUME=UUID=449a6774-7719-42e0-ad0d-0941778d2be5 InstallationDate: Installed on 2016-04-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160414) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:07dc Intel Corp. Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=1505ea58-b580-4f52-b408-26294cb50da1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.6 dmi.board.name: 0664DJ dmi.board.vendor: Dell Inc.
[Kernel-packages] [Bug 1570195] Re: Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO
This is not happeneing on a ixgbe device that formerly was used by DPDK. But then, that device had to be bound to uio_pci_generic and rebound to be reachable by ethtool. Now in the virtual environment force a reinit of the driver after DPDK used it Reinitialize the driver by rebinding it apt-get install linux-image-extra-virtual /usr/bin/testpmd --pci-blacklist :00:03.0 --socket-mem 2048 -- --interactive --total-num-mbufs=2048 dpdk_nic_bind -b uio_pci_generic :00:04.0 dpdk_nic_bind -b virtio-pci :00:04.0 We see the device "reinitialized" back on the virtio-pci driver. It is also back to 1 of 4 queues being used (as after the reboot. Now this works fine: ethtool -L eth1 combined 4 ethtool -L eth1 combined 3 ethtool -L eth1 combined 4 ** Summary changed: - Network tools like "ethtool" or "ip" freezes when DPDK Apps are running with VirtIO + Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices Status in dpdk package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it up. https://help.ubuntu.com/16.04/serverguide/DPDK.html service openvswitch-switch stop service dpdk stop OVS DPDK Options (/etc/default/openvswitch-switch): -- DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist :00:03.0,:00:04.0' -- service dpdk start service openvswitch-switch start - Enable multi-queue on OVS+DPDK inside of the VM: ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00 * Multi-queue apparently works! ovs-vswitchd consumes more that 100% of CPU, meaning that it multi-queue is there... *** Where it fails? 1- Reboot the VM and try to run ethtool again (or go straight to 2 below): ethtool -L ens5 combined 4 2- Try to fire up ens4: ip link set dev ens4 up # FAIL! Both commands hangs, consuming 100% of guest's CPU... So, it looks like a Linux fault, because it is "allowing" the DPDK VirtIO App (a user land App), to interfere with kernel devices in a strange way... Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 14 00:35 seq crw-rw 1 root audio 116, 33 Apr 14 00:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Thu Apr 14 01:27:27 2016 HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de InstallationDate: Installed on 2016-04-07 (7 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160406) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=9911604e-353b-491f-a0a9-804724350592 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-ge
[Kernel-packages] [Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault
And again. This time with upstream kernel (linux-image-4.5.1-040501-generic): [Fri Apr 15 13:26:56 2016] divide error: [#1] SMP [Fri Apr 15 13:26:56 2016] Modules linked in: vhost_net vhost macvtap macvlan ip6table_mangle nfnetlink_queue nfnetlink xt_CLASSIFY xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 xt_NFQUEUE sch_sfq sch_htb veth dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag ebtable_filter ebtables nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_CT iptable_raw xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter iptable_mangle ip_tables x_tables dummy bridge stp llc ipmi_ssif ipmi_devintf x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd sb_edac input_leds joydev edac_core nf_nat_ftp cdc_ether usbnet nf_conntrack_ftp mii nf_nat_pptp lpc_ich nf_conntrack_pptp nf_nat_proto_gre ioatdma nf_nat_sip nf_nat nfsd ipmi_si nf_conntrack_sip ipmi_msghandler 8250_fintek nf_conntrack_proto_gre acpi_pad nf_connt rack wmi acpi_power_meter shpchp mac_hid auth_rpcgss nfs_acl bonding nfs lp lockd parport grace sunrpc fscache tcp_htcp xfs btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid igb raid6_pq ixgbe libcrc32c raid1 i2c_algo_bit vxlan ahci ip6_udp_tunnel dca raid0 libahci udp_tunnel ptp megaraid_sas pps_core multipath mdio fjes linear [Fri Apr 15 13:26:56 2016] CPU: 10 PID: 9261 Comm: ceph-osd Not tainted 4.5.1-040501-generic #201604121331 [Fri Apr 15 13:26:56 2016] Hardware name: Dell Inc. PowerEdge R720/08RW36, BIOS 2.5.2 01/28/2015 [Fri Apr 15 13:26:56 2016] task: 8846b4611c80 ti: 8846b4704000 task.ti: 8846b4704000 [Fri Apr 15 13:26:56 2016] RIP: 0010:[] [] task_numa_find_cpu+0x23c/0x710 [Fri Apr 15 13:26:56 2016] RSP: :8846b4707bd8 EFLAGS: 00010206 [Fri Apr 15 13:26:56 2016] RAX: RBX: 8846b4707c78 RCX: [Fri Apr 15 13:26:56 2016] RDX: RSI: 88239f94 RDI: 88237a510200 [Fri Apr 15 13:26:56 2016] RBP: 8846b4707c40 R08: 000101378ff0 R09: 0012 [Fri Apr 15 13:26:56 2016] R10: 00ee R11: 0003 R12: 8846b46b0e40 [Fri Apr 15 13:26:56 2016] R13: 0001 R14: R15: 00e0 [Fri Apr 15 13:26:56 2016] FS: 7f95c52c8700() GS:88239f94() knlGS: [Fri Apr 15 13:26:56 2016] CS: 0010 DS: ES: CR0: 80050033 [Fri Apr 15 13:26:56 2016] CR2: 2b75cc00 CR3: 0047850e4000 CR4: 001426e0 [Fri Apr 15 13:26:56 2016] Stack: [Fri Apr 15 13:26:56 2016] 8846b4707c38 8101667e 000100016b00 8846b4611c80 [Fri Apr 15 13:26:56 2016] 014d fe53 00016b00 014d [Fri Apr 15 13:26:56 2016] 8846b4611c80 8846b4707c78 02ca 014d [Fri Apr 15 13:26:56 2016] Call Trace: [Fri Apr 15 13:26:56 2016] [] ? __switch_to+0x1de/0x5d0 [Fri Apr 15 13:26:56 2016] [] task_numa_migrate+0x43e/0x9b0 [Fri Apr 15 13:26:56 2016] [] numa_migrate_preferred+0x79/0x80 [Fri Apr 15 13:26:56 2016] [] task_numa_fault+0x7f7/0xd40 [Fri Apr 15 13:26:56 2016] [] ? should_numa_migrate_memory+0x55/0x130 [Fri Apr 15 13:26:56 2016] [] handle_mm_fault+0x1160/0x1ad0 [Fri Apr 15 13:26:56 2016] [] ? SYSC_recvfrom+0x144/0x160 [Fri Apr 15 13:26:56 2016] [] __do_page_fault+0x197/0x400 [Fri Apr 15 13:26:56 2016] [] do_page_fault+0x22/0x30 [Fri Apr 15 13:26:56 2016] [] page_fault+0x28/0x30 [Fri Apr 15 13:26:56 2016] Code: 55 b0 4c 89 f7 e8 55 c9 ff ff 48 8b 55 b0 49 8b 4e 78 48 8b 82 18 02 00 00 48 83 c1 01 31 d2 49 0f af 86 b0 00 00 00 4c 8b 73 78 <48> f7 f1 48 8b 4b 20 49 89 c0 48 29 c1 48 8b 45 d0 4c 03 43 48 [Fri Apr 15 13:26:56 2016] RIP [] task_numa_find_cpu+0x23c/0x710 [Fri Apr 15 13:26:56 2016] RSP [Fri Apr 15 13:26:56 2016] ---[ end trace ce23f377286f87a4 ]--- -- 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/1568729 Title: divide error: [#1] SMP in task_numa_migrate - handle_mm_fault Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: While running qemu 2.5 on a trusty host running 4.4.0-15.31~14.04.1 the host system has crashed (load > 200) 3 times in the last 3 days. Always with this stack trace: Apr 9 19:01:09 cnode9.0 kernel: [197071.195577] divide error: [#1] SMP Apr 9 19:01:09 cnode9.0 kernel: [197071.195633] Modules linked in: vhost_net vhost macvtap macvlan arc4 md4 nls_utf8 ci fs nfnetlink_queue nfnetlink xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 xt_NFQUEUE xt_CLASSIFY ip6table_mangle sch_sfq sch_htb veth dccp_diag dccp tcp_di
[Kernel-packages] [Bug 1570775] Re: makekdump should re-exec with cio_ignore on s390x
--- Comment From heinz-werner_se...@de.ibm.com 2016-04-15 07:33 EDT--- Reverse Mirror Request for following LP bugzilla: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1570775 ** Tags added: architecture-s39064 bugnameltc-140369 severity-medium targetmilestone-inin1610 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1570775 Title: makekdump should re-exec with cio_ignore on s390x Status in makedumpfile package in Ubuntu: Confirmed Bug description: As per https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19 We should re-exec with cio_ignore lines. As per report there, it should result in lowered required crashdump setting. Hypothetically, one should be able to test this imperially by lowering crashdump memory settings until kdump does not succeed anymore. And then generated and append `cio_ignore -k -u` to the KDUMP_CMDLINE_APPEND= and see that kdump starts working again with a lower memory usage. Once this is developed / verified / tested, we should probably SRU this back to xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1570775/+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 1570820] [NEW] Suspend failure
Public bug reported: My laptop fails to suspend. The screen turns off, but the fans continue to run (and it may actually get hotter). I wait and wait, and nothing happens (the power indicator remains always on). I tried suspending using the GUI, pressing the power button, closing the lid, and even through the terminal with the "pm-suspend" command. Nothing worked. Suspend worked fine on Ubuntu 15.10 and older releases, but since I upgraded to 16.04 I'm unable to put it to sleep. In fact, I had an old 4.2 kernel installed from Wily. I booted into it and it suspended and then resumed flawlessly, so it really seems to be a kernel related bug. I'll gladly perform any testing procedures that you may need to try to identify what the problem may be. I really hope that you are able to fix this soon, even if it will probably after the final release. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedro 2579 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 15 12:39:05 2016 HibernationDevice: RESUME=UUID=761da9d5-d078-4fb5-a4fc-eff7de723b18 InstallationDate: Installed on 2015-10-27 (170 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=8d1874c5-ce9f-481e-8d2a-ce85da5cd7fe ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-09 (5 days ago) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP870Z5E-X01PT dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP870Z5E-X01PT:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug kernel-bug sleep suspend xenial ** Attachment added: "/proc/acpi/wakeup" https://bugs.launchpad.net/bugs/1570820/+attachment/4637621/+files/wakeup -- 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/1570820 Title: Suspend failure Status in linux package in Ubuntu: Confirmed Bug description: My laptop fails to suspend. The screen turns off, but the fans continue to run (and it may actually get hotter). I wait and wait, and nothing happens (the power indicator remains always on). I tried suspending using the GUI, pressing the power button, closing the lid, and even through the terminal with the "pm-suspend" command. Nothing worked. Suspend worked fine on Ubuntu 15.10 and older releases, but since I upgraded to 16.04 I'm unable to put it to sleep. In fact, I had an old 4.2 kernel installed from Wily. I booted into it and it suspended and then resumed flawlessly, so it really seems to be a kernel related bug. I'll gladly perform any testing procedures that you may need to try to identify what the problem may be. I really hope that you are able to fix this soon, even if it will probably after the final release. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedro 2579 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 15 12:39:05 2016 HibernationDevice: RESUME=UUID=761da9d5-d078-4fb5-a4fc-eff7de723b18 InstallationDate: Installed on 2015-10-27 (170 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=8d1874c5-ce9f-481e-8d2a-ce85da5cd7fe ro quiet splash vt.handoff=7 Related
[Kernel-packages] [Bug 1570820] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570820 Title: Suspend failure Status in linux package in Ubuntu: Confirmed Bug description: My laptop fails to suspend. The screen turns off, but the fans continue to run (and it may actually get hotter). I wait and wait, and nothing happens (the power indicator remains always on). I tried suspending using the GUI, pressing the power button, closing the lid, and even through the terminal with the "pm-suspend" command. Nothing worked. Suspend worked fine on Ubuntu 15.10 and older releases, but since I upgraded to 16.04 I'm unable to put it to sleep. In fact, I had an old 4.2 kernel installed from Wily. I booted into it and it suspended and then resumed flawlessly, so it really seems to be a kernel related bug. I'll gladly perform any testing procedures that you may need to try to identify what the problem may be. I really hope that you are able to fix this soon, even if it will probably after the final release. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedro 2579 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 15 12:39:05 2016 HibernationDevice: RESUME=UUID=761da9d5-d078-4fb5-a4fc-eff7de723b18 InstallationDate: Installed on 2015-10-27 (170 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=8d1874c5-ce9f-481e-8d2a-ce85da5cd7fe ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-09 (5 days ago) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP870Z5E-X01PT dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP870Z5E-X01PT:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1570195] Re: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices
There is no obvious run-until-success loop in any of the involved code. Only this in virtnet_send_command could be related /* Spin for a response, the kick causes an ioport write, trapping * into the hypervisor, so the request should be handled immediately. */ while (!virtqueue_get_buf(vi->cvq, &tmp) && !virtqueue_is_broken(vi->cvq)) cpu_relax(); We need to catch who is calling whom and how often to get a better idea what is going on when going to get stuck. Interesting are from the stack: cpu_relax virtnet_send_command virtnet_set_queues virtnet_set_channels ethtool_set_channels dev_ethtool cd /sys/kernel/debug/tracing echo 0 > tracing_on echo function_graph > current_tracer tail -f trace # get global and one on each of our 4 CPUs from trace and per_cpu/cpu[0-3]/trace echo 1 > tracing_on ethtool -L eth1 combined 3 The system is stuck enough that all hang immediately without reporting. Need to go deeper with debugging, but that is probably monday then. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices Status in dpdk package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Guys, I'm facing an issue here with both "ethtool" and "ip", while trying to manage black-listed by DPDK PCI VirtIO devices. You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to run those tests PCI device example from inside a Xenial guest: --- # lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Red Hat, Inc Virtio network device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device 00:06.0 Ethernet controller: Red Hat, Inc Virtio network device --- Where "ens3" is the first / default interface, attached to Libvirt's "default" network. The "ens4" is reserved for "ethtool / ip" tests (attached to another Libvirt's network without IPs or DHCP), "ens5" will be "dpdk0" and "ens6" "dpdk1"... --- *** How it works? 1- For example, try to enable multi-queue on DPDK's devices, boot your Xenial guest, and run: ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it up. https://help.ubuntu.com/16.04/serverguide/DPDK.html service openvswitch-switch stop service dpdk stop OVS DPDK Options (/etc/default/openvswitch-switch): -- DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist :00:03.0,:00:04.0' -- service dpdk start service openvswitch-switch start - Enable multi-queue on OVS+DPDK inside of the VM: ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00 * Multi-queue apparently works! ovs-vswitchd consumes more that 100% of CPU, meaning that it multi-queue is there... *** Where it fails? 1- Reboot the VM and try to run ethtool again (or go straight to 2 below): ethtool -L ens5 combined 4 2- Try to fire up ens4: ip link set dev ens4 up # FAIL! Both commands hangs, consuming 100% of guest's CPU... So, it looks like a Linux fault, because it is "allowing" the DPDK VirtIO App (a user land App), to interfere with kernel devices in a strange way... Best, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 14 00:35 seq crw-rw 1 root audio 116, 33 Apr 14 00:35 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A Date: Thu Apr 14 01:27:27 2016 HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de InstallationDate: Installed on 2016-04-07 (7 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160406) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=9911604e-353b-491f-a0a9-804724350592 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N
[Kernel-packages] [Bug 1570820] Re: Suspend failure
Meanwhile I tried to install the latest 4.4.x mainline kernel and it works nicely. uname -a Linux alpha 4.4.7-040407-generic #201604121331 SMP Tue Apr 12 17:33:19 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux The official 4.4.0-18-generic kernel is based on which mainline kernel? -- 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/1570820 Title: Suspend failure Status in linux package in Ubuntu: Confirmed Bug description: My laptop fails to suspend. The screen turns off, but the fans continue to run (and it may actually get hotter). I wait and wait, and nothing happens (the power indicator remains always on). I tried suspending using the GUI, pressing the power button, closing the lid, and even through the terminal with the "pm-suspend" command. Nothing worked. Suspend worked fine on Ubuntu 15.10 and older releases, but since I upgraded to 16.04 I'm unable to put it to sleep. In fact, I had an old 4.2 kernel installed from Wily. I booted into it and it suspended and then resumed flawlessly, so it really seems to be a kernel related bug. I'll gladly perform any testing procedures that you may need to try to identify what the problem may be. I really hope that you are able to fix this soon, even if it will probably after the final release. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedro 2579 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 15 12:39:05 2016 HibernationDevice: RESUME=UUID=761da9d5-d078-4fb5-a4fc-eff7de723b18 InstallationDate: Installed on 2015-10-27 (170 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=8d1874c5-ce9f-481e-8d2a-ce85da5cd7fe ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-09 (5 days ago) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP870Z5E-X01PT dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP870Z5E-X01PT:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570820/+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 1564475] Comment bridged from LTC Bugzilla
--- Comment From thorsten.di...@de.ibm.com 2016-04-15 08:13 EDT--- (In reply to comment #25) > I have, for now, added things to https://wiki.ubuntu.com/S390X -> feel free > to edit and/or improve that. And I will open a new bug report to get those > updates into the Ubuntu Server Guide. Dimitri, upon second reading I want at least to replace crashdebug by crashkernel, i.e.: Depending on the number of available devices the amount of memory specified by the "crashkernel" kernel parameter in /etc/zipl.conf may not be sufficient. One can either increase it further, or limit the amount of devices visible to the kernel, and thus lower the requirements for the "crashkernel" setting. ... and if you think it's appropriate, please remind to invoke "zipl -V" after each change of /etc/zipl.conf (for the z Systems newbies) Nevertheless, I also appreciate your LP1570775. Thanks again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1564475 Title: 128M is not enough for kdump on s390 LPARs Status in Ubuntu on IBM z Systems: Fix Released Status in makedumpfile package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in zipl-installer package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Invalid Status in s390-tools source package in Xenial: Fix Released Status in zipl-installer source package in Xenial: Fix Released Bug description: == Comment: #0 - Michael Holzheu - 2016-03-31 10:59:26 == With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt"). On z/VM guests 128M seems to be sufficient. One reason on our test LPAR is that a lot of devices are attached (see attachment "lscss_lpar.txt") which are not required for kdump but consume a lot of memory because the s390 CIO layer allocates data structures in the kernel for those devices. We can disable the devices by using the "cio_ignore=" kernel parameter in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD 0.0.e934 for /var/crash, we added the following line to disable the devices: KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1 cio_ignore=all,!condev,!0.0.e934" For more information on the "cio_ignore=" kernel parameter see: https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO Even with "cio_ignore=" we still get out-of-memory with "crashkernel=128M". With "crashkernel=196M" and "cio_ignore=" we are able to create a dump on our LPAR. We currently do not know why kdump with "cio_ignore=" on LPAR consumes more memory than on z/VM guests. == Comment: #1 - Michael Holzheu - 2016-03-31 11:03:15 == Kernel messages of kdump out-of-memory crash on LPAR with many devices without cio_ignore parameter and 128M crashkernel memory. == Comment: #2 - Michael Holzheu - 2016-03-31 11:04:10 == Output of lscss showing all attached (not online) devices on the LPAR. == Comment: #3 - Michael Holzheu - 2016-03-31 11:07:35 == To solve this issue our recommendation is: 1) Increase "crashkernel=" default to 196M on Ubuntu for s390. 2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used to decrease memory consumption for kdump on systems with many devices that are not required for kdump. The most user friendly solution would be to automatically determine the required kdump devices and set the correct "cio_ignore=" kernel parameter. But this is not trivial, because it can be difficult to find out the required devices for stacked setups like LVM or for network dump. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1564475/+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 1515301] Re: [Hyper-V] issues with linux-next on 15.04 kdump functionality
** Changed in: linux (Ubuntu) Status: Triaged => 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/1515301 Title: [Hyper-V] issues with linux-next on 15.04 kdump functionality Status in linux package in Ubuntu: Fix Released Bug description: Using linux-next 4.3.0-next-20151106 kdump is failing to start as a service. On RHEL and SLES with upstream, kdump is working as expected so only Ubuntu has this issue as observed from our testing. A similar issue with the same error message from kdump has been already reported here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400319 However that behavior was on 32bit Ubuntu only, and now with upstream this seems to extend to 64bit as well. So I'm not sure if we should link these 2 bug reports at this point. Issues description: 1. kdump-tools service fails to start on 15.04 64bit, when runnig the linux-next kernel Error returned is: Starting kdump-tools: Could not find a free area of memory of 0xa637000 bytes... (full log below) By default, kdump sets crashkernel to 394M-:128M 2. If crashkernel is set to 384M, the dump file will fail to create due to OOM messages when a crash is triggered. Attaching the full serial log with crashkernel=384M. The log is the same with 512M as crashkernel. Can this be a memory leak in the kdump kernel, making even already high values as 512M for the crashkernel to not be enough? VM RAM has been set to 2GB and also 4GB, and with minimal load on the system that isn't a problem. Work-around for issue #1: Set crashkernel size to 384M, instead of the default 384M-:128M. With this, kdump-tools will start. However the dump file doesn't get written and the system will hang, without rebooting. Values used to trigger a kdump: - 384M - 512M - 384M-:128M - kdump-tools will not properly load. Full kdump service log: root@ubuntu1504srv:~# service kdump-tools status â kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2015-11-11 06:02:28 PST; 20min ago Process: 792 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) Main PID: 792 (code=exited, status=0/SUCCESS) CGroup: /system.slice/kdump-tools.service Nov 11 06:02:20 ubuntu1504srv systemd[1]: Starting Kernel crash dump capture service... Nov 11 06:02:28 ubuntu1504srv kdump-tools[792]: Starting kdump-tools: Could not find a free area of memory of 0xa637000 bytes... Nov 11 06:02:28 ubuntu1504srv kdump-tools[792]: locate_hole failed Nov 11 06:02:28 ubuntu1504srv kdump-tools[792]: * failed to load kdump kernel Nov 11 06:02:28 ubuntu1504srv systemd[1]: Started Kernel crash dump capture service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515301/+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 1516547] Re: Ubuntu 15.10 crashes with RAID-10
Hi Joseph. Sorry for the late reply. Ubuntu 16.04, which uses kernel 4.4, has been tested without facing these errors and Ubuntu 15.10 is also end-of-life July 2016. Therefore we've decided to stop our testings as it seems to be a much deeper investigation. Thank you for all the help. -- 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/1516547 Title: Ubuntu 15.10 crashes with RAID-10 Status in linux package in Ubuntu: Confirmed Status in linux source package in Wily: In Progress Bug description: When trying to install Ubuntu 15.10 with a RAID-10 created the system crashes after some time during the installation. Hitting Alt+F4 gives the following output as seen from screenshots in attachments. It looks like kernel 4.2 have some issues with RAID-10 as we can install Ubuntu 15.04 (with kernel 3.19) without problems. If we upgrade to kernel 4.2 in Ubuntu 15.04 we get the same errors. We have no problems when installing without RAID, RAID-0 or RAID-1. We've also tried on different hardware and different disk types/sizes but we still get system crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516547/+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 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
Positive test results: https://lists.ubuntu.com/archives/kernel- team/2016-April/076269.html ** Changed in: linux (Ubuntu Xenial) Status: In Progress => 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/1566465 Title: [regression]: Failed to call clock_adjtime(): Invalid argument Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Steps to reproduce: 1) Force a time delta date -s "now - 1 hour" 2) Restart systemd-timesyncd to have it fix the time systemctl restart systemd-timesyncd Expected behavior: The clock should be back in sync. Actual (problematic) behavior: The clock stays out of sync because the call to clock_adjtime() failed. # systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: active (running) since Tue 2016-04-05 14:26:25 EDT; 1s ago Docs: man:systemd-timesyncd.service(8) Main PID: 11567 (systemd-timesyn) Status: "Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 512) Memory: 260.0K CPU: 15ms CGroup: /system.slice/systemd-timesyncd.service └─11567 /lib/systemd/systemd-timesyncd Apr 05 14:26:25 simon-laptop systemd[1]: Starting Network Time Synchronization... Apr 05 14:26:25 simon-laptop systemd[1]: Started Network Time Synchronization. Apr 05 14:26:25 simon-laptop systemd-timesyncd[11567]: Failed to call clock_adjtime(): Invalid argument Apr 05 14:26:25 simon-laptop systemd-timesyncd[11567]: Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com). This problem doesn't happen when running kernel 4.4.0-16.32. Looking at the changelog of 4.4.0-17.33 it could be because of the new feature introduced in LP: #1519625. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-17-generic 4.4.0-17.33 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simon 5198 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Apr 5 14:21:22 2016 HibernationDevice: RESUME=/dev/mapper/crypt-swap MachineType: LENOVO 2516CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-17-generic root=/dev/mapper/crypt-xroot ro quiet splash cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-xroot possible_cpus=4 nmi_watchdog=0 kaslr quiet splash cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-xroot possible_cpus=4 nmi_watchdog=0 kaslr vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-17-generic N/A linux-backports-modules-4.4.0-17-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566465/+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 1570441] Re: Kernel Panic in Ubuntu 16.04 netboot installer
I have forgotten to mention that on our machine hyperthreading is disabled. -- 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/1570441 Title: Kernel Panic in Ubuntu 16.04 netboot installer Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Hello, we are working with the Ubuntu 16.04 developer preview. Yesterday we observed a kernel panic of the installer kernel on one of our machines. The machine is of type Supermicro X10DRH LN4/X10DRH-CLN4, BIOS s1.0b 12/01/2015 We are installing the machine via PXEboot with the netboot installer system using the following kernel/initrd: dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/initrd.gz dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/linux When using this version the kernel crashes (see attached log file). We have also tried the version 447 instead of 446. This version shows the same effect. Some time ago we worked with the installer version 441. This release worked as expected. Someone out there knows what has changed? It seems that the kernel has a problem with the harddisk IO system. In our machine the mpt3sas disk controller is required to get access to the harddisks. If I should test some new stuff please let me know. Or if I can help you in some other way to solve this issue contact me. Thank you for your help Dr. Johann Pfefferl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570441/+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 1570441] Re: Kernel Panic in Ubuntu 16.04 netboot installer
I got a request to provide infomation about the kernel version we used so far to boot the system: Failed: 4.4.0-18-generic Success: 4.4.0-15-generic -- 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/1570441 Title: Kernel Panic in Ubuntu 16.04 netboot installer Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Hello, we are working with the Ubuntu 16.04 developer preview. Yesterday we observed a kernel panic of the installer kernel on one of our machines. The machine is of type Supermicro X10DRH LN4/X10DRH-CLN4, BIOS s1.0b 12/01/2015 We are installing the machine via PXEboot with the netboot installer system using the following kernel/initrd: dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/initrd.gz dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/linux When using this version the kernel crashes (see attached log file). We have also tried the version 447 instead of 446. This version shows the same effect. Some time ago we worked with the installer version 441. This release worked as expected. Someone out there knows what has changed? It seems that the kernel has a problem with the harddisk IO system. In our machine the mpt3sas disk controller is required to get access to the harddisks. If I should test some new stuff please let me know. Or if I can help you in some other way to solve this issue contact me. Thank you for your help Dr. Johann Pfefferl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570441/+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 1570441] Re: Kernel Panic in Ubuntu 16.04 netboot installer
commit 31c2013e4ea2e594522980acc3d20e88664b19f1 ('x86/topology: Create
logical package id') was used as a prerequisite patch for bug #1397880
(Memory bandwidth manager). However, being a 4.6-rc1 commit it caused
some problems. Subsequent fixup patches are as mentioned in comment #3.
--
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/1570441
Title:
Kernel Panic in Ubuntu 16.04 netboot installer
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
Hello,
we are working with the Ubuntu 16.04 developer preview. Yesterday we
observed a kernel panic of the installer kernel on one of our machines.
The machine is of type
Supermicro X10DRH LN4/X10DRH-CLN4, BIOS s1.0b 12/01/2015
We are installing the machine via PXEboot with the netboot installer
system using the following kernel/initrd:
dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/initrd.gz
dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/linux
When using this version the kernel crashes (see attached log file). We
have also tried the version 447 instead of 446. This version shows
the same effect.
Some time ago we worked with the installer version 441. This release
worked as expected.
Someone out there knows what has changed? It seems that the kernel has a
problem with the harddisk IO system. In our machine the mpt3sas disk
controller is required to get access to the harddisks.
If I should test some new stuff please let me know. Or if I can help you
in some other way to solve this issue contact me.
Thank you for your help
Dr. Johann Pfefferl
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570441/+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 1570441] Re: Kernel Panic in Ubuntu 16.04 netboot installer
x86/topology: Fix AMD core count xen/apic: Provide Xen-specific version of cpu_present_to_apicid APIC op x86/topology: Use total_cpus not nr_cpu_ids for logical packages x86/topology: Fix Intel HT disable x86/topology: Fix logical package mapping ** Changed in: linux (Ubuntu Xenial) Status: In Progress => 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/1570441 Title: Kernel Panic in Ubuntu 16.04 netboot installer Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Hello, we are working with the Ubuntu 16.04 developer preview. Yesterday we observed a kernel panic of the installer kernel on one of our machines. The machine is of type Supermicro X10DRH LN4/X10DRH-CLN4, BIOS s1.0b 12/01/2015 We are installing the machine via PXEboot with the netboot installer system using the following kernel/initrd: dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/initrd.gz dists/xenial/main/installer-amd64/20101020ubuntu446/images/netboot/ubuntu-installer/amd64/linux When using this version the kernel crashes (see attached log file). We have also tried the version 447 instead of 446. This version shows the same effect. Some time ago we worked with the installer version 441. This release worked as expected. Someone out there knows what has changed? It seems that the kernel has a problem with the harddisk IO system. In our machine the mpt3sas disk controller is required to get access to the harddisks. If I should test some new stuff please let me know. Or if I can help you in some other way to solve this issue contact me. Thank you for your help Dr. Johann Pfefferl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570441/+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 1570872] [NEW] Trusty update to 3.16.7-ckt27 stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The 3.16.7-ckt27 upstream
stable
patch set is now available. It should be included in the Ubuntu
kernel as well.
git://kernel.ubuntu.com/ubuntu/linux.git
TEST CASE: TBD
The following patches from the 3.16.7-ckt27 stable release shall
be applied:
ipv4: Don't do expensive useless work during inetdev destroy.
Input: powermate - fix oops with malicious USB descriptors
USB: iowarrior: fix oops with malicious USB descriptors
ALSA: usb-audio: Fix NULL dereference in create_fixed_stream_quirk()
ALSA: usb-audio: Add sanity checks for endpoint accesses
include/linux/poison.h: fix LIST_POISON{1,2} offset
cpu: Defer smpboot kthread unparking until CPU known to scheduler
ipr: Fix out-of-bounds null overwrite
ipr: Fix regression when loading firmware
Input: ati_remote2 - fix crashes on detecting device with invalid descriptor
USB: cdc-acm: more sanity checking
ceph: fix request time stamp encoding
cpu: Provide smpboot_thread_init() on !CONFIG_SMP kernels as well
x86/iopl/64: Properly context-switch IOPL on Xen PV
staging: comedi: ni_tiocmd: change mistaken use of start_src for start_arg
drm/radeon: hold reference to fences in radeon_sa_bo_new (3.17 and older)
Drivers: hv: vmbus: prevent cpu offlining on newer hypervisors
Linux 3.16.7-ckt27
** Affects: linux-lts-utopic (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-lts-utopic (Ubuntu Trusty)
Importance: Undecided
Status: New
** Tags: kernel-stable-tracking-bug
** Tags added: kernel-stable-tracking-bug
** Also affects: linux-lts-utopic (Ubuntu Trusty)
Importance: Undecided
Status: New
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The 3.16.7-ckt27 upstream
stable
+ patch set is now available. It should be included in the Ubuntu
+ kernel as well.
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 3.16.7-ckt27 upstream
stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+ git://kernel.ubuntu.com/ubuntu/linux.git
-git://kernel.ubuntu.com/ubuntu/linux.git
+ TEST CASE: TBD
- TEST CASE: TBD
+ The following patches from the 3.16.7-ckt27 stable release shall
+ be applied:
-The following patches from the 3.16.7-ckt27 stable release shall
- be applied:
+ ipv4: Don't do expensive useless work during inetdev destroy.
+ Input: powermate - fix oops with malicious USB descriptors
+ USB: iowarrior: fix oops with malicious USB descriptors
+ ALSA: usb-audio: Fix NULL dereference in create_fixed_stream_quirk()
+ ALSA: usb-audio: Add sanity checks for endpoint accesses
+ include/linux/poison.h: fix LIST_POISON{1,2} offset
+ cpu: Defer smpboot kthread unparking until CPU known to scheduler
+ ipr: Fix out-of-bounds null overwrite
+ ipr: Fix regression when loading firmware
+ Input: ati_remote2 - fix crashes on detecting device with invalid descriptor
+ USB: cdc-acm: more sanity checking
+ ceph: fix request time stamp encoding
+ cpu: Provide smpboot_thread_init() on !CONFIG_SMP kernels as well
+ x86/iopl/64: Properly context-switch IOPL on Xen PV
+ staging: comedi: ni_tiocmd: change mistaken use of start_src for start_arg
+ drm/radeon: hold reference to fences in radeon_sa_bo_new (3.17 and older)
+ Drivers: hv: vmbus: prevent cpu offlining on newer hypervisors
+ Linux 3.16.7-ckt27
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1570872
Title:
Trusty update to 3.16.7-ckt27 stable release
Status in linux-lts-utopic package in Ubuntu:
New
Status in linux-lts-utopic source package in Trusty:
New
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug,
[Kernel-packages] [Bug 1564475] Comment bridged from LTC Bugzilla
--- Comment From thorsten.di...@de.ibm.com 2016-04-15 09:39 EDT--- well, here my complete proposed wording: Depending on the number of available devices the amount of memory specified by the "crashkernel" kernel parameter in /etc/zipl.conf may not be sufficient. One can either increase it further, or limit the amount of devices visible to the kernel, and thus lower the requirements for the "crashkernel" setting. To ignore devices you can run the "cio_ignore" tool to generate an appropriate stanza to ignore all devices, except the currently active /in-use. $ sudo cio_ignore -u -k cio_ignore=all,!c000-c002,!e000,!e100 You can simply add the "cio_ignore" kernel parameter with the stanza from above to KDUMP_CMDLINE_APPEND in /etc/default/kdump-tools and activate the setting with "systemctl restart kdump-tools.service". As an alternative which blacklists the channel devices also for the production system, you can add the generated stanza to the boot parameters in /etc/zipl.conf. To activate the setting call "zipl -V" and then reboot the system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1564475 Title: 128M is not enough for kdump on s390 LPARs Status in Ubuntu on IBM z Systems: Fix Released Status in makedumpfile package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in zipl-installer package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Invalid Status in s390-tools source package in Xenial: Fix Released Status in zipl-installer source package in Xenial: Fix Released Bug description: == Comment: #0 - Michael Holzheu - 2016-03-31 10:59:26 == With the current Ubuntu default setting "crashkernel=128M" kdump on LPARs crashes with out-of-memory (see attachment "dmesg_lpar_out_of_mem_128M.txt"). On z/VM guests 128M seems to be sufficient. One reason on our test LPAR is that a lot of devices are attached (see attachment "lscss_lpar.txt") which are not required for kdump but consume a lot of memory because the s390 CIO layer allocates data structures in the kernel for those devices. We can disable the devices by using the "cio_ignore=" kernel parameter in "/etc/default/kdump-tools". For example, on our LPAR that uses DASD 0.0.e934 for /var/crash, we added the following line to disable the devices: KDUMP_CMDLINE_APPEND="irqpoll maxcpus=1 cio_ignore=all,!condev,!0.0.e934" For more information on the "cio_ignore=" kernel parameter see: https://github.com/torvalds/linux/blob/master/Documentation/s390/CommonIO Even with "cio_ignore=" we still get out-of-memory with "crashkernel=128M". With "crashkernel=196M" and "cio_ignore=" we are able to create a dump on our LPAR. We currently do not know why kdump with "cio_ignore=" on LPAR consumes more memory than on z/VM guests. == Comment: #1 - Michael Holzheu - 2016-03-31 11:03:15 == Kernel messages of kdump out-of-memory crash on LPAR with many devices without cio_ignore parameter and 128M crashkernel memory. == Comment: #2 - Michael Holzheu - 2016-03-31 11:04:10 == Output of lscss showing all attached (not online) devices on the LPAR. == Comment: #3 - Michael Holzheu - 2016-03-31 11:07:35 == To solve this issue our recommendation is: 1) Increase "crashkernel=" default to 196M on Ubuntu for s390. 2) Document that KDUMP_CMDLINE_APPEND with "cio_ignore=" can be used to decrease memory consumption for kdump on systems with many devices that are not required for kdump. The most user friendly solution would be to automatically determine the required kdump devices and set the correct "cio_ignore=" kernel parameter. But this is not trivial, because it can be difficult to find out the required devices for stacked setups like LVM or for network dump. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1564475/+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 1570897] Re: [ASUSTeK COMPUTER INC. X550JK] late resume failure
** Tags removed: need-duplicate-check -- 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/1570897 Title: [ASUSTeK COMPUTER INC. X550JK] late resume failure Status in linux package in Ubuntu: Confirmed Bug description: late resume failure ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1493 F pulseaudio cirelli1845 F pulseaudio /dev/snd/controlC1: gdm1493 F pulseaudio cirelli1845 F pulseaudio Date: Fri Apr 15 16:13:35 2016 DuplicateSignature: late resume:ASUSTeK COMPUTER INC. X550JK:X550JK.303 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=723c3959-bf09-4534-8786-d64e7af798e8 InstallationDate: Installed on 2016-02-23 (51 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160222) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 002: ID 15ca:00c3 Textech International Ltd. Mini Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=71fb4ac9-1d11-46f1--d8a7cffee69f ro quiet splash acpi_osi= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux Title: [ASUSTeK COMPUTER INC. X550JK] late resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570897/+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 1570897] [NEW] [ASUSTeK COMPUTER INC. X550JK] late resume failure
Public bug reported: late resume failure ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1493 F pulseaudio cirelli1845 F pulseaudio /dev/snd/controlC1: gdm1493 F pulseaudio cirelli1845 F pulseaudio Date: Fri Apr 15 16:13:35 2016 DuplicateSignature: late resume:ASUSTeK COMPUTER INC. X550JK:X550JK.303 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=723c3959-bf09-4534-8786-d64e7af798e8 InstallationDate: Installed on 2016-02-23 (51 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160222) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 002: ID 15ca:00c3 Textech International Ltd. Mini Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=71fb4ac9-1d11-46f1--d8a7cffee69f ro quiet splash acpi_osi= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux Title: [ASUSTeK COMPUTER INC. X550JK] late resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops hibernate resume resume-late-hang xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570897 Title: [ASUSTeK COMPUTER INC. X550JK] late resume failure Status in linux package in Ubuntu: Confirmed Bug description: late resume failure ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1493 F pulseaudio cirelli1845 F pulseaudio /dev/snd/controlC1: gdm1493 F pulseaudio cirelli1845 F pulseaudio Date: Fri Apr 15 16:13:35 2016 DuplicateSignature: late resume:ASUSTeK COMPUTER INC. X550JK:X550JK.303 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=723c3959-bf09-4534-8786-d64e7af798e8 InstallationDate: Installed on 2016-02-23 (51 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160222) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 002: ID 15ca:00c3 Textech International Ltd. Mini Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 ProcFB:
[Kernel-packages] [Bug 1570897] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570897 Title: [ASUSTeK COMPUTER INC. X550JK] late resume failure Status in linux package in Ubuntu: Confirmed Bug description: late resume failure ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1493 F pulseaudio cirelli1845 F pulseaudio /dev/snd/controlC1: gdm1493 F pulseaudio cirelli1845 F pulseaudio Date: Fri Apr 15 16:13:35 2016 DuplicateSignature: late resume:ASUSTeK COMPUTER INC. X550JK:X550JK.303 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=723c3959-bf09-4534-8786-d64e7af798e8 InstallationDate: Installed on 2016-02-23 (51 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160222) InterpreterPath: /usr/bin/python3.5 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 002: ID 15ca:00c3 Textech International Ltd. Mini Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=71fb4ac9-1d11-46f1--d8a7cffee69f ro quiet splash acpi_osi= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux Title: [ASUSTeK COMPUTER INC. X550JK] late resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570897/+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 1570906] [NEW] sysfs mount failure during stateful lxd snapshots
Public bug reported: During a stateful lxd snapshot criu tries to mount sysfs for the container's network namespace from a different user namespace. This fails in xenial because sget() won't allow mounting the same super block in different user namespaces. With sysfs there's no reason that this needs to use the same super block, so kernfs can be updated so that a super block with the same ns tag but in a different userns is not matched. The only other kernfs- based filesystem mountable from non-init user namespaces is cgroupfs, and it's already forcing kernfs to return different super blocks to avoid similar problems. In fact we can revert part of the cgroupfs changes to make this happen if we push this behavior into kernfs. ** Affects: linux (Ubuntu) Importance: High Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux (Ubuntu Xenial) Importance: High Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: High Assignee: Seth Forshee (sforshee) Status: 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/1570906 Title: sysfs mount failure during stateful lxd snapshots Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: During a stateful lxd snapshot criu tries to mount sysfs for the container's network namespace from a different user namespace. This fails in xenial because sget() won't allow mounting the same super block in different user namespaces. With sysfs there's no reason that this needs to use the same super block, so kernfs can be updated so that a super block with the same ns tag but in a different userns is not matched. The only other kernfs- based filesystem mountable from non-init user namespaces is cgroupfs, and it's already forcing kernfs to return different super blocks to avoid similar problems. In fact we can revert part of the cgroupfs changes to make this happen if we push this behavior into kernfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570906/+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 1570906] Re: sysfs mount failure during stateful lxd snapshots
Test build is at http://kernel.ubuntu.com/~sforshee/for-tych0/, confirmed to fix the problem by @tycho-s. -- 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/1570906 Title: sysfs mount failure during stateful lxd snapshots Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: During a stateful lxd snapshot criu tries to mount sysfs for the container's network namespace from a different user namespace. This fails in xenial because sget() won't allow mounting the same super block in different user namespaces. With sysfs there's no reason that this needs to use the same super block, so kernfs can be updated so that a super block with the same ns tag but in a different userns is not matched. The only other kernfs- based filesystem mountable from non-init user namespaces is cgroupfs, and it's already forcing kernfs to return different super blocks to avoid similar problems. In fact we can revert part of the cgroupfs changes to make this happen if we push this behavior into kernfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570906/+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 1570906] Re: sysfs mount failure during stateful lxd snapshots
** Description changed: + SRU Justification: + + Impact: Stateful lxd container snapshotting fails due to a failure to + mount the container's sysfs in the host's user namespace. This is a + regression. + + Fix: Force kernfs to use a new super block for mounts in different user + namespaces. + + Test Case: "lxc snapshot --statefull " fails in the current + xenial kernel without the fix. It succeeds with the fix applied. + + --- + During a stateful lxd snapshot criu tries to mount sysfs for the container's network namespace from a different user namespace. This fails in xenial because sget() won't allow mounting the same super block in different user namespaces. With sysfs there's no reason that this needs to use the same super block, so kernfs can be updated so that a super block with the same ns tag but in a different userns is not matched. The only other kernfs- based filesystem mountable from non-init user namespaces is cgroupfs, and it's already forcing kernfs to return different super blocks to avoid similar problems. In fact we can revert part of the cgroupfs changes to make this happen if we push this behavior into kernfs. ** Description changed: SRU Justification: Impact: Stateful lxd container snapshotting fails due to a failure to mount the container's sysfs in the host's user namespace. This is a regression. Fix: Force kernfs to use a new super block for mounts in different user namespaces. - Test Case: "lxc snapshot --statefull " fails in the current + Test Case: "lxc snapshot --stateful " fails in the current xenial kernel without the fix. It succeeds with the fix applied. --- During a stateful lxd snapshot criu tries to mount sysfs for the container's network namespace from a different user namespace. This fails in xenial because sget() won't allow mounting the same super block in different user namespaces. With sysfs there's no reason that this needs to use the same super block, so kernfs can be updated so that a super block with the same ns tag but in a different userns is not matched. The only other kernfs- based filesystem mountable from non-init user namespaces is cgroupfs, and it's already forcing kernfs to return different super blocks to avoid similar problems. In fact we can revert part of the cgroupfs changes to make this happen if we push this behavior into kernfs. -- 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/1570906 Title: sysfs mount failure during stateful lxd snapshots Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: SRU Justification: Impact: Stateful lxd container snapshotting fails due to a failure to mount the container's sysfs in the host's user namespace. This is a regression. Fix: Force kernfs to use a new super block for mounts in different user namespaces. Test Case: "lxc snapshot --stateful " fails in the current xenial kernel without the fix. It succeeds with the fix applied. --- During a stateful lxd snapshot criu tries to mount sysfs for the container's network namespace from a different user namespace. This fails in xenial because sget() won't allow mounting the same super block in different user namespaces. With sysfs there's no reason that this needs to use the same super block, so kernfs can be updated so that a super block with the same ns tag but in a different userns is not matched. The only other kernfs- based filesystem mountable from non-init user namespaces is cgroupfs, and it's already forcing kernfs to return different super blocks to avoid similar problems. In fact we can revert part of the cgroupfs changes to make this happen if we push this behavior into kernfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570906/+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 1570820] Re: Suspend failure
So I just found this site "Ubuntu to Mainline kernel version mapping" that the official 4.4.0-18 kernel is based upon the updstream 4.4.6 kernel. So I just tried installing that version and suspend is broken. So this is something this must be something that was fixed upstream between 4.4.6 and 4.4.7. I'm not knowledgeable enough to go through all the commits between 4.4.6 and 4.4.7 and find out exactly which one fixed the bug so that you can create a patch for it. However, I did find out that the word "suspend" is mentioned a few times in the 4.4.7's changelog: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.7 So maybe someone else can pick up whatever is needed to fix the kernel suspend issues that I'm facing and import it as a patch to the official kernel. Or maybe you can rebase the oficial kernel to the 4.4.7 version after the oficial LTS release. I don't know if that's possible since I'm not aware of the kernel update policy. -- 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/1570820 Title: Suspend failure Status in linux package in Ubuntu: Confirmed Bug description: My laptop fails to suspend. The screen turns off, but the fans continue to run (and it may actually get hotter). I wait and wait, and nothing happens (the power indicator remains always on). I tried suspending using the GUI, pressing the power button, closing the lid, and even through the terminal with the "pm-suspend" command. Nothing worked. Suspend worked fine on Ubuntu 15.10 and older releases, but since I upgraded to 16.04 I'm unable to put it to sleep. In fact, I had an old 4.2 kernel installed from Wily. I booted into it and it suspended and then resumed flawlessly, so it really seems to be a kernel related bug. I'll gladly perform any testing procedures that you may need to try to identify what the problem may be. I really hope that you are able to fix this soon, even if it will probably after the final release. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedro 2579 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 15 12:39:05 2016 HibernationDevice: RESUME=UUID=761da9d5-d078-4fb5-a4fc-eff7de723b18 InstallationDate: Installed on 2015-10-27 (170 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=8d1874c5-ce9f-481e-8d2a-ce85da5cd7fe ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-09 (5 days ago) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP870Z5E-X01PT dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP870Z5E-X01PT:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570820/+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 1570872] Re: Trusty update to 3.16.7-ckt27 stable release
** Changed in: linux-lts-utopic (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1570872
Title:
Trusty update to 3.16.7-ckt27 stable release
Status in linux-lts-utopic package in Ubuntu:
New
Status in linux-lts-utopic source package in Trusty:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The 3.16.7-ckt27 upstream
stable
patch set is now available. It should be included in the Ubuntu
kernel as well.
git://kernel.ubuntu.com/ubuntu/linux.git
TEST CASE: TBD
The following patches from the 3.16.7-ckt27 stable release
shall be applied:
ipv4: Don't do expensive useless work during inetdev destroy.
Input: powermate - fix oops with malicious USB descriptors
USB: iowarrior: fix oops with malicious USB descriptors
ALSA: usb-audio: Fix NULL dereference in create_fixed_stream_quirk()
ALSA: usb-audio: Add sanity checks for endpoint accesses
include/linux/poison.h: fix LIST_POISON{1,2} offset
cpu: Defer smpboot kthread unparking until CPU known to scheduler
ipr: Fix out-of-bounds null overwrite
ipr: Fix regression when loading firmware
Input: ati_remote2 - fix crashes on detecting device with invalid descriptor
USB: cdc-acm: more sanity checking
ceph: fix request time stamp encoding
cpu: Provide smpboot_thread_init() on !CONFIG_SMP kernels as well
x86/iopl/64: Properly context-switch IOPL on Xen PV
staging: comedi: ni_tiocmd: change mistaken use of start_src for start_arg
drm/radeon: hold reference to fences in radeon_sa_bo_new (3.17 and older)
Drivers: hv: vmbus: prevent cpu offlining on newer hypervisors
Linux 3.16.7-ckt27
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1570872/+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 1454843] Re: 10ec:b723 Realtek RTL8723BE wireless card drops connection
Is there any further information on this bug? I am using an HP Pavilion 15, with RT8723be, on Ubuntu 14.04/ 3.19. I'm having the same issue as this bu (and previous #1320070), and am hesitant about following some of the suggestions as posters tend to report that they do not work, blacklist the card, etc. The wifi works for about 30 minutes, must reboot to regain connection, and speed ridiculously slow. Thanks to advise. -- 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/1454843 Title: 10ec:b723 Realtek RTL8723BE wireless card drops connection Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: I am using Lenovo M30-70. I tried many workarounds from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320070 but no change, the connection is lost after a while. Finally I tried the rtlwifi_new driver from https://bugzilla.kernel.org/show_bug.cgi?id=83641#c1. I first thought it works stable but after a while it also loses the connection (see my comment there). After reconnect it works for a while again. I uninstalled the rtlwifi_new driver for this bug report. (Bluetooth does not work at all, it doesn't find any devices) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-17-generic 3.19.0-17.17 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sledzik2179 F pulseaudio CurrentDesktop: Unity Date: Wed May 13 22:51:38 2015 HibernationDevice: RESUME=UUID=d61164da-04eb-444a-a976-6a1f91fc4ffb InstallationDate: Installed on 2015-03-11 (63 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: LENOVO ZIUS6 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic.efi.signed root=UUID=40721d88-7203-4dfa-ac65-1a2b204fea34 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-17-generic N/A linux-backports-modules-3.19.0-17-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-06 (36 days ago) dmi.bios.date: 10/15/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 8BCN45WW(V3.08) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: INVALID dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvr8BCN45WW(V3.08):bd10/15/2014:svnLENOVO:pnZIUS6:pvrINVALID:rvnLENOVO:rnINVALID:rvrINVALID:cvnLENOVO:ct10:cvrINVALID: dmi.product.name: ZIUS6 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1454843/+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 1570906] Re: sysfs mount failure during stateful lxd snapshots
** Description changed: SRU Justification: Impact: Stateful lxd container snapshotting fails due to a failure to mount the container's sysfs in the host's user namespace. This is a regression. Fix: Force kernfs to use a new super block for mounts in different user namespaces. Test Case: "lxc snapshot --stateful " fails in the current xenial kernel without the fix. It succeeds with the fix applied. --- During a stateful lxd snapshot criu tries to mount sysfs for the container's network namespace from a different user namespace. This fails in xenial because sget() won't allow mounting the same super block in different user namespaces. With sysfs there's no reason that this needs to use the same super block, so kernfs can be updated so that a super block with the same ns tag but in a different userns is not matched. The only other kernfs- based filesystem mountable from non-init user namespaces is cgroupfs, and it's already forcing kernfs to return different super blocks to - avoid similar problems. In fact we can revert part of the cgroupfs - changes to make this happen if we push this behavior into kernfs. + avoid similar problems. -- 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/1570906 Title: sysfs mount failure during stateful lxd snapshots Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: SRU Justification: Impact: Stateful lxd container snapshotting fails due to a failure to mount the container's sysfs in the host's user namespace. This is a regression. Fix: Force kernfs to use a new super block for mounts in different user namespaces. Test Case: "lxc snapshot --stateful " fails in the current xenial kernel without the fix. It succeeds with the fix applied. --- During a stateful lxd snapshot criu tries to mount sysfs for the container's network namespace from a different user namespace. This fails in xenial because sget() won't allow mounting the same super block in different user namespaces. With sysfs there's no reason that this needs to use the same super block, so kernfs can be updated so that a super block with the same ns tag but in a different userns is not matched. The only other kernfs- based filesystem mountable from non-init user namespaces is cgroupfs, and it's already forcing kernfs to return different super blocks to avoid similar problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570906/+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 1516547] Re: Ubuntu 15.10 crashes with RAID-10
** Changed in: linux (Ubuntu Wily) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1516547 Title: Ubuntu 15.10 crashes with RAID-10 Status in linux package in Ubuntu: Incomplete Status in linux source package in Wily: Incomplete Bug description: When trying to install Ubuntu 15.10 with a RAID-10 created the system crashes after some time during the installation. Hitting Alt+F4 gives the following output as seen from screenshots in attachments. It looks like kernel 4.2 have some issues with RAID-10 as we can install Ubuntu 15.04 (with kernel 3.19) without problems. If we upgrade to kernel 4.2 in Ubuntu 15.04 we get the same errors. We have no problems when installing without RAID, RAID-0 or RAID-1. We've also tried on different hardware and different disk types/sizes but we still get system crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516547/+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 1570906] Re: sysfs mount failure during stateful lxd snapshots
New test build: http://kernel.ubuntu.com/~sforshee/lp1570906/ -- 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/1570906 Title: sysfs mount failure during stateful lxd snapshots Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: SRU Justification: Impact: Stateful lxd container snapshotting fails due to a failure to mount the container's sysfs in the host's user namespace. This is a regression. Fix: Force kernfs to use a new super block for mounts in different user namespaces. Test Case: "lxc snapshot --stateful " fails in the current xenial kernel without the fix. It succeeds with the fix applied. --- During a stateful lxd snapshot criu tries to mount sysfs for the container's network namespace from a different user namespace. This fails in xenial because sget() won't allow mounting the same super block in different user namespaces. With sysfs there's no reason that this needs to use the same super block, so kernfs can be updated so that a super block with the same ns tag but in a different userns is not matched. The only other kernfs- based filesystem mountable from non-init user namespaces is cgroupfs, and it's already forcing kernfs to return different super blocks to avoid similar problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570906/+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 1570906] Re: sysfs mount failure during stateful lxd snapshots
I can confirm that the kernels at http://kernel.ubuntu.com/~sforshee/lp1570906/ work for me. Thanks, Seth! -- 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/1570906 Title: sysfs mount failure during stateful lxd snapshots Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: SRU Justification: Impact: Stateful lxd container snapshotting fails due to a failure to mount the container's sysfs in the host's user namespace. This is a regression. Fix: Force kernfs to use a new super block for mounts in different user namespaces. Test Case: "lxc snapshot --stateful " fails in the current xenial kernel without the fix. It succeeds with the fix applied. --- During a stateful lxd snapshot criu tries to mount sysfs for the container's network namespace from a different user namespace. This fails in xenial because sget() won't allow mounting the same super block in different user namespaces. With sysfs there's no reason that this needs to use the same super block, so kernfs can be updated so that a super block with the same ns tag but in a different userns is not matched. The only other kernfs- based filesystem mountable from non-init user namespaces is cgroupfs, and it's already forcing kernfs to return different super blocks to avoid similar problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570906/+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 1570820] Re: Suspend failure
-- PLEASE DISREGARD MY PREVIOUS COMMENT -- The suspend issue is not present on 4.4.6 mainline kernel. So this must be some issue with some additional patching that is done to the official kernel. Meanwhile, I also went back to the 4.4.5 kernel and it suspends and resumes flawlessly. Besides that, I noticed that 4.4.7 is not without its share of problems. First of all, it displays an error on boot stating that radeon VCE failed to initialize (I have a dedicate AMD GPU on my laptop, besides the Intel GPU bundled with the CPU). This is a minor thing (I guess). However, the more concerning issue I noticed is that resuming from a suspended state, I just can't shutdown or reboot the system. It freezes while shutting down on a black screen with a white blinking cursor. I waited for a while and nothing happened. This is probably unrelated with the rest of the bug. Notwithstanding, I thought that I should mention it just so that you are aware that 4.4.7 also introduces a few issues, even though it seems to be unaffected by the suspending issues that I've been facing on the official 4.4.0-18 kernel. -- 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/1570820 Title: Suspend failure Status in linux package in Ubuntu: Confirmed Bug description: My laptop fails to suspend. The screen turns off, but the fans continue to run (and it may actually get hotter). I wait and wait, and nothing happens (the power indicator remains always on). I tried suspending using the GUI, pressing the power button, closing the lid, and even through the terminal with the "pm-suspend" command. Nothing worked. Suspend worked fine on Ubuntu 15.10 and older releases, but since I upgraded to 16.04 I'm unable to put it to sleep. In fact, I had an old 4.2 kernel installed from Wily. I booted into it and it suspended and then resumed flawlessly, so it really seems to be a kernel related bug. I'll gladly perform any testing procedures that you may need to try to identify what the problem may be. I really hope that you are able to fix this soon, even if it will probably after the final release. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedro 2579 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 15 12:39:05 2016 HibernationDevice: RESUME=UUID=761da9d5-d078-4fb5-a4fc-eff7de723b18 InstallationDate: Installed on 2015-10-27 (170 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=8d1874c5-ce9f-481e-8d2a-ce85da5cd7fe ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-09 (5 days ago) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP870Z5E-X01PT dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP870Z5E-X01PT:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570820/+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 1570780] Re: External Monitor makes System with Ubuntu 15.10 and Intel Graphics freeze
Things are getting a little better if I install: - Intel Graphics Installer for Linux* 1.4.0, from here https://01.org/linuxgraphics/downloads - The mainline kernel form here http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc3-wily/ The I can see the external display in System Settings/Display and the desktop background is displayed on the external display. But nevertheless, if I try to apply the new settings, the system freezes. -- 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/1570780 Title: External Monitor makes System with Ubuntu 15.10 and Intel Graphics freeze Status in linux package in Ubuntu: Confirmed Bug description: A Lenovo ThinkPad L460 with Intel Graphics freezes, if an external Monitor is connected via the docking station. Please tell me if any information to solve this issue is needed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic 4.2.0-35.40 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: knut 1724 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 15 11:56:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=3ed9dcc5-0917-4be8-a2df-82cc2f5f36ef InstallationDate: Installed on 2016-04-06 (9 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FVS01500 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic root=UUID=b6aaa9e7-c690-41f8-a56b-dc0043e4cc20 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R08ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FVS01500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR08ET35W(1.09):bd02/04/2016:svnLENOVO:pn20FVS01500:pvrThinkPadL460:rvnLENOVO:rn20FVS01500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FVS01500 dmi.product.version: ThinkPad L460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570780/+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 1570780] Re: External Monitor makes System with Ubuntu 15.10 and Intel Graphics freeze
If I select the external monitor as only used display, things work (up to now). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1570780 Title: External Monitor makes System with Ubuntu 15.10 and Intel Graphics freeze Status in linux package in Ubuntu: Confirmed Bug description: A Lenovo ThinkPad L460 with Intel Graphics freezes, if an external Monitor is connected via the docking station. Please tell me if any information to solve this issue is needed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-35-generic 4.2.0-35.40 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: knut 1724 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 15 11:56:45 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=3ed9dcc5-0917-4be8-a2df-82cc2f5f36ef InstallationDate: Installed on 2016-04-06 (9 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FVS01500 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic root=UUID=b6aaa9e7-c690-41f8-a56b-dc0043e4cc20 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-35-generic N/A linux-backports-modules-4.2.0-35-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R08ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FVS01500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR08ET35W(1.09):bd02/04/2016:svnLENOVO:pn20FVS01500:pvrThinkPadL460:rvnLENOVO:rn20FVS01500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FVS01500 dmi.product.version: ThinkPad L460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570780/+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 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
Ed, can you specify what is no longer happening? -- 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/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: On a recent intel NUC using i915 graphics, I get the following errors in dmesg: [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! There are two monitors connected to this box, one with mini- HDMI->HDMI, one with mini-DP->HDMI cable. Maybe related: https://bugs.freedesktop.org/show_bug.cgi?id=80896 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic 3.19.0.26.25 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Wed Aug 26 10:07:31 2015 InstallationDate: Installed on 2015-08-01 (24 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+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 1570820] Re: Suspend failure
** Tags added: kernel-fixed-upstream -- 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/1570820 Title: Suspend failure Status in linux package in Ubuntu: Confirmed Bug description: My laptop fails to suspend. The screen turns off, but the fans continue to run (and it may actually get hotter). I wait and wait, and nothing happens (the power indicator remains always on). I tried suspending using the GUI, pressing the power button, closing the lid, and even through the terminal with the "pm-suspend" command. Nothing worked. Suspend worked fine on Ubuntu 15.10 and older releases, but since I upgraded to 16.04 I'm unable to put it to sleep. In fact, I had an old 4.2 kernel installed from Wily. I booted into it and it suspended and then resumed flawlessly, so it really seems to be a kernel related bug. I'll gladly perform any testing procedures that you may need to try to identify what the problem may be. I really hope that you are able to fix this soon, even if it will probably after the final release. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedro 2579 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 15 12:39:05 2016 HibernationDevice: RESUME=UUID=761da9d5-d078-4fb5-a4fc-eff7de723b18 InstallationDate: Installed on 2015-10-27 (170 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=8d1874c5-ce9f-481e-8d2a-ce85da5cd7fe ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-09 (5 days ago) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP870Z5E-X01PT dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP870Z5E-X01PT:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570820/+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 1570820] Re: Suspend failure
I found some possible duplicates or related bugs: #1566302 #1565994 #1561301 (Same laptop series as mine) #1560202 #1559469 -- 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/1570820 Title: Suspend failure Status in linux package in Ubuntu: Confirmed Bug description: My laptop fails to suspend. The screen turns off, but the fans continue to run (and it may actually get hotter). I wait and wait, and nothing happens (the power indicator remains always on). I tried suspending using the GUI, pressing the power button, closing the lid, and even through the terminal with the "pm-suspend" command. Nothing worked. Suspend worked fine on Ubuntu 15.10 and older releases, but since I upgraded to 16.04 I'm unable to put it to sleep. In fact, I had an old 4.2 kernel installed from Wily. I booted into it and it suspended and then resumed flawlessly, so it really seems to be a kernel related bug. I'll gladly perform any testing procedures that you may need to try to identify what the problem may be. I really hope that you are able to fix this soon, even if it will probably after the final release. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedro 2579 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 15 12:39:05 2016 HibernationDevice: RESUME=UUID=761da9d5-d078-4fb5-a4fc-eff7de723b18 InstallationDate: Installed on 2015-10-27 (170 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=8d1874c5-ce9f-481e-8d2a-ce85da5cd7fe ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-09 (5 days ago) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP870Z5E-X01PT dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP870Z5E-X01PT:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570820/+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 1570984] [NEW] Unable to dump to multipath root filesystem on ppc64el
Public bug reported: Reproducer 1. Deploy trusty on a multipath rooted machine *(tested on ppc64el, may affect x86 as well). 2. Install 3.16 kernel *(has not been verified with other kernels). 3. sudo apt-get install linux-crashdump 4. Set USE_KDUMP=1 in /etc/default/kdump-tools 5. Set crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@32M in /etc/default/grub.d/kexec-tools.cfg 6. update-grub 7. reboot 8. echo 1 > /proc/sys/kernel/sysrq 9. echo c > /proc/sysrq-trigger Full console output attached. --Interesting parts of console output -- [ 33.160186] sd 0:2:5:0: alua: port group c289 state A preferred supports TOlUSNA [ 33.160324] sd 0:2:5:0: alua: Attached [ 33.160396] alua: device handler registered done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Loading multipath modules ... Success: loaded module dm-multipath. Failure: failed to load module dm-emc. done. Begin: Starting multipathd ... [ 33.194232] multipathd (253): /proc/253/oom_adj is deprecated, please use /proc/253/oom_score_adj instead. [ 33.197208] random: nonblocking pool is initialized done. Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Loading multipath modules ... Success: loaded module dm-multipath. Failure: failed to load module dm-emc. done. Begin: Starting multipathd ... done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mapper/mpath0-part2 does not exist. Dropping to a shell! [ 213.258259] hidraw: raw HID events driver (C) Jiri Kosina BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [ 396.459853] ipr 0003:04:00.0: 9076: Configuration error, missing remote IOA [ 396.459935] ipr 0003:04:00.0: Attached Adapter not discovered within allotted time [PRC: 17101541] [ 396.460023] ipr 0003:04:00.0: Remote IOA VPID/SN: [ 396.460085] ipr 0003:04:00.0: Remote IOA WWN: [ 396.460148] ipr: : 0100 0100 F422 [ 396.460210] ipr: 0010: 4C494344 49424D20 20202020 35374438 [ 396.460271] ipr: 0020: 30303153 4953494F 41202020 [ 396.460333] ipr: 0030: 30303431 4A303337 50050760 5EC28900 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: makedumpfile (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dump_crashkernel=40...@32m.txt" https://bugs.launchpad.net/bugs/1570984/+attachment/4637842/+files/dump_crashkernel%3D4096M%4032M.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1570984 Title: Unable to dump to multipath root filesystem on ppc64el Status in initramfs-tools package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Bug description: Reproducer 1. Deploy trusty on a multipath rooted machine *(tested on ppc64el, may affect x86 as well). 2. Install 3.16 kernel *(has not been verified with other kernels). 3. sudo apt-get install linux-crashdump 4. Set USE_KDUMP=1 in /etc/default/kdump-tools 5. Set crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@32M in /etc/default/grub.d/kexec-tools.cfg 6. update-grub 7. reboot 8. echo 1 > /proc/sys/kernel/sysrq 9. echo c > /proc/sysrq-trigger Full console output attached. --Interesting parts of console output -- [ 33.160186] sd 0:2:5:0: alua: port group c289 state A preferred supports TOlUSNA [ 33.160324] sd 0:2:5:0: alua: Attached [ 33.160396] alua: device handler registered done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Loading multipath modules ... Success: loaded module dm-multipath. Failure: failed to load module dm-emc. done. Begin: Starting multipathd ... [ 33.194232] multipathd (253): /proc/253/oom_adj is deprecated, please use /proc/253/oom_score_adj instead. [ 33.197208] random: nonblocking pool is initialized done. Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Loading multipath modules ... Success: loaded module dm-multipath. Failure: failed to load module dm-emc. done. Begin: Starting multipath
[Kernel-packages] [Bug 1570984] Re: Unable to dump to multipath root filesystem on ppc64el
This may also affect initramfs-tools, as that will likely be the place that any fix needs to be implemented. ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1570984 Title: Unable to dump to multipath root filesystem on ppc64el Status in initramfs-tools package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Bug description: Reproducer 1. Deploy trusty on a multipath rooted machine *(tested on ppc64el, may affect x86 as well). 2. Install 3.16 kernel *(has not been verified with other kernels). 3. sudo apt-get install linux-crashdump 4. Set USE_KDUMP=1 in /etc/default/kdump-tools 5. Set crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@32M in /etc/default/grub.d/kexec-tools.cfg 6. update-grub 7. reboot 8. echo 1 > /proc/sys/kernel/sysrq 9. echo c > /proc/sysrq-trigger Full console output attached. --Interesting parts of console output -- [ 33.160186] sd 0:2:5:0: alua: port group c289 state A preferred supports TOlUSNA [ 33.160324] sd 0:2:5:0: alua: Attached [ 33.160396] alua: device handler registered done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Loading multipath modules ... Success: loaded module dm-multipath. Failure: failed to load module dm-emc. done. Begin: Starting multipathd ... [ 33.194232] multipathd (253): /proc/253/oom_adj is deprecated, please use /proc/253/oom_score_adj instead. [ 33.197208] random: nonblocking pool is initialized done. Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Loading multipath modules ... Success: loaded module dm-multipath. Failure: failed to load module dm-emc. done. Begin: Starting multipathd ... done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mapper/mpath0-part2 does not exist. Dropping to a shell! [ 213.258259] hidraw: raw HID events driver (C) Jiri Kosina BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [ 396.459853] ipr 0003:04:00.0: 9076: Configuration error, missing remote IOA [ 396.459935] ipr 0003:04:00.0: Attached Adapter not discovered within allotted time [PRC: 17101541] [ 396.460023] ipr 0003:04:00.0: Remote IOA VPID/SN: [ 396.460085] ipr 0003:04:00.0: Remote IOA WWN: [ 396.460148] ipr: : 0100 0100 F422 [ 396.460210] ipr: 0010: 4C494344 49424D20 20202020 35374438 [ 396.460271] ipr: 0020: 30303153 4953494F 41202020 [ 396.460333] ipr: 0030: 30303431 4A303337 50050760 5EC28900 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1570984/+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 1542939] Re: system freeze after vt switching
Actually, this upstream bug is more likely to be related: https://bugs.freedesktop.org/show_bug.cgi?id=93509 -- this includes a tentative bisect indicating the commit. -- 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/1542939 Title: system freeze after vt switching Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1542939/+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 1542939] Re: system freeze after vt switching
This is affecting an increasing set of users; for instance, it seems to be the underlying problem in bug 1545238. My Thinkpad X220 is also showing the same problem, which suggests multiple Intel graphics systems may be affected. See upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=92171 and https://bugs.freedesktop.org/show_bug.cgi?id=89108 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Bug watch added: Linux Kernel Bug Tracker #92171 http://bugzilla.kernel.org/show_bug.cgi?id=92171 ** Bug watch added: freedesktop.org Bugzilla #89108 https://bugs.freedesktop.org/show_bug.cgi?id=89108 ** Bug watch added: freedesktop.org Bugzilla #93509 https://bugs.freedesktop.org/show_bug.cgi?id=93509 -- 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/1542939 Title: system freeze after vt switching Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1542939/+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 1570820] Re: Suspend failure
I added the "kernel-fixed-upstream" because the bug is also fixed on the latest upstream kernel available at http://kernel.ubuntu.com/~kernel- ppa/mainline/, which is 4.6.0rc3 at this time. However, please note that the shutdown/reboot issues that I found on 4.4.7 (comment #5) are also present on this kernel. -- 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/1570820 Title: Suspend failure Status in linux package in Ubuntu: Confirmed Bug description: My laptop fails to suspend. The screen turns off, but the fans continue to run (and it may actually get hotter). I wait and wait, and nothing happens (the power indicator remains always on). I tried suspending using the GUI, pressing the power button, closing the lid, and even through the terminal with the "pm-suspend" command. Nothing worked. Suspend worked fine on Ubuntu 15.10 and older releases, but since I upgraded to 16.04 I'm unable to put it to sleep. In fact, I had an old 4.2 kernel installed from Wily. I booted into it and it suspended and then resumed flawlessly, so it really seems to be a kernel related bug. I'll gladly perform any testing procedures that you may need to try to identify what the problem may be. I really hope that you are able to fix this soon, even if it will probably after the final release. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedro 2579 F pulseaudio CurrentDesktop: GNOME Date: Fri Apr 15 12:39:05 2016 HibernationDevice: RESUME=UUID=761da9d5-d078-4fb5-a4fc-eff7de723b18 InstallationDate: Installed on 2015-10-27 (170 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=8d1874c5-ce9f-481e-8d2a-ce85da5cd7fe ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-09 (5 days ago) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP870Z5E-X01PT dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP870Z5E-X01PT:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570820/+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 1542939] Re: system freeze after vt switching
Anther report confirming on x220: https://lists.freedesktop.org/archives /intel-gfx/2016-January/084198.html ** Bug watch added: Red Hat Bugzilla #1313323 https://bugzilla.redhat.com/show_bug.cgi?id=1313323 -- 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/1542939 Title: system freeze after vt switching Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+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 1542939] Re: system freeze after vt switching
And https://bugzilla.redhat.com/show_bug.cgi?id=1313323 ** Also affects: linux via https://bugs.freedesktop.org/show_bug.cgi?id=93509 Importance: Unknown Status: Unknown ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=1313323 Importance: Unknown Status: Unknown -- 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/1542939 Title: system freeze after vt switching Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+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 1530403] Re: CVE-2015-8550
** Description changed: - paravirtualized drivers incautious about shared memory contents + Xen, when used on a system providing PV backends, allows local guest OS + administrators to cause a denial of service (host OS crash) or gain + privileges by writing to memory shared between the frontend and backend, + aka a double fetch vulnerability. Break-Fix: - 454d5d882c7e412b840e3c99010fe81a9862f6fb Break-Fix: - 0f589967a73f1f30ab4ac4dd9ce0bb399b4d6357 Break-Fix: - 68a33bfd8403e4e22847165d149823a2e0e67c9c Break-Fix: - 1f13d75ccb806260079e0679d55d9253e370ec8a Break-Fix: 402b27f9f2c22309d5bb285628765bc27b82fcf5 18779149101c0dd43ded43669ae2a92d21b6f9cb Break-Fix: d9d660f6e562a47b4065eeb7e538910b0471b988 be69746ec12f35b484707da505c6c76ff06f97dc Break-Fix: - 8135cf8b092723dbfcc611fe6fdcb3a36c9951c5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1530403 Title: CVE-2015-8550 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid:
[Kernel-packages] [Bug 1556264] Re: [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read()
Would it be best to wait until the patch lands in mainline? That way we
ensure we are getting the correct version of the patch.
KY filed the first version of that patch on April 2, but then replied Greg to
drop the patch, it was the wrong version:
http://marc.info/?t=14596312011&r=1&w=2
On April 5, another version of the patch was submitted(same title,
different contents).
Also, there is another April 2 version with the title "[PATCH v2 1/1]" here:
http://marc.info/?t=145963331800024&r=1&w=2
If this "new version of the fix" is necessary to fix a bug, we may want
to open a new bug to ensure the fix gets tracked properly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1556264
Title:
[Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read()
Status in linux package in Ubuntu:
Fix Released
Status in linux-lts-vivid package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Fix Committed
Status in linux-lts-vivid source package in Trusty:
Fix Committed
Status in linux source package in Wily:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
The following patch has been submitted upstream in response to
investigation of customer issues with network connections hanging
under high load.
On the consumer side, we have interrupt driven flow management of the
producer. It is sufficient to base the signalling decision on the
amount of space that is available to write after the read is complete.
The current code samples the previous available space and uses this in
making the signalling decision. This state can be stale and is
unnecessary. Since the state can be stale, we end up not signalling
the host (when we should) and this can result in a hang. Fix this
problem by removing the unnecessary check.
I would like to thank Arseney Romanenko
for pointing out this bug.
Signed-off-by: K. Y. Srinivasan
Tested-by: Dexuan Cui
Cc:
---
drivers/hv/ring_buffer.c |7 +++
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c
index 5613e2b..085003a 100644
--- a/drivers/hv/ring_buffer.c
+++ b/drivers/hv/ring_buffer.c
@@ -103,8 +103,7 @@ static bool hv_need_to_signal(u32 old_write, struct
hv_ring_buffer_info *rbi)
*there is room for the producer to send the pending packet.
*/
-static bool hv_need_to_signal_on_read(u32 prev_write_sz,
- struct hv_ring_buffer_info *rbi)
+static bool hv_need_to_signal_on_read(struct hv_ring_buffer_info *rbi)
{
u32 cur_write_sz;
u32 r_size;
@@ -120,7 +119,7 @@ static bool hv_need_to_signal_on_read(u32 prev_write_sz,
cur_write_sz = write_loc >= read_loc ? r_size - (write_loc -
read_loc) :
read_loc - write_loc;
- if ((prev_write_sz < pending_sz) && (cur_write_sz >= pending_sz))
+ if (cur_write_sz >= pending_sz)
return true;
return false;
@@ -455,7 +454,7 @@ int hv_ringbuffer_read(struct hv_ring_buffer_info
*inring_info,
/* Update the read index */
hv_set_next_read_location(inring_info, next_read_location);
- *signal = hv_need_to_signal_on_read(bytes_avail_towrite, inring_info);
+ *signal = hv_need_to_signal_on_read(inring_info);
return ret;
}
We have customers who are encountering this issue. Although this patch
is not yet accepted upstream, we would like to get them a test kernel
as soon as we can.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556264/+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 1454843] Re: 10ec:b723 Realtek RTL8723BE wireless card drops connection
@J A Brows: From what I know the bug is still unpatched. The solutions proposed by some in my case tend to stop working when, for example, a system update is performed. -- 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/1454843 Title: 10ec:b723 Realtek RTL8723BE wireless card drops connection Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: I am using Lenovo M30-70. I tried many workarounds from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320070 but no change, the connection is lost after a while. Finally I tried the rtlwifi_new driver from https://bugzilla.kernel.org/show_bug.cgi?id=83641#c1. I first thought it works stable but after a while it also loses the connection (see my comment there). After reconnect it works for a while again. I uninstalled the rtlwifi_new driver for this bug report. (Bluetooth does not work at all, it doesn't find any devices) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-17-generic 3.19.0-17.17 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sledzik2179 F pulseaudio CurrentDesktop: Unity Date: Wed May 13 22:51:38 2015 HibernationDevice: RESUME=UUID=d61164da-04eb-444a-a976-6a1f91fc4ffb InstallationDate: Installed on 2015-03-11 (63 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: LENOVO ZIUS6 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic.efi.signed root=UUID=40721d88-7203-4dfa-ac65-1a2b204fea34 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-17-generic N/A linux-backports-modules-3.19.0-17-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-06 (36 days ago) dmi.bios.date: 10/15/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 8BCN45WW(V3.08) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: INVALID dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvr8BCN45WW(V3.08):bd10/15/2014:svnLENOVO:pnZIUS6:pvrINVALID:rvnLENOVO:rnINVALID:rvrINVALID:cvnLENOVO:ct10:cvrINVALID: dmi.product.name: ZIUS6 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1454843/+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 1571013] [NEW] CVE-2015-8844
*** This bug is a security vulnerability *** Public security bug reported: A flaw was found in the linux kernel which could cause a kernel panic when restoring machine specific registers on ppc platform. Incorrect transactional memory state registers could inadvertently change the call path on return from userspace and cause the kernel to enter an unknown state in the transactional memory handling code and panic in a BUG_ON() defensively. Break-Fix: 2b0a576d15e0e14751f00f9c87e46bad27f217e7 d2b9d2a5ad5ef04ff978c9923d19730cb05efd55 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-wily (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-xenial (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Medium Status: New ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-wily (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-xenial (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-wily (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-xenial (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu Vivid) Importance: Undecided Status: New ** Affe
[Kernel-packages] [Bug 1571013] Re: CVE-2015-8844
CVE-2015-8844 ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mako (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-goldfish (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-flo (Ubuntu Precise) Status: New => Invalid ** Description changed: - Placeholder + A flaw was found in the linux kernel which could cause a kernel panic + when restoring machine specific registers on ppc platform. Incorrect + transactional memory state registers could inadvertently change the call + path on return from userspace and cause the kernel to enter an unknown + state in the transactional memory handling code and panic in a BUG_ON() + defensively. + + Break-Fix: 2b0a576d15e0e14751f00f9c87e46bad27f217e7 + d2b9d2a5ad5ef04ff978c9923d19730cb05efd55 ** Changed in: linux-lts-trusty (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-lts-trusty (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-trusty (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-lts-trusty (Ubuntu Trusty) Importance: Undecided => Medium ** Changed
[Kernel-packages] [Bug 1571020] [NEW] CVE-2016-3961
*** This bug is a security vulnerability *** Public security bug reported: hugetlbfs use may crash PV Linux guests ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-wily (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-xenial (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Medium Status: New ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-wily (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-xenial (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-wily (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-xenial (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-flo (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-goldfish (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-lts-raring (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-lts-saucy (Ubuntu Vivid) Importance: Undeci
[Kernel-packages] [Bug 1571020] Re: CVE-2016-3961
CVE-2016-3961 ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mako (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-goldfish (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-flo (Ubuntu Precise) Status: New => Invalid ** Description changed: - Placeholder + hugetlbfs use may crash PV Linux guests ** Changed in: linux-lts-trusty (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-lts-trusty (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-trusty (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-lts-trusty (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux-lts-wily (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-lts-wily (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-wily (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-lts-wily (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1571018] [NEW] CVE-2015-8845
*** This bug is a security vulnerability *** Public security bug reported: Similar to CVE-2015-8844, QEMU guests can also modify the same machine specific register values via set_one_reg and guests may invoke the same unknown state and callpath. Break-Fix: fb09692e71f13af7298eb603a1975850b1c7a8d8 7f821fc9c77a9b01fe7b1d6e72717b33d8d64142 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-wily (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-xenial (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Medium Status: New ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-wily (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-xenial (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-wily (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-xenial (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-raspi2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-flo (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-goldfish (Ubuntu Vivid) Importance: Undecided Status: New ** Affects: linux-lts-quanta
[Kernel-packages] [Bug 1571027] [NEW] Wily update to v4.2.8-ckt8 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.2.8-ckt8 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches from the v4.2.8-ckt8 stable release shall be applied: Linux 4.2.8-ckt8 net: phy: at803x: Request 'reset' GPIO only for AT8030 PHY mwifiex: fix corner case association failure ALSA: hda - Add new GPU codec ID 0x10de0082 to snd-hda perf/x86/intel: Fix PEBS data source interpretation on Nehalem/Westmere ipr: Fix regression when loading firmware ipr: Fix out-of-bounds null overwrite lib/ucs2_string: Correct ucs2 -> utf8 conversion efi: Add pstore variables to the deletion whitelist efi: Make efivarfs entries immutable by default efi: Make our variable validation list include the guid efi: Do variable name validation tests in utf8 efi: Use ucs2_as_utf8 in efivarfs instead of open coding a bad version lib/ucs2_string: Add ucs2 -> utf8 helper functions KVM: x86: move steal time initialization to vcpu entry time ip6_tunnel: set rtnl_link_ops before calling register_netdevice pinctrl: nomadik: fix pull debug print inversion ipv6: udp: fix UDP_MIB_IGNOREDMULTI updates net: bcmgenet: fix skb_len in bcmgenet_xmit_single() net: bcmgenet: fix dev->stats.tx_bytes accounting net: macb: replace macb_writel() call by queue_writel() to update queue ISR parisc: Unbreak handling exceptions from kernel modules parisc: Fix kernel crash with reversed copy_from_user() parisc: Avoid function pointers for kernel exception routines gpio: pca953x: Use correct u16 value for register word write libnvdimm: fix smart data retrieval virtio: virtio 1.0 cs04 spec compliance for reset USB: option: add "D-Link DWM-221 B1" device id USB: serial: cp210x: Adding GE Healthcare Device ID USB: serial: ftdi_sio: Add support for ICP DAS I-756xU devices Btrfs: fix file/data loss caused by fsync after rename and new inode rbd: use GFP_NOIO consistently for request allocations compiler-gcc: disable -ftracer for __noclone functions mac80211: properly deal with station hashtable insert errors usb: renesas_usbhs: fix to avoid using a disabled ep in usbhsg_queue_done() xen/events: Mask a moving irq ext4: ignore quota mount options if the quota feature is enabled iio: st_magn: always define ST_MAGN_TRIGGER_SET_STATE mm: fix invalid node in alloc_migrate_target() ALSA: timer: Use mod_timer() for rearming the system timer KVM: x86: Inject pending interrupt even if pending nmi exist ALSA: hda - fix front mic problem for a HP desktop ext4: add lockdep annotations for i_data_sem drm/udl: Use unlocked gem unreferencing drm/dp: move hw_mutex up the call stack sd: Fix excessive capacity printing on devices with blocks bigger than 512 bytes [media] au0828: Fix dev_state handling [media] au0828: fix au0828_v4l2_close() dev_state race condition USB: digi_acceleport: do sanity checking for the number of ports USB: cypress_m8: add endpoint sanity check USB: mct_u232: add sanity checking in probe ALSA: usb-audio: Fix double-free in error paths after snd_usb_add_audio_stream() call ALSA: usb-audio: Minor code cleanup in create_fixed_stream_quirk() btrfs: fix crash/invalid memory access on fsync when using overlayfs usb: renesas_usbhs: disable TX IRQ before starting TX DMAC transfer usb: renesas_usbhs: avoid NULL pointer derefernce in usbhsf_pkt_handler() pinctrl: sunxi: Fix A33 external interrupts not working pinctrl: pistachio: fix mfio84-89 function description and pinmux. powerpc/mm: Fixup preempt underflow with huge pages drm/radeon: add a dpm quirk for all R7 370 parts drm/radeon: add another R7 370 quirk hwmon: (max) Return -ENODEV from max_read_channel if not instantiated nfs: use file_dentry() fs: add file_dentry() drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 ALSA: hda - Apply fix for white noise on Asus N550JV, too ALSA: hda - Fix white noise on Asus N750JV headphone ALSA: hda - Asus N750JV external subwoofer fixup PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Wily) Importance: Undecided Status: Fix Committed ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New -- 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/1571027 Title: Wily update to v4.2.8-ckt8 stable release Status in linux pack
[Kernel-packages] [Bug 1571018] Re: CVE-2015-8845
CVE-2015-8845 ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-xenial (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mako (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-goldfish (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-flo (Ubuntu Precise) Status: New => Invalid ** Description changed: - Placeholder + Similar to CVE-2015-8844, QEMU guests can also modify the same machine + specific register values via set_one_reg and guests may invoke the same + unknown state and callpath. + + Break-Fix: fb09692e71f13af7298eb603a1975850b1c7a8d8 + 7f821fc9c77a9b01fe7b1d6e72717b33d8d64142 ** Changed in: linux-lts-trusty (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-lts-trusty (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-trusty (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-lts-trusty (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux-lts-wily (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux-lts-wily (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux-lts-wily (Ubuntu Xenial) Im
[Kernel-packages] [Bug 1571027] Re: Wily update to v4.2.8-ckt8 stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The v4.2.8-ckt8 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The v4.2.8-ckt8 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://kernel.ubuntu.com/ubuntu/linux.git -git://kernel.ubuntu.com/ubuntu/linux.git + TEST CASE: TBD - TEST CASE: TBD + The following patches from the v4.2.8-ckt8 stable release shall + be applied: -The following patches from the v4.2.8-ckt8 stable release shall - be applied: + Linux 4.2.8-ckt8 + net: phy: at803x: Request 'reset' GPIO only for AT8030 PHY + mwifiex: fix corner case association failure + ALSA: hda - Add new GPU codec ID 0x10de0082 to snd-hda + perf/x86/intel: Fix PEBS data source interpretation on Nehalem/Westmere + ipr: Fix regression when loading firmware + ipr: Fix out-of-bounds null overwrite + lib/ucs2_string: Correct ucs2 -> utf8 conversion + efi: Add pstore variables to the deletion whitelist + efi: Make efivarfs entries immutable by default + efi: Make our variable validation list include the guid + efi: Do variable name validation tests in utf8 + efi: Use ucs2_as_utf8 in efivarfs instead of open coding a bad version + lib/ucs2_string: Add ucs2 -> utf8 helper functions + KVM: x86: move steal time initialization to vcpu entry time + ip6_tunnel: set rtnl_link_ops before calling register_netdevice + pinctrl: nomadik: fix pull debug print inversion + ipv6: udp: fix UDP_MIB_IGNOREDMULTI updates + net: bcmgenet: fix skb_len in bcmgenet_xmit_single() + net: bcmgenet: fix dev->stats.tx_bytes accounting + net: macb: replace macb_writel() call by queue_writel() to update queue ISR + parisc: Unbreak handling exceptions from kernel modules + parisc: Fix kernel crash with reversed copy_from_user() + parisc: Avoid function pointers for kernel exception routines + gpio: pca953x: Use correct u16 value for register word write + libnvdimm: fix smart data retrieval + virtio: virtio 1.0 cs04 spec compliance for reset + USB: option: add "D-Link DWM-221 B1" device id + USB: serial: cp210x: Adding GE Healthcare Device ID + USB: serial: ftdi_sio: Add support for ICP DAS I-756xU devices + Btrfs: fix file/data loss caused by fsync after rename and new inode + rbd: use GFP_NOIO consistently for request allocations + compiler-gcc: disable -ftracer for __noclone functions + mac80211: properly deal with station hashtable insert errors + usb: renesas_usbhs: fix to avoid using a disabled ep in usbhsg_queue_done() + xen/events: Mask a moving irq + ext4: ignore quota mount options if the quota feature is enabled + iio: st_magn: always define ST_MAGN_TRIGGER_SET_STATE + mm: fix invalid node in alloc_migrate_target() + ALSA: timer: Use mod_timer() for rearming the system timer + KVM: x86: Inject pending interrupt even if pending nmi exist + ALSA: hda - fix front mic problem for a HP desktop + ext4: add lockdep annotations for i_data_sem + drm/udl: Use unlocked gem unreferencing + drm/dp: move hw_mutex up the call stack + sd: Fix excessive capacity printing on devices with blocks bigger than 512 bytes + [media] au0828: Fix dev_state handling + [media] au0828: fix au0828_v4l2_close() dev_state race condition + USB: digi_acceleport: do sanity checking for the number of ports + USB: cypress_m8: add endpoint sanity check + USB: mct_u232: add sanity checking in probe + ALSA: usb-audio: Fix double-free in error paths after snd_usb_add_audio_stream() call + ALSA: usb-audio: Minor code cleanup in create_fixed_stream_quirk() + btrfs: fix crash/invalid memory access on fsync when using overlayfs + usb: renesas_usbhs: disable TX IRQ before starting TX DMAC transfer + usb: renesas_usbhs: avoid NULL pointer derefernce in usbhsf_pkt_handler() + pinctrl: sunxi: Fix A33 external interrupts not working + pinctrl: pistachio: fix mfio84-89 function description and pinmux. + powerpc/mm: Fixup preempt underflow with huge pages + drm/radeon: add a dpm quirk for all R7 370 parts + drm/radeon: add another R7 370 quirk + hwmon: (max) Return -ENODEV from max_read_channel if not instantiated + nfs: use file_dentry() + fs: add file_dentry() + drm/radeon: add a dpm qui
[Kernel-packages] [Bug 1545441] Re: Xenial/4.4 kernel does not honor biosdevname=0
The desired behaviour can be achieved by adding the following to the default boot options: biosdevname=0 net.ifnames=0 vagrant@xenialvagranttest:~$ uname -ar Linux xenialvagranttest 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:01:02 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux vagrant@xenialvagranttest:~$ ifconfig eth eth0 Link encap:Ethernet HWaddr 00:1c:42:57:c7:7b inet addr:10.211.55.87 Bcast:10.211.55.255 Mask:255.255.255.0 inet6 addr: fdb2:2c26:f4e4:0:21c:42ff:fe57:c77b/64 Scope:Global inet6 addr: fe80::21c:42ff:fe57:c77b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:430 errors:0 dropped:0 overruns:0 frame:0 TX packets:299 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:49716 (49.7 KB) TX bytes:46366 (46.3 KB) (Based on xenial-server-amd64 daily 15-Apr-2016 07:01 / MD5: 5bc331a1aa7faaa330278bd31a1b101d) preseed.cfg: d-i debian-installer/add-kernel-opts string biosdevname=0 net.ifnames=0 -- 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/1545441 Title: Xenial/4.4 kernel does not honor biosdevname=0 Status in linux package in Ubuntu: Confirmed Bug description: I installed the Xenial daily testing image dated 2-13-2016 (ttp://cdimage.ubuntu.com/lubuntu/daily-live/20160213/xenial- desktop-i386.iso). I'm booting the kernel with the following: ipv6.disable=1 biosdevname=0 longhaul.enable=0 audit=0 quiet splash However, eth0 is being named enp3s0: $ dmesg | egrep 'r8169|net|eth' [0.017363] Initializing cgroup subsys net_cls [0.017377] Initializing cgroup subsys net_prio [3.150713] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [3.150735] r8169 :03:00.0: can't disable ASPM; OS doesn't have ASPM control [3.150765] r8169 :03:00.0: PCI: Disallowing DAC for device [3.151266] r8169 :03:00.0 eth0: RTL8102e at 0xf844a000, 00:e0:4c:52:ca:07, XID 04e0 IRQ 26 [3.263623] r8169 :03:00.0 enp3s0: renamed from eth0 [ 15.729303] r8169 :03:00.0 enp3s0: link down [ 15.729327] r8169 :03:00.0 enp3s0: link down [ 17.381617] r8169 :03:00.0 enp3s0: link up And: $ cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp And: $ ls -Al /etc/udev/rules.d/ total 0 The thing that looks most different (to me) is systemd. For more information on biosdevname, see "Consistent Network Device Naming in Linux," http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf. $ uname -a Linux via 4.4.0-4-generic #19-Ubuntu SMP Fri Feb 5 17:38:10 UTC 2016 i686 i686 i686 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 Codename: xenial And hats of for fixing the Xserver problems with the VIA P4M900 chipset (http://bugs.launchpad.net/ubuntu/+bug/1540774). --- ApportVersion: 2.19.4-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jwalton1598 F lxpanel CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=89996fc5-18ba-4db7-b7d9-9be56ec02a13 InstallationDate: Installed on 2016-02-14 (0 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160213) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic root=UUID=edc978dd-91b1-4f90-8e6a-1e69dd73f5d8 ro ipv6.disable=1 biosdevname=0 longhaul.enable=0 audit=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 RelatedPackageVersions: linux-restricted-modules-4.4.0-4-generic N/A linux-backports-modules-4.4.0-4-generic N/A linux-firmware 1.155 RfKill: Tags: xenial Uname: Linux 4.4.0-4-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/17/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Weibu dmi.board.vendor: WB dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.cha
[Kernel-packages] [Bug 1571034] [NEW] Vivid update to v3.19.8-ckt19 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v3.19.8-ckt19 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches from the v3.19.8-ckt19 stable release shall be applied: Linux 3.19.8-ckt19 net: phy: at803x: Request 'reset' GPIO only for AT8030 PHY mwifiex: fix corner case association failure ALSA: hda - Add new GPU codec ID 0x10de0082 to snd-hda perf/x86/intel: Fix PEBS data source interpretation on Nehalem/Westmere ipr: Fix regression when loading firmware ipr: Fix out-of-bounds null overwrite lib/ucs2_string: Correct ucs2 -> utf8 conversion efi: Add pstore variables to the deletion whitelist efi: Make efivarfs entries immutable by default efi: Make our variable validation list include the guid efi: Do variable name validation tests in utf8 efi: Use ucs2_as_utf8 in efivarfs instead of open coding a bad version lib/ucs2_string: Add ucs2 -> utf8 helper functions KVM: x86: move steal time initialization to vcpu entry time ipv6: udp: fix UDP_MIB_IGNOREDMULTI updates pinctrl: nomadik: fix pull debug print inversion net: bcmgenet: fix skb_len in bcmgenet_xmit_single() ip6_tunnel: set rtnl_link_ops before calling register_netdevice parisc: Unbreak handling exceptions from kernel modules parisc: Fix kernel crash with reversed copy_from_user() gpio: pca953x: Use correct u16 value for register word write ext4: ignore quota mount options if the quota feature is enabled KVM: x86: Inject pending interrupt even if pending nmi exist ALSA: hda - fix front mic problem for a HP desktop drm/udl: Use unlocked gem unreferencing drm/dp: move hw_mutex up the call stack sd: Fix excessive capacity printing on devices with blocks bigger than 512 bytes ALSA: usb-audio: Fix double-free in error paths after snd_usb_add_audio_stream() call ALSA: usb-audio: Minor code cleanup in create_fixed_stream_quirk() drm/radeon: add a dpm quirk for all R7 370 parts parisc: Avoid function pointers for kernel exception routines USB: option: add "D-Link DWM-221 B1" device id USB: serial: cp210x: Adding GE Healthcare Device ID USB: serial: ftdi_sio: Add support for ICP DAS I-756xU devices rbd: use GFP_NOIO consistently for request allocations xen/events: Mask a moving irq iio: st_magn: always define ST_MAGN_TRIGGER_SET_STATE mm: fix invalid node in alloc_migrate_target() ALSA: timer: Use mod_timer() for rearming the system timer ext4: add lockdep annotations for i_data_sem USB: digi_acceleport: do sanity checking for the number of ports USB: cypress_m8: add endpoint sanity check USB: mct_u232: add sanity checking in probe usb: renesas_usbhs: disable TX IRQ before starting TX DMAC transfer usb: renesas_usbhs: avoid NULL pointer derefernce in usbhsf_pkt_handler() powerpc/mm: Fixup preempt underflow with huge pages drm/radeon: add another R7 370 quirk hwmon: (max) Return -ENODEV from max_read_channel if not instantiated drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 ALSA: hda - Apply fix for white noise on Asus N550JV, too ALSA: hda - Fix white noise on Asus N750JV headphone ALSA: hda - Asus N750JV external subwoofer fixup PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Vivid) Importance: Undecided Status: Fix Committed ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The v3.19.8-ckt19 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The v3.19.8-ckt19 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as we
[Kernel-packages] [Bug 1571041] [NEW] Trusty update to v3.13.11-ckt39 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v3.13.11-ckt39 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches from the v3.13.11-ckt39 stable release shall be applied: Linux 3.13.11-ckt39 ip6_tunnel: set rtnl_link_ops before calling register_netdevice parisc: Avoid function pointers for kernel exception routines USB: option: add "D-Link DWM-221 B1" device id USB: serial: cp210x: Adding GE Healthcare Device ID USB: serial: ftdi_sio: Add support for ICP DAS I-756xU devices iio: st_magn: always define ST_MAGN_TRIGGER_SET_STATE mm: fix invalid node in alloc_migrate_target() ALSA: timer: Use mod_timer() for rearming the system timer USB: digi_acceleport: do sanity checking for the number of ports USB: cypress_m8: add endpoint sanity check USB: mct_u232: add sanity checking in probe usb: renesas_usbhs: disable TX IRQ before starting TX DMAC transfer usb: renesas_usbhs: avoid NULL pointer derefernce in usbhsf_pkt_handler() drm/radeon: add another R7 370 quirk hwmon: (max) Return -ENODEV from max_read_channel if not instantiated drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: Fix Committed ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New -- 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/1571041 Title: Trusty update to v3.13.11-ckt39 stable release Status in linux package in Ubuntu: New Status in linux source package in Trusty: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v3.13.11-ckt39 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches from the v3.13.11-ckt39 stable release shall be applied: Linux 3.13.11-ckt39 ip6_tunnel: set rtnl_link_ops before calling register_netdevice parisc: Avoid function pointers for kernel exception routines USB: option: add "D-Link DWM-221 B1" device id USB: serial: cp210x: Adding GE Healthcare Device ID USB: serial: ftdi_sio: Add support for ICP DAS I-756xU devices iio: st_magn: always define ST_MAGN_TRIGGER_SET_STATE mm: fix invalid node in alloc_migrate_target() ALSA: timer: Use mod_timer() for rearming the system timer USB: digi_acceleport: do sanity checking for the number of ports USB: cypress_m8: add endpoint sanity check USB: mct_u232: add sanity checking in probe usb: renesas_usbhs: disable TX IRQ before starting TX DMAC transfer usb: renesas_usbhs: avoid NULL pointer derefernce in usbhsf_pkt_handler() drm/radeon: add another R7 370 quirk hwmon: (max) Return -ENODEV from max_read_channel if not instantiated drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571041/+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 1454843] Re: 10ec:b723 Realtek RTL8723BE wireless card drops connection
Have you already checked post #13? In my case, the hp pavillion runs like a charm after switching the antenna cable to the second socket on the wifi-card. -- 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/1454843 Title: 10ec:b723 Realtek RTL8723BE wireless card drops connection Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: I am using Lenovo M30-70. I tried many workarounds from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320070 but no change, the connection is lost after a while. Finally I tried the rtlwifi_new driver from https://bugzilla.kernel.org/show_bug.cgi?id=83641#c1. I first thought it works stable but after a while it also loses the connection (see my comment there). After reconnect it works for a while again. I uninstalled the rtlwifi_new driver for this bug report. (Bluetooth does not work at all, it doesn't find any devices) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-17-generic 3.19.0-17.17 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sledzik2179 F pulseaudio CurrentDesktop: Unity Date: Wed May 13 22:51:38 2015 HibernationDevice: RESUME=UUID=d61164da-04eb-444a-a976-6a1f91fc4ffb InstallationDate: Installed on 2015-03-11 (63 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: LENOVO ZIUS6 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic.efi.signed root=UUID=40721d88-7203-4dfa-ac65-1a2b204fea34 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-17-generic N/A linux-backports-modules-3.19.0-17-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-06 (36 days ago) dmi.bios.date: 10/15/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 8BCN45WW(V3.08) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: INVALID dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvr8BCN45WW(V3.08):bd10/15/2014:svnLENOVO:pnZIUS6:pvrINVALID:rvnLENOVO:rnINVALID:rvrINVALID:cvnLENOVO:ct10:cvrINVALID: dmi.product.name: ZIUS6 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1454843/+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 1571041] Re: Trusty update to v3.13.11-ckt39 stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The v3.13.11-ckt39 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The v3.13.11-ckt39 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://kernel.ubuntu.com/ubuntu/linux.git -git://kernel.ubuntu.com/ubuntu/linux.git + TEST CASE: TBD - TEST CASE: TBD + The following patches from the v3.13.11-ckt39 stable release + shall be applied: -The following patches from the v3.13.11-ckt39 stable release - shall be applied: + Linux 3.13.11-ckt39 + ip6_tunnel: set rtnl_link_ops before calling register_netdevice + parisc: Avoid function pointers for kernel exception routines + USB: option: add "D-Link DWM-221 B1" device id + USB: serial: cp210x: Adding GE Healthcare Device ID + USB: serial: ftdi_sio: Add support for ICP DAS I-756xU devices + iio: st_magn: always define ST_MAGN_TRIGGER_SET_STATE + mm: fix invalid node in alloc_migrate_target() + ALSA: timer: Use mod_timer() for rearming the system timer + USB: digi_acceleport: do sanity checking for the number of ports + USB: cypress_m8: add endpoint sanity check + USB: mct_u232: add sanity checking in probe + usb: renesas_usbhs: disable TX IRQ before starting TX DMAC transfer + usb: renesas_usbhs: avoid NULL pointer derefernce in usbhsf_pkt_handler() + drm/radeon: add another R7 370 quirk + hwmon: (max) Return -ENODEV from max_read_channel if not instantiated + drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 ** Changed in: linux (Ubuntu Trusty) 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/1571041 Title: Trusty update to v3.13.11-ckt39 stable release Status in linux package in Ubuntu: New Status in linux source package in Trusty: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v3.13.11-ckt39 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://kernel.ubuntu.com/ubuntu/linux.git TEST CASE: TBD The following patches from the v3.13.11-ckt39 stable release shall be applied: Linux 3.13.11-ckt39 ip6_tunnel: set rtnl_link_ops before calling register_netdevice parisc: Avoid function pointers for kernel exception routines USB: option: add "D-Link DWM-221 B1" device id USB: serial: cp210x: Adding GE Healthcare Device ID USB: serial: ftdi_sio: Add support for ICP DAS I-756xU devices iio: st_magn: always define ST_MAGN_TRIGGER_SET_STATE mm: fix invalid node in alloc_migrate_target() ALSA: timer: Use mod_timer() for rearming the system timer USB: digi_acceleport: do sanity checking for the number of ports USB: cypress_m8: add endpoint sanity check USB: mct_u232: add sanity checking in probe usb: renesas_usbhs: disable TX IRQ before starting TX DMAC transfer usb: renesas_usbhs: avoid NULL pointer derefernce in usbhsf_pkt_handler() drm/radeon: add another R7 370 quirk hwmon: (max) Return -ENODEV from max_read_channel if not instantiated drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571041/+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 1542939] Re: system freeze after vt switching
Launchpad has imported 7 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=93509. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-12-26T10:54:43+00:00 Tomas Janousek wrote: I'm sometimes getting "vblank wait timed out on crtc 0" when switching between X and console on my ThinkPad T420. Steps to reproduce: 1. get a machine with sandybridge and optimus 2. boot it with some 4.4-rc kernel 3. power off nvidia using bbswitch (couldn't reproduce without this) 4. switch between X and console a few times (while :; do chvt 10; sleep 2; chvt 1; sleep 2; done) 5. this happens: [ cut here ] WARNING: CPU: 0 PID: 1382 at drivers/gpu/drm/drm_irq.c:1216 drm_wait_one_vblank+0x1b0/0x1c0() vblank wait timed out on crtc 0 Modules linked in: ccm br_netfilter bridge stp llc dm_thin_pool dm_persistent_data dm_bio_prison libcrc32c dm_bufio binfmt_misc tun bnep nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ip6table_filter ip6_tables xt_multiport xt_conntrack iptable_raw uvcvideo xt_TCPMSS xt_tcpudp iptable_mangle btusb ipt_MASQUERADE nf_nat_masquerade_ipv4 videobuf2_vmalloc btrtl xt_addrtype videobuf2_memops videobuf2_v4l2 btbcm iptable_nat arc4 nf_conntrack_ipv4 btintel videobuf2_core iwldvm bluetooth nf_defrag_ipv4 nf_nat_ipv4 v4l2_common nf_nat videodev mac80211 iptable_filter ip_tables x_tables x86_pkg_temp_thermal kvm_intel kvm iwlwifi snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec cfg80211 irqbypass crc32_pclmul snd_hwdep crc32c_intel sdhci_pci snd_hda_core sdhci snd_pcm_oss aesni_intel mmc_core aes_x86_64 lrw hdaps(O) thinkpad_ec(O) glue_helper psmouse ablk_helper snd_mixer_oss cryptd snd_pcm serio_raw e1000e thinkpad_acpi ehci_pci snd_timer nvram ehci_hcd wmi usbcore ptp s nd pps_core tpm_rng tpm_tis tpm battery bbswitch(O) nf_conntrack_netlink soundcore ac i2c_i801 usb_common nfnetlink evdev nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_h323 nf_conntrack_irc nf_conntrack_ftp nf_conntrack coretemp hwmon ecryptfs loop dm_crypt CPU: 0 PID: 1382 Comm: Xorg Tainted: G O4.4.0-rc2-lis64-bisect+ #13 Hardware name: LENOVO 4178A3G/4178A3G, BIOS 83ET76WW (1.46 ) 07/05/2013 61618deb 88041fc0b790 8f301fcc 88041fc0b7d8 88041fc0b7c8 8f05a062 88042ad01000 0f58 88042b485a08 Call Trace: [] dump_stack+0x4e/0x82 [] warn_slowpath_common+0x82/0xc0 [] warn_slowpath_fmt+0x5c/0x80 [] ? _raw_spin_unlock_irqrestore+0xe/0x10 [] ? finish_wait+0x55/0x70 [] drm_wait_one_vblank+0x1b0/0x1c0 [] ? wake_atomic_t_function+0x60/0x60 [] intel_atomic_commit+0x732/0x1890 [] ? drm_atomic_check_only+0x18e/0x590 [] ? drm_atomic_add_affected_connectors+0x27/0xf0 [] drm_atomic_commit+0x37/0x60 [] restore_fbdev_mode+0x22f/0x260 [] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [] drm_fb_helper_set_par+0x2d/0x50 [] intel_fbdev_set_par+0x1a/0x60 [] ? fb_set_var+0x301/0x450 [] fb_set_var+0x248/0x450 [] ? update_curr+0x5c/0x120 [] ? check_preempt_wakeup+0xdd/0x1c0 [] fbcon_blank+0x363/0x3b0 [] do_unblank_screen+0xc3/0x190 [] complete_change_console+0x59/0xe0 [] vt_ioctl+0x710/0x12e0 [] ? drm_ioctl+0x189/0x540 [] ? drm_setmaster_ioctl+0xa0/0xa0 [] vt_compat_ioctl+0x188/0x3b0 [] ? __call_rcu.constprop.56+0x250/0x250 [] tty_compat_ioctl+0x54/0xc0 [] compat_SyS_ioctl+0xeb/0x11f0 [] ? percpu_up_read+0x17/0x40 [] ? __sb_end_write+0x21/0x30 [] ? vfs_write+0x165/0x1a0 [] do_fast_syscall_32+0x9a/0x150 [] sysenter_flags_fixed+0x8/0x12 ---[ end trace 5d6ad91f242dc76e ]--- I couldn't reproduce this on 4.3 so I bisected it and got: 43d59eda1f69631c267e06ab6b94ed3c14f1f6d1 is the first bad commit commit 43d59eda1f69631c267e06ab6b94ed3c14f1f6d1 Author: Matt Roper Date: Thu Sep 24 15:53:07 2015 -0700 drm/i915: Eliminate usage of plane_wm_parameters from ILK-style WM code (v2) Just pull the info out of the plane state structure rather than staging it in an additional structure. v2: Add 'visible' condition to sprites_scaled so that we don't limit the WM level when the sprite isn't enabled. (Ville) Signed-off-by: Matt Roper Reviewed-by(v1): Ander Conselvan de Oliveira Reviewed-by: Maarten Lankhorst Signed-off-by: Daniel Vetter :04 04 b11db95f066a752dcccb0082490eabf21f62e8db 88bc02171246d693a868cd9ddb3144ee5d9b0ea8 M drivers I also tried merging yesterday's drm-intel-next (7447a2b221cd4df3960e82478a4ee29312589611) to yesterday's master (a88164345b81292b55a8d4829fdd35c8d611cd7d) and couldn't reproduce it e
[Kernel-packages] [Bug 1564901] Re: xpad rumble causes full system hang
@Alistar, do you see the regression Matt posted in comment #7? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1564901 Title: xpad rumble causes full system hang Status in linux package in Ubuntu: In Progress Status in linux-lts-utopic package in Ubuntu: In Progress Status in linux-lts-vivid package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: To reproduce: 1. Have a wired xbox controller. 2. Modify the SDL2 testrumble.c so it runs forever. (attached) 3. Build and run it. 4. Kill it with sigkill from another terminal. Expected result: The program should stop running. Actual result: Entire computer freezes. Soundcard continuously plays the last second of audio. No response from any input devices or the network. The bug can also be reproduced by playing the game Borderlands 2 while having a wired xbox controller connected. The system will randomly freeze in the exact same way. The bug has existed since at least 14.04. The last thing the kernel prints is this: Apr 1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB device number 2 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device found, idVendor=045e, idProduct=0288 Apr 1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found Apr 1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports detected Apr 1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed USB device number 3 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device found, idVendor=045e, idProduct=0289 Apr 1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad v2 (US) as /devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23 Apr 1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new interface driver xpad Apr 1 03:40:09 al-desktop kernel: [94242.318271] [ cut here ] Apr 1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 at /build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 usb_submit_urb+0x51/0x70() Apr 1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 submitted while active Apr 1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r em28xx_dvb d vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm snd_seq_midi_event btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp tea575x tveeprom edac _core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x v4l2_common videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd soundcore drm shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp parport autofs4 uas u sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci r8169 mii Apr 1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: testrumble Tainted: P OE 4.2.0-34-generic #39-Ubuntu Apr 1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010 Apr 1 03:40:09 al-desktop kernel: [94242.318328] 4da02d75 88010a9c3ba8 817ebed3 Apr 1 03:40:09 al-desktop kernel: [94242.318330] 88010a9c3c00 88010a9c3be8 8107b986 Apr 1 03:40:09 al-desktop kernel: [94242.318331] 88010a9c3bd8 0010 880103216f08 88010a9c3cd0 Apr 1 03:40:09 al-desktop kernel: [94242.318333] Call Trace: Apr 1 03:40:09 al-desktop kernel: [94242.318337] [] dump_stack+0x45/0x57 Apr 1 03:40:09 al-desktop kernel: [94242.318340] [] warn_slowpath_common+0x86/0xc0 Apr 1 03:40:09 al-desktop kernel: [94242.318342] [] warn_slowpath_fmt+0x55/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318345] [] usb_submit_urb+0x51/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318348] [] xpad_play_effect+0x130/0x240 [xpad] Apr 1 03:
[Kernel-packages] [Bug 1571069] [NEW] linux: 4.4.0-20.36 -proposed tracker
Public bug reported: This bug is for tracking the 4.4.0-20.36 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 15. April 2016 20:18 UTC kernel-phase-changed:Friday, 15. April 2016 20:18 UTC kernel-phase:Prepare ** Affects: kernel-development-workflow Importance: Medium Status: In Progress ** Affects: kernel-development-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-development-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-development-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Xenial) Importance: Medium Status: New ** Tags: block-proposed kernel-release-tracking-bug xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Also affects: kernel-development-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-development-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-development-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-development-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-development-workflow Status: New => In Progress ** Changed in: kernel-development-workflow Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-development-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-development-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-development-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-development-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1571069 Title: linux: 4.4.0-20.36 -proposed tracker Status in Kernel Development Workflow: In
[Kernel-packages] [Bug 1570906] Re: sysfs mount failure during stateful lxd snapshots
** Changed in: linux (Ubuntu Xenial) Status: In Progress => 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/1570906 Title: sysfs mount failure during stateful lxd snapshots Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification: Impact: Stateful lxd container snapshotting fails due to a failure to mount the container's sysfs in the host's user namespace. This is a regression. Fix: Force kernfs to use a new super block for mounts in different user namespaces. Test Case: "lxc snapshot --stateful " fails in the current xenial kernel without the fix. It succeeds with the fix applied. --- During a stateful lxd snapshot criu tries to mount sysfs for the container's network namespace from a different user namespace. This fails in xenial because sget() won't allow mounting the same super block in different user namespaces. With sysfs there's no reason that this needs to use the same super block, so kernfs can be updated so that a super block with the same ns tag but in a different userns is not matched. The only other kernfs- based filesystem mountable from non-init user namespaces is cgroupfs, and it's already forcing kernfs to return different super blocks to avoid similar problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570906/+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 1454843] Re: 10ec:b723 Realtek RTL8723BE wireless card drops connection
The best solution so far for me is from the same Thread as #13 but two pages later (page 6): http://ubuntuforums.org/showthread.php?t=2304607&page=6 There is an alternative driver rock.new_btcoex this works for me much better on my lenovo m30-70. But I did not switch to antenna 2, I am still on 1, this was better for me. -- 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/1454843 Title: 10ec:b723 Realtek RTL8723BE wireless card drops connection Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: I am using Lenovo M30-70. I tried many workarounds from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320070 but no change, the connection is lost after a while. Finally I tried the rtlwifi_new driver from https://bugzilla.kernel.org/show_bug.cgi?id=83641#c1. I first thought it works stable but after a while it also loses the connection (see my comment there). After reconnect it works for a while again. I uninstalled the rtlwifi_new driver for this bug report. (Bluetooth does not work at all, it doesn't find any devices) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-17-generic 3.19.0-17.17 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sledzik2179 F pulseaudio CurrentDesktop: Unity Date: Wed May 13 22:51:38 2015 HibernationDevice: RESUME=UUID=d61164da-04eb-444a-a976-6a1f91fc4ffb InstallationDate: Installed on 2015-03-11 (63 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: LENOVO ZIUS6 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic.efi.signed root=UUID=40721d88-7203-4dfa-ac65-1a2b204fea34 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-17-generic N/A linux-backports-modules-3.19.0-17-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-06 (36 days ago) dmi.bios.date: 10/15/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 8BCN45WW(V3.08) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: INVALID dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvr8BCN45WW(V3.08):bd10/15/2014:svnLENOVO:pnZIUS6:pvrINVALID:rvnLENOVO:rnINVALID:rvrINVALID:cvnLENOVO:ct10:cvrINVALID: dmi.product.name: ZIUS6 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1454843/+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 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Status: Triaged => 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/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+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 1571069] Re: linux: 4.4.0-20.36 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-development-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-development-workflow/prepare-package-signed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.4.0-20.36 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 15. April 2016 20:18 UTC - kernel-phase-changed:Friday, 15. April 2016 20:18 UTC - kernel-phase:Prepare + kernel-phase:Packaging + kernel-phase-changed:Friday, 15. April 2016 21:01 UTC ** Description changed: This bug is for tracking the 4.4.0-20.36 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 15. April 2016 20:18 UTC kernel-phase:Packaging kernel-phase-changed:Friday, 15. April 2016 21:01 UTC + + -- swm properties -- + phase: Packaging -- 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/1571069 Title: linux: 4.4.0-20.36 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-20.36 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 15. April 2016 20:18 UTC kernel-phase:Packaging kernel-phase-changed:Friday, 15. April 2016 21:01 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1571069/+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 1571069] Re: linux: 4.4.0-20.36 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) ** Changed in: kernel-development-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) ** Changed in: kernel-development-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) ** Description changed: This bug is for tracking the 4.4.0-20.36 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 15. April 2016 20:18 UTC - kernel-phase:Packaging - kernel-phase-changed:Friday, 15. April 2016 21:01 UTC - -- swm properties -- phase: Packaging + kernel-phase-changed:Friday, 15. April 2016 22:01 UTC + kernel-phase:Uploaded ** Description changed: This bug is for tracking the 4.4.0-20.36 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 15. April 2016 20:18 UTC -- swm properties -- - phase: Packaging - kernel-phase-changed:Friday, 15. April 2016 22:01 UTC - kernel-phase:Uploaded + phase: Uploaded -- 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/1571069 Title: linux: 4.4.0-20.36 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-20.36 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 15. April 2016 20:18 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1571069/+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 1570348] Re: linux: 4.4.0-19.35 -proposed tracker
Here's the relevant information: xenial linux 4.4.0-19.35 REGR summary Please verify test results in http://people.canonical.com/~kernel/status /adt-matrix/overall.txt ** Changed in: kernel-development-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-development-workflow/promote-to-proposed Status: Confirmed => Fix Released ** Changed in: kernel-development-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-development-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug is for tracking the 4.4.0-19.35 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 14. April 2016 12:11 UTC - kernel-phase:Uploaded - kernel-phase-changed:Thursday, 14. April 2016 13:00 UTC - -- swm properties -- phase: Uploaded + kernel-phase-changed:Friday, 15. April 2016 22:01 UTC + kernel-phase:Promoted to proposed ** Description changed: This bug is for tracking the 4.4.0-19.35 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 14. April 2016 12:11 UTC -- swm properties -- - phase: Uploaded - kernel-phase-changed:Friday, 15. April 2016 22:01 UTC - kernel-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true -- 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/1570348 Title: linux: 4.4.0-19.35 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-19.35 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 14. April 2016 12:11 UTC -- swm properties -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1570348/+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 1570124] Re: [Hyper-V] In-flight PCI Passthrough Patches
I built a Xenial test kernel with the six requested commits. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1570124/ Can you test this kernel and post back if it resolves this bug? -- 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/1570124 Title: [Hyper-V] In-flight PCI Passthrough Patches Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Some additional patches for PCI Passthrough have been submitted but not accepted upstream that are necessary for accessing multiple GPUs on the host. These are expected to get accepted upstream, but since there is not much time left in 16.04 I'm submitting them before they are accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570124/+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 1570348] dwalin (amd64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-19.35/dwalin__4.4.0-19.35__2016-04-15_22-14-00/results-index.html -- 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/1570348 Title: linux: 4.4.0-19.35 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-19.35 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Thursday, 14. April 2016 12:11 UTC -- swm properties -- phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1570348/+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
