[Kernel-packages] [Bug 1734326] Re: qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed error
After discussion the offfending change in zesty-proposed will be cancelled. Once done I'll set this to "Fix Released" (even thou it is the non-release that fixes 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/1734326 Title: qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed error Status in linux package in Ubuntu: Invalid Status in qemu-kvm package in Ubuntu: Confirmed Bug description: This is a potential regression for ARM64 qemu-kvm package (1:2.8+dfsg- 3ubuntu2.8). With qemu-kvm updated from 1:2.8+dfsg-3ubuntu2.7, the kvm-unit-test in our test suite will fail with: Unexpected error in kvm_device_access() at /build/qemu-2b6oyQ/qemu-2.8+dfsg/kvm-all.c:2151: qemu-system-aarch64: KVM_GET_DEVICE_ATTR failed: Group 6 attr 0xc664: No such device or address QEMU Aborted Steps: 1. Deploy a ARM64 zesty system 2. git clone https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3. cd kvm-unit-tests 4. ./configure; make 5. sudo ./run_tests -v 6. Enable proposed and upgrade the qemu-kvm package, repeat step 5 $ dpkg -l | grep qemu ii ipxe-qemu 1.0.0+git-20150424.a25a16d-1ubuntu2 all PXE boot firmware - ROM images for qemu ii qemu-block-extra:arm64 1:2.8+dfsg-3ubuntu2.7 arm64extra block backend modules for qemu-system and qemu-utils ii qemu-kvm 1:2.8+dfsg-3ubuntu2.8 arm64QEMU Full virtualization ii qemu-system-arm1:2.8+dfsg-3ubuntu2.8 arm64QEMU full system emulation binaries (arm) ii qemu-system-common 1:2.8+dfsg-3ubuntu2.7 arm64QEMU full system emulation binaries (common files) ii qemu-utils 1:2.8+dfsg-3ubuntu2.7 arm64QEMU utilities ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-40-generic 4.10.0-40.44 ProcVersionSignature: User Name 4.10.0-40.44-generic 4.10.17 Uname: Linux 4.10.0-40-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 11:12 seq crw-rw 1 root audio 116, 33 Nov 24 11:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu4.8 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: CurrentDmesg: Date: Fri Nov 24 11:26:56 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Cavium ThunderX CRB PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA 1 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic root=UUID=c5160401-c147-4329-9683-b946ce7d0d37 ro RelatedPackageVersions: linux-restricted-modules-4.10.0-40-generic N/A linux-backports-modules-4.10.0-40-generic N/A linux-firmware 1.164.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 0 dmi.chassis.vendor: Cavium dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.: dmi.product.name: ThunderX CRB dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Cavium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734326/+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 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
Occams, Can you try if the Linux source tree here works for you? https://github.com/khfeng/linux/tree/r8169 -- 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/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940
>If the problem is solved, change the tag 'verification-needed-zesty' to
'verification-done-zesty'.
Can someone help me here?
Is this action on me? Problem is solved with the above 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/1719697
Title:
Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940
Status in dellserver:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
Fix Committed
Bug description:
== SRU Justification ==
Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
and 4.10.0-33 HWE as well.
Seen only with 4.10 HWE kernels of Ubuntu-16.04.3. 4.4 kernels of
Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.
Reducing the core count to <26 cores helps here. Boot & installation of
HWE-kernel works fine.
This bug was introduced by commit:
dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when
booting")
It is resolved by reverting commit dc6db24d2476, which was done in mainline
by
commit c962cff17df as of v4.11-rc3.
There are three additiona commits introduced by the same patch author when
commit c962cff17df was submitted. However, it was confirmed that only the
single
revert is needed to fix this particular bug. Upstream thread:
https://lkml.org/lkml/2017/2/20/66
== Fix ==
commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
Author: Dou Liyang
Date: Fri Mar 3 16:02:23 2017 +0800
Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
booting"
== Regression Potential ==
This is reverting a commit that introduced a bug. This commit has also
been reverted upstream.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Setup:
Dell PowerEdge R940 having 2 socket populated with 28 cores.
Impact:
This is a boot and installation failure for R940 users having 2 socket x 28
cores.
Requesting an SRU for the fix.
Steps:
1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
2. Start installation of Ubuntu-16.04.3 with HWE kernel.
3. Observe the screen remains blank. Console logs indicate kernel crash.
Additional Info:
* Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server
17.10 works fine.
* Reducing the core count to <26 cores helps here. Boot & installation
of HWE-kernel works fine.
* Attaching the console log and acpidump from the setup.
* Patch causing this failure:
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
x86/acpi: Set persistent cpuid <-> nodeid mapping when booting
* Fix patch series: https://lkml.org/lkml/2017/2/20/66
Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d
Revert"x86/acpi: Enable MADT APIs to return disabled apicids"
https://github.com/torvalds/linux/commit/09c3f2bd5c7e5f18687663acb6adc6b167484ca5
acpi/processor: Implement DEVICE operator for processor enumeration
https://github.com/torvalds/linux/commit/8c8cb30f49b86333d8e036e1945cf1a78c03577e
acpi/processor: Check for duplicate processor ids at hotplug time
https://github.com/torvalds/linux/commit/a77d6cd968497792e072b74dff45b891ba778ddb
To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1719697/+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 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940
After adding xenial-proposed to /etc/apt/sources.list,
#apt-get install linux-generic-hwe-16.04/xenial-proposed
Confirmed Booting pass with:
# uname -a
Linux dhcp-165-167 4.10.0-41-generic #45~16.04.1-Ubuntu SMP Fri Nov 24 15:06:20
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Thanks for including the fix.
http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=hwe&id=dcde44490772d2059ecc5035a3b6c994176c6212
--
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/1719697
Title:
Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940
Status in dellserver:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
Fix Committed
Bug description:
== SRU Justification ==
Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
and 4.10.0-33 HWE as well.
Seen only with 4.10 HWE kernels of Ubuntu-16.04.3. 4.4 kernels of
Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.
Reducing the core count to <26 cores helps here. Boot & installation of
HWE-kernel works fine.
This bug was introduced by commit:
dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when
booting")
It is resolved by reverting commit dc6db24d2476, which was done in mainline
by
commit c962cff17df as of v4.11-rc3.
There are three additiona commits introduced by the same patch author when
commit c962cff17df was submitted. However, it was confirmed that only the
single
revert is needed to fix this particular bug. Upstream thread:
https://lkml.org/lkml/2017/2/20/66
== Fix ==
commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
Author: Dou Liyang
Date: Fri Mar 3 16:02:23 2017 +0800
Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
booting"
== Regression Potential ==
This is reverting a commit that introduced a bug. This commit has also
been reverted upstream.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Setup:
Dell PowerEdge R940 having 2 socket populated with 28 cores.
Impact:
This is a boot and installation failure for R940 users having 2 socket x 28
cores.
Requesting an SRU for the fix.
Steps:
1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
2. Start installation of Ubuntu-16.04.3 with HWE kernel.
3. Observe the screen remains blank. Console logs indicate kernel crash.
Additional Info:
* Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server
17.10 works fine.
* Reducing the core count to <26 cores helps here. Boot & installation
of HWE-kernel works fine.
* Attaching the console log and acpidump from the setup.
* Patch causing this failure:
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
x86/acpi: Set persistent cpuid <-> nodeid mapping when booting
* Fix patch series: https://lkml.org/lkml/2017/2/20/66
Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d
Revert"x86/acpi: Enable MADT APIs to return disabled apicids"
https://github.com/torvalds/linux/commit/09c3f2bd5c7e5f18687663acb6adc6b167484ca5
acpi/processor: Implement DEVICE operator for processor enumeration
https://github.com/torvalds/linux/commit/8c8cb30f49b86333d8e036e1945cf1a78c03577e
acpi/processor: Check for duplicate processor ids at hotplug time
https://github.com/torvalds/linux/commit/a77d6cd968497792e072b74dff45b891ba778ddb
To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1719697/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Try it here: http://people.canonical.com/~khfeng/lp1728244-multitouch/ -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1729010] USB hub stops working after suspend(s?)
> On 28 Nov 2017, at 11:23 PM, Joe Barnett wrote: > > I should probably test a few more suspend cycles, but so far on > 4.12.0-11-generic I'm not seeing the issue Please find the first non-working v4.13-rc* release, so we can find the commit(s) that causes the regression. > > -- > You received this bug notification because you are subscribed to linux > in Ubuntu. > https://bugs.launchpad.net/bugs/1729010 > > Title: > USB hub stops working after suspend(s?) > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > On initial boot, my usb hub works fine, but after a (series of?) > suspends, I stop being able to see devices that are plugged into it. > journalctl output on plugging it in: > > Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 > using xhci_hcd > Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, > idProduct=005a > Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, > Product=0, SerialNumber=0 > Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found > Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected > Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= > SRC=fe80::::a299:9bff:fe17:9047 > DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 > FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 > Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 > using xhci_hcd > Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, > idVendor=0b95, idProduct=772a > Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, > Product=2, SerialNumber=3 > Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A > Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. > Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 > Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at > usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] > manager: (eth0): new Ethernet device > (/org/freedesktop/NetworkManager/Devices/7) > Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: > "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" > Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP > device > Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is > unset or enabled, the speed and duplex are not writable. > Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from > eth0 > Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session > opened for user root by (uid=1000) > Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] > [TTY=unknown] [CWD=/home/jbarnett] > [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness > 31] > Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another > user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] > [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness > 48] > Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error > executing command as another user: Not authorized > Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This > incident has been reported. > Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to > enx0050b647ede2 > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] > device (eth0): interface index 10 renamed iface from 'eth0' to > 'enx0050b647ede2' > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] > devices added (path: > /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, > iface: enx0050b647ede2) > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] > device added (path: > /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, > iface: enx0050b647ede2): no ifupdown configuration found. > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] > device (enx0050b647ede2): state change: unmanaged -> unavailable (reason > 'managed', internal state 'external') > Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: > link is not ready > Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: > link is not ready > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] > keyfile: add connection in-memory > (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") > Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] > settings: (enx0050b647ede2): created default wired connection 'Wired > connection 4' > Oct 31 07:08:37 spiny systemd[1]: Starting > systemd-resolved-update-resolvconf.service... > Oct 31 07:08:37 spiny systemd[1]: Started > systemd-resolved-update-resolvconf.service. > O
[Kernel-packages] [Bug 1453812] Re: System freeze when using LibreOffice Writer
Vitaly Yevstigneyev, given you have different hardware, you likely have a different root cause altogether (i.e. not the same problem). For example, I have Intel hardware, and cannot reproduce the issue on various versions of Ubuntu and LibreOffice. Hence, it will help immensely if you use the computer the problem is reproducible with, file a new report with Ubuntu by first ensuring the package xdiagnose is installed, click the Yes button for attaching additional debugging information after running the following from a terminal: ubuntu-bug xorg Also, please feel free to subscribe me to 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/1453812 Title: System freeze when using LibreOffice Writer Status in linux package in Ubuntu: Incomplete Bug description: LibreOffice Writer is freezing the system after a few minutes (Ubuntu 15.04, libreoffice-writer 4.4.2-0ubuntu1): the only possible action is moving the mouse pointer on the screen. Impossible to connect to a tty session to kill Xorg. A physical reboot is necessary. Note that I used LibreOffice Calc without problem. The problem has been encountered also under Fedora 21: http://forums.fedora-fr.org/viewtopic.php?id=63428 WORKAROUND: Use nvidia-304-updates or 340.76. --- .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96GL [Quadro FX 580] [10de:0659] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:063a] LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP Z400 Workstation Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Tags: vivid ubuntu compiz-0.9 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/06/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G3 v03.07 dmi.board.asset.tag: CZC0195Y06 dmi.board.name: 0B4Ch dmi.board.vendor: Hewlett-Packard dmi.board.version: D dmi.chassis.asset.tag: CZC0195Y06 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G3v03.07:bd04/06/2010:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0B4Ch:rvrD:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z400 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Wed May 20 08:19:58 2015 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1453812/+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 1728523] Re: QCA6174A XR cannot find any WiFi AP
In git://kernel.ubuntu.com/ubuntu/linux-firmware.git xenail 849a338 (HEAD -> refs/heads/xenial, refs/remotes/ubuntu/xenial) ath10k: QCA6174 hw3.0: update board-2.bin 5a39a84 ath10k: QCA6174 hw3.0: update board-2.bin a98b778 ath10k: QCA6174 hw3.0: update board-2.bin -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1728523 Title: QCA6174A XR cannot find any WiFi AP Status in HWE Next: Fix Committed Status in linux-firmware package in Ubuntu: Fix Committed Bug description: QCA6174A XR requires an update firmware [ 16.158772] ath10k_pci :02:00.0: failed to enable dynamic BW: -11 [ 22.162575] ath10k_pci :02:00.0: could not suspend target (-11) [ 27.533002] ath10k_pci :02:00.0: failed to enable dynamic BW: -11 [ 33.535958] ath10k_pci :02:00.0: could not suspend target (-11) [ 38.890790] ath10k_pci :02:00.0: failed to enable dynamic BW: -11 [ 44.893968] ath10k_pci :02:00.0: could not suspend target (-11) [ 46.358194] i2c_designware i2c_designware.0: controller timed out [ 47.358231] i2c_designware i2c_designware.0: controller timed out [ 48.358506] i2c_designware i2c_designware.0: controller timed out [ 49.566240] i2c_designware i2c_designware.2: controller timed out [ 50.566862] i2c_designware i2c_designware.2: controller timed out [ 51.566307] i2c_designware i2c_designware.2: controller timed out [ 52.670330] i2c_designware i2c_designware.3: controller timed out [ 53.670775] i2c_designware i2c_designware.3: controller timed out [ 54.670427] i2c_designware i2c_designware.3: controller timed out [ 60.326619] ath10k_pci :02:00.0: failed to enable dynamic BW: -11 [ 66.327117] ath10k_pci :02:00.0: could not suspend target (-11) [ 71.678943] ath10k_pci :02:00.0: failed to enable dynamic BW: -11 [ 77.679084] ath10k_pci :02:00.0: could not suspend target (-11) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1728523/+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 1717259] Re: adaptec starfire fails to initializewith recent kernels
** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=198035 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/1717259 Title: adaptec starfire fails to initializewith recent kernels Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Re-opening https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473200 (expired) Adaptec ethernet adapter using starfire driver fails to initialize when recent kernels are used. This hardware/driver can be successfully initialized under a 3.2.0-126-generic kernel (from precise) but initialization is known to fail under 3.13.0-129-generic kernel and under -pae kernel builds of many vintages. initialization also fails under current 4.x series kernel. Full kernel bisect is not yet complete. Specific indication from dmesg: [3.536508] starfire.c:v1.03 7/26/2000 Written by Donald Becker (unofficial 2.2/2.4 kernel port, version 2.1, July 6, 2008) [3.536509] starfire: polling (NAPI) enabled [3.536771] ioremap: invalid physical address fe48 [3.536773] [ cut here ] [3.536784] WARNING: CPU: 1 PID: 115 at /build/linux-CK3pdl/linux-4.4.0/arch/x86/mm/ioremap.c:104 __ioremap_caller+0x40f/0x440() [3.536790] Modules linked in: starfire(+) mii fjes floppy(+) [3.536795] CPU: 1 PID: 115 Comm: systemd-udevd Not tainted 4.4.0-93-generic #116-Ubuntu [3.536797] Hardware name: Intel/SE7501BR2S, BIOS SBR20.86B.0082.P23.050407173004/07/2005 [3.536805] c1ae9967 73b5a5ce 0286 c01ddb90 c13add2f c19d0e40 c01ddbc0 [3.536811] c1070387 c19d8dd4 0001 0073 c19d0e40 0068 c105fe2f c105fe2f [3.536818] 0fff fe4f c01ddbd0 c1070492 0009 c01ddc3c [3.536819] Call Trace: [3.536829] [] dump_stack+0x58/0x79 [3.536835] [] warn_slowpath_common+0x87/0xc0 [3.536840] [] ? __ioremap_caller+0x40f/0x440 [3.536843] [] ? __ioremap_caller+0x40f/0x440 [3.536847] [] warn_slowpath_null+0x22/0x30 [3.536850] [] __ioremap_caller+0x40f/0x440 [3.536855] [] ? __pci_request_region+0xb4/0x180 [3.536861] [] ? starfire_init_one+0xc6/0x680 [starfire] [3.536866] [] ? starfire_init_one+0xc6/0x680 [starfire] [3.536869] [] ioremap_nocache+0x1f/0x30 [3.536874] [] ? starfire_init_one+0xc6/0x680 [starfire] [3.536879] [] starfire_init_one+0xc6/0x680 [starfire] [3.536885] [] ? __pm_runtime_resume+0x51/0x80 [3.536889] [] pci_device_probe+0x7b/0xf0 [3.536894] [] ? devices_kset_move_last+0x2d/0xa0 [3.536899] [] driver_probe_device+0x1f9/0x4a0 [3.536904] [] ? sysfs_create_dir_ns+0x37/0x90 [3.536907] [] ? pci_match_device+0xdc/0x100 [3.536911] [] __driver_attach+0x79/0x80 [3.536915] [] ? driver_probe_device+0x4a0/0x4a0 [3.536918] [] bus_for_each_dev+0x57/0xa0 [3.536921] [] driver_attach+0x1e/0x20 [3.536925] [] ? driver_probe_device+0x4a0/0x4a0 [3.536928] [] bus_add_driver+0x1ef/0x290 [3.536931] [] ? 0xf8465000 [3.536933] [] ? 0xf8465000 [3.536936] [] driver_register+0x5d/0xf0 [3.536939] [] __pci_register_driver+0x33/0x40 [3.536944] [] starfire_init+0x2b/0x1000 [starfire] [3.536948] [] do_one_initcall+0xaa/0x200 [3.536951] [] ? 0xf8465000 [3.536955] [] ? kfree+0x120/0x130 [3.536958] [] ? kmem_cache_alloc_trace+0x185/0x1e0 [3.536964] [] ? do_init_module+0x21/0x1a6 [3.536967] [] ? do_init_module+0x21/0x1a6 [3.536970] [] do_init_module+0x50/0x1a6 [3.536975] [] load_module+0x1533/0x1a40 [3.536979] [] ? copy_module_from_fd.isra.53+0xf9/0x190 [3.536984] [] SyS_finit_module+0xa5/0xf0 [3.536988] [] ? vm_mmap_pgoff+0xa3/0xc0 [3.536993] [] do_fast_syscall_32+0x8d/0x150 [3.536998] [] sysenter_past_esp+0x3d/0x61 [3.537001] ---[ end trace 2c05306d6389bc20 ]--- [3.537005] starfire :08:04.0: cannot remap 0x8 @ 0xfe48, aborting [3.537162] ioremap: invalid physical address fe38 [3.537166] starfire :08:05.0: cannot remap 0x8 @ 0xfe38, aborting [3.537308] ioremap: invalid physical address fe30 [3.537313] starfire :08:06.0: cannot remap 0x8 @ 0xfe30, aborting [3.537453] ioremap: invalid physical address fe20 Additional information: ~# lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 # uname -a Linux trafcap4 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:52 UTC 2017 i686 i686 i686 GNU/Linux # cat /proc/version_signature Ubuntu 4.4.0-93.116-generic 4.4.79 # dmidecode -s bios-v
[Kernel-packages] [Bug 1732056] Re: Touchpad stops working after a few seconds in Lenovo ideapad 320
** Description changed: + === SRU Justifications === + + [Impact] + Touchpad freezes after a brief usage. + + [Fix] + Quote from the commit log: + "The stale cached value written at the final stage undoes the masking. + Fix this by re-reading the register before clearing the interrupt. + + I also spotted that the interrupt-clearing code can race against + amd_gpio_irq_mask() / amd_gpio_irq_unmask(), so add locking there. + Presumably this race was leading to the loss of interrupts." + + [Test Case] + Touchpad no longer freezes on ideapad 320-15ABR, a new Dell Latitude and + a new Dell Inspiron. + + [Regression Potential] + Low. It limits to AMD laptops + + === Original Bug Report === + I have installed ubuntu bionic on a Lenovo ideapad 320. The touchpad stops working a few seconds after I log in. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: rebeca 1440 F pulseaudio - /dev/snd/controlC0: rebeca 1440 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: rebeca 1440 F pulseaudio + /dev/snd/controlC0: rebeca 1440 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 13 20:03:41 2017 InstallationDate: Installed on 2017-09-22 (53 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918) MachineType: LENOVO 80XS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1e55f665-bd98-4113-9ae8-ec766bfc424f ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.13.0-16-generic N/A - linux-backports-modules-4.13.0-16-generic N/A - linux-firmware 1.169 + linux-restricted-modules-4.13.0-16-generic N/A + linux-backports-modules-4.13.0-16-generic N/A + linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-11-14 (0 days ago) dmi.bios.date: 05/22/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN16WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15ABR dmi.modalias: dmi:bvnLENOVO:bvr5QCN16WW:bd05/22/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR: dmi.product.family: ideapad 320-15ABR dmi.product.name: 80XS dmi.product.version: Lenovo ideapad 320-15ABR dmi.sys.vendor: LENOVO -- 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/1732056 Title: Touchpad stops working after a few seconds in Lenovo ideapad 320 Status in linux package in Ubuntu: Incomplete Bug description: === SRU Justifications === [Impact] Touchpad freezes after a brief usage. [Fix] Quote from the commit log: "The stale cached value written at the final stage undoes the masking. Fix this by re-reading the register before clearing the interrupt. I also spotted that the interrupt-clearing code can race against amd_gpio_irq_mask() / amd_gpio_irq_unmask(), so add locking there. Presumably this race was leading to the loss of interrupts." [Test Case] Touchpad no longer freezes on ideapad 320-15ABR, a new Dell Latitude and a new Dell Inspiron. [Regression Potential] Low. It limits to AMD laptops === Original Bug Report === I have installed ubuntu bionic on a Lenovo ideapad 320. The touchpad stops working a few seconds after I log in. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rebeca 1440 F pulseaudio /dev/snd/controlC0: rebeca 1440 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 13 20:03:41 2017 InstallationDate: Installed on 2017-09-22 (53 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918) MachineType: LENOVO 80XS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1e55f665-bd98-4113-9ae8-ec766bfc424f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: lin
[Kernel-packages] [Bug 1732627] Re: enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- 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/1732627 Title: enable CONFIG_SND_SOC_INTEL_BYT_CHT_NOCODEC_MACH easily confuse users Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: The author of this config (pierre-louis.boss...@linux.intel.com) suggested that we should disable this config from ubuntu artful kernel, he said, "this is really for test environments or platforms with a connector. I don't think it should be enabled by default (better to fail the probe rather than get questions from users that they have no sound)." I also investigated this issue on my own, if our kernel is running on a platform which has a codec and the codec is supported by the existing driver, enabling this config will not bring side effect; if the platform has a codec but the codec is not supported by existing driver yet, the driver will fallback to this NOCODEC_MACH if this config is enabled, and snd-soc-sst-byt-cht-nocodec.ko will be loaded into the kernel, then user is easily confused that the kernel driver is loaded but I can't hear sound from the codec. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732627/+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 1655100] Re: NVME devices and Network devices disappears upon suspend
Confirm this bug occurs on Ubuntu 16.04 w/Alienware 17R3, i7 6700HQ, HM170 chipset. The workaround to use `acpiphp.disable=1` on kernel command line fixes suspend/resume cycle. -- 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/1655100 Title: NVME devices and Network devices disappears upon suspend Status in linux package in Ubuntu: Triaged Status in linux source package in Yakkety: Won't Fix Bug description: Ubuntu 16.10 on a Alienware 15 R2 when resuming from suspend the NVME devices and network devices are gone. I can force the devices to re-appear issuing echo 1 > /sys/bus/pci/rescan, that was what I did to be able to submit this bug report from a live USB stick. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 CurrentDesktop: Unity Date: Mon Jan 9 17:55:50 2017 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Alienware Alienware 15 R2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- 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.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.9 dmi.board.name: 0X70NC dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.9:bd09/30/2016:svnAlienware:pnAlienware15R2:pvr1.3.9:rvnAlienware:rn0X70NC:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 15 R2 dmi.product.version: 1.3.9 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
I see Tobia already submitted apport-collect 1734147. Would you like a second set from me as well or is one set of data enough? -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage notific
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Regarding UEFI vs Legacy mode. If I understand it correctly it happened in UEFI and not Legacy mode. I am not sure but I think my Lenovo Yoga 2 doesn't have Legacy "old school" BIOS and it only has UEFI. It has "BIOS backport" feature but I don't know if that's what you mean. In either case BIOS backport was disable by default on the laptop. -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-7
[Kernel-packages] [Bug 1728417] Re: Xubuntu suspend fails - shuts down instead
Yes - I installed Windows 10 on the machine last night to experiment with something else, and saw that I have the same problem with Windows, so must be BIOS related. Thanks for your help and sorry for the wild goose chase, I'll close this ticket. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728417 Title: Xubuntu suspend fails - shuts down instead Status in linux package in Ubuntu: Invalid Bug description: Suspending my machine (Xubuntu Whisker menu/Log out/Suspend) causes it to shut down instead (or at the very least, to restart when powering on again). Observed: after clicking on 'Suspend', the screen blanks, 10 seconds pass, then the machine powers down. When I power up again, it returns to the BIOS post screen, then Xubuntu boot splash screen, then login. Notes: * machine is a recent build, previously running 17.04. Had the same issue (and suspend error messages in syslog), so this does not appear to be related to the 17.10 upgrade. * given the "wpasupplicant failed with error code 254" line in syslog, and following comments in https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=835648, I tried removing wpasupplicant from /lib/systemd/system-suspend. This resulted in the machine suspending sooner (no time-out), but suspend still failed. * Separately, I tried switching to the nouveau driver (I'd seem some mentions of problematic proprietary nvidia drivers). This too made no difference. Please let me know if I can provide any other information. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: colin 1460 F pulseaudio /dev/snd/controlC1: colin 1460 F pulseaudio CurrentDesktop: XFCE Date: Sun Oct 29 15:03:36 2017 InstallationDate: Installed on 2017-10-13 (15 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=dcb5dfa5-9644-4b53-be57-ffadb28e8f45 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago) dmi.bios.date: 09/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd09/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728417/+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 1729573] Re: netplan breaks Xen VIF driver
Hello Dan, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-failed-xenial ** Tags added: verification-needed verification-needed-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/1729573 Title: netplan breaks Xen VIF driver Status in linux package in Ubuntu: Won't Fix Status in nplan package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in nplan source package in Xenial: Fix Committed Status in linux source package in Zesty: Won't Fix Status in nplan source package in Zesty: Fix Committed Status in linux source package in Artful: Won't Fix Status in nplan source package in Artful: In Progress Status in linux source package in Bionic: Won't Fix Status in nplan source package in Bionic: Fix Released Bug description: [Impact] Some network interfaces on a Xen guest are broken by new behavior introduced by netplan. On a Xen guest instance, when netplan is run to 'apply' its configuration, under certain circumstances netplan will try to "reset" the interface by unbinding and then re-binding the interface driver from the interface, by using the sysfs "bind" and "unbind" functions of the driver. Normally, this results in the interface being released and then fully re-initialized by the driver. However the Xen VIF driver breaks when this is done. The internal Xen backend state of the interface remains in 'closed' state after the driver re-connects to the interface, and attempts to open and use the interface result in a kernel Oops in the Xen VIF driver. To users, it appears that the interface is unusable because it has an all 0 mac address; but if the mac is manually set and the interface brought up the driver Oopses as mentioned above. This problem makes booting painful because of very long timeouts waiting for all network interfaces to start, and affected Xen VIF interfaces will of course never complete startup. [Fix] No fix yet. Upstream kernel does not appear fixed. [Test Case] Create a guest instance under a Xen hypervisor (e.g. an AWS instance) that has Ubuntu Artful 17.10 installed. Use only a single interface at first when creating it. Then once it is ready, attach a second network interface to the instance. From inside the instance, configure the new interface in netplan (i.e. add a /etc/netplan/ config for it). Make sure the new interface is down (netplan does not appear to unbind/bind interfaces that are up), and then run: $ sudo netplan apply or for debug, $ sudo netplan --debug apply this will unbind and re-bind the second interface, which will then have all-0 mac, and will be unusable, as described above. [Regression Potential] Changes to the Xen VIF driver can result in unusable network interfaces, or problems while using Xen VIF interfaces. [Other Info] Problem appears to exist upstream also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729573/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Steve Langasek (vorlon) wrote 1 hour ago: #48 Based on the description of how the problem arises - Ubuntu 17.10 installed on a system booted in legacy mode, not in UEFI mode. The problem appeared to me in UEFI mode, not Legacy. -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dm
[Kernel-packages] [Bug 1734147] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016384/+files/RfKill.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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage
[Kernel-packages] [Bug 1734147] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016378/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO
[Kernel-packages] [Bug 1734147] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016382/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO
[Kernel-packages] [Bug 1734147] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016379/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.v
[Kernel-packages] [Bug 1734147] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016380/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO
[Kernel-packages] [Bug 1734147] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016372/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage noti
[Kernel-packages] [Bug 1734147] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016386/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name:
[Kernel-packages] [Bug 1734147] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016370/+files/WifiSyslog.txt ** Description changed: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO + --- + ApportVersion: 2.20.7-0ubuntu3.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: tob1608 F pulseaudio + /dev/snd/controlC0: tob1608 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2017-10-22 (37 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + MachineType: LENOVO 20378 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-17-generic N/A + linux-backports-modules-4.13.0-17-generic N/A + linux-firmware 1.169 + Tags: artful wayland-session + Uname: Linux 4.13.0-17-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/12/2015 + dmi.bios.vendor: LENOVO + dmi.bios.version: 9ECN43WW(V3.03) + dmi.board.asset.tag: No Asset Tag + dmi.board.name: Lenovo Y50-70 + dmi.board.vendor: LENOVO + dmi.board.version: Not Defined + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Lenovo Y50-70 + dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: + dmi.product.family: IDEAPAD + dmi.product.name: 20378 + dmi.product.version: Lenovo Y50-70 + dmi.sys.vendor: LENOVO -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux p
[Kernel-packages] [Bug 1734147] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016374/+files/IwConfig.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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To ma
[Kernel-packages] [Bug 1734147] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016371/+files/AlsaInfo.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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To ma
[Kernel-packages] [Bug 1734147] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016376/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage no
[Kernel-packages] [Bug 1734147] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016373/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOV
[Kernel-packages] [Bug 1734147] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016385/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage
[Kernel-packages] [Bug 1734147] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016383/+files/PulseList.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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To
[Kernel-packages] [Bug 1734147] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016375/+files/JournalErrors.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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LEN
[Kernel-packages] [Bug 1734147] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016381/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: L
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Logs sent via apport-collect status changed -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/17
[Kernel-packages] [Bug 1734147] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016377/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage no
[Kernel-packages] [Bug 1734147] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016369/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage
[Kernel-packages] [Bug 1734147] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016367/+files/PulseList.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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To
[Kernel-packages] [Bug 1734147] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016362/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO
[Kernel-packages] [Bug 1734147] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016359/+files/JournalErrors.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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LEN
[Kernel-packages] [Bug 1734147] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016357/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOV
[Kernel-packages] [Bug 1734147] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016360/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage no
[Kernel-packages] [Bug 1734147] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016363/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.v
[Kernel-packages] [Bug 1734147] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016366/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO
[Kernel-packages] [Bug 1734147] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016368/+files/RfKill.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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage
[Kernel-packages] [Bug 1734147] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016365/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: L
[Kernel-packages] [Bug 1734147] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016364/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO
[Kernel-packages] [Bug 1734147] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016361/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage no
[Kernel-packages] [Bug 1734147] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016358/+files/IwConfig.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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To ma
[Kernel-packages] [Bug 1734147] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016356/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage noti
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
apport information ** Tags added: apport-collected wayland-session ** Description changed: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) + --- + ApportVersion: 2.20.7-0ubuntu3.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: tob1608 F pulseaudio + /dev/snd/controlC0: tob1608 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2017-10-22 (37 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + MachineType: LENOVO 20378 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-17-generic N/A + linux-backports-modules-4.13.0-17-generic N/A + linux-firmware 1.169 + Tags: artful wayland-session + Uname: Linux 4.13.0-17-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/12/2015 + dmi.bios.vendor: LENOVO + dmi.bios.version: 9ECN43WW(V3.03) + dmi.board.asset.tag: No Asset Tag + dmi.board.name: Lenovo Y50-70 + dmi.board.vendor: LENOVO + dmi.board.version: Not Defined + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Lenovo Y50-70 + dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: + dmi.product.family: IDEAPAD + dmi.product.name: 20378 + dmi.product.version: Lenovo Y50-70 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1734147/+attachment/5016355/+files/AlsaInfo.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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro qui
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
@vorlon, sorry that I haven't mentioned that, but the Ubuntu 17.10 and other distributions that I mentioned before were installed in the UEFI mode every time. -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.ve
[Kernel-packages] [Bug 1728739] Re: Attempt to map rbd image from ceph jewel/luminous hangs
Successfully verified this with kernel 4.4.0-102-generic in the xenial- proposed repository. I verified mapping rbd devices against Ceph versions: 0.94.10 Hammer release (from trusty-kilo cloud-archive) 10.2.7 Jewel release (from xenial-updates) 12.2.0 Luminous release (from xenial-pike cloud-archive) All versions had optimal tunables set, which previously prevented rbd mapping from completing for Jewel and Luminous releases due to missing TUNABLES5 support. All tests successfully mapped, formatted, and mounted. Relevant kernel log snippets: Nov 29 18:59:29 juju-49feb5-ceph-6 kernel: [0.00] Linux version 4.4.0-102-generic (buildd@lgw01-amd64-055) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) ) #125-Ubuntu SMP Tue Nov 21 15:15:11 UTC 2017 (Ubuntu 4.4.0-102.125-generic 4.4.98) RBD Mapping to Ceph Hammer Cluster v0.94.10 (trusty-kilo cloud-archive) Nov 29 19:01:45 juju-49feb5-ceph-6 kernel: [ 148.314991] Key type ceph registered Nov 29 19:01:45 juju-49feb5-ceph-6 kernel: [ 148.317382] libceph: loaded (mon/osd proto 15/24) Nov 29 19:01:45 juju-49feb5-ceph-6 kernel: [ 148.323276] rbd: loaded (major 251) Nov 29 19:01:45 juju-49feb5-ceph-6 kernel: [ 148.343492] libceph: client44139 fsid 6547bd3e-1397-11e2-82e5-53567c8d32dc Nov 29 19:01:45 juju-49feb5-ceph-6 kernel: [ 148.346357] libceph: mon2 10.5.0.3:6789 session established Nov 29 19:01:45 juju-49feb5-ceph-6 kernel: [ 148.415717] rbd: rbd0: added with size 0x28000 Nov 29 19:02:04 juju-49feb5-ceph-6 kernel: [ 167.519366] EXT4-fs (rbd0): mounted filesystem with ordered data mode. Opts: (null) RBD Mapping to Ceph Jewel Cluster v10.2.7 (xenial/trusty-mitaka cloud-archive) Nov 29 19:17:48 juju-49feb5-ceph-6 kernel: [ .874853] libceph: client64310 fsid 6547bd3e-1397-11e2-82e5-53567c8d32dc Nov 29 19:17:48 juju-49feb5-ceph-6 kernel: [ .876730] libceph: mon1 10.5.0.14:6789 session established Nov 29 19:17:48 juju-49feb5-ceph-6 kernel: [ .924995] rbd: rbd0: added with size 0x28000 Nov 29 19:17:54 juju-49feb5-ceph-6 kernel: [ 1117.704119] EXT4-fs (rbd0): mounted filesystem with ordered data mode. Opts: (null) RBD Mapping to Ceph Luminous Cluster v12.2.0 (xenial-ocata cloud-archive) Nov 29 19:41:42 juju-49feb5-ceph-6 kernel: [ 2545.672870] libceph: client4216 fsid 6547bd3e-1397-11e2-82e5-53567c8d32dc Nov 29 19:41:42 juju-49feb5-ceph-6 kernel: [ 2545.679350] libceph: mon1 10.5.0.12:6789 session established Nov 29 19:41:42 juju-49feb5-ceph-6 kernel: [ 2545.717272] rbd: rbd0: added with size 0x28000 Nov 29 19:42:04 juju-49feb5-ceph-6 kernel: [ 2567.088206] EXT4-fs (rbd0): mounted filesystem with ordered data mode. Opts: (null) ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1728739 Title: Attempt to map rbd image from ceph jewel/luminous hangs Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: [Impact] Attempting to map an rbd image using the 4.4 LTS (Xenial) kernel client from a Jewel or Luminous Ceph cluster with optimal tunables fails due to feature set mismatch. The Jewel release of Ceph introduced a new set of CRUSH tunables. These tunables were first introduced in the 4.5 Linux kernel and are thus not available in the 16.04 LTS 4.4 Linux Kernel. Attempting to map RBD images as block devices will fail due to not being able to understand these new tunables: (from kern.log) Oct 30 21:19:05 ceph-7 kernel: [ 815.674075] Key type ceph registered Oct 30 21:19:05 ceph-7 kernel: [ 815.676862] libceph: loaded (mon/osd proto 15/24) Oct 30 21:19:05 ceph-7 kernel: [ 815.678970] rbd: loaded (major 251) Oct 30 21:19:05 ceph-7 kernel: [ 815.689556] libceph: mon0 10.5.0.19:6789 feature set mismatch, my 106b84a842a42 < server's 40106b84a842a42, missing 400 Oct 30 21:19:05 ceph-7 kernel: [ 815.692897] libceph: mon0 10.5.0.19:6789 missing required protocol features Support for the new CRUSH tunables were added in upstream kernel 4.5 in http://www.spinics.net/lists/ceph-devel/msg28421.html. [Test Case] 1. Deploy a Jewel or Luminous Ceph cluster. 2. Create rbd image suitable for the kernel client: $ rbd create --pool rbd --image-feature layering --size 1G test 3. Map the rbd image to the local server: $ rbd map --pool rbd test [Regression Potential] Minimal. Code is limited to kernel rbd driver and new code should primarily affect clients connecting to clusters with the new tunables options. [Additional Info] A workaround is to change the crush tunables configured for the Ceph cluster to a legacy version (hammer or lower) via: $ ceph osd crush tunables hammer However, changing the tunables to hammer fails to allow
[Kernel-packages] [Bug 1734147] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1734147 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: artful -- 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Incomplete Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1733864] Re: kernel 4.10.0-40 is hanging with a CPU soft lock
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin16044 -- 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/1733864 Title: kernel 4.10.0-40 is hanging with a CPU soft lock Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: Kernel 4.10.0-40-generic is causing CPU hung on POWER machines. I got this problem on a POWER8 KVM virtual machine [ 1912.003255] NMI watchdog: BUG: soft lockup - CPU#12 stuck for 24s! [dpkg-deb:31284] [ 1912.004496] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ipt_REJECT nf_reject_ipv4 xfrm_user xfrm_algo xt_addrtype xt_conntrack br_netfilter ebtable_filter ebtables ip6table_filter ip6_tables ib_srpt dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio tcm_qla2xxx qla2xxx vhost_scsi vhost usb_f_tcm tcm_usb_gadget libcomposite udc_core tcm_fc libfc scsi_transport_fc tcm_loop iscsi_target_mod target_core_file target_core_iblock target_core_pscsi target_core_mod ipmi_devintf ipmi_msghandler xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp iptable_filter ip_tables x_tables openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) [ 1912.004575] znvpair(PO) spl(O) bridge 8021q garp mrp stp llc vmx_crypto kvm ib_iser rdma_cm iw_cm ib_cm ib_core configfs 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 ibmvscsi ibmveth crc32c_vpmsum virtio_blk [ 1912.004624] CPU: 12 PID: 31284 Comm: dpkg-deb Tainted: P O 4.10.0-40-generic #44~16.04.1-Ubuntu [ 1912.004626] task: c00775551e00 task.stack: c007755ac000 [ 1912.004627] NIP: 3fff86b71960 LR: 3fff86b7319c CTR: 002d [ 1912.004628] REGS: c007755afea0 TRAP: 0901 Tainted: P O (4.10.0-40-generic) [ 1912.004629] MSR: 8280f033 [ 1912.004635] CR: 42004442 XER: 2000 [ 1912.004636] CFAR: 3fff86b719b4 SOFTE: 1 GPR00: 00a4 3fffd53f7d70 3fff86ba5008 0040 GPR04: 038a20fc 3fff86467d4b 036c0ed8 002a GPR08: 3fff81c41010 000a20f5 0081 ffec0ed1 GPR12: 00a6 3fff86c8db30 [ 1912.004646] NIP [3fff86b71960] 0x3fff86b71960 [ 1912.004647] LR [3fff86b7319c] 0x3fff86b7319c [ 1912.004647] Call Trace: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733864/+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 1667239] Comment bridged from LTC Bugzilla
--- Comment From cdead...@us.ibm.com 2017-11-29 14:29 EDT--- State: Verify by: anitrap on 29 November 2017 13:18:44 I have accepted my verify records based on results from other testers. An official fix was not available when I had this hardware. There are still other verify records opened (we used a workaround to avoid seeing issue... seems like this bug is for ubuntu only?...) -- 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/1667239 Title: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: == Comment: #1 - Application Cdeadmin - 2016-06-02 15:28:27 == State: Open by: anitrap on 01 June 2016 17:36:39 Contact: Anitra Powell (anit...@us.ibm.com ) Backup: Dion Bell (bel...@us.ibm.com) Primary BMC (1603G): = # cat /proc/ractrends/Helper/FwInfo FW_VERSION=2.13.91819 FW_DATE=Mar 10 2016 FW_BUILDTIME=10:59:31 CDT FW_DESC=8335 SRC BUILD RR9 03102016 FW_PRODUCTID=1 FW_RELEASEID=RR9 FW_CODEBASEVERSION=2.X # PNOR (1603G): # ipmitool -H 127.0.0.1 -I lanplus -U ADMIN -P admin fru list 47 Product Name : OpenPOWER Firmware Product Version : IBM-firestone-ibm-OP8_v1.7_1.62 Product Extra : hostboot-bc98d0b-1a29dff Product Extra : occ-0362706-16fdfa7 Product Extra : skiboot-5.1.13 Product Extra : hostboot-binaries-43d5a59 Product Extra : firestone-xml-e7b4fa2-c302f0e Product Extra : capp-ucode-105cb8f Partition Info: = ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 16.04 LTS \n \l Kernel Version: 4.4.8c0ffee0+ HTX Version: htxubuntu-396 Host Name: fsbmc30p1 Machine Serial No: 210995A Machine Type/Model: 8335-GCA root@fsbmc30p1:~# uname -a Linux fsbmc30p1 4.4.8c0ffee0+ #2 SMP Tue May 24 10:50:26 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux FlashGT NVMe setup: === 1 FlashGT card in slot 1 running in superpipe mode with 128 LUNs per port (total of 256 LUNs). lsscsi [0:0:0:0]diskATA ST1000NX0313 BE33 /dev/sda [1:0:0:0]diskATA ST1000NX0313 BE33 /dev/sdb [4:0:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdc [4:1:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdd [5:0:0:0]cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 [5:0:0:1]cd/dvd AMI Virtual CDROM1 1.00 /dev/sr1 [5:0:0:2]cd/dvd AMI Virtual CDROM2 1.00 /dev/sr2 [5:0:0:3]cd/dvd AMI Virtual CDROM3 1.00 /dev/sr3 [6:0:0:0]diskAMI Virtual Floppy0 1.00 /dev/sde [6:0:0:1]diskAMI Virtual Floppy1 1.00 /dev/sdf [6:0:0:2]diskAMI Virtual Floppy2 1.00 /dev/sdg [6:0:0:3]diskAMI Virtual Floppy3 1.00 /dev/sdh [7:0:0:0]diskAMI Virtual HDisk0 1.00 /dev/sdi [7:0:0:1]diskAMI Virtual HDisk1 1.00 /dev/sdj [7:0:0:2]diskAMI Virtual HDisk2 1.00 /dev/sdk [7:0:0:3]diskAMI Virtual HDisk3 1.00 /dev/sdl [7:0:0:4]diskAMI Virtual HDisk4 1.00 /dev/sdm lspci | grep -i acc 0004:01:00.0 Processing accelerators: IBM Device 0601 (rev 01) ls -l /sys/class/cxl total 0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0m -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0m lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0s -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0s lrwxrwxrwx 1 root root 0 May 31 13:27 card0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0 lscfg | grep afu + afu0.0 Slot1/card0/afu0.0 + afu0.0m Slot1/card0/afu0.0/afu0.0m + afu0.0s Slot1/card0/afu0.0/afu0.0s /opt/ibm/capikv/bin/cxlfstatus CXL Flash Device Status Found 0601 0004:01:00.0 Slot1 Device: SCSI Block Mode LUN WWID sg2:4:0:0:0, sdc, superpipe, 600253800253824633000460 sg3:4:1:0:0, sdd, superpipe, 600253800253824633000520 dpkg -l | grep capi 4el no description given 3.0-1970-3042652 ppc6 4el no description given 3.0-1970-3042652 ppc6 root@fsbmc30p1:/tmp#
[Kernel-packages] [Bug 1717443] Re: Call trace observed when running xfstests on btrfs filesystem
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1710 -- 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/1717443 Title: Call trace observed when running xfstests on btrfs filesystem Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Invalid Bug description: == Comment: #0 - Harish Sriram <> - 2017-07-21 00:34:58 == Problem Description Call trace observed when running xfstests on btrfs filesystem Environment -- Kernel Build: 4.11.0-10-generic System Name : ltc-boston124 Model : 9006-22C Platform: PowerNV ( P9 ) Uname output --- # uname -a Linux ltc-boston124 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with btrfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.config for running with created loop device 5.. Run xfstests-dev test : ./check tests/btrfs/130 Dmesg: -- [Fri Jul 21 01:26:55 2017] INFO: rcu_sched self-detected stall on CPU [Fri Jul 21 01:26:55 2017]4-...: (210013 ticks this GP) idle=6db/141/0 softirq=18227470/18227470 fqs=104791 [Fri Jul 21 01:26:55 2017] (t=210039 jiffies g=10179019 c=10179018 q=1388) [Fri Jul 21 01:26:55 2017] Task dump for CPU 4: [Fri Jul 21 01:26:55 2017] btrfs R running task0 24224 19847 0x00042006 [Fri Jul 21 01:26:55 2017] Call Trace: [Fri Jul 21 01:26:55 2017] [c0002003dd62efb0] [c01240dc] sched_show_task+0xcc/0x150 (unreliable) [Fri Jul 21 01:26:55 2017] [c0002003dd62f020] [c0b80d20] rcu_dump_cpu_stacks+0xd0/0x134 [Fri Jul 21 01:26:55 2017] [c0002003dd62f070] [c0177214] rcu_check_callbacks+0x9f4/0xb40 [Fri Jul 21 01:26:55 2017] [c0002003dd62f1a0] [c0180968] update_process_times+0x48/0x90 [Fri Jul 21 01:26:55 2017] [c0002003dd62f1d0] [c0197a70] tick_sched_handle.isra.7+0x30/0xb0 [Fri Jul 21 01:26:55 2017] [c0002003dd62f200] [c0197b54] tick_sched_timer+0x64/0xd0 [Fri Jul 21 01:26:55 2017] [c0002003dd62f240] [c0181408] __hrtimer_run_queues+0x108/0x390 [Fri Jul 21 01:26:55 2017] [c0002003dd62f2c0] [c0182458] hrtimer_interrupt+0xf8/0x330 [Fri Jul 21 01:26:55 2017] [c0002003dd62f390] [c0023dcc] __timer_interrupt+0x8c/0x270 [Fri Jul 21 01:26:55 2017] [c0002003dd62f3e0] [c00241cc] timer_interrupt+0x9c/0xe0 [Fri Jul 21 01:26:55 2017] [c0002003dd62f410] [c00090a4] decrementer_common+0x114/0x120 [Fri Jul 21 01:26:55 2017] --- interrupt: 901 at find_parent_nodes+0x97c/0x1680 [btrfs] LR = find_parent_nodes+0x930/0x1680 [btrfs] [Fri Jul 21 01:26:55 2017] [c0002003dd62f700] [c008571bcbfc] find_parent_nodes+0x874/0x1680 [btrfs] (unreliable) [Fri Jul 21 01:26:55 2017] [c0002003dd62f840] [c008571bee64] iterate_extent_inodes+0x3ec/0x440 [btrfs] [Fri Jul 21 01:26:55 2017] [c0002003dd62f960] [c008571ccddc] process_extent+0x804/0xc00 [btrfs] [Fri Jul 21 01:26:55 2017] [c0002003dd62fa80] [c008571d06cc] changed_cb+0x574/0xe00 [btrfs] [Fri Jul 21 01:26:55 2017] [c0002003dd62fb40] [c008571d1f74] btrfs_ioctl_send+0x101c/0x10e0 [btrfs] [Fri Jul 21 01:26:55 2017] [c0002003dd62fc40] [c00857186218] btrfs_ioctl+0x16e0/0x23f0 [btrfs] [Fri Jul 21 01:26:55 2017] [c0002003dd62fd40] [c0372124] do_vfs_ioctl+0xd4/0x8c0 [Fri Jul 21 01:26:55 2017] [c0002003dd62fde0] [c03729e4] SyS_ioctl+0xd4/0xf0 [Fri Jul 21 01:26:55 2017] [c0002003dd62fe30] [c000b184] system_call+0x38/0xe0 [Fri Jul 21 01:27:58 2017] INFO: rcu_sched self-detected stall on CPU [Fri Jul 21 01:27:58 2017]4-...: (225763 ticks this GP) idle=6db/141/0 softirq=18227470/18227470 fqs=112651 [Fri Jul 21 01:27:58 2017] (t=225792 jiffies g=10179019 c=10179018 q=2542) [Fri Jul 21 01:27:58 2017] Task dump for CPU 4: [Fri Jul 21 01:27:58 2017] btrfs R running task0 24224 19847 0x00042006 [Fri Jul 21 01:27:58 2017] Call Trace: [Fri Jul 21 01:27:58 2017] [c0002003dd62efb0] [c01240dc] sched_show_task+0xcc/0x150 (unreliable) [Fri Jul 21 01:27:58 2017] [c0002003dd62f020] [c0b80d20] rcu_dump_cpu_stacks+0xd0/0x134 [Fri Jul 21 01:27:58 2017] [c0002003dd62f070] [c0177214] rcu_check_callbacks+0x9f4/0xb40 [Fri Jul 21 01:27:58 2017] [c0002003dd62f1a0] [c0180968] update_process_times+0x48/0x90 [Fri Jul 21 01:27:58 2017] [c0002003dd62f1d0] [c0197a70] tick_sched_handle.isra.7+0x30/0xb0 [Fri Jul 21 01:27:58 2017] [c0002003dd62f200] [c0197b54] tick_sched_timer+0x64/0xd
[Kernel-packages] [Bug 1735271] [NEW] Update firmware for netronome SmartNICs
Public bug reported: Feature request for Bionic Update firmware for Netronome SmartNICs. It is planned to provide updated firmware to the linux-firmware project in the coming days and update this bug with the list of updated firmware accordingly. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1735271 Title: Update firmware for netronome SmartNICs Status in linux-firmware package in Ubuntu: New Bug description: Feature request for Bionic Update firmware for Netronome SmartNICs. It is planned to provide updated firmware to the linux-firmware project in the coming days and update this bug with the list of updated firmware accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1735271/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Based on the description of how the problem arises - Ubuntu 17.10 installed on a system booted in legacy mode, not in UEFI mode, and the problem showing up only after upgrade to Ubuntu 17.10 when Ubuntu 17.04 was running fine - it is likely that any problems here are in the Linux kernel rather than in the bootloader. When booting in BIOS mode instead of UEFI mode, the grub package does not do anything that touches firmware settings; and there have been no relevant changes to the grub code when booting in BIOS mode, between 17.04 and 17.10. Therefore reassigning this bug to the kernel. ** Package changed: grub2 (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: New Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1734147] [NEW] Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
You have been subscribed to a public bug: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. For example: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-or-boot-with-USB/m-p/3849142 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3601285 https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/y50-70-BIOS-can-t -save-settings-and-I-can-t-boot-system/m-p/3865727 Thank you!! UPDATE (27/11/2017) LENOVO machines affected so far: Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) ** Affects: linux (Ubuntu) Importance: High Status: New -- Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models https://bugs.launchpad.net/bugs/1734147 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Where are there directions on how to compile this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1637978] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2017-11-29 14:04 EDT--- Closing as current ubuntu includes this command. -- 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/1637978 Title: take 'P' command from upstream xmon Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: upstream commit 6dfb54049f9a99b24fe5d5cd2d3af19eadc8f31f contains an enhancement to xmon to allow listing running tasks. This is vital to debugging efforts, and so needs to be added to as many release streams as possible, as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637978/+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 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
Boot with acpi_osi="!Windows 2015" and all tunables set manually to good, powertop still shows lowest package state C3 but fans turned off properly. Attached new dmesg output anyway, but problem seems to be "workarounded" (not resolved) as I have to set tunables to good manually or via script. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+attachment/5016311/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Compiling this http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- next/current/ with the last 3 commits by Hans de Goede from this https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git/log/?h=for-4.16 /hid-quirks-cleanup/multitouch should save the day. I am unable to compile right 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1729145] Re: /dev/bcache/by-uuid links not created after reboot
So, the kernel fix could look like this: * instead of just failing with "device already registered" * the kernel would emit another uevent with CACHED_UUID which would be processed another time to set up a symlink It seems like this approach with "synthetic uevents" may be used for other purposes as well with changes that landed in 4.13 http://elixir.free-electrons.com/linux/v4.14.2/source/Documentation/ABI/testing/sysfs-uevent "Enable passing additional variables for synthetic uevents that are generated by writing /sys/.../uevent file Recognized extended format is ACTION [UUID [KEY=VALUE ...] Users: udev, userspace tools generating synthetic uevents" -- 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/1729145 Title: /dev/bcache/by-uuid links not created after reboot Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: 1. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 2. $ apt-cache policy linux-image-`uname -r` linux-image-4.13.0-16-generic: Installed: 4.13.0-16.19 Candidate: 4.13.0-16.19 Version table: *** 4.13.0-16.19 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3. After creating some bcache devices and rebooting /dev/bcache/by-uuid/ -> ../../bcacheN symlinks point to the current bcache device which is caching the dev.uuid found after creating a backing device. 4. /dev/bcache/by-uuid does not exist and there are not symlinks underneath It appears that since the initramfs loads the bcache module which probes and finds all of the cache devices and backing devices then once the rootfs is mounted and udev gets to run, the bcache kernel module does not emit the CACHED_UUID value into the environment if the underlying devices are already registered. In dmesg, one can see that prior to mounting the rootfs, we see bcache register events: [5.333973] bcache: register_bdev() registered backing device vdb2 [5.354138] bcache: register_bdev() registered backing device vdb4 [5.365665] bcache: register_bdev() registered backing device vdb3 [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 entries, seq 1 [5.428683] bcache: register_cache() registered cache device vdb1 then rootfs ismounted and systemd starts systemd-udev [9.350889] systemd[1]: Listening on udev Kernel Socket. And then the coldplug replay of kernel events triggers /lib/udev/rules.d/69-bcache.rules which invokes /lib/udev/bcache-register which writes the device name (/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the bcache kernel driver attempting to register the block device. However, there is already a bcache device associated already and registration fails [ 11.173141] bcache: register_bcache() error opening /dev/vdb2: device already registered [ 11.184617] bcache: register_bcache() error opening /dev/vdb3: device already registered [ 11.199130] bcache: register_bcache() error opening /dev/vdb1: device already registered [ 11.271694] bcache: register_bcache() error opening /dev/vdb4: device already registered The problem then is that only a kernel call to bch_cached_dev_run() which happens like this: bcache_register() register_bdev() bch_cached_dev_run() kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env); where env includes: "DRIVER=bcache", kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid), NULL, NULL, }; Since that event is not emitted for any previously registered device, then the symlink will not be created. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 31 22:09 seq crw-rw 1 root audio 116, 33 Oct 31 22:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Nov 1 01:39:01 2017 Ec2AMI: ami-030b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus
[Kernel-packages] [Bug 1735024] Re: Cannot boot without acpi=off
Of course, installed 4.15.0-041500rc1-generic kernel from upstream. Results by added boot options: : reboots acpi=off: works without ACPI info acpi=ht: reboots pci=noacpi: freezes after kernel loading acpi=noirq: freezes after kernel loading pnpacpi=off: freezes after kernel loading noapic: reboots nolapic: boots, shows kernel messages and then freezes More information: `sudo acpidump` returns: Cannot open directory - /sys/firmware/acpi/tables Could not get ACPI tables, AE_NOT_FOUND `sudo fwts acpidump` in attachment. ** Attachment added: "results.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735024/+attachment/5016295/+files/results.log ** Tags added: kernel-bug-exists-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/1735024 Title: Cannot boot without acpi=off Status in linux package in Ubuntu: Incomplete Bug description: Bought a new laptop but after reinstalling cannot boot without acpi=off ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-generic 4.13.0.17.18 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arseniuss954 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 29 02:25:57 2017 InstallationDate: Installed on 2017-11-26 (2 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-51 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=7105a1eb-3d1e-4b00-9668-da7cce948f4e ro acpi=off RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_KLS dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnNitroAN515-51:pvrV1.05:rvnKBL:rnFreed_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-51 dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735024/+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 1729145] Re: /dev/bcache/by-uuid links not created after reboot
I reviewed this once again: 1. persistent /dev/bcache - not possible or needed due to how kernel enumeration works 2. our userspace handles /dev/by-dname/ properly so we just need CACHED_UUID given to us during coldplug in some way to properly create /dev/bcache/by-uuid/ symlinks and consequently by-dname symlinks. 3. bcache, like almost all block device drivers, gets "struct device_type disk_type" by using alloc_disk from genhd.c which gives us standard contents for the uevent file. Partitions are a notable exception and use "struct device_type part_type" which has a .uevent field (http://elixir.free-electrons.com/linux/v4.14.2/source/block /partition-generic.c#L223) that allows customization of uevent file contents in a bus-, class- and type-specific manner (http://elixir.free- electrons.com/linux/v4.14.2/source/drivers/base/core.c#L903). cat /sys/class/block/nvme0n1/uevent MAJOR=259 MINOR=0 DEVNAME=nvme0n1 DEVTYPE=disk as opposed to the following with partitions cat /sys/class/block/nvme0n1p1/uevent MAJOR=259 MINOR=1 DEVNAME=nvme0n1p1 DEVTYPE=partition PARTN=1 PARTNAME=Basic data partition While we could have a new block device type of "bcache" with a custom uevent content that had CACHED_UUID of a superblock this would be a userspace breakage which is hardly upstreamable. -- 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/1729145 Title: /dev/bcache/by-uuid links not created after reboot Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: 1. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 2. $ apt-cache policy linux-image-`uname -r` linux-image-4.13.0-16-generic: Installed: 4.13.0-16.19 Candidate: 4.13.0-16.19 Version table: *** 4.13.0-16.19 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3. After creating some bcache devices and rebooting /dev/bcache/by-uuid/ -> ../../bcacheN symlinks point to the current bcache device which is caching the dev.uuid found after creating a backing device. 4. /dev/bcache/by-uuid does not exist and there are not symlinks underneath It appears that since the initramfs loads the bcache module which probes and finds all of the cache devices and backing devices then once the rootfs is mounted and udev gets to run, the bcache kernel module does not emit the CACHED_UUID value into the environment if the underlying devices are already registered. In dmesg, one can see that prior to mounting the rootfs, we see bcache register events: [5.333973] bcache: register_bdev() registered backing device vdb2 [5.354138] bcache: register_bdev() registered backing device vdb4 [5.365665] bcache: register_bdev() registered backing device vdb3 [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 entries, seq 1 [5.428683] bcache: register_cache() registered cache device vdb1 then rootfs ismounted and systemd starts systemd-udev [9.350889] systemd[1]: Listening on udev Kernel Socket. And then the coldplug replay of kernel events triggers /lib/udev/rules.d/69-bcache.rules which invokes /lib/udev/bcache-register which writes the device name (/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the bcache kernel driver attempting to register the block device. However, there is already a bcache device associated already and registration fails [ 11.173141] bcache: register_bcache() error opening /dev/vdb2: device already registered [ 11.184617] bcache: register_bcache() error opening /dev/vdb3: device already registered [ 11.199130] bcache: register_bcache() error opening /dev/vdb1: device already registered [ 11.271694] bcache: register_bcache() error opening /dev/vdb4: device already registered The problem then is that only a kernel call to bch_cached_dev_run() which happens like this: bcache_register() register_bdev() bch_cached_dev_run() kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env); where env includes: "DRIVER=bcache", kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid), NULL, NULL, }; Since that event is not emitted for any previously registered device, then the symlink will not be created. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 31 22:09 seq crw-rw 1
[Kernel-packages] [Bug 1734734] Re: linux-lts-trusty: 3.13.0-136.185~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1734733 phase: Uploaded + kernel-stable-phase-changed:Wednesday, 29. November 2017 18:01 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1734733 - phase: Uploaded - kernel-stable-phase-changed:Wednesday, 29. November 2017 18:01 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1734734 Title: linux-lts-trusty: 3.13.0-136.185~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1734733 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1734734/+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 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
** Description changed: - ppc64el ADT log: + [Impact] + + The killswitches-no-urfkill autopkgtest fails sometimes because nmcli + reports the old state when it's called right after rfkill block/unblock. + Adding a sleep before calling nmcli fixes the issue. + + ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' - AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o - CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o - Building modules, stage 2. - MODPOST 1 modules - CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o - LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko + AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o + CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o + Building modules, stage 2. + MODPOST 1 modules + CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o + LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 + + + [Test Case] + + 2.1. Download network-manager package source code + $ apt-get source network-manager + + 2.2. Run killswitches-no-urfkill testcase + $ cd network-manager-1.8.4 + $ sudo ./debian/tests/killswitches-no-urfkill + + + [Regression Potential] + + No regression potential. The fix touches only the testcase shipped with + the source package and it doesn't change the binary package. The sleep + time added is very small, so no possibility of causing testcase timeout. + + + [Other Info] + + On ppc64el architecture, it was observed that a fix for systemd is also + needed (see bug 1734908) for the testcase to be successful. -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in linux package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in linux source package in Artful: Triaged Status in network-manager source package in Artful: New Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] No regressio
[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration
** Tags removed: verification-needed-zesty verification-ocata-needed ** Tags added: verification-failed-zesty verification-ocata-failed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1710019 Title: support GICv3 ITS save/restore & migration Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive ocata series: Fix Committed Status in Ubuntu Cloud Archive pike series: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in qemu source package in Xenial: Won't Fix Status in linux source package in Zesty: In Progress Status in qemu source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Committed Status in qemu source package in Artful: Fix Released Bug description: [Impact] Virtual machines on GICv3-based ARM systems cannot be saved/restored or migrated. This feature was added in QEMU 2.10. [Test Case] ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav Domain 7936-0 saved to 7936-0.sav ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav error: Failed to restore domain from 7396-0.sav error: operation failed: job: unexpectedly failed ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log 2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by non-migratable device 'arm_gicv3_its' 2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: Invalid argument 2017-08-10 21:26:38.217+: shutting down, reason=failed [Regression Risk] The kernel changes are restricted to ARM, minimizing the regression risk on other architectures. Other than one minor offset adjustment, all patches are clean cherry-picks from upstream. Tested on Cavium ThunderX and Qualcomm Centriq. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1710019/+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 1734761] Re: enable new configure options for 4.15
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Seth Forshee (sforshee) -- 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/1734761 Title: enable new configure options for 4.15 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Hi, When 4.15 is brought into Ubuntu bionic I wanted to make sure that a few configure options were selected to compile as module (as they won't come by default): 1) Intel WMI thunderbolt driver 2) Dell SMBIOS WMI driver 3) Dell SMBIOS SMM driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration
On Fri, Nov 24, 2017 at 4:51 AM, ChristianEhrhardt <1710...@bugs.launchpad.net> wrote: > Hi Dann, > maybe it was good to hold off on this. > It seems it causes a regression on arm, see bug 1734326. > Also by holding for an arbitrary amount of time it might block the SRU queue > for something else. Sorry for the late reply - holidays, and behind on e-mail :( > If you agree I'd ask you to let the SRU team cancel the upload from proposed. I agree. I think it is best to scrap the zesty backport at this point. I will request the reject. > And you can then take time to: > a) continue with the kernel Team discussions > b) analyze how bug 1734326 would be related and how to fix it > > If you do so I'd immediately do a revert in the qemu git so that the > next SRU doesn't push the same by accident. > > @Coreycb - if done that way you likely want to cancel ocata proposed as > well. +1 cancelling the current ocata-proposed QEMU. I'll make a todo to investigate LP: #1734326 to see if it can be easily resolved and, if so, possibly request that we carry these patches as a diff in the ocata cloud archive. -- 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/1710019 Title: support GICv3 ITS save/restore & migration Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive ocata series: Fix Committed Status in Ubuntu Cloud Archive pike series: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in qemu source package in Xenial: Won't Fix Status in linux source package in Zesty: In Progress Status in qemu source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Committed Status in qemu source package in Artful: Fix Released Bug description: [Impact] Virtual machines on GICv3-based ARM systems cannot be saved/restored or migrated. This feature was added in QEMU 2.10. [Test Case] ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav Domain 7936-0 saved to 7936-0.sav ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav error: Failed to restore domain from 7396-0.sav error: operation failed: job: unexpectedly failed ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log 2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by non-migratable device 'arm_gicv3_its' 2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: Invalid argument 2017-08-10 21:26:38.217+: shutting down, reason=failed [Regression Risk] The kernel changes are restricted to ARM, minimizing the regression risk on other architectures. Other than one minor offset adjustment, all patches are clean cherry-picks from upstream. Tested on Cavium ThunderX and Qualcomm Centriq. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1710019/+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 1729119] Re: NVMe timeout is too short
[VERIFICATION TRUSTY] #changelog linux (3.13.0-136.185) trusty; urgency=low * linux: 3.13.0-136.185 -proposed tracker (LP: #1734733) * NVMe timeout is too short (LP: #1729119) - NVMe: Make I/O timeout a module parameter - nvme: update timeout module parameter type # lsb_release -r Release:14.04 # uname -r 3.13.0-136-generic # lsmod | grep -i nvme # modprobe nvme io_timeout=123456 # lsmod | grep -i nvme nvme 59545 0 # cat /sys/module/nvme/parameters/io_timeout 123456 - Eric ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1729119 Title: NVMe timeout is too short Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux-aws source package in Trusty: New Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Committed Status in linux-aws source package in Zesty: Invalid Status in linux source package in Artful: Fix Committed Status in linux-aws source package in Artful: Invalid Bug description: [SRU Justification] [Impact] Some NVMe operations time out too quickly. The module parameters allow the timeouts to be extended, but only up to 255s, as the counters are bytes. [Fix] The underlying parameters are unsigned ints, so make the module parameters unsigned ints too, by picking patch http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.html (Trusty specific) This also requires picking the patch that converts the constant into a parameter, which is a clean cherry-pick. [Regression Potential] (X/Z/A) Very limited: only types of module parameters are changing, the patch is easily reviewable. (Trusty specific) Limited: a module parameter is added and its type is changed. The patches are easily reviewable. [Testing] (Trusty only) Boot tested on a c5.large instance on AWS which uses NVMe to boot. Verified that the system still boots with the patches, and that a timeout of 123456s is permitted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729119/+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 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
This is a debdiff for Artful applicable to network-manager 1.8.4-1ubuntu3. This was built with pbuilder and the testcase shipped with the source packaged works as expected (on the environment described on this bug report only if the fix for bug 1734908 is also applied). ** Patch added: "1-1.8.4-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+attachment/5016266/+files/1-1.8.4-1ubuntu4.debdiff -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in linux package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in linux source package in Artful: Triaged Status in network-manager source package in Artful: New Bug description: ppc64el ADT log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733321/+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 1734733] Re: linux: 3.13.0-136.185 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1734733 Title: linux: 3.13.0-136.185 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 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 backports: 1734734 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1734733/+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 1734733] Re: linux: 3.13.0-136.185 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing 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/1734733 Title: linux: 3.13.0-136.185 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 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 backports: 1734734 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1734733/+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 1725350] Re: KVM on 17.10 crashes the machine
** Tags added: bugnameltc-159844 severity-critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1725350 Title: KVM on 17.10 crashes the machine Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: When you start qemu on a 17.10 machine, the whole machine goes down and crashes: [ 90.689627] Unable to handle kernel paging request for data at address 0xf2d3bda0 [ 90.689705] Faulting instruction address: 0xc0361224 [ 90.689840] Oops: Kernel access of bad area, sig: 11 [#1] [ 90.689911] SMP NR_CPUS=2048 [ 90.689912] NUMA [ 90.690053] PowerNV [ 90.690092] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack_netlink nf_conntrack nfnetlink idt_89hpesx snd_hda_codec_hdmi xfs joydev input_leds mac_hid snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore ofpart opal_prd cmdlinepart powernv_flash mtd at24 ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng uio_pdrv_genirq vmx_crypto ibmpowernv uio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables [ 90.690724] autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage ast crct10dif_vpmsum i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm tg3 ahci libahci [ 90.690937] CPU: 48 PID: 3986 Comm: qemu-system-ppc Not tainted 4.13.0-12-generic #13-Ubuntu [ 90.691001] task: c00b122d8700 task.stack: c00b431cc000 [ 90.691167] NIP: c0361224 LR: c0998960 CTR: c09a19b0 [ 90.691223] REGS: c00bff61b800 TRAP: 0300 Not tainted (4.13.0-12-generic) [ 90.691277] MSR: 90009033 [ 90.691282] CR: 88002844 XER: [ 90.691347] CFAR: c099895c DAR: f2d3bda0 DSISR: 4000 SOFTE: 0 [ 90.691347] GPR00: c0998960 c00bff61ba80 c15e3000 c00b4ef61f20 [ 90.691347] GPR04: c00b44c61680 001f 001f [ 90.691347] GPR08: 001f 02d3bd80 c178e8e8 c00b5a0c26f0 [ 90.691347] GPR12: 28002842 cfadf800 c00b52d07880 c00b44c61680 [ 90.691347] GPR16: 001f 001f c553a560 [ 90.691347] GPR20: 0001 0002 08000553a560 c00b5c62a228 [ 90.691347] GPR24: c5531110 c00b5c632238 0210 [ 90.691347] GPR28: c0998960 c00bff61bc20 c00b4ef61f20 f2d3bd80 [ 90.692089] NIP [c0361224] kfree+0x54/0x270 [ 90.692133] LR [c0998960] xhci_urb_free_priv+0x20/0x40 [ 90.692325] Call Trace: [ 90.692345] [c00bff61ba80] [c00bff61bad0] 0xc00bff61bad0 (unreliable) [ 90.692402] [c00bff61bac0] [c0998960] xhci_urb_free_priv+0x20/0x40 [ 90.692459] [c00bff61bae0] [c099bfc8] xhci_giveback_urb_in_irq.isra.22+0x78/0x190 [ 90.692645] [c00bff61bb40] [c099c350] xhci_td_cleanup+0x130/0x200 [ 90.692702] [c00bff61bbc0] [c09a175c] handle_tx_event+0x74c/0x1380 [ 90.692759] [c00bff61bcc0] [c09a2894] xhci_irq+0x504/0xf20 [ 90.692808] [c00bff61bde0] [c017b110] __handle_irq_event_percpu+0x90/0x300 [ 90.692977] [c00bff61bea0] [c017b3b8] handle_irq_event_percpu+0x38/0x90 [ 90.693038] [c00bff61bee0] [c017b474] handle_irq_event+0x64/0xb0 [ 90.693094] [c00bff61bf10] [c0180da0] handle_fasteoi_irq+0xc0/0x230 [ 90.693155] [c00bff61bf40] [c017972c] generic_handle_irq+0x4c/0x70 [ 90.693332] [c00bff61bf60] [c001767c] __do_irq+0x7c/0x1c0 [ 90.693383] [c00bff61bf90] [c002ab70] call_do_irq+0x14/0x24 [ 90.693431] [c00b431cf9d0] [c001785c] do_IRQ+0x9c/0x130 [ 90.693478] [c00b431cfa20] [c0008ac4] hardware_interrupt_common+0x114/0x120 [ 90.693663] --- interrupt: 501 at __copy_tofrom_user_power7+0x1f4/0x7cc [ 90.693663] LR = _copy_to_user+0x3c/0x60 [ 90.693736] [c00b431cfd10] [c00b431cfdc0] 0xc00b431cfdc0 (unreliable) [ 90.693797] [c00b431cfd30] [c03bfa90] poll_select_copy_remaining+0
[Kernel-packages] [Bug 1729119] Re: NVMe timeout is too short
[VERIFICATION ARTFUL] # rmadison linux-image-4.13.0-18-generic | 4.13.0-18.21 | artful-proposed | amd64, arm64, armhf, i386, ppc64el, s390x # apt-get changelog linux-image-4.13.0-18-generic * NVMe timeout is too short (LP: #1729119) - nvme: update timeout module parameter type # lsb_release -r Release:17.10 # uname -r 4.13.0-18-generic I had no nvme drive at my disposal but the following test should suffice : # lsmod | grep -i nvme # modprobe nvme_core io_timeout=123456 # lsmod | grep -i nvme nvme_core 53248 0 # cat /sys/module/nvme_core/parameters/io_timeout 123456 - Eric ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1729119 Title: NVMe timeout is too short Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux-aws source package in Trusty: New Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Committed Status in linux-aws source package in Zesty: Invalid Status in linux source package in Artful: Fix Committed Status in linux-aws source package in Artful: Invalid Bug description: [SRU Justification] [Impact] Some NVMe operations time out too quickly. The module parameters allow the timeouts to be extended, but only up to 255s, as the counters are bytes. [Fix] The underlying parameters are unsigned ints, so make the module parameters unsigned ints too, by picking patch http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.html (Trusty specific) This also requires picking the patch that converts the constant into a parameter, which is a clean cherry-pick. [Regression Potential] (X/Z/A) Very limited: only types of module parameters are changing, the patch is easily reviewable. (Trusty specific) Limited: a module parameter is added and its type is changed. The patches are easily reviewable. [Testing] (Trusty only) Boot tested on a c5.large instance on AWS which uses NVMe to boot. Verified that the system still boots with the patches, and that a timeout of 123456s is permitted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729119/+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 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
Happy to supply any info that might help. On Arch based Antergos with the patched realtek driver, and powertop tunables set to good, CPU package reaches C7 and fan issue is resolved. Only other difference I can think of is that I have acpi_osi="!Windows 2015" as a kernel boot parameter. -- 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/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1735159] Re: powerpc/powernv: Flush console before platform error reboot
I built a Zesty test kernel with your back port. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1735159/ Can you test this kernel and see 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/1735159 Title: powerpc/powernv: Flush console before platform error reboot Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Unrecovered MCE and HMI errors are sent through a special restart OPAL call to log the platform error. The downside is that they don't go through normal Linux crash paths, so they don't give much information to the Linux console. We need to have the commit b746e3e01e70d23ef53dcde1203ab78a1b7ac514 in kernel 4.10. I did the backport and that will be attached to this bug. I also tested kernel -41 with this patch in several scenarios (KVM guest, Hypervisor) and I see no regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1735159/+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 1734542] Re: Acpi support not set: throttling not working
As said into the initial comment: "(neither all the previous ubuntu kernels)" ** 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/1734542 Title: Acpi support not set: throttling not working Status in linux package in Ubuntu: Confirmed Bug description: I am seeing a throttling difference about 4.13.13 kernel: - the Artful kernel 4.13.0-18-generic, based on 4.13.13, does not manage the cpu frequency (neither all the previous ubuntu kernels) CPU type : Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz Min/Max frequency : 800/3200 MHz acpi -V No support for device type: power_supply No support for device type: power_supply Cooling 0: Processor 0 of 3 Cooling 1: Processor 0 of 3 Cooling 2: LCD 0 of 100 Cooling 3: pch_skylake no state information available Cooling 4: Processor 0 of 3 Cooling 5: Processor 0 of 3 Cooling 6: intel_powerclamp no state information available Cooling 7: x86_pkg_temp no state information available - The same pc also have a bionic partition, where the 4.13.13 vanilla kernel perfectly manage the cpu dynamic frequency, so it is not related to the uefi settings in that case. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-18-generic 4.13.0-18.21 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: oem1438 F...m pulseaudio /dev/snd/controlC0: oem1438 F pulseaudio CurrentDesktop: GNOME Date: Sun Nov 26 16:15:43 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3 IwConfig: lono wireless extensions. enp2s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro RelatedPackageVersions: linux-restricted-modules-4.13.0-18-generic N/A linux-backports-modules-4.13.0-18-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.00 dmi.board.name: B150M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734542/+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 1735183] Re: built-in tests: fail early when preparation steps fail
** Changed in: ubuntu-fan (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-fan (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1735183 Title: built-in tests: fail early when preparation steps fail Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: In Progress Status in ubuntu-fan source package in Zesty: In Progress Status in ubuntu-fan source package in Artful: Fix Released Bug description: [SRU justification] Impact: Preparing the test environment (shared between host and slave side) currently is not checking for errors. This was observed when we had issues with docker containers failing to have DNS resolution. This lead to required utils not being installed which was not detected and then the test was stuck until forcefully terminated. Fix: Additional code during the preparation of the test environment which checks for errors and returns those to the caller. And additional error handling from the callers. Testcase: Only regression testing possible without running into other issues. But while docker problems were still present the tests were failed after a few minutes of runtime instead of timing out. Regression potential: Minimal. The modified code is used by the ADT tests which are run as part of the release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1735183/+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 1734490] Re: Graphics mode never switches from console mode on Artful kernel
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".
Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: performing-bisect
--
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/1734490
Title:
Graphics mode never switches from console mode on Artful kernel
Status in linux package in Ubuntu:
Confirmed
Bug description:
Booting a Lenovo S-10 Ideal pad on the 4.13 kernel in Artful fails to
bring up the Graphical display (only the mouse shows). Console-mode
works fine. Switch back to previous release kernel (4.10) works fine.
Booting includes an intel graphics assertion about plane B switching.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-17-generic 4.13.0-17.20
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.13.0-17-generic.
AplayDevices:
Home directory not accessible: Permission denied
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: i386
ArecordDevices:
Home directory not accessible: Permission denied
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p',
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x5834 irq 26'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,17aac000,0011'
Controls : 25
Simple ctrls : 12
Date: Sat Nov 25 16:49:10 2017
HibernationDevice: RESUME=UUID=aafbc493-1d2a-461a-abf2-6b6d98917d8c
InstallationDate: Installed on 2017-05-06 (202 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
MachineType: LENOVO 2957
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic
root=UUID=1976e1af-afbb-46db-a689-b0d7ef818e9e ro quiet splash vt.handoff=7
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.13.0-17-generic N/A
linux-backports-modules-4.13.0-17-generic N/A
linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-11-17 (8 days ago)
dmi.bios.date: 06/05/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 1ACN16WW(V1.07)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mariana2
dmi.board.vendor: LENOVO
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnLENOVO:bvr1ACN16WW(V1.07):bd06/05/2009:svnLENOVO:pn2957:pvrLenovoIdeaPadS10-2:rvnLENOVO:rnMariana2:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: 2957
dmi.product.version: Lenovo IdeaPad S10-2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734490/+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 1732717] Re: docker test broken by systemd-resolv environment
** Changed in: ubuntu-fan (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: ubuntu-fan (Ubuntu Zesty) Status: New => In Progress ** Changed in: ubuntu-fan (Ubuntu Zesty) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: ubuntu-fan (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: ubuntu-fan (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-fan (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: ubuntu-fan (Ubuntu) Assignee: Stefan Bader (smb) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1732717 Title: docker test broken by systemd-resolv environment Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: In Progress Status in ubuntu-fan source package in Zesty: In Progress Status in ubuntu-fan source package in Artful: In Progress Bug description: Inside a docker container DNS lookups are routed to 127.0.0.11:53 which is provided by the docker environment in some way. The real DNS service is taken from the hosts /etc/resolv.conf. The docker man page claims that selecting a good automatic default would not work if the hosts uses local resolvers (127.0.0.0/8). Since switching to netplan/systemd-resolvd there is only a local resolver (127.0.0.53) added to /etc/resolv.conf on the host. Surprisingly this does not seem to be an issue for an artful(or later) VM running on my own local desktop. But in the Canonical CI environment DNS lookups fail inside a docker container. SRU Justification: Impact: DNS lookups inside docker containers can fail if the host environment is set up to only use a local resolver. The built-in docker test of fanatic will always fail in that case. Fix: Add code to built-in tests which detect systemd-resolvd being in use and pass the IP address which systemd-resolv is using as forwarder with the --dns option to the docker run command. Testcase: - If the test host is using systemd-resolvd as its primary DNS server, there will be the following message in the test log: local docker test: *** Using DNS override *** --dns= - Otherwise no message is printed. - For all cases docker ADT test should (continue to) pass Risk of regression: minimal, only testing affected which is run as ADT tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1732717/+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 1728908] Re: a300_[pfp|pm4].fw clashes when installing linux-firmware
Good in artful too. ubuntu@dragon410c:~$ dpkg -l | grep firmware ii linux-firmware 1.169.1 all Firmware for Linux kernel drivers ii linux-firmware-snapdragon 1.3-0ubuntu3~17.10.1 arm64 DragonBoard410c wifi firmware ubuntu@dragon410c:~$ apt-cache policy linux-firmware linux-firmware: Installed: 1.169.1 Candidate: 1.169.1 Version table: *** 1.169.1 500 500 http://ports.ubuntu.com artful-proposed/main arm64 Packages 100 /var/lib/dpkg/status 1.169 500 500 http://ports.ubuntu.com artful/main arm64 Packages ubuntu@dragon410c:~$ apt-cache policy linux-firmware-snapdragon linux-firmware-snapdragon: Installed: 1.3-0ubuntu3~17.10.1 Candidate: 1.3-0ubuntu3~17.10.1 Version table: *** 1.3-0ubuntu3~17.10.1 990 500 http://ports.ubuntu.com artful-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1728908 Title: a300_[pfp|pm4].fw clashes when installing linux-firmware Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware-snapdragon package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware-snapdragon source package in Xenial: Fix Committed Status in linux-firmware source package in Artful: Fix Committed Status in linux-firmware-snapdragon source package in Artful: Fix Committed Bug description: [Impact] Starting with linux-firmware 1.157.13, two files (a300_[pfp|pm4].fw) that were previously part of linux-firmware-snapdragon 1.2-0ubuntu1, are now integrated in the linux-firmware package itself, resulting in a file clash when these two packages are installed together: .. Selecting previously unselected package linux-firmware-snapdragon. Preparing to unpack .../linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb ... Unpacking linux-firmware-snapdragon (1.2-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb (--unpack): trying to overwrite '/lib/firmware/a300_pm4.fw', which is also in package linux-firmware 1.157.13 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Selecting previously unselected package linux-image-snapdragon. Preparing to unpack .../linux-image-snapdragon_4.4.0.1077.69_arm64.deb ... Unpacking linux-image-snapdragon (4.4.0.1077.69) ... Errors were encountered while processing: /var/cache/apt/archives/linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) make: *** [all] Error 100 ... This problem is particularly evident when a new snapdragon kernel snap is assembled, since the the building process breaks (and no kernel snap is generated): https://launchpadlibrarian.net/343287945 /buildlog_snap_ubuntu_xenial_arm64_snapdragon-kernel- test_BUILDING.txt.gz To fix the problem i removed the two files from linux-firmware- snapdragon 1.3-0ubuntu1 and pushed this new version to my ppa: https://launchpad.net/~p-pisati/+archive/ubuntu/embedded/+packages linux-firmware-snapdragon - 1.3-0ubuntu1 [Test case] Try to build a snapdragon kernel snap using Xenial/updates - with linux-firmware 1.157.13 and linux-firmware-snapdragon 1.2-0ubuntu1 it won't complete, while with linux-firmware-snapdragon 1.3-0ubuntu1 it will successfully complete. [Regression risk] The files imported in linux-firmware are the same files we shipped in linux-firmware-snapdragon: $ md5sum /lib/firmware/qcom/a300_pfp.fw 25aa81977303142bdc4490efad16138b /lib/firmware/qcom/a300_pfp.fw $ md5sum /lib/firmware/qcom/a300_pm4.fw d657cacd951742d9bbbe74224347cffe /lib/firmware/qcom/a300_pm4.fw $ md5sum dragon410c-firmware.orig/lib/a300_pfp.fw 25aa81977303142bdc4490efad16138b dragon410c-firmware.orig/lib/a300_pfp.fw $ md5sum dragon410c-firmware.orig/lib/a300_pm4.fw d657cacd951742d9bbbe74224347cffe dragon410c-firmware.orig/lib/a300_pm4.fw so the regression risk is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1728908/+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 1734542] Re: Acpi support not set: throttling not working
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** 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/1734542 Title: Acpi support not set: throttling not working Status in linux package in Ubuntu: Confirmed Bug description: I am seeing a throttling difference about 4.13.13 kernel: - the Artful kernel 4.13.0-18-generic, based on 4.13.13, does not manage the cpu frequency (neither all the previous ubuntu kernels) CPU type : Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz Min/Max frequency : 800/3200 MHz acpi -V No support for device type: power_supply No support for device type: power_supply Cooling 0: Processor 0 of 3 Cooling 1: Processor 0 of 3 Cooling 2: LCD 0 of 100 Cooling 3: pch_skylake no state information available Cooling 4: Processor 0 of 3 Cooling 5: Processor 0 of 3 Cooling 6: intel_powerclamp no state information available Cooling 7: x86_pkg_temp no state information available - The same pc also have a bionic partition, where the 4.13.13 vanilla kernel perfectly manage the cpu dynamic frequency, so it is not related to the uefi settings in that case. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-18-generic 4.13.0-18.21 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: oem1438 F...m pulseaudio /dev/snd/controlC0: oem1438 F pulseaudio CurrentDesktop: GNOME Date: Sun Nov 26 16:15:43 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=06a0e343-7443-402b-a607-1fe53f3c1ac3 IwConfig: lono wireless extensions. enp2s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic root=UUID=8a00317c-669e-447c-bc40-1e06010b49ca ro RelatedPackageVersions: linux-restricted-modules-4.13.0-18-generic N/A linux-backports-modules-4.13.0-18-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.00 dmi.board.name: B150M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734542/+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 1734744] Re: OOM killer with kernel 4.4.0-92
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.102 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: performing-bisect ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Xenial) 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/1734744 Title: OOM killer with kernel 4.4.0-92 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: When putting pressure on a Linux Node in Azure we see OOM killers (similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 but not this is a different kernel) Reverting the kernel to 4.4.0-57 fixes the problem. dmesg and kernel.log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734744/+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 1729119] Re: NVMe timeout is too short
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed- trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1729119 Title: NVMe timeout is too short Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux-aws source package in Trusty: New Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Committed Status in linux-aws source package in Zesty: Invalid Status in linux source package in Artful: Fix Committed Status in linux-aws source package in Artful: Invalid Bug description: [SRU Justification] [Impact] Some NVMe operations time out too quickly. The module parameters allow the timeouts to be extended, but only up to 255s, as the counters are bytes. [Fix] The underlying parameters are unsigned ints, so make the module parameters unsigned ints too, by picking patch http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.html (Trusty specific) This also requires picking the patch that converts the constant into a parameter, which is a clean cherry-pick. [Regression Potential] (X/Z/A) Very limited: only types of module parameters are changing, the patch is easily reviewable. (Trusty specific) Limited: a module parameter is added and its type is changed. The patches are easily reviewable. [Testing] (Trusty only) Boot tested on a c5.large instance on AWS which uses NVMe to boot. Verified that the system still boots with the patches, and that a timeout of 123456s is permitted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729119/+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 1734686] Re: BUG: unable to handle kernel paging request at ffffdf3cd60001a0
** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734686 Title: BUG: unable to handle kernel paging request at df3cd60001a0 Status in linux package in Ubuntu: Triaged Bug description: I can consistently reproduce this with the Ubuntu 17.10 kernel. It never happens with a mainline 4.13.11 kernel built from source. To reproduce: 1. clone https://github.com/nodejs/node (currently at commit 4ca4db0d4c) 2. ./configure && make -j8 3. ./out/Release/cctest cctest is sometimes killed, sometimes locks up the computer. When the computer is still usable, the following message is logged: [36488.886799] BUG: unable to handle kernel paging request at df3cd60001a0 [36488.886824] IP: kfree+0x53/0x190 [36488.886831] PGD 0 [36488.886831] P4D 0 [36488.886844] Oops: [#2] PREEMPT SMP [36488.886851] Modules linked in: xt_tcpudp iptable_filter cfg80211 binfmt_misc snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_realtek snd_hda_codec_generic intel_cstate r8712u(C) intel_rapl_perf snd_seq_midi snd_seq_midi_event input_leds snd_hda_intel snd_rawmidi snd_hda_codec snd_hda_core snd_seq snd_hwdep snd_pcm snd_seq_device snd_timer snd ie31200_edac soundcore mei_me shpchp mei lpc_ich mac_hid cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 nouveau mxm_wmi wmi i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect hid_generic sysimgblt uas ahci fb_sys_fops usbhid usb_storage r8169 drm libahci hid mii video [36488.886940] CPU: 6 PID: 21882 Comm: cctest Tainted: G D C 4.13.0-17-lowlatency #20-Ubuntu [36488.886947] Hardware name: MEDION H77H2-EM/H77H2-EM, BIOS EM0411-M8 04/11/2012 [36488.886951] task: 8ebd7c18a640 task.stack: a003ce10c000 [36488.886957] RIP: 0010:kfree+0x53/0x190 [36488.886961] RSP: 0018:a003ce10fd30 EFLAGS: 00010282 [36488.886965] RAX: RBX: 6fa8 RCX: 0002 [36488.886970] RDX: 314521002bc0 RSI: 00010080 RDI: 7145 [36488.888247] RBP: a003ce10fd48 R08: 0001f640 R09: a27c7979 [36488.890131] R10: df3cd6000180 R11: 0100 R12: 8ebe84406900 [36488.892024] R13: a23aa5ee R14: R15: 8ebe8c611820 [36488.901718] FS: 7f7666764b80() GS:8ebe9ed8() knlGS: [36488.906872] CS: 0010 DS: ES: CR0: 80050033 [36488.908816] CR2: df3cd60001a0 CR3: 0002fc3c5000 CR4: 001406e0 [36488.910711] Call Trace: [36488.912512] security_sk_free+0x3e/0x50 [36488.914232] __sk_destruct+0x108/0x190 [36488.915872] sk_destruct+0x20/0x30 [36488.917483] __sk_free+0x82/0xa0 [36488.919064] sk_free+0x19/0x20 [36488.920626] tcp_close+0x230/0x3f0 [36488.922183] inet_release+0x3c/0x60 [36488.923714] inet6_release+0x30/0x40 [36488.925242] sock_release+0x1f/0x80 [36488.926785] sock_close+0x12/0x20 [36488.932837] __fput+0xe1/0x220 [36488.937778] fput+0xe/0x10 [36488.942441] task_work_run+0x76/0x90 [36488.943956] exit_to_usermode_loop+0xc4/0xd0 [36488.945467] syscall_return_slowpath+0x59/0x60 [36488.946973] entry_SYSCALL_64_fastpath+0xa7/0xa9 [36488.948468] RIP: 0033:0x7f7666376df0 [36488.949967] RSP: 002b:7ffe98391250 EFLAGS: 0293 ORIG_RAX: 0003 [36488.951522] RAX: RBX: 000c RCX: 7f7666376df0 [36488.953073] RDX: RSI: 0002 RDI: 000c [36488.954639] RBP: 000c R08: 55a301618920 R09: 000a [36488.956208] R10: 7ffe9839126c R11: 0293 R12: 0011 [36488.957774] R13: 0020 R14: 0001 R15: 7ffe983916ec [36488.959354] Code: 00 80 49 01 da 0f 82 47 01 00 00 48 c7 c7 00 00 00 80 48 2b 3d ef 98 c1 00 49 01 fa 49 c1 ea 0c 49 c1 e2 06 4c 03 15 cd 98 c1 00 <49> 8b 42 20 48 8d 50 ff a8 01 4c 0f 45 d2 49 8b 52 20 48 8d 42 [36488.961040] RIP: kfree+0x53/0x190 RSP: a003ce10fd30 [36488.962714] CR2: df3cd60001a0 [36488.964377] ---[ end trace 46732cc399d66b31 ]--- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-17-lowlatency 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-lowlatency 4.13.8 Uname: Linux 4.13.0-17-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnoordhuis 1664 F pulseaudio /dev/snd/controlC0: bnoordhuis 1664 F pulseaudio Curr
[Kernel-packages] [Bug 1734757] Re: Add installer support for new Broadcom network drivers.
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key -- 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/1734757 Title: Add installer support for new Broadcom network drivers. Status in linux package in Ubuntu: Confirmed Bug description: Please add bnxt_en_bpo to nic-modules to Ubuntu kernel 4.4. bnxt_en_pbo has been available since SAUCE commits with 4.4.0-94. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734757/+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 1726299] Re: Apple Thunderbolt 2 to FireWire adapter not working
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ ** Changed in: linux (Ubuntu) Status: New => Incomplete ** 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/1726299 Title: Apple Thunderbolt 2 to FireWire adapter not working Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt 2 adapter. Ubuntu seems not to recognize the Firewire adapter. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty uname -r 4.10.0-19-generic sudo lshw -short H/W-Pfad Gerät Klasse Beschreibung === system Z170N-Gaming 5 (Default string) /0 busZ170N-Gaming 5 /0/0memory 64KiB BIOS /0/3d memory 16GiB Systemspeicher /0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/1 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/3 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/43 memory 128KiB L1 Cache /0/44 memory 512KiB L2 Cache /0/45 memory 3MiB L3 Cache /0/46 processor Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz /0/100 bridge Skylake Host Bridge/DRAM Registers /0/100/1bridge Skylake PCIe Controller (x16) /0/100/1/0 displayOland GL [FirePro W2100] /0/100/1/0.1multimedia Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] /0/100/14 busSunrise Point-H USB 3.0 xHCI Controller /0/100/14/0 usb1 busxHCI Host Controller /0/100/14/0/6 input USB Gaming Keyboard /0/100/14/0/d communication Bluetooth-Schnittstelle /0/100/14/1 usb2 busxHCI Host Controller /0/100/14/1/5scsi6 storageStorage Media /0/100/14/1/5/0.0.0 /dev/sdb disk 15GB Storage Media /0/100/14/1/5/0.0.0/0/dev/sdb disk 15GB /0/100/14/1/5/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT Laufwerk /0/100/16 communication Sunrise Point-H CSME HECI #1 /0/100/17 storageSunrise Point-H SATA controller [AHCI mode] /0/100/1b bridge Sunrise Point-H PCI Root Port #17 /0/100/1b.2 bridge Sunrise Point-H PCI Root Port #19 /0/100/1b.3 bridge Sunrise Point-H PCI Root Port #20 /0/100/1c bridge Sunrise Point-H PCI Express Root Port #1 /0/100/1c/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/1 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2/0 busDSL6540 USB 3.1 Controller [Alpine Ridge] /0/100/1c/0/2/0/0usb3 busxHCI Host Controller /0/100/1c/0/2/0/0/1 genericThunderbolt 3 (USB-C) to Thunderbolt 2 Adapter /0/100/1c/0/2/0/0/2 input USB Optical Mouse /0/100/1c/0/2/0/1usb4 busxHCI Host Controller /0/100/1c/0/4 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /
[Kernel-packages] [Bug 1735024] Re: Cannot boot without acpi=off
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** 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/1735024 Title: Cannot boot without acpi=off Status in linux package in Ubuntu: Incomplete Bug description: Bought a new laptop but after reinstalling cannot boot without acpi=off ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-generic 4.13.0.17.18 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arseniuss954 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 29 02:25:57 2017 InstallationDate: Installed on 2017-11-26 (2 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-51 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=7105a1eb-3d1e-4b00-9668-da7cce948f4e ro acpi=off RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_KLS dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnNitroAN515-51:pvrV1.05:rvnKBL:rnFreed_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-51 dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735024/+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 1734805] Re: Asus ROG GL553VE Shutdown/Restart freeze in kernel 4.14
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ ** 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/1734805 Title: Asus ROG GL553VE Shutdown/Restart freeze in kernel 4.14 Status in linux package in Ubuntu: Incomplete Bug description: I'm usung Asus ROG GL553VE. If I use an updated kernel I can't shutdown/restart, it just freezes. First I updated my linux kernel into v4.10 and experienced the issue. Then again I updated my kernel into v4.14 and this issue still exists. However If I go back to kernel v4.4 this issue seems to be resolved. So seems like it's a kernel issue(v4.14). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734805/+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 1734761] Re: enable new configure options for 4.15
** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Wishlist Status: Triaged ** Tags added: bionic kernel-da-key -- 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/1734761 Title: enable new configure options for 4.15 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Hi, When 4.15 is brought into Ubuntu bionic I wanted to make sure that a few configure options were selected to compile as module (as they won't come by default): 1) Intel WMI thunderbolt driver 2) Dell SMBIOS WMI driver 3) Dell SMBIOS SMM driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734761/+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 1735099] Re: Realtek Card Reader not working (kernel driver)
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ -- 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/1735099 Title: Realtek Card Reader not working (kernel driver) Status in linux package in Ubuntu: Incomplete Bug description: This is the situation if I use the normal 4.13 kernel driver [ 1899.245301] mmc0: cannot verify signal voltage switch [ 1899.377540] mmc0: new ultra high speed SDR104 SDXC card at address e624 [ 1899.401829] mmcblk0: mmc0:e624 AGGCE 59.5 GiB [ 1899.404700] mmcblk0: p1 [ 1899.620084] mmcblk0: error -110 sending status command, retrying [ 1899.620231] mmcblk0: error -22 sending status command, retrying [ 1899.620419] mmcblk0: error -22 sending status command, aborting [ 1899.905535] mmc0: cannot verify signal voltage switch [ 1900.136253] mmcblk0: error -22 sending status command, retrying [ 1900.136396] mmcblk0: error -22 sending status command, retrying [ 1900.240070] mmcblk0: error -110 sending status command, aborting [ 1900.240084] print_req_error: I/O error, dev mmcblk0, sector 8 but it works perfectly if I use the patched driver on kernel 4.4-4.7 this one https://github.com/Zibri/Realtek-rts5229-for-4.4-kernel the problem is that I can't compile it on 4.13 and anyway this affects a lot of systems using 5229/5227 many laptops use this. any solution?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735099/+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 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
I was not able to achieve C7 (pc7) with your old kernel either (I just tried a few days ago). The new kernel does not achieve C7 (pc7) either. It gets down to C3 at best ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+attachment/5016209/+files/dmesg.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/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+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 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen
** Changed in: linux
Status: Incomplete => Confirmed
** Changed in: linux
Importance: Medium => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1724639
Title:
Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in openSUSE:
Unknown
Bug description:
Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
the install went smoothly. When the system is rebooted, however,
switching to graphics mode results in the below described screen
corruption:-
Left Hand Side 80% of screen black with a blue of white pixels and some blue
lines at the top
Right Hand Side 20% of screen OK.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.13.0-16-generic.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.20.7-0ubuntu3
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ian 918 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,144dca00,0011'
Controls : 25
Simple ctrls : 12
CurrentDesktop: LXDE
Date: Wed Oct 18 18:30:15 2017
HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
InstallationDate: Installed on 2017-10-18 (0 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.13.0-16-generic N/A
linux-backports-modules-4.13.0-16-generic N/A
linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 07CA.M002.20090414.KTW
dmi.board.name: NC10
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: NC10
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1724639/+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 1734733] Re: linux: 3.13.0-136.185 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the 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 backports: 1734734 derivatives: - kernel-stable-phase-changed:Tuesday, 28. November 2017 16:01 UTC - kernel-stable-phase:Uploaded - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Wednesday, 29. November 2017 15:31 UTC ** Description changed: This bug is for tracking the 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 backports: 1734734 derivatives: -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Wednesday, 29. November 2017 15:31 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: 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/1734733 Title: linux: 3.13.0-136.185 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 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 backports: 1734734 derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1734733/+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 1481347] Re: Power8 Nest PMU Instrumentation support
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- 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/1481347 Title: Power8 Nest PMU Instrumentation support Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Fix Committed Bug description: This is a bug for Canonical awareness that we want to have the following patches included in 15.10. They are still under development/review: https://patchwork.ozlabs.org/patch/482968/ https://patchwork.ozlabs.org/patch/482969/ https://patchwork.ozlabs.org/patch/482970/ https://patchwork.ozlabs.org/patch/482971/ https://patchwork.ozlabs.org/patch/482972/ https://patchwork.ozlabs.org/patch/482973/ https://patchwork.ozlabs.org/patch/482974/ Patches under review. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481347/+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 1710019] Re: support GICv3 ITS save/restore & migration
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- 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/1710019 Title: support GICv3 ITS save/restore & migration Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive ocata series: Fix Committed Status in Ubuntu Cloud Archive pike series: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in qemu source package in Xenial: Won't Fix Status in linux source package in Zesty: In Progress Status in qemu source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Committed Status in qemu source package in Artful: Fix Released Bug description: [Impact] Virtual machines on GICv3-based ARM systems cannot be saved/restored or migrated. This feature was added in QEMU 2.10. [Test Case] ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav Domain 7936-0 saved to 7936-0.sav ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav error: Failed to restore domain from 7396-0.sav error: operation failed: job: unexpectedly failed ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log 2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by non-migratable device 'arm_gicv3_its' 2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: Invalid argument 2017-08-10 21:26:38.217+: shutting down, reason=failed [Regression Risk] The kernel changes are restricted to ARM, minimizing the regression risk on other architectures. Other than one minor offset adjustment, all patches are clean cherry-picks from upstream. Tested on Cavium ThunderX and Qualcomm Centriq. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1710019/+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 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- 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/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in bluez source package in Xenial: New Status in linux source package in Xenial: Fix Committed Status in bluez source package in Zesty: New Status in linux source package in Zesty: Fix Committed Status in bluez source package in Artful: New Status in linux source package in Artful: Fix Committed Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+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
