[Kernel-packages] [Bug 1704614] Re: very long kernel boot time with some KVM switch
Ok, didn't notice it's two different machines - please file an upstream 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/1704614 Title: very long kernel boot time with some KVM switch Status in linux package in Ubuntu: Confirmed Bug description: I am using a Aten KVM switch CS1794 hooked on my computer. It allows the switching for USB, HDMI, and audio. http://www.aten.com/global/en/products/kvm/desktop-kvm-switches/cs1794/#.WWrnguk9iUk I run a Ubuntu 17.04 system. I experience a very long boot time, having done an analysis it appears that the main problem is the kernel boot time and more specifically the time it takes to start its USB subsystem. when you look at the dsmg output you can clearly see a gap between 4-78s and 79-91s, all in the USB sub-process. --- ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: stranche 3670 F pulseaudio /dev/snd/controlC1: stranche 3670 F pulseaudio /dev/snd/controlC0: stranche 3670 F pulseaudio DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=28d4f703-2b20-4dd3-ba8b-aa363ad5141d InstallationDate: Installed on 2017-07-14 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed root=UUID=4fde9883-6d7f-4954-90d6-779f37bbdc93 ro console=tty console=ttyUSB0,57600 noplymouth debug ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH Z77 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704614/+subscriptions -- Mailing list: https://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 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
I think the touchpad should work - can you try use xinput to disable/enable the touchpad device? Also, try blacklisting kernel module psmouse. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5 U: Uniq= H: Handlers=sysrq kbd event5 leds B: PROP=0 B: EV=120013 B: KEY=e080ffdf01cf fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=04d9 Product=a070 Version=011
[Kernel-packages] [Bug 1704730] Comment bridged from LTC Bugzilla
--- Comment From hasri...@in.ibm.com 2017-07-24 02:15 EDT--- (In reply to comment #9) > Did this issue start happening after an update/upgrade? Was there a prior > kernel version where you were not having this particular problem? > Not sure if any prior kernel did not have this issue.. But issue seems to occur on 17 10 base kernel. > Would it be possible for you to test the latest upstream kernel? Refer to > https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 > kernel[0]. Tested with 4.13-rc2 from the same link, Issue is still observed. xfstests-dev# ./check tests/generic/044 FSTYP -- ext4 PLATFORM -- Linux/ppc64le ltc-test-ci2 4.13.0-041300rc2-generic MKFS_OPTIONS -- /dev/loop1 MOUNT_OPTIONS -- -o acl,user_xattr /dev/loop1 /mnt/scratch generic/044 - output mismatch (see /root/harish/xfstests-dev/results//generic/044.out.bad) --- tests/generic/044.out 2017-07-20 07:57:37.069755021 -0400 +++ /root/harish/xfstests-dev/results//generic/044.out.bad 2017-07-24 02:10:00.86000 -0400 @@ -1 +1,1000 @@ QA output created by 044 +corrupt file /mnt/scratch/1 - non-zero size but no extents +corrupt file /mnt/scratch/2 - non-zero size but no extents +corrupt file /mnt/scratch/3 - non-zero size but no extents +corrupt file /mnt/scratch/4 - non-zero size but no extents +corrupt file /mnt/scratch/5 - non-zero size but no extents +corrupt file /mnt/scratch/6 - non-zero size but no extents ... (Run 'diff -u tests/generic/044.out /root/harish/xfstests-dev/results//generic/044.out.bad' to see the entire diff) Ran: generic/044 Failures: generic/044 Failed 1 of 1 tests Thanks, Harish S -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704730 Title: xfstest fails with corrupt file /mnt/scratch/1 - non-zero size but no extents ( ext4 ) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Incomplete Bug description: xfstests fails non-zero size but no extents on ext4 filesystem Environment -- Kernel Build: 4.12.1-041201-generic Model : 8247-22L Platform: PowerNV ( P8 ) Uname output --- # uname -a Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with ext4 filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.config for running with created loop device 5. Run xfstests-dev test : ./check tests/generic/044 The test 044 fails with following generic/044 - output mismatch (see /root/harish/xfstests-dev/results//generic/044.out.bad) --- tests/generic/044.out 2017-07-13 06:04:36.208323135 -0400 +++ /root/harish/xfstests-dev/results//generic/044.out.bad 2017-07-14 06:24:08.153731112 -0400 @@ -1 +1,1000 @@ QA output created by 044 +corrupt file /mnt/scratch/1 - non-zero size but no extents +corrupt file /mnt/scratch/2 - non-zero size but no extents +corrupt file /mnt/scratch/3 - non-zero size but no extents +corrupt file /mnt/scratch/4 - non-zero size but no extents +corrupt file /mnt/scratch/5 - non-zero size but no extents +corrupt file /mnt/scratch/6 - non-zero size but no extents ... (Run 'diff -u tests/generic/044.out /root/harish/xfstests-dev/results//generic/044.out.bad' to see the entire diff) Ran: generic/044 Failures: generic/044 Failed 1 of 1 tests Dmesg: -- [17244.878673] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [17245.517227] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17245.697100] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17245.710634] run fstests generic/044 at 2017-07-14 06:23:49 [17246.534410] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17246.535534] EXT4-fs (loop2): shut down requested (1) [17246.535625] Aborting journal on device loop2-8. [17247.278467] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17259.888304] EXT4-fs (loop2): shut down requested (2) [17259.995751] Aborting journal on device loop2-8. [17260.113582] EXT4-fs (loop2): recovery complete [17260.113902] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17260.190076] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr [17264.821978] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: acl,user_xattr == Comment: #2 - SEETEENA THOUFEEK - 2017-07-17 02:10:52 == Issue does not happen when running the same test with xfs file system. (ie, creating l
[Kernel-packages] [Bug 1584542] Re: Wifi Adapter Fails to come up after restart. after power off works fine
Just saw a message in January 2017 about a fix (well, it seemed to me just another workaround). Maybe it is fixed in 4.9.6 or 7. I"ll try. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584542 Title: Wifi Adapter Fails to come up after restart. after power off works fine Status in linux package in Ubuntu: Expired Bug description: I just installed Ubuntu Gnome 16.04 on my Laptop and I have noticed that Wifi somtimes doesn't work. after observing the problem I have come to the conclusion that it doesn't work after a reboot. I need to power it off and then back on to get the WiFi adapter working. my laptop is HP Pavilion and using a Ralink RT3290 Wireless adapter. this is the dmesg output when it's working: [ 12.190373] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 12.198413] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected [ 12.230518] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 22.490620] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 22.566482] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 this is when it's not working: [ 12.434107] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 12.437567] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected [ 12.453872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 22.603249] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 22.634727] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 [ 24.250054] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 25.850083] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 25.851000] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5) [ 27.994185] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 29.594240] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 29.595203] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hussain2002 F pulseaudio /dev/snd/controlC0: hussain2002 F pulseaudio CurrentDesktop: GNOME Date: Mon May 23 00:52:12 2016 HibernationDevice: RESUME=UUID=50a78741-d9a5-4656-a841-0c17259a4155 InstallationDate: Installed on 2016-05-22 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=69cc5799-74c4-41f7-b65d-5f9dafb54f43 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd08/08/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08971030410610100:rvnHewlett-Packard:rn2166:rvr29.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 08971030410610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584542/+subscriptions -- Mailing list: https://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 1584542] Re: Wifi Adapter Fails to come up after restart. after power off works fine
Yes, I saw the timeout message and tried with a 100, but no luck. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584542 Title: Wifi Adapter Fails to come up after restart. after power off works fine Status in linux package in Ubuntu: Expired Bug description: I just installed Ubuntu Gnome 16.04 on my Laptop and I have noticed that Wifi somtimes doesn't work. after observing the problem I have come to the conclusion that it doesn't work after a reboot. I need to power it off and then back on to get the WiFi adapter working. my laptop is HP Pavilion and using a Ralink RT3290 Wireless adapter. this is the dmesg output when it's working: [ 12.190373] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 12.198413] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected [ 12.230518] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 22.490620] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 22.566482] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 this is when it's not working: [ 12.434107] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 12.437567] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected [ 12.453872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 22.603249] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 22.634727] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 [ 24.250054] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 25.850083] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 25.851000] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5) [ 27.994185] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 29.594240] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 29.595203] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hussain2002 F pulseaudio /dev/snd/controlC0: hussain2002 F pulseaudio CurrentDesktop: GNOME Date: Mon May 23 00:52:12 2016 HibernationDevice: RESUME=UUID=50a78741-d9a5-4656-a841-0c17259a4155 InstallationDate: Installed on 2016-05-22 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=69cc5799-74c4-41f7-b65d-5f9dafb54f43 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd08/08/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08971030410610100:rvnHewlett-Packard:rn2166:rvr29.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 08971030410610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584542/+subscriptions -- Mailing list: https://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 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge
You need to do a kernel bisection. Build kernel yourself will be a much faster process. Also, give daily build iso [1] a try - maybe the fix is in userspace. [1] http://cdimages.ubuntu.com/daily-live/current/artful-desktop- amd64.iso -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609242 Title: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: When I install Ubuntu 16.04 on my computer the screen goes blank at login. I can blindly login and it boots but I cannot use the display (external monitor through HDMI). I've looked online for an answer to this issue but could not find a solution. However, many people report this issue in forums with the 4.4x kernel. On my main computer, I upgraded from 14.04 to 16.04.1. On this computer I was able to switch back to the 3.13 kernel which *does work*. On the same computer, if I use a 16.04 live CD, it does the same thing. The screen goes blank. UEFI may be part of the issue as well. I have it disabled in bios (set to legacy mode) but when I first boot, it seems to go into UEFI mode first and then, after rebooting with it shows me the list of kernels. I can select the kernel from there but if I use a 4.4x kernel, it blanks out at encryption passphrase screen. There are also people with similar issues on AskUbuntu. Here's some basic HW info. If you require more, please ask. sudo lshw | head zbox description: Notebook product: ZBOX-ID18 (NA) vendor: ZOTAC version: XX serial: G211X width: 64 bits capabilities: smbios-2.7 dmi-2.7 vsyscall32 configuration: boot=normal chassis=notebook family=NA sku=NA uuid=00020003-0004-0005-0006-000700080009 *-core sudo lshw -C display *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:45 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user5536 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38 InstallationDate: Installed on 2014-07-23 (743 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313) MachineType: ZOTAC ZBOX-ID18 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-92-generic N/A linux-backports-modules-3.13.0-92-generic N/A linux-firmware 1.157.2 RfKill: StagingDrivers: rts5139 Tags: xenial staging Uname: Linux 3.13.0-92-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 03/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B211P011 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID18 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 10 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA: dmi.product.name: ZBOX-ID18 dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609242/+subscriptions -- Mailing list: https://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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Alex, Can you provide link on how DragonflyBSD fixed 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks 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/ubuntu/+source/linux/+bug/1690085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-
[Kernel-packages] [Bug 1362313] Re: PulseAudio can't find Bluetooth device after reconnecting
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1362313 Title: PulseAudio can't find Bluetooth device after reconnecting Status in bluez package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: What happens? 1. connct a2dp device 2. start playback 3. reconnect a2dp device from remote 4. ubuntu reports device is connected 5. a2dp device does not show up in pulseaudio nor does music playback work (via a2dp device). sometimes there are "timeout" error messages in kde. 6. try to reconnect from ubuntu, restart bluetooth daemon, restart pulseaudio daemon. it all does not help. 7. what does help is restarting 1. dbus 2. bluetooth and 3. pulseaudio then connect the device (if not already auto-connected) After step 3, there is the following error message in syslog (no other errors in syslog or dmesg): pulseaudio[7812]: [bluetooth] bluetooth-util.c: Failed to release transport /org/bluez/7791/hci0/dev_C8_84_47_10_24_A2/fd2: Method "Release" with signature "s" on interface "org.bluez.MediaTransport" doesn't exist What I expected to happen? After the device reconnect, the music playback switches playback back to the bluetooth device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Wed Aug 27 21:41:34 2014 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/linux64-root64 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-06-18 (70 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: B85 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:02:72:CC:E6:D5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:100536 acl:18 sco:0 events:14179 errors:0 TX bytes:24059553 acl:28186 sco:0 commands:77 errors:0 syslog: Aug 27 20:46:20 charlie bluetoothd[1538]: /org/bluez/1538/hci0/dev_C8_84_47_10_24_A2/fd0: fd(25) ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1362313/+subscriptions -- Mailing list: https://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 1362313] Re: PulseAudio can't find Bluetooth device after reconnecting
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1362313 Title: PulseAudio can't find Bluetooth device after reconnecting Status in bluez package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: What happens? 1. connct a2dp device 2. start playback 3. reconnect a2dp device from remote 4. ubuntu reports device is connected 5. a2dp device does not show up in pulseaudio nor does music playback work (via a2dp device). sometimes there are "timeout" error messages in kde. 6. try to reconnect from ubuntu, restart bluetooth daemon, restart pulseaudio daemon. it all does not help. 7. what does help is restarting 1. dbus 2. bluetooth and 3. pulseaudio then connect the device (if not already auto-connected) After step 3, there is the following error message in syslog (no other errors in syslog or dmesg): pulseaudio[7812]: [bluetooth] bluetooth-util.c: Failed to release transport /org/bluez/7791/hci0/dev_C8_84_47_10_24_A2/fd2: Method "Release" with signature "s" on interface "org.bluez.MediaTransport" doesn't exist What I expected to happen? After the device reconnect, the music playback switches playback back to the bluetooth device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Wed Aug 27 21:41:34 2014 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/linux64-root64 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-06-18 (70 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: B85 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:02:72:CC:E6:D5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:100536 acl:18 sco:0 events:14179 errors:0 TX bytes:24059553 acl:28186 sco:0 commands:77 errors:0 syslog: Aug 27 20:46:20 charlie bluetoothd[1538]: /org/bluez/1538/hci0/dev_C8_84_47_10_24_A2/fd0: fd(25) ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1362313/+subscriptions -- Mailing list: https://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 1699004] Re: APST gets enabled against explicit kernel option
Just realized you were replying previous comment...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1699004
Title:
APST gets enabled against explicit kernel option
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
Fix Committed
Bug description:
[Impact]
The NVMe driver doesn't set APSTE on APST quirked devices at initialization.
If the BIOS or NVMe enables APST before driver loading, APST will never be
disabled, it also ignores explicit kernel option as result.
So the faulty NVMe may not work as intended.
[Test Case]
$ sudo nvme get-feature -f 0x0c -H /dev/nvme0
...will show APST is "Disabled" instead of "Enabled"
[Regression Potential]
Very low.
This SRU didn't change anything really - it just explicitly set APSTE at
initialization.
---
I have a Lenovo ThinkPad X270 with a Toshiba nvme SSD
$ sudo nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 177S10WYTAMT THNSF5256GPUK TOSHIBA
1 256.06 GB / 256.06 GB512 B + 0 B 51025KLA
I was affected by this bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184?comments=all
before. After disabling APST by adding
"nvme_core.default_ps_max_latency_us=0" in /etc/default/grub, the bug went away.
Since yesterday, however the bug has returned, with the system dying
with I/O errors after an hour or so.
I verified, that the kernel option is still being set
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
however it turns out that it is being ignored for some reason, and
running
$ sudo nvme get-feature -f 0x0c -H /dev/nvme0
reports that APST is enabled. I can successfully disable it manually
using
$ sudo nvme set-feature -f 0x0c -v=0 /dev/nvme0
and the problem goes away. However, after any reboot and even after
waking the system from suspend, it is reenabled, causing the system to
crash after a short while.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-22-generic 4.10.0-22.24
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: maeher 1669 F...m pulseaudio
/dev/snd/controlC0: maeher 1669 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Mon Jun 19 23:29:31 2017
InstallationDate: Installed on 2017-04-17 (64 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 20HN001RUS
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.10.0-22-generic N/A
linux-backports-modules-4.10.0-22-generic N/A
linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: R0IET30W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HN001RUS
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:bvrR0IET30W(1.08):bd01/16/2017:svnLENOVO:pn20HN001RUS:pvrThinkPadX270:rvnLENOVO:rn20HN001RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20HN001RUS
dmi.product.version: ThinkPad X270
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699004/+subscriptions
--
Mailing list: https://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 1699004] Re: APST gets enabled against explicit kernel option
@Nils,
Wha you need to do is to enable -proposed repository, and verify that
the Linux kernel in -proposed actually fixes the problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1699004
Title:
APST gets enabled against explicit kernel option
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
Fix Committed
Bug description:
[Impact]
The NVMe driver doesn't set APSTE on APST quirked devices at initialization.
If the BIOS or NVMe enables APST before driver loading, APST will never be
disabled, it also ignores explicit kernel option as result.
So the faulty NVMe may not work as intended.
[Test Case]
$ sudo nvme get-feature -f 0x0c -H /dev/nvme0
...will show APST is "Disabled" instead of "Enabled"
[Regression Potential]
Very low.
This SRU didn't change anything really - it just explicitly set APSTE at
initialization.
---
I have a Lenovo ThinkPad X270 with a Toshiba nvme SSD
$ sudo nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 177S10WYTAMT THNSF5256GPUK TOSHIBA
1 256.06 GB / 256.06 GB512 B + 0 B 51025KLA
I was affected by this bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184?comments=all
before. After disabling APST by adding
"nvme_core.default_ps_max_latency_us=0" in /etc/default/grub, the bug went away.
Since yesterday, however the bug has returned, with the system dying
with I/O errors after an hour or so.
I verified, that the kernel option is still being set
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
however it turns out that it is being ignored for some reason, and
running
$ sudo nvme get-feature -f 0x0c -H /dev/nvme0
reports that APST is enabled. I can successfully disable it manually
using
$ sudo nvme set-feature -f 0x0c -v=0 /dev/nvme0
and the problem goes away. However, after any reboot and even after
waking the system from suspend, it is reenabled, causing the system to
crash after a short while.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-22-generic 4.10.0-22.24
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: maeher 1669 F...m pulseaudio
/dev/snd/controlC0: maeher 1669 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Mon Jun 19 23:29:31 2017
InstallationDate: Installed on 2017-04-17 (64 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 20HN001RUS
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed
root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.10.0-22-generic N/A
linux-backports-modules-4.10.0-22-generic N/A
linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: R0IET30W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HN001RUS
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:bvrR0IET30W(1.08):bd01/16/2017:svnLENOVO:pn20HN001RUS:pvrThinkPadX270:rvnLENOVO:rn20HN001RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20HN001RUS
dmi.product.version: ThinkPad X270
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699004/+subscriptions
--
Mailing list: https://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 1246670] ☑lovely place
Hey! I wanted to share with you my experience in visiting a lovely place, just take a look http://coffeebeds.com/administrator.php?e9e8 Piero Bonatti Sent from Mail for Windows 10 ** Attachment added: "BB138ADE7A06685A.jpg" https://bugs.launchpad.net/bugs/1246670/+attachment/4920035/+files/BB138ADE7A06685A.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1246670 Title: 14e4:4727 [Dell Inspiron 10z (1120)] Ubuntu 12.04.3 LTS: can't connect to WIFI Status in linux package in Ubuntu: Expired Bug description: After the last updates I can't connect anymore to WIFI networks, including: - office wifi (WPA / WPA2 enterprise + PEAP) - public wifi from airport lounges, hotels, conferences. The notebook (dell inspiron) still detects the available newtorks. If they are protected, then additional data are requested (passwords and the like). So it seems that the wifi card is working well with the current driver (see below for further evidence). However, then the connection times out before getting any IP address. When I switch to Windows, I immediately get the connection (then the wifi network and the notebook's hardware are OK). Sometimes, when I switch back to Ubuntu, the connection starts spontaneously and I can work normally (as if the problem were in the DHCP protocol execution, and the Windows connection "did some work" that Ubuntu currently can't do). (further evidence that the driver is OK). I'm using the proprietary driver proposed by Ubuntu: "This package contains Broadcom 802.11 Linux STA wireless driver for use with Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware." --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: ALC259 Analog [ALC259 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bonatti1690 F pulseaudio /dev/snd/controlC0: bonatti1690 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xd040 irq 16' Mixer name : 'Realtek ALC259' Components : 'HDA:10ec0269,10280470,00100100' Controls : 18 Simple ctrls : 10 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd011 irq 19' Mixer name : 'ATI RS690/780 HDMI' Components : 'HDA:1002791a,00791a00,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=8b9f8be8-b5ce-42d9-b311-de81faa160f6 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: Dell Inc. Inspiron 1120 MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-55-generic-pae root=UUID=891059fc-57ca-484c-941a-e405cd31b74e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-55.85-generic-pae 3.2.51 RelatedPackageVersions: linux-restricted-modules-3.2.0-55-generic-pae N/A linux-backports-modules-3.2.0-55-generic-pae N/A linux-firmware1.79.7 Tags: precise running-unity Uname: Linux 3.2.0-55-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo dmi.bios.date: 07/26/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.asset.tag: 1234567890 dmi.board.name: 090DNY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.asset.tag: 1234567890 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A03 dmi.modalias: dmi:bvnDellInc.:bvrA03:bd07/26/2010:svnDellInc.:pnInspiron1120:pvrA03:rvnDellInc.:rn090DNY:rvrA03:cvnDellInc.:ct8:cvrA03: dmi.product.name: Inspiron 1120 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1246670/+subscriptions -- Mailing list: https://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 1543755] Re: "sudo bluetoothd --compat" fails with "SDP session setup failed, disabling bluetooth"
Sorry, but 16.10 reached end-of-life four days ago: https://wiki.ubuntu.com/Releases ** Changed in: bluez (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1543755 Title: "sudo bluetoothd --compat" fails with "SDP session setup failed, disabling bluetooth" Status in bluez package in Ubuntu: Invalid Bug description: `sudo bluetoothd --compat --nodetach` fails with `SDP session setup failed, disabling bluetooth`. That is unexplicable and not helpful, please provide usable feedback and instructions how to handle the problem. $ obexpushd -B -n obexpushd 0.11.2 Copyright (C) 2006-2010 Hendrik Sattler This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. Listening on bluetooth/[00:00:00:00:00:00]:9 SDP session setup failed, disabling bluetooth net_init() failed ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 Uname: Linux 4.4.1-040401-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 9 20:32:08 2016 InstallationDate: Installed on 2013-10-17 (845 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: rfcomm btusb bnep bluetooth MachineType: LENOVO IdeaPad U410 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.1-040401-generic root=UUID=8c488557-8173-43a2-a3a8-df0a24695c08 ro rootflags=subvol=ubuntu-main-root quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to wily on 2015-11-19 (82 days ago) dmi.bios.date: 09/25/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 65CN90WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo U410 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr65CN90WW:bd09/25/2012:svnLENOVO:pnIdeaPadU410:pvrLenovoU410:rvnLENOVO:rnLenovo:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoU410: dmi.product.name: IdeaPad U410 dmi.product.version: Lenovo U410 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 84:A6:C8:63:22:B5 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:1003513 acl:2928 sco:0 events:2524 errors:0 TX bytes:36304 acl:872 sco:0 commands:1396 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1543755/+subscriptions -- Mailing list: https://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 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
** Changed in: bluez (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- Mailing list: https://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 1705882] Re: Bluetooth connection to device fails from Ubuntu 16.04
I was experiencing similar problems, sometimes, until recently. The problem went away for me more recently in 17.10. Can you please try live booting: http://cdimage.ubuntu.com/daily-live/current/ and see if the problem is fixed there in 17.10? -- 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/1705882 Title: Bluetooth connection to device fails from Ubuntu 16.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth connection to a bluetooth IOIO device fails using a USB bluetooth adapter from a Ubuntu 16.04 system. The same device could be successfully connected using two non-Ubuntu systems: a) The same system hardware setup (dual-boot) running Windows 8 could connect without any problems. Also could run applications using serial-port associated with this connection. b) Android Note 4 device using bluetooth was able to successfully connect and run apps. Therefore, it was concluded that the Ubuntu 16.04 bluetooth service has a problem. Note: The USB bluetooth adapter used: BTA8000 from Cirago on the ubuntu system as well as the IOIO device. The adapters on the device and system have been verified to have different MAC addresses and works well with other devices. Procedure: Using the Bluetooth control in system-tray -> Bluetooth settings -> +, the device was located as IOIO (8A:22). Here, device was clicked upon, changed PIN to 4545 and pressing next resulted in the device being successfully added. However, the system-tray status of the device continues to say Connection is OFF. Attempting to turnon connection results in changing the system-tray blue-tooth icon to Keys-Icon for few seconds and then reverting back to the bluetooth icon. The device remains in disconnected state and cannot be accessed. The btmon trace (log-line 1277) and bluetoothd syslog (log-line 405) logs seem to indicate that the local host is sending a disconnect request after receiving a SDP: Service Search Attribute Response from the device. The src/device.c:connect_profiles() /org/bluez/hci0/dev_00_1B_DC_06_8A_22 (all), client :1.73 must result in connection setup - not disconnect. Log information was collected for the above procedure. systemInfo.txt: Information about the system bluetooth. syslog.blue: syslog with busr/lib/bluetooth/bluetoothd --noplugin=sap -d in /lib/systemd/system/bluetooth.service btmon.log: result of running sudo btmon ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 23 01:28:38 2017 InstallationDate: Installed on 2017-06-03 (49 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InterestingModules: rfcomm bnep btusb bluetooth JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Hewlett-Packard HP ENVY dv7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed root=UUID=1c1d284c-53a1-46dc-bc01-8555da60ad7e ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181C dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/02/2012:svnHewlett-Packard:pnHPENVYdv7NotebookPC:pvr088A1130592620100:rvnHewlett-Packard:rn181C:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY dv7 Notebook PC dmi.product.version: 088A1130592620100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:1B:DC:06:89:C5 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:242328 acl:898 sco:0 events:316 errors:0 TX bytes:11991 acl:125 sco:0 commands:112 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1705882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-pa
[Kernel-packages] [Bug 1650895] Re: Several new Asus laptops are missing touchpad support
These messages come from the i2c_hid module, which is a module that sits between the hid-aus driver and the i2c driver. The message indicates that the i2c_hid module received an invalid INPUT report and has discarded it. The hid-asus driver is never made aware that this occurred. I can think of three possible causes: a) an electronic signalling issue; b) a firmware issue; or c) a proprietary function of the device There's little that can be done for a) or b) - it's effectively faulty (or poorly shielded) hardware. For c) - if there were documentation we might be able to do something. But it would likely require a quirk at the lower levels (i.e. the i2c_hid module). And given (in my experience) the minimal impact of these messages - that might be something the kernel maintainers would consider undesirable. You could investigate further by modifying the i2c_hid module to dump the contents of the discarded message. But since a recent change to the i2c_hid module (which put a sleep inbetween the POWER ON and RESET commands) I no longer seem to get these messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1650895 Title: Several new Asus laptops are missing touchpad support Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: E502SA and several other new Asus laptops are missing touchpad support. Support for the Asus touchpad has been introduced only recently: http://www.spinics.net/lists/linux-input/msg48143.html From the development kernel git: "commit 9ce12d8be12c94334634dd57050444910415e45f Author: Brendan McGrath Date: Tue Nov 29 18:59:25 2016 +1100 HID: asus: Add i2c touchpad support Update the hid-asus module to add multitouch support for the Asus i2c touchpad. This patch aims to resolve the issue raised here:E https://bugzilla.kernel.org/show_bug. The latest mainline kernel, Linux 4.9 that was released 11th of December doesn't contain this patch. I was able to get touchpad features to work with E502SA after patching Xenial Xerus kernel with the above patch and the patches it depends on. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jamse 2045 F pulseaudio CurrentDesktop: Unity Date: Sun Dec 18 15:41:30 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d46d5e40-bd0f-41a5-87bb-f4f470f7b4d6 InstallationDate: Installed on 2016-12-14 (4 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E502SA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic.efi.signed root=UUID=17457b58-fc63-470b-a916-2eedb0dbd58e ro quiet splash intel_idle.max_cstate=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-53-generic N/A linux-backports-modules-4.4.0-53-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E502SA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E502SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE502SA.300:bd07/20/2016:svnASUSTeKCOMPUTERINC.:pnE502SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE502SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E502SA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650895/+subscriptions -- Mailing list: https://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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
If any of your RAM timings are odd (eg. 17), setting them to the next even number (eg. 18) helps a lot. Recompiling the kernel with CONFIG_RCU_NOCB_CPU and CONFIG_RCU_NOCB_CPU_ALL, and disabling ASLR is still necessary though. It may also be a good idea to give the SOC slightly more voltage, but not more than 1.2 V. -- You 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 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 upgrad
[Kernel-packages] [Bug 1705939] [NEW] package linux-firmware (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/mrvl/pcie8897_uapsta.bin' a '/lib/f
Public bug reported: when update packages, crash ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware (not installed) ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-firmware: Install linux-firmware: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Jul 23 21:24:54 2017 ErrorMessage: no se pudieron copiar los datos extraídos de './lib/firmware/mrvl/pcie8897_uapsta.bin' a '/lib/firmware/mrvl/pcie8897_uapsta.bin.dpkg-new': fin de fichero o de flujo inesperado RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-firmware Title: package linux-firmware (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/mrvl/pcie8897_uapsta.bin' a '/lib/firmware/mrvl/pcie8897_uapsta.bin.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1705939 Title: package linux-firmware (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/mrvl/pcie8897_uapsta.bin' a '/lib/firmware/mrvl/pcie8897_uapsta.bin.dpkg-new': fin de fichero o de flujo inesperado Status in linux-firmware package in Ubuntu: New Bug description: when update packages, crash ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware (not installed) ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-firmware: Install linux-firmware: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Jul 23 21:24:54 2017 ErrorMessage: no se pudieron copiar los datos extraídos de './lib/firmware/mrvl/pcie8897_uapsta.bin' a '/lib/firmware/mrvl/pcie8897_uapsta.bin.dpkg-new': fin de fichero o de flujo inesperado RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-firmware Title: package linux-firmware (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/mrvl/pcie8897_uapsta.bin' a '/lib/firmware/mrvl/pcie8897_uapsta.bin.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1705939/+subscriptions -- Mailing list: https://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 1705921] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919839/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919844/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919842/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919843/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919838/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919848/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919840/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919836/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919841/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919845/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919837/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919846/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919847/+files/UdevDb.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] Re: Wifi isn't identified for Ampak AP6212
apport information ** Tags added: apport-collected xenial ** Description changed: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh + --- + ApportVersion: 2.20.1-0ubuntu2.9 + Architecture: i386 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: + country IL: DFS-ETSI + (2402 - 2482 @ 40), (N/A, 20), (N/A) + (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR + (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 + InstallationDate: Installed on 2017-04-06 (108 days ago) + InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) + MachineType: Insyde BayTrail + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 + RelatedPackageVersions: + linux-restricted-modules-4.10.0-27-generic N/A + linux-backports-modules-4.10.0-27-generic N/A + linux-firmware 1.157.11 + RfKill: + 1: phy1: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: xenial + Uname: Linux 4.10.0-27-generic i686 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/29/2014 + dmi.bios.vendor: INSYDE Corp. + dmi.bios.version: DSO.00 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: Type2 - Board Product Name + dmi.board.vendor: Type2 - Board Manufacturer + dmi.board.version: Type2 - Board Version + dmi.chassis.asset.tag: Chassis Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Chassis Manufacturer + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: + dmi.product.name: BayTrail + dmi.product.version: Type1 - TBD by OEM + dmi.sys.vendor: Insyde ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1705921/+attachment/4919835/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manu
[Kernel-packages] [Bug 1705921] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1705921 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Incomplete Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] Re: Wifi isn't identified for Ampak AP6212
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: New Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://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 1705921] [NEW] Wifi isn't identified for Ampak AP6212
You have been subscribed to a public bug: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Wifi isn't identified for Ampak AP6212 https://bugs.launchpad.net/bugs/1705921 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge
Yes. It happens on 4.13-rc1. Black Screen. The last good version of the kernel was 4.2.8 - all others since give me the black screen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609242 Title: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: When I install Ubuntu 16.04 on my computer the screen goes blank at login. I can blindly login and it boots but I cannot use the display (external monitor through HDMI). I've looked online for an answer to this issue but could not find a solution. However, many people report this issue in forums with the 4.4x kernel. On my main computer, I upgraded from 14.04 to 16.04.1. On this computer I was able to switch back to the 3.13 kernel which *does work*. On the same computer, if I use a 16.04 live CD, it does the same thing. The screen goes blank. UEFI may be part of the issue as well. I have it disabled in bios (set to legacy mode) but when I first boot, it seems to go into UEFI mode first and then, after rebooting with it shows me the list of kernels. I can select the kernel from there but if I use a 4.4x kernel, it blanks out at encryption passphrase screen. There are also people with similar issues on AskUbuntu. Here's some basic HW info. If you require more, please ask. sudo lshw | head zbox description: Notebook product: ZBOX-ID18 (NA) vendor: ZOTAC version: XX serial: G211X width: 64 bits capabilities: smbios-2.7 dmi-2.7 vsyscall32 configuration: boot=normal chassis=notebook family=NA sku=NA uuid=00020003-0004-0005-0006-000700080009 *-core sudo lshw -C display *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:45 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user5536 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38 InstallationDate: Installed on 2014-07-23 (743 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313) MachineType: ZOTAC ZBOX-ID18 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-92-generic N/A linux-backports-modules-3.13.0-92-generic N/A linux-firmware 1.157.2 RfKill: StagingDrivers: rts5139 Tags: xenial staging Uname: Linux 3.13.0-92-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 03/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B211P011 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID18 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 10 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA: dmi.product.name: ZBOX-ID18 dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609242/+subscriptions -- Mailing list: https://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 1705586] Re: Mute key LED does not work on HP ProBook 440
Yes, you can reference the bug here. And https://bugzilla.kernel.org/ is the right place. File bug with these additional information: Product -> Drivers Component -> Sound(ALSA) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705586 Title: Mute key LED does not work on HP ProBook 440 Status in linux package in Ubuntu: Confirmed Bug description: this is probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I was asked to file a new bug. The mute button on my laptop has a led that changes the color based on the status of the audio-master channel. At least it should. There is a slider for the LED in alsamixer but it doesn't change anything. Are there any tests I should run? cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17 --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 2550 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=4ce0e490-8f95-4de2-9a8f-456e1455444d InstallationDate: Installed on 2015-06-07 (774 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04ca:7063 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic.efi.signed root=UUID=27108123-06bd-4347-a0c5-9ea2ba62a034 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-07-09 (11 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2017 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.06 dmi.board.name: 822E dmi.board.vendor: HP dmi.board.version: KBC Version 42.65 dmi.chassis.asset.tag: 5CD709684F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.06:bd06/18/2017:svnHP:pnHPProBook440G4:pvr:rvnHP:rn822E:rvrKBCVersion42.65:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 440 G4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586/+subscriptions -- Mailing list: https://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 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge
Does it happen on v4.13-rc1? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609242 Title: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Bug description: When I install Ubuntu 16.04 on my computer the screen goes blank at login. I can blindly login and it boots but I cannot use the display (external monitor through HDMI). I've looked online for an answer to this issue but could not find a solution. However, many people report this issue in forums with the 4.4x kernel. On my main computer, I upgraded from 14.04 to 16.04.1. On this computer I was able to switch back to the 3.13 kernel which *does work*. On the same computer, if I use a 16.04 live CD, it does the same thing. The screen goes blank. UEFI may be part of the issue as well. I have it disabled in bios (set to legacy mode) but when I first boot, it seems to go into UEFI mode first and then, after rebooting with it shows me the list of kernels. I can select the kernel from there but if I use a 4.4x kernel, it blanks out at encryption passphrase screen. There are also people with similar issues on AskUbuntu. Here's some basic HW info. If you require more, please ask. sudo lshw | head zbox description: Notebook product: ZBOX-ID18 (NA) vendor: ZOTAC version: XX serial: G211X width: 64 bits capabilities: smbios-2.7 dmi-2.7 vsyscall32 configuration: boot=normal chassis=notebook family=NA sku=NA uuid=00020003-0004-0005-0006-000700080009 *-core sudo lshw -C display *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:45 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user5536 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38 InstallationDate: Installed on 2014-07-23 (743 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313) MachineType: ZOTAC ZBOX-ID18 Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-92-generic N/A linux-backports-modules-3.13.0-92-generic N/A linux-firmware 1.157.2 RfKill: StagingDrivers: rts5139 Tags: xenial staging Uname: Linux 3.13.0-92-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 03/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B211P011 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID18 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 10 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA: dmi.product.name: ZBOX-ID18 dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609242/+subscriptions -- Mailing list: https://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 1705586] Re: Mute key LED does not work on HP ProBook 440
can you give me a hint where exactly I should file this bug. Is https://bugzilla.kernel.org/ the right place? And can I just reference this bug 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/1705586 Title: Mute key LED does not work on HP ProBook 440 Status in linux package in Ubuntu: Confirmed Bug description: this is probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I was asked to file a new bug. The mute button on my laptop has a led that changes the color based on the status of the audio-master channel. At least it should. There is a slider for the LED in alsamixer but it doesn't change anything. Are there any tests I should run? cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17 --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 2550 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=4ce0e490-8f95-4de2-9a8f-456e1455444d InstallationDate: Installed on 2015-06-07 (774 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04ca:7063 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic.efi.signed root=UUID=27108123-06bd-4347-a0c5-9ea2ba62a034 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-07-09 (11 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2017 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.06 dmi.board.name: 822E dmi.board.vendor: HP dmi.board.version: KBC Version 42.65 dmi.chassis.asset.tag: 5CD709684F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.06:bd06/18/2017:svnHP:pnHPProBook440G4:pvr:rvnHP:rn822E:rvrKBCVersion42.65:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 440 G4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586/+subscriptions -- Mailing list: https://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 1705586] Re: Mute key LED does not work on HP ProBook 440
mode=mute-led-gpio enables mic mute led for 840 G3. Can you file an upstream bug for this issue? Maybe some dev have the machine to look into 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/1705586 Title: Mute key LED does not work on HP ProBook 440 Status in linux package in Ubuntu: Confirmed Bug description: this is probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I was asked to file a new bug. The mute button on my laptop has a led that changes the color based on the status of the audio-master channel. At least it should. There is a slider for the LED in alsamixer but it doesn't change anything. Are there any tests I should run? cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17 --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 2550 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=4ce0e490-8f95-4de2-9a8f-456e1455444d InstallationDate: Installed on 2015-06-07 (774 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04ca:7063 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic.efi.signed root=UUID=27108123-06bd-4347-a0c5-9ea2ba62a034 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-07-09 (11 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2017 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.06 dmi.board.name: 822E dmi.board.vendor: HP dmi.board.version: KBC Version 42.65 dmi.chassis.asset.tag: 5CD709684F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.06:bd06/18/2017:svnHP:pnHPProBook440G4:pvr:rvnHP:rn822E:rvrKBCVersion42.65:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 440 G4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586/+subscriptions -- Mailing list: https://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 1704374] Re: system randomly hangs itself
After several attempts it seems the system is stable. What I've done: 1) installed the latest stable kernel (it appears to not solve completely the problem): 2) switched to PLASMA dark theme on Kubuntu (it seems to not solve completely the problem; 3) installed again NVIDIA official drivers; 4) enable dithering into it; 5) reset all the video monitor setting; 6) disabled the effect since the boot. No longer problems. I don't know exactly what seems to fix the inconvenient however I assume that the concerns could be caused by the effects due to incompatibility hardware issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704374 Title: system randomly hangs itself Status in linux package in Ubuntu: Incomplete Bug description: this problem affect my system on Kubuntu 17.04 64bit Kde Plasma: 5.10.3 kernel: 4.10.0.26 Kde frameworks: 5.36.0 Qt release: 5.7.1 Probably I've solved with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1" Randomly the operating system hangs both eist and or c1e options enabled or disabled. I hope that Kubuntu has not damaged my hardware. However what kind of workaround should be made on the klernel to have this problem solved once and forever? My hardware specs: maximus eteme; latest bios; 8gb ram 4x2gb corsaire xms 1333; gigabyte gt 730 1gb OC xonar d2x. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-26-generic 4.10.0-26.30 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 1353 F pulseaudio /dev/snd/controlC1: james 1353 F pulseaudio CurrentDesktop: KDE Date: Fri Jul 14 12:39:32 2017 InstallationDate: Installed on 2017-04-25 (79 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer Maximus Extreme ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=52f9b441-fe75-4643-bbec-f912736d397b ro quiet splash intel_idle.max_cstate=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.164.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Maximus Extreme dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/24/2009:svnSystemmanufacturer:pnMaximusExtreme:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusExtreme:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: Maximus Extreme dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704374/+subscriptions -- Mailing list: https://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 1705906] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705906 Title: package linux-image-extra-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1 Status in linux package in Ubuntu: Confirmed Bug description: не получается очистить диск ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-62-generic 4.4.0-62.83 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ddim 3284 F pulseaudio /dev/snd/controlC0: ddim 3284 F pulseaudio Date: Sun Jul 23 14:17:06 2017 DpkgHistoryLog: Start-Date: 2017-07-23 14:16:52 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-4.4.0-62-generic:amd64 (4.4.0-62.83), linux-image-extra-4.4.0-62-generic:amd64 (4.4.0-62.83) ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код ошибки 1 HibernationDevice: RESUME=UUID=df5a65bf-912a-4e41-ba54-b42470559d6e InstallationDate: Installed on 2016-06-18 (399 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 305E4A/305E5A/305E7A ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=097201a3-b673-4e67-9748-ea9b7ef26a95 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.7 SourcePackage: linux Title: package linux-image-extra-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 04QR.ME30.20121101.SKK dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 305E4A/305E4A dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 04QR dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr04QR.ME30.20121101.SKK:bd11/01/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn305E4A/305E5A/305E7A:pvr04QR:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305E4A/305E4A:rvr04QR:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 305E4A/305E5A/305E7A dmi.product.version: 04QR dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705906/+subscriptions -- Mailing list: https://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 1584542] Re: Wifi Adapter Fails to come up after restart. after power off works fine
Maybe change the sleep time from 10 to an even larger number? See commit 08e5310028359. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584542 Title: Wifi Adapter Fails to come up after restart. after power off works fine Status in linux package in Ubuntu: Expired Bug description: I just installed Ubuntu Gnome 16.04 on my Laptop and I have noticed that Wifi somtimes doesn't work. after observing the problem I have come to the conclusion that it doesn't work after a reboot. I need to power it off and then back on to get the WiFi adapter working. my laptop is HP Pavilion and using a Ralink RT3290 Wireless adapter. this is the dmesg output when it's working: [ 12.190373] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 12.198413] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected [ 12.230518] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 22.490620] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 22.566482] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 this is when it's not working: [ 12.434107] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 12.437567] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected [ 12.453872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 22.603249] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 22.634727] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 [ 24.250054] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 25.850083] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 25.851000] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5) [ 27.994185] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 29.594240] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 29.595203] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hussain2002 F pulseaudio /dev/snd/controlC0: hussain2002 F pulseaudio CurrentDesktop: GNOME Date: Mon May 23 00:52:12 2016 HibernationDevice: RESUME=UUID=50a78741-d9a5-4656-a841-0c17259a4155 InstallationDate: Installed on 2016-05-22 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=69cc5799-74c4-41f7-b65d-5f9dafb54f43 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd08/08/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08971030410610100:rvnHewlett-Packard:rn2166:rvr29.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 08971030410610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584542/+subscriptions -- Mailing list: https://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 1705906] [NEW] package linux-image-extra-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1
Public bug reported: не получается очистить диск ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-62-generic 4.4.0-62.83 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ddim 3284 F pulseaudio /dev/snd/controlC0: ddim 3284 F pulseaudio Date: Sun Jul 23 14:17:06 2017 DpkgHistoryLog: Start-Date: 2017-07-23 14:16:52 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-4.4.0-62-generic:amd64 (4.4.0-62.83), linux-image-extra-4.4.0-62-generic:amd64 (4.4.0-62.83) ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код ошибки 1 HibernationDevice: RESUME=UUID=df5a65bf-912a-4e41-ba54-b42470559d6e InstallationDate: Installed on 2016-06-18 (399 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 305E4A/305E5A/305E7A ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=097201a3-b673-4e67-9748-ea9b7ef26a95 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.7 SourcePackage: linux Title: package linux-image-extra-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 04QR.ME30.20121101.SKK dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 305E4A/305E4A dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 04QR dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr04QR.ME30.20121101.SKK:bd11/01/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn305E4A/305E5A/305E7A:pvr04QR:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305E4A/305E4A:rvr04QR:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 305E4A/305E5A/305E7A dmi.product.version: 04QR dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705906 Title: package linux-image-extra-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1 Status in linux package in Ubuntu: New Bug description: не получается очистить диск ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-62-generic 4.4.0-62.83 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ddim 3284 F pulseaudio /dev/snd/controlC0: ddim 3284 F pulseaudio Date: Sun Jul 23 14:17:06 2017 DpkgHistoryLog: Start-Date: 2017-07-23 14:16:52 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-4.4.0-62-generic:amd64 (4.4.0-62.83), linux-image-extra-4.4.0-62-generic:amd64 (4.4.0-62.83) ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код ошибки 1 HibernationDevice: RESUME=UUID=df5a65bf-912a-4e41-ba54-b42470559d6e InstallationDate: Installed on 2016-06-18 (399 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 305E4A/305E5A/305E7A ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=097201a3-b673-4e67-9748-ea9b7ef26a95 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.7 SourcePackage: linux Title: package linux-image-extra-4.4.0-62-generic 4.4.0-62.83 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 04QR.ME30.20121101.SKK dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 305E4A/305E4A dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 04QR dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO.
[Kernel-packages] [Bug 1705900] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1705900 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705900 Title: Lenovo e73 USB webcam problems Status in linux package in Ubuntu: Incomplete Bug description: I'm experiencing problems with USB webcam on Lenovo e73 with Ubuntu 16.04.2 Xenial 32bit. Originally with 4.4 connecting the camera often resulted in complete hang of the system (apparently not even SysRq worked, though I did not test that personally since it is a system I'm administering remotely for a family member). There was always a null pointer dereference just before the hang, so I suspect that is the culprit (see the attached kernel log). After some updates the system no longer hangs. I suspect this was fixed by going from linux 4.4 to 4.8. However, the webcam still often doesn't work and most application just return error. This is usually fixed after several tries, but sometimes it is necessary to reboot computer. Updating BIOS didn't help. The kernel logs still contain the same null pointer dereference with exactly the same stack trace for both 4.8 and 4.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705900/+subscriptions -- Mailing list: https://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 1705900] Re: Lenovo e73 USB webcam problems
** Attachment added: "report generated by ubuntu-bug" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705900/+attachment/4919675/+files/ubuntu-bug_report -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705900 Title: Lenovo e73 USB webcam problems Status in linux package in Ubuntu: New Bug description: I'm experiencing problems with USB webcam on Lenovo e73 with Ubuntu 16.04.2 Xenial 32bit. Originally with 4.4 connecting the camera often resulted in complete hang of the system (apparently not even SysRq worked, though I did not test that personally since it is a system I'm administering remotely for a family member). There was always a null pointer dereference just before the hang, so I suspect that is the culprit (see the attached kernel log). After some updates the system no longer hangs. I suspect this was fixed by going from linux 4.4 to 4.8. However, the webcam still often doesn't work and most application just return error. This is usually fixed after several tries, but sometimes it is necessary to reboot computer. Updating BIOS didn't help. The kernel logs still contain the same null pointer dereference with exactly the same stack trace for both 4.8 and 4.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705900/+subscriptions -- Mailing list: https://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 1705900] [NEW] Lenovo e73 USB webcam problems
Public bug reported: I'm experiencing problems with USB webcam on Lenovo e73 with Ubuntu 16.04.2 Xenial 32bit. Originally with 4.4 connecting the camera often resulted in complete hang of the system (apparently not even SysRq worked, though I did not test that personally since it is a system I'm administering remotely for a family member). There was always a null pointer dereference just before the hang, so I suspect that is the culprit (see the attached kernel log). After some updates the system no longer hangs. I suspect this was fixed by going from linux 4.4 to 4.8. However, the webcam still often doesn't work and most application just return error. This is usually fixed after several tries, but sometimes it is necessary to reboot computer. Updating BIOS didn't help. The kernel logs still contain the same null pointer dereference with exactly the same stack trace for both 4.8 and 4.10. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "kernel log" https://bugs.launchpad.net/bugs/1705900/+attachment/4919674/+files/kernel_log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705900 Title: Lenovo e73 USB webcam problems Status in linux package in Ubuntu: New Bug description: I'm experiencing problems with USB webcam on Lenovo e73 with Ubuntu 16.04.2 Xenial 32bit. Originally with 4.4 connecting the camera often resulted in complete hang of the system (apparently not even SysRq worked, though I did not test that personally since it is a system I'm administering remotely for a family member). There was always a null pointer dereference just before the hang, so I suspect that is the culprit (see the attached kernel log). After some updates the system no longer hangs. I suspect this was fixed by going from linux 4.4 to 4.8. However, the webcam still often doesn't work and most application just return error. This is usually fixed after several tries, but sometimes it is necessary to reboot computer. Updating BIOS didn't help. The kernel logs still contain the same null pointer dereference with exactly the same stack trace for both 4.8 and 4.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705900/+subscriptions -- Mailing list: https://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 1584542] Re: Wifi Adapter Fails to come up after restart. after power off works fine
I found a workaround. Maybe someone find it useful. In kernel source, file: drivers/net/wireless/ralink/rt2x00/rt2800lib.c function: int rt2800_wait_wpdma_ready(struct rt2x00_dev *rt2x00dev) replace: return -EACCES; by: return 0; That forces the code to continue even if the card seems to be busy. But it works for me. Maybe is not really busy... Who knows. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584542 Title: Wifi Adapter Fails to come up after restart. after power off works fine Status in linux package in Ubuntu: Expired Bug description: I just installed Ubuntu Gnome 16.04 on my Laptop and I have noticed that Wifi somtimes doesn't work. after observing the problem I have come to the conclusion that it doesn't work after a reboot. I need to power it off and then back on to get the WiFi adapter working. my laptop is HP Pavilion and using a Ralink RT3290 Wireless adapter. this is the dmesg output when it's working: [ 12.190373] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 12.198413] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected [ 12.230518] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 22.490620] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 22.566482] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 this is when it's not working: [ 12.434107] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected [ 12.437567] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected [ 12.453872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 22.603249] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin' [ 22.634727] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37 [ 24.250054] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 25.850083] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 25.851000] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5) [ 27.994185] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 29.594240] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x0068] [ 29.595203] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hussain2002 F pulseaudio /dev/snd/controlC0: hussain2002 F pulseaudio CurrentDesktop: GNOME Date: Mon May 23 00:52:12 2016 HibernationDevice: RESUME=UUID=50a78741-d9a5-4656-a841-0c17259a4155 InstallationDate: Installed on 2016-05-22 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=69cc5799-74c4-41f7-b65d-5f9dafb54f43 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd08/08/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08971030410610100:rvnHewlett-Packard:rn2166:rvr29.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 08971030410610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
Likewise, on a non-congested network (802.11ac), directly from the laptop to the AP: uname -r 4.13.0-rc1 ➜ linux git:(5771a8c08880) ✗ cat /proc/sys/net/ipv4/tcp_congestion_control bbr ➜ linux git:(5771a8c08880) ✗ iperf3 -u -b 1000M -c rtr Connecting to host rtr, port 5201 [ 4] local 10.10.10.76 port 49939 connected to rtr port 5201 [ ID] Interval Transfer Bandwidth Total Datagrams [ 4] 0.00-1.00 sec 24.6 MBytes 207 Mbits/sec 3153 [ 4] 1.00-2.00 sec 27.2 MBytes 228 Mbits/sec 3484 [ 4] 2.00-3.00 sec 26.9 MBytes 226 Mbits/sec 3441 [ 4] 3.00-4.00 sec 26.8 MBytes 225 Mbits/sec 3432 [ 4] 4.00-5.00 sec 27.0 MBytes 226 Mbits/sec 3453 [ 4] 5.00-6.00 sec 27.2 MBytes 228 Mbits/sec 3479 [ 4] 6.00-7.00 sec 26.7 MBytes 224 Mbits/sec 3421 [ 4] 7.00-8.00 sec 27.3 MBytes 229 Mbits/sec 3492 [ 4] 8.00-9.00 sec 27.2 MBytes 228 Mbits/sec 3484 [ 4] 9.00-10.00 sec 27.0 MBytes 227 Mbits/sec 3457 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth JitterLost/Total Datagrams [ 4] 0.00-10.00 sec 268 MBytes 225 Mbits/sec 0.035 ms 8231/34295 (24%) [ 4] Sent 34295 datagrams iperf Done. ➜ linux git:(5771a8c08880) ✗ iperf3 -c rtr Connecting to host rtr, port 5201 [ 4] local 10.10.10.76 port 48172 connected to rtr port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 1.70 MBytes 14.2 Mbits/sec0 11.3 KBytes [ 4] 1.00-2.00 sec 1.59 MBytes 13.4 Mbits/sec0 8.48 KBytes [ 4] 2.00-3.00 sec 1.49 MBytes 12.5 Mbits/sec0 11.3 KBytes [ 4] 3.00-4.00 sec 1.54 MBytes 12.9 Mbits/sec0 11.3 KBytes [ 4] 4.00-5.00 sec 1.55 MBytes 13.0 Mbits/sec0 8.48 KBytes [ 4] 5.00-6.00 sec 1.50 MBytes 12.6 Mbits/sec0 8.48 KBytes [ 4] 6.00-7.00 sec 1.50 MBytes 12.6 Mbits/sec0 8.48 KBytes [ 4] 7.00-8.00 sec 1.47 MBytes 12.3 Mbits/sec0 8.48 KBytes [ 4] 8.00-9.00 sec 1.32 MBytes 11.1 Mbits/sec0 8.48 KBytes [ 4] 9.00-10.00 sec 1.43 MBytes 12.0 Mbits/sec0 8.48 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 15.1 MBytes 12.7 Mbits/sec0 sender [ 4] 0.00-10.00 sec 15.0 MBytes 12.6 Mbits/sec receiver iperf Done. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Update (2017-05-20): Kalle Valo suggested a hack which increased client -> AP TCP performance - so it does not look like a firmware issue as I thought originally, rather an ath10k driver issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11 https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom) Tested here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17 Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ - 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
@ Rex Tsai Thanks for prebuilt kernel. I've installed packages you provided via http://people.canonical.com/~chihchun/lp1680904/ Will try to test it for a while and write if I got any news/conclusions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7 11:20:28 doe kernel: [26003.797523] Call Trace: Apr 7 11:20:28 doe kernel:
[Kernel-packages] [Bug 1705586] Re: Mute key LED does not work on HP ProBook 440
I'm running it again Linux probook 4.12.0-041200-generic #201707022031 SMP Mon Jul 3 00:32:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705586 Title: Mute key LED does not work on HP ProBook 440 Status in linux package in Ubuntu: Confirmed Bug description: this is probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I was asked to file a new bug. The mute button on my laptop has a led that changes the color based on the status of the audio-master channel. At least it should. There is a slider for the LED in alsamixer but it doesn't change anything. Are there any tests I should run? cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17 --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 2550 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=4ce0e490-8f95-4de2-9a8f-456e1455444d InstallationDate: Installed on 2015-06-07 (774 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04ca:7063 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic.efi.signed root=UUID=27108123-06bd-4347-a0c5-9ea2ba62a034 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-07-09 (11 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2017 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.06 dmi.board.name: 822E dmi.board.vendor: HP dmi.board.version: KBC Version 42.65 dmi.chassis.asset.tag: 5CD709684F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.06:bd06/18/2017:svnHP:pnHPProBook440G4:pvr:rvnHP:rn822E:rvrKBCVersion42.65:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 440 G4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586/+subscriptions -- Mailing list: https://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 1436940] Re: Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041] is not supported
great instructions and explanations! it works for my lenovo ideapad, ubuntu 16.1 and atheros card, thank you very much! best Bert -- 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/1436940 Title: Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041] is not supported Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux source package in Xenial: Invalid Status in linux-firmware source package in Xenial: Invalid Bug description: The firmware for this card isn't included with Ubuntu. The firmware provided in /lib/firmware/ath10k/QCA6174 in Ubuntu 16.04 crashes when used with this card. This included firmware is likely for the QCA6174 instead of this card, the QCA6164. Yes, you read that right: the files for the QCA6164 need to be a folder called QCA6174 in order for the card to work. Running "modprobe ath10k_pci" shows that the ath10k_pci module looks for firmware in a folder called QCA6174, but not in any folder called QCA6164. It seems that before this issue can be resolved, the ath10k_pci module must be changed so that it recognizes firmware for both the QCA6164 and QCA6174, in separate folders. --- HOW TO GET THIS CARD TO WORK: 1) Use a kernel that supports this card According to WikiDevi, support for this card was added in kernel 4.3. If you're running Ubuntu 16.04 LTS or above, your kernel is fine; skip to the next step. If you're running Ubuntu 15.10 or below, see https://wiki.ubuntu.com/Kernel/MainlineBuilds for info on installing a newer kernel. Alternatively, you can use backports. This is a lot more work, but if you really need to keep using an older kernel for some reason, there are some guides to installing backports in the comments below. 2) Get rid of the firmware folder for this card that's included with Ubuntu: sudo rm -r /lib/firmware/ath10k/QCA6174/ 3) Download the latest firmware: wget https://github.com/kvalo/ath10k-firmware/archive/master.zip 4) Unzip the downloaded file. Inside the ath10k-firmware-master folder is a folder named QCA6174. Copy the QCA6174 folder to /lib/firmware/ath10k: unzip master.zip sudo cp -r ath10k-firmware-master/QCA6174/ /lib/firmware/ath10k/ 5) Rename two of the firmware files like so: cd /lib/firmware/ath10k/QCA6174/hw2.1/ sudo mv firmware-5.bin_SW_RM.1.1.1-00157-QCARMSWPZ-1 firmware-5.bin cd /lib/firmware/ath10k/QCA6174/hw3.0/ sudo mv firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 firmware-4.bin 6) Reboot your computer. Run "lshw -C network" to see if your card is recognized. You can delete the files you downloaded earlier: cd ~ rm master.zip rm -r ath10k-firmware-master/ I've verified that this works with Ubuntu 16.04 LTS (with kernel 4.4.0-21-generic); let me know if it doesn't work for you in the comments below. --- Miles Krell Last updated May 23, 2016 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+subscriptions -- Mailing list: https://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 1705586] Re: Mute key LED does not work on HP ProBook 440
Do you use kernel version > 4.12? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705586 Title: Mute key LED does not work on HP ProBook 440 Status in linux package in Ubuntu: Confirmed Bug description: this is probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I was asked to file a new bug. The mute button on my laptop has a led that changes the color based on the status of the audio-master channel. At least it should. There is a slider for the LED in alsamixer but it doesn't change anything. Are there any tests I should run? cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17 --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 2550 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=4ce0e490-8f95-4de2-9a8f-456e1455444d InstallationDate: Installed on 2015-06-07 (774 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04ca:7063 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic.efi.signed root=UUID=27108123-06bd-4347-a0c5-9ea2ba62a034 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-07-09 (11 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2017 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.06 dmi.board.name: 822E dmi.board.vendor: HP dmi.board.version: KBC Version 42.65 dmi.chassis.asset.tag: 5CD709684F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.06:bd06/18/2017:svnHP:pnHPProBook440G4:pvr:rvnHP:rn822E:rvrKBCVersion42.65:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 440 G4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586/+subscriptions -- Mailing list: https://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 1705586] Re: Mute key LED does not work on HP ProBook 440
hello kai, unfortunately adding "options snd-hda-intel mode=mute-led-gpio" to "/etc/modprobe.d/alsa-base.conf didn't work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705586 Title: Mute key LED does not work on HP ProBook 440 Status in linux package in Ubuntu: Confirmed Bug description: this is probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I was asked to file a new bug. The mute button on my laptop has a led that changes the color based on the status of the audio-master channel. At least it should. There is a slider for the LED in alsamixer but it doesn't change anything. Are there any tests I should run? cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17 --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 2550 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=4ce0e490-8f95-4de2-9a8f-456e1455444d InstallationDate: Installed on 2015-06-07 (774 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04ca:7063 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic.efi.signed root=UUID=27108123-06bd-4347-a0c5-9ea2ba62a034 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-07-09 (11 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2017 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.06 dmi.board.name: 822E dmi.board.vendor: HP dmi.board.version: KBC Version 42.65 dmi.chassis.asset.tag: 5CD709684F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.06:bd06/18/2017:svnHP:pnHPProBook440G4:pvr:rvnHP:rn822E:rvrKBCVersion42.65:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 440 G4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586/+subscriptions -- Mailing list: https://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 1511842] Re: Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Operation not supported.
I have the same problem: but I'm using ubuntu 16.04 LTS with Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter (rev 01) -- 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/1511842 Title: Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Operation not supported. Status in bcmwl package in Ubuntu: New Bug description: help me ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.0.2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.11 Architecture: i386 Date: Sat Oct 31 03:12:34 2015 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1511842/+subscriptions -- Mailing list: https://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 1705882] [NEW] Bluetooth connection to device fails from Ubuntu 16.04
Public bug reported: Bluetooth connection to a bluetooth IOIO device fails using a USB bluetooth adapter from a Ubuntu 16.04 system. The same device could be successfully connected using two non-Ubuntu systems: a) The same system hardware setup (dual-boot) running Windows 8 could connect without any problems. Also could run applications using serial-port associated with this connection. b) Android Note 4 device using bluetooth was able to successfully connect and run apps. Therefore, it was concluded that the Ubuntu 16.04 bluetooth service has a problem. Note: The USB bluetooth adapter used: BTA8000 from Cirago on the ubuntu system as well as the IOIO device. The adapters on the device and system have been verified to have different MAC addresses and works well with other devices. Procedure: Using the Bluetooth control in system-tray -> Bluetooth settings -> +, the device was located as IOIO (8A:22). Here, device was clicked upon, changed PIN to 4545 and pressing next resulted in the device being successfully added. However, the system-tray status of the device continues to say Connection is OFF. Attempting to turnon connection results in changing the system-tray blue-tooth icon to Keys- Icon for few seconds and then reverting back to the bluetooth icon. The device remains in disconnected state and cannot be accessed. The btmon trace (log-line 1277) and bluetoothd syslog (log-line 405) logs seem to indicate that the local host is sending a disconnect request after receiving a SDP: Service Search Attribute Response from the device. The src/device.c:connect_profiles() /org/bluez/hci0/dev_00_1B_DC_06_8A_22 (all), client :1.73 must result in connection setup - not disconnect. Log information was collected for the above procedure. systemInfo.txt: Information about the system bluetooth. syslog.blue: syslog with busr/lib/bluetooth/bluetoothd --noplugin=sap -d in /lib/systemd/system/bluetooth.service btmon.log: result of running sudo btmon ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 23 01:28:38 2017 InstallationDate: Installed on 2017-06-03 (49 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InterestingModules: rfcomm bnep btusb bluetooth JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Hewlett-Packard HP ENVY dv7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed root=UUID=1c1d284c-53a1-46dc-bc01-8555da60ad7e ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181C dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/02/2012:svnHewlett-Packard:pnHPENVYdv7NotebookPC:pvr088A1130592620100:rvnHewlett-Packard:rn181C:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY dv7 Notebook PC dmi.product.version: 088A1130592620100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:1B:DC:06:89:C5 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:242328 acl:898 sco:0 events:316 errors:0 TX bytes:11991 acl:125 sco:0 commands:112 errors:0 syslog: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "log.tar.gz" https://bugs.launchpad.net/bugs/1705882/+attachment/4919585/+files/log.tar.gz -- 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/1705882 Title: Bluetooth connection to device fails from Ubuntu 16.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth connection to a bluetooth IOIO device fails using a USB bluetooth adapter from a Ubuntu 16.04 system. The same device could be successfully connected using two non-Ubuntu systems: a) The same system hardware setup (dual-boot) running Windows 8 could connect without any problems. Also could run applications using serial-port associated with this connection. b) Android Note 4 device using
[Kernel-packages] [Bug 1705586] Re: Mute key LED does not work on HP ProBook 440
Add "options snd-hda-intel mode=mute-led-gpio" to "/etc/modprobe.d/alsa- base.conf", see if this works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705586 Title: Mute key LED does not work on HP ProBook 440 Status in linux package in Ubuntu: Confirmed Bug description: this is probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683277, but I was asked to file a new bug. The mute button on my laptop has a led that changes the color based on the status of the audio-master channel. At least it should. There is a slider for the LED in alsamixer but it doesn't change anything. Are there any tests I should run? cat /proc/version_signature > Ubuntu 4.10.0-28.32-generic 4.10.17 --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benjamin 2550 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=4ce0e490-8f95-4de2-9a8f-456e1455444d InstallationDate: Installed on 2015-06-07 (774 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04ca:7063 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic.efi.signed root=UUID=27108123-06bd-4347-a0c5-9ea2ba62a034 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: Upgraded to zesty on 2017-07-09 (11 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2017 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.06 dmi.board.name: 822E dmi.board.vendor: HP dmi.board.version: KBC Version 42.65 dmi.chassis.asset.tag: 5CD709684F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.06:bd06/18/2017:svnHP:pnHPProBook440G4:pvr:rvnHP:rn822E:rvrKBCVersion42.65:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 440 G4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
