[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Lenovo B50-80 is also affected by this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: 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. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 The bug also affects Acer Aspire E5-771G. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- 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/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 1638862] Re: [Dell Latitude E5460] bluetooth is not supported on 16.04.1.
You can send a patch to the git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git tree. -- 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/1638862 Title: [Dell Latitude E5460] bluetooth is not supported on 16.04.1. Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Dell Latitude E5460 (CID 201507-18776) Ubuntu 16.04.1 (updated to kernel 4.4.0-45-generic) [Steps to reproduce] 1. Install Ubuntu 16.04.1 via Live USB. 2. On desktop, open the terminal to issue the command to check the status[1]. 3. Open Bluetooth setup window. 4. Update the system and do the same steps from 1~3. [Expected Result] Bluetooth setup window is ready for you to setup bluetooth devices. [Actual Result] The bluetooth setup window shows "Bluetooth is disabled". [1] ubuntu@201507-18776:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 2: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1523 F pulseaudio CurrentDesktop: Unity Date: Thu Nov 3 17:56:50 2016 HibernationDevice: RESUME=UUID=e104534d-b5db-4ef1-9955-2b8178924bcb InstallationDate: Installed on 2016-11-02 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=a02ea97e-ff66-470f-aa17-74a60670faa1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.6 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.6:bd01/10/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638862/+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 1735941] Re: no stereo on reconnect or by default for Sony 1000xm2 headphones
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1735941 Title: no stereo on reconnect or by default for Sony 1000xm2 headphones Status in bluez package in Ubuntu: Confirmed Bug description: Expectation: Bluetooth headphones attach with stereo sound on every connect. Issue: only stereo after manual switch of settings on first pair. Reconnect only has mono connection. Ubuntu 17.10 on a System76 Serval WS. Mono audio with the Sony 1000XM2 bluetooth headphones is the default on first pairing and is the only option after turning off the bluetooth or headphones. On a new pairing the default is HSP with mono audio. Manually I have to change to A2DP in the sound settings and I am able to have stereo sound. Disabling bluetooth or turning off the headphones followed by a connection will result in mono audio in HSP and switching to A2DP will also be mono. Temporary Workaround: remove the headphones from the paired devices and pair again as a new device to get access to stereo sound again. This procedure has to be repeated on every reconnect. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 2 14:54:12 2017 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: System76, Inc. Serval WS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=90a6c4ca-5b2a-461e-8792-18cd7e54a2fb ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA:bd03/08/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:85:00:36:47:F9 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN INQUIRY RX bytes:18865088 acl:249 sco:362504 events:45487 errors:0 TX bytes:53430737 acl:40447 sco:362442 commands:2995 errors:9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1735941/+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 1738534] Re: Processor turbo dsiabled/throttled after suspend
As a workaround, I created a post-resume script that runs the above
commands at /lib/systemd/system-sleep/throttle-workaround. It works in
the first scenario, but not if the full power cycle was done on battery
power.
#!/bin/sh
# Action script to prevent CPU throttling after resume.
set -e
PATH=/sbin:/usr/sbin:/bin:/usr/bin
case "${1}" in
post)
x86_energy_perf_policy --turbo-enable 1
cpufreq-set -r --max=3.0GHz
;;
esac
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738534
Title:
Processor turbo dsiabled/throttled after suspend
Status in linux package in Ubuntu:
Confirmed
Bug description:
After suspending/resuming my laptop on battery power, I noticed choppy
video playback. I've narrowed it down to the CPU being locked to
lower frequencies after suspend/resume (only on battery). Plugging
the laptop back in does not restore the normal performance, nor does
suspend/resume after plugging it back in. The performance doesn't
drop until after the suspend/resume, I'm not sure if it is _supposed_
to throttle when on battery, but either way the behaviour is wrong.
Doing a full shutdown and restart restores the performance to normal.
Prior to a suspend/resume cycle, cpupower reports:
$ sudo cpupower frequency-info
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 800 MHz - 3.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 3.00 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.26 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
2800 MHz max turbo 4 active cores
2800 MHz max turbo 3 active cores
2800 MHz max turbo 2 active cores
3000 MHz max turbo 1 active cores
Afterwards, the frequency is clamped (cpufreq-set -r --max=3.0GHz has
no effect) and turbo is disabled:
$ sudo cpupower frequency-info
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 800 MHz - 3.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 1.80 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 950 MHz (asserted by call to kernel)
boost state support:
Supported: no
Active: no
2800 MHz max turbo 4 active cores
2800 MHz max turbo 3 active cores
2800 MHz max turbo 2 active cores
3000 MHz max turbo 1 active cores
Trying to re-enable turbo mode by setting the no_turbo intel_pstate
/sys/ entry back to 0 is rejected:
$ echo 0 | sudo tee /sys/devices/system/cpu/intel_pstate/no_turbo
0
tee: /sys/devices/system/cpu/intel_pstate/no_turbo: Operation not permitted
However, these two commands *do* work around the problem, forcing
turbo mode back on and then restoring the normal frequency range:
sudo x86_energy_perf_policy --turbo-enable 1
sudo cpufreq-set -r --min=0.8GHz --max=3.0GHz
I also see this error in dmesg after some resumes (but the above
problem sometimes happens without this error message):
Dec 16 11:36:25 shauns-laptop kernel: intel_pstate: Turbo disabled by
BIOS or unavailable on processor
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-19-generic 4.13.0-19.22
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: shaun 1194 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 16 11:18:12 2017
InstallationDate: Installed on 2017-12-14 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
Bus 001 Device 004: ID 2232:1024 Silicon Motion
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D
ProcFB
[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
My Acer e5-471 is affected here. After installing ubuntu 17.10 my bios won't save any changes except the date and time. It won't boot from either HDD or USB. I still can boot from live cd though. -- You 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 Status in linux source package in Artful: 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. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 The bug also affects Acer Aspire E5-771G. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- 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/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 405525] Fw: grateful
I'm extremely grateful to you personally for all you will get done , please read my message to you here http://www.marcnehme.com/marcnehme/blog/wp- content/aepgx.php?UE80MDU1MjVAYlVnUy5sYVVuQ2hwYWQuTmV0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/405525 Title: [Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)] suspend/resume failure Status in linux package in Ubuntu: Expired Bug description: Under 8.10 suspend worked pretty much flawlessly. Installed Karmic as 9.04 my sound card would not work for some reason. may end up going back to 8.10 as My vid card is not supported anymore by ATI after that version. but that is not here nor there. tried to wake up my laptop like normal. system stayed at black screen. backlight sis not come on. I know this is alpha and I am not mad but I am reporting this so the developers know it. I have no idea what caused the problem but hopefully the bug catcher included stuff to help trace it. If not please delete this bug as I have no other Idea what could have caused it. Thanks for making a great product. I have used Ubuntu since 6.06 and have watched it get better and better every release (with exception to 9.04) ;) thanks again guys. ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 Date: Mon Jul 27 17:10:03 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3a408910-86e2-46ec-a784-90545d8f3f2c InterpreterPath: /usr/bin/python2.6 MachineType: Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA) Package: linux-image-2.6.31-4-generic 2.6.31-4.22 ProcCmdLine: root=UUID=fe6d390e-5c59-40db-98f8-09dbdbd0b864 ro vga=792 ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-4.22-generic RelatedPackageVersions: linux-backports-modules-2.6.31-4-generic N/A SourcePackage: linux Tags: resume suspend Title: [Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)] suspend/resume failure Uname: Linux 2.6.31-4-generic i686 UserGroups: dmi.bios.date: 02/24/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.name: 3096 dmi.board.vendor: Quanta dmi.board.version: 47.0E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd02/24/2006:svnHewlett-Packard:pnHPPavilionze2000(EC205UA#ABA):pvrRev1:rvnQuanta:rn3096:rvr47.0E:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion ze2000 (EC205UA#ABA) dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/405525/+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 1738632] [NEW] linux 4.14.0-12.14 ADT test failure with linux 4.14.0-12.14
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/amd64/l/linux/20171217_033543_755bb@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/arm64/l/linux/20171217_025131_755bb@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/i386/l/linux/20171217_033325_755bb@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/ppc64el/l/linux/20171217_034439_755bb@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/s390x/l/linux/20171217_032308_755bb@/log.gz ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) 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/1738632 Title: linux 4.14.0-12.14 ADT test failure with linux 4.14.0-12.14 Status in linux package in Ubuntu: In Progress Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/amd64/l/linux/20171217_033543_755bb@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/arm64/l/linux/20171217_025131_755bb@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/i386/l/linux/20171217_033325_755bb@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/ppc64el/l/linux/20171217_034439_755bb@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/s390x/l/linux/20171217_032308_755bb@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738632/+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 1738632] Re: linux 4.14.0-12.14 ADT test failure with linux 4.14.0-12.14
== FAIL: test_02_stack_limit (__main__.KernelASLRCollisionsTest) Process stack is normal size -- Traceback (most recent call last): File "./test-kernel-aslr-collisions.py", line 69, in test_02_stack_limit self.assertEqual(-1, stack[1]) AssertionError: -1 != 8388608 == FAIL: test_stack_collision (__main__.KernelASLRCollisionsTest) Check if stack crashes into mmap in 100,000 execs (amd64 only?) (LP: #504164) -- Traceback (most recent call last): File "./test-kernel-aslr-collisions.py", line 88, in test_stack_collision self.assertShellExitEquals(0, ['./aslr-crash']) File "/tmp/autopkgtest.PPgnXF/build.Dmb/src/autotest/client/tmp/ubuntu_qrt_kernel_aslr_collisions/src/qa-regression-testing/scripts/testlib.py", line 1134, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: Got exit code 1, expected 0 Command: './aslr-crash' Output: Failed to set stack rlimit:: Invalid argument -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738632 Title: linux 4.14.0-12.14 ADT test failure with linux 4.14.0-12.14 Status in linux package in Ubuntu: In Progress Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/amd64/l/linux/20171217_033543_755bb@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/arm64/l/linux/20171217_025131_755bb@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/i386/l/linux/20171217_033325_755bb@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/ppc64el/l/linux/20171217_034439_755bb@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/s390x/l/linux/20171217_032308_755bb@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738632/+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 1738632] Re: linux 4.14.0-12.14 ADT test failure with linux 4.14.0-12.14
This looks to be due to a change in behavior regarding the hard RLIMIT_STACK value on setuid. Previously the hard limit of RLIM_INFINITY would have been preserved across the setuid exec, now it has been limited so that values greater than 8MB (including RLIM_INFINITY) are clamped down to that value. This is no doubt due to 04e35f4495dd "exec: avoid RLIMIT_STACK races with prlimit()." The test expects the hard limit to always be RLIM_INIFINITY. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738632 Title: linux 4.14.0-12.14 ADT test failure with linux 4.14.0-12.14 Status in linux package in Ubuntu: In Progress Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/amd64/l/linux/20171217_033543_755bb@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/arm64/l/linux/20171217_025131_755bb@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/i386/l/linux/20171217_033325_755bb@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/ppc64el/l/linux/20171217_034439_755bb@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-unstable/bionic/s390x/l/linux/20171217_032308_755bb@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738632/+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
It happened again right now, on another G40-30 Lenovo laptop, running Windows 10 and Ubuntu 16.04, both in legacy mode. As soon as we inserted an Ubuntu 17.10 live USB, the boot setup had the USB listed twice. One in legacy and another as EFI (I repeat, the OSs on that laptop are installed in legacy mode). By selecting to boot the live USB which was listed as EFI, it booted fine. We did not install the new OS, but after shutting down the laptop, the BIOS refused to save any changes and also refused to read that same USB flash drive in boot options. There has to be something very seriously wrong here. -- You 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 Status in linux source package in Artful: 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. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 The bug also affects Acer Aspire E5-771G. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- 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/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 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu
The patch doesn't work on a GT72 2QE Dominator Pro. It compiled and installed succesfully with the patch but the system keeps reporting that no adapter is found. It also keeps saying that the ar3k/AthrBT_0x0200.dfu patch file could not be found. -- 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/1542743 Title: Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu Status in bluez package in Ubuntu: Confirmed Bug description: Since some Versions of Linux Kernel and Ubuntu Releases this problem exists. I am now running ubuntu 16.04 prerelease and still have the same problem. Bluetooth does not work with the atheros device on msi gt 72 2qd notebook. WORKAROUND FOR [0CF3:3004] DEVICE ONLY with kernel 4.4: sudo apt install dkms wget https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb sudo dpkg -i btusb-lp1542743-dkms_0.1_all.deb FOR KERNEL 4.8 A WORKAROUND DKMS DEB IS https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files /btusb-lp1542743-dkms_0.2~4.8_all.deb dmesg | grep Bluetooth: [2.655360] Bluetooth: Core ver 2.21 [2.655373] Bluetooth: HCI device and connection manager initialized [2.655377] Bluetooth: HCI socket layer initialized [2.655379] Bluetooth: L2CAP socket layer initialized [2.655385] Bluetooth: SCO socket layer initialized [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.612794] Bluetooth: BNEP filters: protocol multicast [6.612798] Bluetooth: BNEP socket layer initialized [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu [9.016882] Bluetooth: Loading patch file failed hwinfo | grep Bluetooth: <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 <6>[6.612794] Bluetooth: BNEP filters: protocol multicast <6>[6.612798] Bluetooth: BNEP socket layer initialized <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu <3>[9.016882] Bluetooth: Loading patch file failed 60: USB 00.0: 11500 Bluetooth Device Model: "Atheros AR3012 Bluetooth 4.0" Device: usb 0x3004 "AR3012 Bluetooth 4.0" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.36-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Sun Feb 7 00:38:04 2016 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2015-10-24 (105 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: bnep btusb bluetooth MachineType: Micro-Star International Co., Ltd. GT72 2QD ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago) dmi.bios.date: 12/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10I dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10I:bd12/19/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QD:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QD dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1542743/+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 1574196] Re: Card with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz networks with high channel number.
Is it possible that the driver doesn't support the DFS channels? (they must be yielded to prioritized users such as weather radar) https://www.wi-fi.org/knowledge-center/faq/what-is-dynamic-frequency-selection-dfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1574196 Title: Card with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz networks with high channel number. Status in bcmwl package in Ubuntu: Confirmed Bug description: The card Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) doesn't see 5Ghz networks with an high channel number, if you change the channel back to a lower one the network will be found again. In my case with channel 104 the network wasn't seen by the card, with channel 40 it works fine wireless-info script result: ## wireless info START ## Report from: 22 Apr 2016 19:23 CEST +0200 Booted last: 22 Apr 2016 18:51 CEST +0200 Script from: 27 Sep 2015 00:34 UTC + # release ### Distributor ID: Ubuntu Description: Ubuntu 14.04.4 LTS Release: 14.04 Codename: trusty # kernel Linux 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Parameters: ro, quiet, splash, vt.handoff=7 # desktop ### Ubuntu # lspci # 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7758] Kernel driver in use: r8169 04:00.0 Network controller [0280]: Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03) Subsystem: Broadcom Corporation Device [14e4:0619] Kernel driver in use: wl # lsusb # Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 004: ID 1532:0016 Razer USA, Ltd DeathAdder Mouse Bus 001 Device 003: ID 258a:0001 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # PCMCIA card info ## # rfkill 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no # lsmod # wl 6367819 0 mxm_wmi13021 1 nouveau wmi19177 2 mxm_wmi,nouveau cfg80211 496328 1 wl # interfaces auto lo iface lo inet loopback # ifconfig ## eth0 Link encap:Ethernet HWaddr UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) virbr0Link encap:Ethernet HWaddr inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan2 Link encap:Ethernet HWaddr inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:45040 errors:0 dropped:0 overruns:0 frame:7469 TX packets:33232 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:33581962 (33.5 MB) TX bytes:6334838 (6.3 MB) Interrupt:18 # iwconfig ## eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. wlan2 IEEE 802.11abg ESSID:"LamerTexWiFi" Mode:Managed Frequency:2.437 GHz Access Point: Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off # route # Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Discovered this problem yesterday, which led me to this bug-report: Middle-button clicking was dead and didn't work on a clean new xenial install, same mouse works fine on an upgraded PC. Testing with xev showed nothing on the new PC: Middle button clicks were not recognised. "xinput list" told the mouse was: "PixArt HP USB Optical Mouse id=1 [slave pointer (2)] Ran a few "xinput test " commands. (NOT only on the mouse's ID (15) but a another to initially, lower number, typo.) And alas: Middle button clicks were suddenly detected and worked like charm - for half an hour. Then it died again. I repeated the "xinput test" deal, now on several ID's, lastly the mouse. After this, the middle button clicks were once again detected. This time i rebooted the PC, power-pff/on. Wheel-clicking survived the reboot and still works, 36 hours later or so. I'm not a kernel person but as an old-time user I got a little back-flash to the days of kernel 2.0, when devices often had to be added and linked manually. A look in /dev revealed several recent changes, from the time of the xinput tests. Grep'ed around and found: me@pc:/dev$ ls -latr |grep "11:48" drwxr-xr-x 4 root root 520 Dec 16 11:48 input drwxr-xr-x 21 root root4200 Dec 16 11:48 . crw--- 1 root root247, 0 Dec 16 11:48 hidraw0 drwxr-xr-x 2 root root4140 Dec 16 11:48 char me@pc:/dev/input$ ls -latr |grep "11:48" drwxr-xr-x 21 root root4200 Dec 16 11:48 .. drwxr-xr-x 4 root root 520 Dec 16 11:48 . crw-rw 1 root input 13, 34 Dec 16 11:48 mouse2 crw-rw 1 root input 13, 80 Dec 16 11:48 event16 drwxr-xr-x 2 root root 220 Dec 16 11:48 by-path drwxr-xr-x 2 root root 100 Dec 16 11:48 by-id me@pc:/dev/input/by-path$ ls -latr |grep "11:48" drwxr-xr-x 4 root root 520 Dec 16 11:48 .. lrwxrwxrwx 1 root root 9 Dec 16 11:48 pci-:00:14.0-usb-0:1:1.0-mouse -> ../mouse2 lrwxrwxrwx 1 root root 10 Dec 16 11:48 pci-:00:14.0-usb-0:1:1.0-event-mouse -> ../event16 me@pc:/dev/input/by-id$ drwxr-xr-x 4 root root 520 Dec 16 11:48 .. lrwxrwxrwx 1 root root 9 Dec 16 11:48 usb-PixArt_HP_USB_Optical_Mouse-mouse -> ../mouse2 lrwxrwxrwx 1 root root 10 Dec 16 11:48 usb-PixArt_HP_USB_Optical_Mouse-event-mouse -> ../event16 drwxr-xr-x 2 root root 100 Dec 16 11:48 . me@pc:/dev/char$ lrwxrwxrwx 1 root root 18 Dec 16 11:48 189:8 -> ../bus/usb/001/009 lrwxrwxrwx 1 root root 10 Dec 16 11:48 247:0 -> ../hidraw0 lrwxrwxrwx 1 root root 15 Dec 16 11:48 13:34 -> ../input/mouse2 lrwxrwxrwx 1 root root 16 Dec 16 11:48 13:80 -> ../input/event16 Hoping the listings above can be of help in solving this annoyance. I agree "Importance" should be raised to major. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Cl
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Forgot a detail: The first initial "fix" i experienced was when unplugging the mouse and trying another USB port. Middle buttin clicking then worked for a few merryt minutes before it died iff again. Changing ports yet again had no effect. Some system information: Product Name: HP EliteBook 850 G3 $ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PS/2 Generic Mouseid=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=12 [slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ HP HD Camera id=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] ↳ HP Wireless hotkeys id=13 [slave keyboard (3)] ↳ HP WMI hotkeysid=14 [slave keyboard (3)] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: re
[Kernel-packages] [Bug 1738224] Re: Suspend broken after kernel upgrade
No, I did not. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738224 Title: Suspend broken after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: My machine (XPS 13 9360) won't go into suspend properly after upgrading from linux-image-4.13.0-17-generic to linux- image-4.13.0-19-generic. This affects both suspend through lid close and "systemctl suspend". Screen goes off, power led remains lit. Then after some time the screen comes back on, is stuck and lets me wait for a few before becoming responsive again. Booting back into 4.13.0-17 resolved the issue. --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeffrey1963 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5 InstallationDate: Installed on 2017-10-18 (56 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful wayland-session Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
> It happened again right now, on another G40-30 Lenovo laptop, running > Windows 10 and Ubuntu 16.04, both in legacy mode. As soon as we inserted > an Ubuntu 17.10 live USB, the boot setup had the USB listed twice. One > in legacy and another as EFI (I repeat, the OSs on that laptop are > installed in legacy mode). By selecting to boot the live USB which was > listed as EFI, it booted fine. We did not install the new OS, but after > shutting down the laptop, the BIOS refused to save any changes and also > refused to read that same USB flash drive in boot options. There has to > be something very seriously wrong here. Given the evidence of this to date, I would not suggest that anyone do further investigation on this problem with their own hardware that would require expensive professional recovery. A probable fix is in progress for the kernel package. -- You 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 Status in linux source package in Artful: 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. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 The bug also affects Acer Aspire E5-771G. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- 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/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 1735032] Re: rebase iproute2 to newer version
** Changed in: iproute2 (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1735032 Title: rebase iproute2 to newer version Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 package in Debian: Fix Released Bug description: Ubuntu's iproute2 version [1] is still many kernel versions behind. It's still on 4.9, whereas shipped kernel is on 4.13 in the meantime! iproute2 is developed alongside the kernel, so new kernel features will also get updates to iproute2 whenever they change related code. Meaning, these features cannot be used out of the box if the actual shipped iproute2 version here is not on par with the kernel version (the release tags have 1:1 mapping with kernel releases) [2]. Please consider updating iproute2 package, and please also consider updating it regularly along with officially shipped kernels in Ubuntu, so that all the added networking features can be used there without forcing users to do a manual compilation of iproute2. Thanks, Daniel [1] http://changelogs.ubuntu.com/changelogs/pool/main/i/iproute2/iproute2_4.9.0-1ubuntu2/changelog [2] https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/refs/tags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1735032/+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 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported
just found the latest firmware is already in xenial-proposed linux-firmware (1.157.15) xenial; urgency=medium * QCA6174A XR cannot find any WiFi AP (LP: #1728523) - ath10k: QCA6174 hw3.0: update board-2.bin - ath10k: QCA6174 hw3.0: update board-2.bin - ath10k: QCA6174 hw3.0: update board-2.bin * Intel 9260/9462/9560 firmware support (LP: #1734243) - iwlwifi: add firmware version 33 for new 9000 series - linux-firmware: Add firmware file for Intel Bluetooth 9560 - linux-firmware: Add firmware file for Intel Bluetooth 9260 * Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react (LP: #1729389) - linux-firmware: Update firmware patch for Intel Bluetooth,8260 - linux-firmware: Update firmware file for Intel Bluetooth 8265 - linux-firmware: Update firmware patch for Intel Bluetooth 8260 -- Seth Forshee Tue, 12 Dec 2017 08:26:17 -0600 On Sun, Dec 17, 2017 at 5:18 AM, Wren Turkal <1520...@bugs.launchpad.net> wrote: > The latest firmware is not included in the linux-firmware package on > artful. Is this intended? I see that it is only included in the latest > LTS and bionic. > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1520343 > > Title: > Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported > > Status in HWE Next: > New > Status in OEM Priority Project: > Triaged > Status in linux-firmware package in Ubuntu: > Confirmed > > Bug description: > --- > > STATUS 2016-03-17: > > == > WARNING: You need at least kernel 4.5.0 for the following new fix to work, > else refer to the old method described in post #22 > == > > The support for this card has now been merged to > https://github.com/kvalo/ath10k-firmware. The repository now contains > the required board.bin, board-2.bin and firmware-4.bin files for the > card to initialize and connect to a bgn-access point (5GHz (ac- > protocol) is still untested, feel free to modify this if you can > confirm it works). Here are the new commands to get you online: > > sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/ > > sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null > > sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin > https://github.com/kvalo/ath10k- > firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true > > sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin > https://github.com/kvalo/ath10k- > firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true > > sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin > https://github.com/kvalo/ath10k- > > firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true > > Reboot or reload the ath10k_pci module and you should be able to > connect! > > --- > > STATUS 2015-12-22: > > Currently there is a fix for this problem in post #22 (originally post > #19, but reposted due to command typos!) which seems to have fixed the > issue for many. This bug is unique to revision 32 of the card > [168c:003e], fixes for older revisions don't seem to work. > > There are a couple of issues regarding the fix for some people (not > all): > > 1. Wireless works, but network throughput stops some time after > connecting to access point > > 2. Bluetooth communications take a noticeable performance hit when > transferring something over WiFi > > --- > > Original description: > > I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an > Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card > doesn't work in it or 16.04. > The card has the device id 168c:003e as many other cards, for example the > Qualcomm Atheros Killer > (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a > newer revision number (32) and the suggested fixes work only partially and > the wireless is unusable. > > The computer has just been released this summer and is Intel Skylake > -based. > > I've tried the patch from bug 1383184, which has a fix for the card > revision 20: > Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch > files: > board.bin > firmware-4.bin > notice_ath10k_firmware-4.txt > > ath10k_pci succeeds in loading the firmware, but it seems that the > firmware is not working correctly: > > dmesg | grep ath > [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode > 0 reset_mode 0 > [5.678420] ath10k_pci :07:00.0: Direct firmware load for > ath10k/cal-pci-:07:00.0.bin failed with error -2 > [5.678773] ath10k_pci :07:00.0: Direct firmware load for > ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with e
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
well another lock up. I've now disabled C6 in the bios and added max_cstates=1 to the boot parameters -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions
[Kernel-packages] [Bug 1380046] Re: [AV200 - Xonar STX, playback] Loud pop when switching to headphones
Apparently this line gpio &= GPIO_ST_OUTPUT_ENABLE; Should be gpio |= GPIO_ST_OUTPUT_ENABLE; instead. Please ask the author to send the patch to upstream Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1380046 Title: [AV200 - Xonar STX, playback] Loud pop when switching to headphones Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When switching the port to either headphone ports from the speaker port there is a loud pop in the headphones. When I am playing music through the speakers at 100% volume and then switch, I can hear the music at a very loud volume through the headphones for a fraction of a second before dropping to the proper headphones volume which is much lower. Even if I mute the output before switching ports there is still a pop although not nearly as loud. I believe this is a driver issue (oxygen/virtuoso). The Essense STX uses a relay to switch between the speaker and headphones ports. I am guessing the the power for the speaker (line out) port is much higher than that used for the headphones port and the drivers need to mute the sound at a hardware level before switching to elmininate the pop. On Windows when switching to and from speaker and headphones port the output would be muted for almost a second as the port was switched so there was no pop. On Ubuntu there is no delay when switching ports. I have looked at the driver source code and there is an anti_pop_delay of 800 milliseconds used on the Xonar init method. I think this same delay should probably be added when switching to the headphone ports. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: michael 20842 F pulseaudio /dev/snd/controlC0: michael 20842 F pulseaudio /dev/snd/pcmC0D0p: michael 20842 F...m pulseaudio /dev/snd/controlC1: michael 20842 F pulseaudio CurrentDesktop: Unity Date: Sat Oct 11 22:50:15 2014 InstallationDate: Installed on 2014-10-07 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:STX successful Symptom_Card: HD Webcam C910 - USB Device 0x46d:0x821 Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [AV200 - Xonar STX, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/20/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2404 F pulseaudio /dev/snd/controlC2: michael2404 F pulseaudio /dev/snd/controlC1: michael2404 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=89201542-3d78-4588-9f0f-3725c7c22875 InstallationDate: Installed on 2014-10-07 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=fbc05121-3d98-42ce-8073-986171e4b73f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10
Please find the first -rc version kernel that does not work in [1]. [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738560 Title: touch pad stopped working after upgrade to artful 17.10 Status in linux package in Ubuntu: Confirmed Bug description: The touch pad worked fine on 16.10 and 17.04, but it stopped working after upgrade to artful 17.10. It doesn't appear with xinput list, and I cannot find any line in dmesg referring to the touchpad ... so I need help even to report the exact device id! Ubuntu 4.13.0-19.22-generic 4.13.13 --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pang 1303 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df InstallationDate: Installed on 2017-12-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Micro-Star International Co., Ltd. GP62M 7RD Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: G dmi.product.name: GP62M 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738560/+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 1738224] Re: Suspend broken after kernel upgrade
What's the value of "/sys/power/mem_sleep" on 4.13.0-19? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738224 Title: Suspend broken after kernel upgrade Status in linux package in Ubuntu: Confirmed Bug description: My machine (XPS 13 9360) won't go into suspend properly after upgrading from linux-image-4.13.0-17-generic to linux- image-4.13.0-19-generic. This affects both suspend through lid close and "systemctl suspend". Screen goes off, power led remains lit. Then after some time the screen comes back on, is stuck and lets me wait for a few before becoming responsive again. Booting back into 4.13.0-17 resolved the issue. --- ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeffrey1963 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5 InstallationDate: Installed on 2017-10-18 (56 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 Tags: artful wayland-session Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker input libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.1 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+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 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Do you get mid click event in `evtest`? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toby 11625 F pulseaudio /dev/snd/controlC0: toby 11625 F pulseaudio /dev/snd/pcmC1D0p: toby 11625 F...m pulseaudio /dev/snd/controlC1: toby 11625 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5e3a6d2e-05f8-4d01-b80c-a9f200e6 InstallationDate: Installed on 2014-04-24 (749 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: LENOVO 20AL00C6GE Package: linux (no
[Kernel-packages] [Bug 1737226] Re: Bluetooth module doesn't work properly
Maybe this? https://bugzilla.kernel.org/show_bug.cgi?id=197147 ** Bug watch added: Linux Kernel Bug Tracker #197147 https://bugzilla.kernel.org/show_bug.cgi?id=197147 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737226 Title: Bluetooth module doesn't work properly Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth on Thinkpad X1C (5th gen) in Ubuntu 4.13.0-17.20-generic 4.13.8 with Cinnamon DE - adapter can be seen - devices can be added - can connect to some devices (phone) - can't use the devices (transfer files, audio source) - can't connect to some devices (speakers) I'm able to initialize sending files to/from my phone, but the transfer fails. I'm able to pair notebook with SRS-X11 speakers, but connection effor fails after asking for PIN (it is for the speakers). Using blueman as a manager. Adapter works fine in windows. Let me know if any other logs/outputs are needed. 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 x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ondrej 1690 F...m pulseaudio /dev/snd/controlC0: ondrej 1690 F pulseaudio CurrentDesktop: X-Cinnamon Date: Fri Dec 8 19:19:33 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e328f760-1028-4ef6-8bc0-3012b0991133 InstallationDate: Installed on 2017-11-26 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HRCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=75af2706-1521-4e35-85da-1b69d233774e ro quiet splash vt.handoff=7 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.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET39W(1.24):bd09/27/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737226/+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
** 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. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 - The bug also affects Acer Aspire E5-771G. + The bug also affects Acer laptops: + Acer Aspire E5-771G + Acer Aspire E5-471 --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- 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 package in Ubuntu: Confirmed Status in linux source package in Artful: 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. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 The bug also affects Acer laptops: Acer Aspire E5-771G Acer Aspire E5-471 --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- 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 ProcKer
[Kernel-packages] [Bug 1626299] Re: ACPI Errors in dmesg, battery monitor shows empty
Do you use the same machine as the original bug? If not, please file a new 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/1626299 Title: ACPI Errors in dmesg, battery monitor shows empty Status in linux package in Ubuntu: Expired Bug description: I am using Xubuntu, and the power manager show an empty battery at all times, regardless of battery level. I essentially have no indicators of how much power my laptop has left. Once I run out of power, the laptop obviously shuts down causing data corruption. my dmesg shows: [ 10.587295] ACPI Error: No handler for Region [PMRG] (88015a0c0090) [GenericSerialBus] (20150930/evregion-163) [ 10.587303] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20150930/exfldio-297) [ 10.587309] ACPI Error: Method parse/execution failed [\_SB.TAMB._TMP] (Node 88015a0f7208), AE_NOT_EXIST (20150930/psparse-542) [ 10.587325] thermal thermal_zone0: failed to read out thermal zone (-5) [ 10.598876] ACPI Error: No handler for Region [PMRG] (88015a0c0090) [GenericSerialBus] (20150930/evregion-163) [ 10.598882] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20150930/exfldio-297) [ 10.598886] ACPI Error: Method parse/execution failed [\_SB.TEFN._TMP] (Node 88015a0f76e0), AE_NOT_EXIST (20150930/psparse-542) [ 10.598898] thermal thermal_zone1: failed to read out thermal zone (-5) [ 10.600460] ACPI Error: No handler for Region [PMRG] (88015a0c0090) [GenericSerialBus] (20150930/evregion-163) [ 10.600465] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20150930/exfldio-297) [ 10.600469] ACPI Error: Method parse/execution failed [\_SB.TSKN._TMP] (Node 88015a0f94b0), AE_NOT_EXIST (20150930/psparse-542) [ 10.600479] thermal thermal_zone2: failed to read out thermal zone (-5) later it shows: [ 11.235601] acer_wmi: Enabling Launch Manager failed: 0xe4 - 0x0 It's unfortunate to never know how much power is left, as one might imagine. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: coder 1607 F pulseaudio /dev/snd/controlC1: coder 1607 F pulseaudio CurrentDesktop: XFCE Date: Thu Sep 22 00:34:51 2016 HibernationDevice: RESUME=UUID=c0846449-28bd-4d6a-9ccb-732cf1582f3a InstallationDate: Installed on 2016-09-08 (13 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Acer Aspire SW5-173 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Crepe dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd04/11/2016:svnAcer:pnAspireSW5-173:pvrV1.08:rvnAcer:rnCrepe:rvrV1.08:cvnAcer:ct9:cvrV1.08: dmi.product.name: Aspire SW5-173 dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626299/+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 1737934] Re: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable
Please try this kernel without "nvme_core.default_ps_max_latency_us=". http://people.canonical.com/~khfeng/lp1737934/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737934 Title: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable Status in linux package in Ubuntu: Confirmed Bug description: Seems related to these bugs: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748 Problem: At seemingly random times my computer (brand new Lenovo Thinkpad T470) seems to lose access to the Samsung SM961 256GB SSD drive it has inside. When this happens the whole OS freezes up and when I try to power down I see a black terminal-like screen that prints the following errors: EXT4-fs error (device nvme0n1p2): ext4_find_entry:1431: inode #7471275 (or #741278): comm gmain (or systemd-journal or ...): reading directory iblock 0 This error seems to be repeated endlessly, though I've only let it go for a few minutes. No other errors are printed. This is the only drive it has. I don't know if this occurs in Windows too since I removed Windows and installed Ubuntu immediatly after updating the BIOS. Info: Distro: Ubuntu MATE 17.10 sudo uname -r 4.13.0-19-generic sudo nvme get-feature -f 0x0c -H /dev/nvme0 (with latency set to 250) get-feature:0xc (Autonomous Power State Transition), Current value:0x01 Autonomous Power State Transition Enable (APSTE): Enabled Auto PST Entries. Entry[ 0] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 1] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 2] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 3] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 4] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 5] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 6] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 7] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 8] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 9] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[10] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[11] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[12] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[13] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[14] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[15] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[16] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[17] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[18] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 ...
