[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
Why does *removing* a linux-image-extra package cause post-*installation* scripts to be run? This sounds like a bug on the kernel side, to me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: New Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 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.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79: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/update-notifier/+bug/1458204/+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 1669071] Re: package linux-firmware 1.127.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Expired -- 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/1669071 Title: package linux-firmware 1.127.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux-firmware package in Ubuntu: Expired Bug description: whenever i try to update my operating system (linux ubuntu 14.04) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.127.23 ProcVersionSignature: Ubuntu 3.13.0-73.116-generic 3.13.11-ckt30 Uname: Linux 3.13.0-73-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.23 Architecture: i386 Date: Wed Mar 1 18:47:27 2017 Dependencies: DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-05-22 (1014 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: linux-firmware Title: package linux-firmware 1.127.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 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/1669071/+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 1687353] Re: System freezes due to ALSA error and recovers after significant time
** Description changed: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. + Edit: one thing I noticed with indicator-multiload, the internal HDD + activity completely stopped while this problem was happening and soon + after it started to function. It was like the computer was recovering + with the internal HDD turned off. The HDD usage ramped up and the system + returned to normal. May this be related with the power management + issues? + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: - gcc-6-base 6.0.1-0ubuntu1 - libasound2-data 1.1.0-0ubuntu1 - libc6 2.23-0ubuntu7 - libgcc1 1:6.0.1-0ubuntu1 + gcc-6-base 6.0.1-0ubuntu1 + libasound2-data 1.1.0-0ubuntu1 + libc6 2.23-0ubuntu7 + libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: New Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting.
[Kernel-packages] [Bug 1687353] [NEW] System freezes due to ALSA error and recovers after significant time
Public bug reported: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. Edit: one thing I noticed with indicator-multiload, the internal HDD activity completely stopped while this problem was happening and soon after it started to function. It was like the computer was recovering with the internal HDD turned off. The HDD usage ramped up and the system returned to normal. May this be related with the power management issues? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "syslog when the freeze occurred" https://bugs.launchpad.net/bugs/1687353/+attachment/4870156/+files/PULSEKERNELALSA -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: New Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to
[Kernel-packages] [Bug 1686268] Re: Backlight brightness level not restored after reboot
I forgot to say that the above output comes after commenting out the @reboot cron entry workaround and restarting, so it is exactly what it does without any workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686268 Title: Backlight brightness level not restored after reboot Status in linux package in Ubuntu: Incomplete Bug description: I am not sure if this is the right place to report this, so feel free to move it elsewhere. It looks like the systemd-backlight service (/lib/systemd/system /systemd-backlight@.service) does not restore the brightness level (although it saves it before shut-down). However the following command does restore the saved brightness: sudo /lib/systemd/systemd-backlight load backlight:intel_backlight As a temporary solution to automate it at boot I am using the following line added to the root cron: @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight - Ubuntu 4.10.0-20.22-generic 4.10.8 - Gnome 3.24 Please, let me know if you need more info. Thanks. --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dd 1540 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-12 (13 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170411) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=/dev/mapper/nvme-ubuntu_gnome ro systemd.restore_state=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/29/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+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 1686268] Re: Backlight brightness level not restored after reboot
The exact command you wrote: $ systemctl status systemd-backlight@intel_backlight.service systemd-backlight@intel_backlight.service - Load/Save Screen Backlight Brightness of intel_backlight Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-backlight@.service(8) However the following one (with an added "backlight:") gives a different answer: $ systemctl status systemd-backlight@backlight:intel_backlight.service systemd-backlight@backlight:intel_backlight.service - Load/Save Screen Backlight Brightness of backlight:intel_backlight Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; vendor preset: enabled) Active: active (exited) since Mon 2017-05-01 09:50:53 +07; 9min ago Docs: man:systemd-backlight@.service(8) Main PID: 446 (code=exited, status=0/SUCCESS) May 01 09:50:52 x1 systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight... May 01 09:50:53 x1 systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:intel_backlight. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686268 Title: Backlight brightness level not restored after reboot Status in linux package in Ubuntu: Incomplete Bug description: I am not sure if this is the right place to report this, so feel free to move it elsewhere. It looks like the systemd-backlight service (/lib/systemd/system /systemd-backlight@.service) does not restore the brightness level (although it saves it before shut-down). However the following command does restore the saved brightness: sudo /lib/systemd/systemd-backlight load backlight:intel_backlight As a temporary solution to automate it at boot I am using the following line added to the root cron: @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight - Ubuntu 4.10.0-20.22-generic 4.10.8 - Gnome 3.24 Please, let me know if you need more info. Thanks. --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dd 1540 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-12 (13 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170411) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=/dev/mapper/nvme-ubuntu_gnome ro systemd.restore_state=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/29/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+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 1687267] Re: kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!
I have had what I think is the same problem (it requires restarting the whole system): [85581.367885] [ cut here ] [85581.367926] kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129! [85581.367967] invalid opcode: [#1] SMP [85581.367988] Modules linked in: cmac rfcomm bnep hid_generic dell_wmi sparse_keymap snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_core coretemp snd_hwdep dell_laptop dell_smbios kvm_intel kvm dcdbas irqbypass crct10dif_pclmul crc32_pclmul snd_pcm ghash_clmulni_intel pcbc snd_seq_midi snd_seq_midi_event aesni_intel uvcvideo aes_x86_64 videobuf2_vmalloc crypto_simd glue_helper cryptd intel_cstate videobuf2_memops videobuf2_v4l2 intel_rapl_perf usbhid snd_rawmidi videobuf2_core uas hid videodev arc4 usb_storage media snd_seq ath9k input_leds joydev ath9k_common serio_raw ath9k_hw ath3k btusb btrtl btbcm snd_seq_device snd_timer ath btintel mac80211 bluetooth cfg80211 lpc_ich snd soundcore mei_me shpchp [85581.368323] mei acpi_als kfifo_buf industrialio mac_hid binfmt_misc parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt psmouse fb_sys_fops ahci drm libahci wmi video fjes [85581.368432] CPU: 1 PID: 15936 Comm: firefox Not tainted 4.10.0-20-generic #22-Ubuntu [85581.368470] Hardware name: Dell Inc. Dell System XPS L322X/0PJHXN, BIOS A09 05/15/2013 [85581.368512] task: 88322e1a1680 task.stack: a74208398000 [85581.368548] RIP: 0010:__migration_entry_wait+0x16a/0x180 [85581.368575] RSP: :a7420839bd68 EFLAGS: 00010246 [85581.368601] RAX: 000fc0048078 RBX: e16f80d4f170 RCX: e16f80d4f170 [85581.368636] RDX: 0001 RSI: 8830353c5800 RDI: e16f8198c000 [85581.368669] RBP: a7420839bd80 R08: 88322d6f5d00 R09: 88322d6f5d00 [85581.368703] R10: 0001 R11: 0438 R12: e16f8198c000 [85581.368737] R13: 3e066300 R14: a7420839be30 R15: 883017cfd4b0 [85581.368772] FS: 7fcfc4066740() GS:88323f24() knlGS: [85581.368811] CS: 0010 DS: ES: CR0: 80050033 [85581.368839] CR2: 7fcf43b00b30 CR3: 0001dc64f000 CR4: 001406e0 [85581.368873] Call Trace: [85581.368891] migration_entry_wait+0x74/0x80 [85581.368916] do_swap_page+0x5b3/0x770 [85581.368937] handle_mm_fault+0x873/0x1360 [85581.368959] __do_page_fault+0x23e/0x4e0 [85581.368981] do_page_fault+0x22/0x30 [85581.369003] page_fault+0x28/0x30 [85581.369022] RIP: 0033:0x5589b0c2f278 [85581.369041] RSP: 002b:7ffdfdeb9e40 EFLAGS: 00010283 [85581.369067] RAX: 7fcfc2c001b0 RBX: 0010 RCX: 0003 [85581.369102] RDX: 7fcf43b00b30 RSI: 000c RDI: 7fcfc2c001a8 [85581.369135] RBP: 7fcfc2c001a0 R08: 7fcfc2c00040 R09: 7fcf233eec70 [85581.369168] R10: 0001 R11: 0438 R12: 7fcfc2c00040 [85581.369202] R13: R14: 7fcf43b00b30 R15: 7fcf258a [85581.369235] Code: ff ff ff 4c 89 e7 e8 96 a2 f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb [85581.369351] RIP: __migration_entry_wait+0x16a/0x180 RSP: a7420839bd68 [85581.380908] ---[ end trace d138c13e149bf666 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687267 Title: kernel BUG at /build/linux- 2NWldV/linux-4.10.0/include/linux/swapops.h:129! Status in linux package in Ubuntu: Confirmed Bug description: First traceback looks to be the cause. The second traceback is the effect that followed (repeatedly). Don't think it's specific to system76. Apr 30 09:56:10 galago kernel: [97085.090114] [ cut here ] Apr 30 09:56:10 galago kernel: [97085.090137] kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129! Apr 30 09:56:10 galago kernel: [97085.090157] invalid opcode: [#1] SMP Apr 30 09:56:10 galago kernel: [97085.090167] Modules linked in: nls_iso8859_1 uas usb_storage ccm rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc aufs ec_sys cmac bnep arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_via ghash_clmulni_intel snd_hda_codec_generic pcbc snd_hda_intel snd_hda_codec iwlmvm snd_hda_core snd_hwdep aesni_intel snd_pcm uvcvideo mac80211 aes_x86_64 snd_seq_midi videobuf2_vmalloc crypto_simd snd_seq_midi_event glue_helper
[Kernel-packages] [Bug 1502668] Re: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01)
Hey, i'm having the same issue with [14e4:4365] (rev 01) on Ubuntu 16.04 LTS, The connection have really slow signal, WiFi bars moves constantly, It is also really unstable, i have to reconnect all the time. I have this issue for a couple of years now, i hope you can do something about it. I will really appreciated it. -- 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/1502668 Title: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Status in bcmwl package in Ubuntu: Confirmed Bug description: WIFI connection not works properly, after clicking on a URL lots of re-connecting of starts, for that security password input always is necessary in spite of password was stored, if connection is established, data flow is extremely low - no chance to load websites ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: wl (not installed) ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 19:08:51 2015 InstallationDate: Installed on 2015-09-22 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150922) SourcePackage: wl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1502668/+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 1613158] Re: Booting with Nvidia GTX 970 hangs with an orange/corrupt screen in kernels 4.8-4.11 (but works with 4.4.0)
This is happening to me too on released 17.04 64bit. Also with a GTX 970. 16.04 worked just fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1613158 Title: Booting with Nvidia GTX 970 hangs with an orange/corrupt screen in kernels 4.8-4.11 (but works with 4.4.0) Status in linux package in Ubuntu: Confirmed Bug description: Booting with Nvidia GTX 970 hangs with an orange screen in kernels 4.7 and 4.8rc1 (but works with 4.4.0). I've tried: * Plain yakkety 4.4.0-34-generic * Mainline kernel 4.7 * Mainline kernel 4.8rc1 and only the first one works. Kernels 4.7 and 4.8rc1 freeze with a bright orange screen. Best I can tell, the frozen orange screen coincides with kernel log messages: Aug 15 12:24:23 x51 kernel: [1.761197] fb: switching to nouveaufb from simple Aug 15 12:24:23 x51 kernel: [1.761210] Console: switching to colour dummy device 80x25 ... Aug 15 12:24:26 x51 kernel: [ 11.896160] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.897225] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.898292] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.899358] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.900423] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.901489] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.902555] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.903621] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.904686] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.905753] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.906818] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.907883] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.908949] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.910014] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.911079] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.912145] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] Aug 15 12:24:26 x51 kernel: [ 11.913210] nouveau :01:00.0: fifo: SCHED_ERROR 08 [] ... ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613158/+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 1458204] Re: removing kernels should not require a restart afterward
When removing a linux-image-extra package, kernel post-installation scripts including /etc/kernel/postinst.d/update-notifier will be run. That is a symbolic link to /usr/share/update-notifier/notify-reboot- required, which can be modified to fix this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: New Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 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.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79: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/update-notifier/+bug/1458204/+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 1684010] Re: 17.04, i915 freeze on VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
4.10.0 from mainline works fine here. Running it for two days now without flaws. $ uname -a Linux piccard 4.10.0-041000-generic #201702191831 SMP Sun Feb 19 23:33:19 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Hmm. 4.10.0 from mainline works, 4.10.0(.19) from the regular repo does not. Now I'm not sure which one to test next, because I don't know how numbers of the regular repo are related to numbers of the mainline repo. Is 4.10-rc5 or 4.10.6 the next candidate? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1684010 Title: 17.04, i915 freeze on VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Status in linux package in Ubuntu: Confirmed Bug description: Just freezes all unity and/or X. Nothing in any logs though. 16.10 worked just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684010/+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 1458204] Re: removing kernels should not require a restart afterward
** Also affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Also affects: update-notifier Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: New Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 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.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79: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/update-notifier/+bug/1458204/+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 1634881] Re: Installation/Live-System freezes on Splash screen
I found a sad solution for me now. After more than 10 years of ubuntu, I installed Windows 10 on my laptop. Just because it works way better with all that hardware. Now I can actually use it like it is meant to be used. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634881 Title: Installation/Live-System freezes on Splash screen Status in linux package in Ubuntu: Confirmed Bug description: A USB Stick prepared with 16.04.1 no matter whether "Try Ubuntu" or "Install" is chosen, it freezes on splash-Screen. With "quiet splash" removed, I get the output on the picture attached. In the last line it says: "BUG Can't handle kernel" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634881/+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 1645631] Re: Sending files fails because obex not loaded
Happens in Zesty too. Updated from previous distribution versions 16.04->16.10->17.04. Manually starting the service fixes the problem until reboot. -- 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/1645631 Title: Sending files fails because obex not loaded Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: If I run bluetooth-sendto from command line and try to send the file, it quits after selecting the target device with following command line output: "Acquiring proxy failed: Error calling StartServiceByName for org.bluez.obex: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.obex.service not found." After I run "systemctl --user start obex", it proceeds to send the file. Even then it for some reason gets stuck, but I do not know what causes it and it is probably a different problem. This system is upgraded from xenial. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-bluetooth 3.20.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Nov 29 11:04:11 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-12 (77 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=fi TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to yakkety on 2016-11-01 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645631/+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 1645631] Re: Sending files fails because obex not loaded
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-bluetooth (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1645631 Title: Sending files fails because obex not loaded Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: If I run bluetooth-sendto from command line and try to send the file, it quits after selecting the target device with following command line output: "Acquiring proxy failed: Error calling StartServiceByName for org.bluez.obex: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.obex.service not found." After I run "systemctl --user start obex", it proceeds to send the file. Even then it for some reason gets stuck, but I do not know what causes it and it is probably a different problem. This system is upgraded from xenial. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-bluetooth 3.20.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Nov 29 11:04:11 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-12 (77 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=fi TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to yakkety on 2016-11-01 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645631/+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 1645631] Re: Sending files fails because obex not loaded
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1645631 Title: Sending files fails because obex not loaded Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: If I run bluetooth-sendto from command line and try to send the file, it quits after selecting the target device with following command line output: "Acquiring proxy failed: Error calling StartServiceByName for org.bluez.obex: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.obex.service not found." After I run "systemctl --user start obex", it proceeds to send the file. Even then it for some reason gets stuck, but I do not know what causes it and it is probably a different problem. This system is upgraded from xenial. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-bluetooth 3.20.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Nov 29 11:04:11 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-12 (77 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=fi TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to yakkety on 2016-11-01 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645631/+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 1681838] Re: IR pilot is not working after kernel change from 3.13 to 4.4
Re-assigning to kernel packagem possiblye the wrong one., ** Package changed: lirc (Ubuntu) => kernel-package (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/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.127.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M 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.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 Tags: trusty Uname: Linux 4.11.0-041100rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1681838/+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 1681062] Re: Bluetooth doesn't work after update to 17.04
Some additional info: Bluetooth stop wokring after hibernation, but not always. Only way to get it work again is to completly power off computer and turn it on, reboot doesn't help. -- 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/1681062 Title: Bluetooth doesn't work after update to 17.04 Status in bluez package in Ubuntu: New Bug description: After update to 17.04 bluetooth stopped to work. some logs that could be useful: asudak@asudak-Inspiron-One-2330:~$ hciconfig hci0: Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:38 errors:7 asudak@asudak-Inspiron-One-2330:~$ sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sat Apr 8 13:04:36 2017 InstallationDate: Installed on 2013-12-27 (1197 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron One 2330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=13b39ae0-892a-4b5a-ab81-62dba9463c1a ro quiet splash radeon.dpm=1 radeon.runpm=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to zesty on 2017-02-25 (41 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09JR1D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 27147636_1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/13/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn09JR1D:rvrA00:cvnDellInc.:ct13:cvr27147636_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:40 errors:9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1681062/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Hello I installed 17.04 on my Gigybyte 370 Gaming 5/Ryzen 1700x with acpi=off und integrated the the 4.11RC8 Kernal into that installled Version - but without apcpi=off it still crashes like before. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1667160] Re: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2
Having similar issues (kernel panic, not being able to connect to wireless networks both from network manager and nmtui) with RTL8188CUS wifi adapter on Ubuntu Mate 16.04 and now on 17.04. Following the instructions here solved the problem: https://sites.google.com/site/easylinuxtipsproject/reserve-7#TOC-Realtek-RTL8188CUS-and-RTL8192CU-chipsets-0bda:8176-and-0bda:8178- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667160 Title: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2 Status in linux package in Ubuntu: Confirmed Status in linux-meta-raspi2 package in Ubuntu: Confirmed Bug description: I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And there's a RTL2838 DVB-T USB stick attached to monitor airplane positions for Flightradar24. After updateing the kernel from 4.8.0-1024, which runs flawlessly, to -1025, there's a kernel panic happening 10-20 seconds after booting up to the login prompt. I thought the -1026 fixed that, but it's still no worky. The trace is scrolling so fast I can't read anything but the last page: [<808c76c8>] (sock_sendmsg) from... [<808c7778>] (sock_write_iter) from... [<802c39c8>] (new_sync_write) from... [<802c3a4c>] (__vfs_write) from... [<802c48d8>] (vfs_write) from... [<802c5ab4>] (SyS_write) from... Code: e5922004 e0033002 e353 0a0a (e5902034) ---[ end trace 0f53d17efe0c6ba ]--- Kernel panic - not syncing: Fatal exception in interrupt CPU2: stopping CPU: 2 PID: 21 Comm: migration/2 Tainted: G D 4.8.0-1026-raspi2 #29-Ubuntu Hardware name: BCM2709 [<801120ac>] (unwind_backtrace) from ... [<8010d2dc>] (show_stack) from ... [<8059c38c>] (handle_IPI) from ... [<80101564>] (bcm2836_arm_irqchip_handle_irq) from [<80a49f3c>] (__irq_svc+0x5c/0x7c) Exception stack(0xbb99de68 to 0xbb99deb0) de60: 0004 0001 bac05de0 0001 de80: bac05dcc a00e0013 bac05d6c bb99dedc bb99dee0 bb99deb8 dea0: 801d367c 801d35f4 600e0013 [<80a49f3c>] (__irq_svc) from ... [<801d35f4>] (multi_cpu_stop) from ... [<801d38ec>] (cpu_stopper_thread) from ... [<8014b71c>] (smpboot_thread_fn) from ... [<80147770>] (kthread) from [<80108e28>] (ret_from_fork+0x14/0x2c) And then this block repeats with CPU3 and CPU0. Going back to 4.8.0-1024 makes everything work again. Affected packages: linux-image-4.8.0-1025-raspi2:armhf (4.8.0-1025.28) linux-image-4.8.0-1026-raspi2:armhf (4.8.0-1026.29) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 25 2016 seq crw-rw 1 root audio 116, 33 Jul 25 2016 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-1024-raspi2. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.3-0ubuntu8.2 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.10 Lsusb: Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0xecd3f749 smsc95xx.macaddr=B8:27:EB:D3:F7:49 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3ea0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait ProcVersionSignature: Ubuntu 4.8.0-1024.27-raspi2 4.8.16 RelatedPackageVersions: linux-restricted-modules-4.8.0-1024-raspi2 N/A linux-backports-modules-4.8.0-1024-raspi2 N/A linux-firmware 1.161.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.8.0-1024-raspi2 armv7l UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to yakkety on 2016-10-24 (122 days ago) UserGroups: adm audio cdrom dialout floppy fuse netdev plugdev sudo users video www-data _MarkForUpload: False To manage notifications about this bug go to:
[Kernel-packages] [Bug 1643455] Re: Bluetooth does not work but WiFi does on Intel 7265 with both Ubuntu 16.04 and 16.10
No improvement. # uname -a Linux galois-l 4.11.0-041100rc7-generic #201704161731 SMP Sun Apr 16 21:32:58 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # hcitool dev Devices: # hcitool scan Device is not available: No such device -- 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/1643455 Title: Bluetooth does not work but WiFi does on Intel 7265 with both Ubuntu 16.04 and 16.10 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On an Acer V3-574-7481 with built-in stock Intel 7265 wireless hardware, WiFi works perfectly but Bluetooth does not. The System Settings applet reports "No Bluetooth adapters found" and the option to enable Bluetooth is grayed out. However, Bluetooth hardware is reported by "dmesg" and a firmware patch file is applied automatically during boot. *Bluetooth works on this same machine booted into Windows 10.* The machine is dual-boot from separate partitions. # uname -a Linux galois-l 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux # head -6 /etc/os-release NAME="Ubuntu" VERSION="16.10 (Yakkety Yak)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.10" VERSION_ID="16.10" # rfkill list 1: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no # lspci -knn | grep -A3 Net 03:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5010] Kernel driver in use: iwlwifi Kernel modules: iwlwifi # lsusb Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 002 Device 003: ID 04f2:b526 Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # hcitool dev Devices: # hcitool scan Device is not available: No such device # dmesg | grep -i bluetooth [ 26.310459] Bluetooth: Core ver 2.21 [ 26.310476] Bluetooth: HCI device and connection manager initialized [ 26.310478] Bluetooth: HCI socket layer initialized [ 26.310480] Bluetooth: L2CAP socket layer initialized [ 26.310483] Bluetooth: SCO socket layer initialized [ 26.514833] Bluetooth: hci0: read Intel version: 370810011003110e00 [ 26.794565] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq [ 26.987853] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [ 39.604402] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 39.604404] Bluetooth: BNEP filters: protocol multicast [ 39.604407] Bluetooth: BNEP socket layer initialized # locate ibt-hw /lib/firmware/intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq /lib/firmware/intel/ibt-hw-37.7.10-fw-1.0.2.3.d.bseq /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq /lib/firmware/intel/ibt-hw-37.7.bseq /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.2.27.d.bseq /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq /lib/firmware/intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq /lib/firmware/intel/ibt-hw-37.8.bseq # dpkg -S /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq linux-firmware: /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq # dpkg -s linux-firmware | grep Version Version: 1.161 This behavior was identical first under Ubuntu 16.04 and then under 16.10 after upgrade. Command and response examples above are under 16.10 after upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1643455/+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 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)
Update: After upgrading to 17.04 (i.e. kernel 4.10*), I no longer have this 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/1655356 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04) Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this problem started with errors, OOM and an eventual kernel panic. It can run fine for about 3-4 hours or so. I see the following errors on syslog (also attached w/ other logs and information I can gather). Jan 9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [kswapd0:50] Jan 9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:50] Jan 9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50] Jan 9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:50] Jan 8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0 Jan 9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0 Jan 9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0 Jan 8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long (2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 Jan 8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long (3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500 Jan 8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long (3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5 Jan 8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long (4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4 Jan 8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long (2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 Jan 8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long (3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500 Jan 9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long (3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500 Jan 9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long (4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500 Jan 9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long (6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250 Jan 9 07:36:53 gorilla kernel: [69325.386696] perf: interrupt took too long (7723 > 7712), lowering
[Kernel-packages] [Bug 1681838] Re: IR pilot is not working after kernel change from 3.13 to 4.4
For the sake of order, this bug should be re-assigned to the kernel package instead of the user-space lirc package. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681838 Title: IR pilot is not working after kernel change from 3.13 to 4.4 Status in linux package in Ubuntu: Confirmed Status in lirc package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 linux-image-4.4.0-72-generic I'm using custom IR receiver with CIR header in my ASRock MoBo. This one IR receiver serves 3 devices - HTPC, TV and amplifier. Everything was ok, but after kernel change from 3.13 to 4.4 my pilot stopped to work with HTPC. mode2 app shows, that IR header is receiving something, but there is something wrong. Example pulse-pause timings for 3.13 kernel are: space 2949 pulse 39 space 1157 pulse 39 space 1159 pulse 39 Example pulse-pause timings for 4.4 kernel are: space 16777176 pulse 1 space 16777176 pulse 1 space 16777176 pulse 1 for this same button. Maybe I'm not only one which wants still to use lirc_sir Please, help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Apr 11 11:55:14 2017 SourcePackage: lirc UpgradeStatus: Upgraded to trusty on 2014-05-03 (1073 days ago) mtime.conffile..etc.lirc.hardware.conf: 2017-04-10T19:55:43.264756 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dugi 10933 F pulseaudio /dev/snd/controlC0: dugi 10933 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e122fa67-c5de-4c9f-a5d7-29a46f392c41 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic root=UUID=417adaf4-1977-49fe-bb64-943e27d3da1b ro video=uvesafb:mode_option=1280x720-32@50,mtrr=3,scroll=ywrap,noedid nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.127.23 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: lirc_sir Tags: trusty staging trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A75 Pro4-M 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.60:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75Pro4-M: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. mtime.conffile..etc.lirc.hardware.conf: 2017-04-11T17:20:08.048386 mtime.conffile..etc.lirc.lircd.conf: 2014-06-11T20:46:26.833289 --- ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 Package: lirc 0.9.0-0ubuntu5 PackageArchitecture: amd64 Tags: trusty Uname: Linux 4.11.0-041100rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to trusty on 2014-05-03 (1074 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681838/+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 1686268] Re: Backlight brightness level not restored after reboot
What's the output of `systemctl status systemd- backlight@intel_backlight.service`? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686268 Title: Backlight brightness level not restored after reboot Status in linux package in Ubuntu: Incomplete Bug description: I am not sure if this is the right place to report this, so feel free to move it elsewhere. It looks like the systemd-backlight service (/lib/systemd/system /systemd-backlight@.service) does not restore the brightness level (although it saves it before shut-down). However the following command does restore the saved brightness: sudo /lib/systemd/systemd-backlight load backlight:intel_backlight As a temporary solution to automate it at boot I am using the following line added to the root cron: @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight - Ubuntu 4.10.0-20.22-generic 4.10.8 - Gnome 3.24 Please, let me know if you need more info. Thanks. --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dd 1540 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-12 (13 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170411) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=/dev/mapper/nvme-ubuntu_gnome ro systemd.restore_state=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/29/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+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 1682892] Re: failed command: READ FPDMA QUEUED
Now using:
4.8.0-49-generic #52-Ubuntu SMP Thu Apr 20 09:38:39 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
related to heavy disc load, typically an rsync running as part of
backup. But the sda drive is the only one that generates the errors,
sdb and sdc that actually have the backup files don't give errors.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1682892
Title:
failed command: READ FPDMA QUEUED
Status in linux package in Ubuntu:
Incomplete
Bug description:
occurs intermittently usually when under load, causes the system to
hang for a while, needs a reboot which then normally fixes the file
system errors.
Seems same symptoms and error message as bug 550559 but in a current
kernel.
I have a Seagate SSHD drive as ata5.
Trying the libata.force=noncq kernel param to see if the hangs and
errors go away.
Drive passes SMART self test.
RElevant part of kern.log:
Apr 14 16:52:01 mark-linux kernel: [14294.691801] ata5.00: exception Emask
0x0 SAct 0x8000 SErr 0x0 action 0x6
Apr 14 16:52:01 mark-linux kernel: [14294.691814] ata5.00: irq_stat 0x4008
Apr 14 16:52:01 mark-linux kernel: [14294.691823] ata5.00: failed command:
READ FPDMA QUEUED
Apr 14 16:52:01 mark-linux kernel: [14294.691839] ata5.00: cmd
60/08:78:77:46:25/00:00:62:00:00/40 tag 15 ncq dma 4096 in
Apr 14 16:52:01 mark-linux kernel: [14294.691839] res
41/84:08:78:46:25/00:00:62:00:00/00 Emask 0x410 (ATA bus error)
Apr 14 16:52:01 mark-linux kernel: [14294.691847] ata5.00: status: { DRDY ERR
}
Apr 14 16:52:01 mark-linux kernel: [14294.691853] ata5.00: error: { ICRC ABRT
}
Apr 14 16:52:01 mark-linux kernel: [14294.691863] ata5: hard resetting link
Apr 14 16:52:01 mark-linux kernel: [14295.167467] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
Apr 14 16:52:02 mark-linux kernel: [14295.244272] ata5.00: configured for
UDMA/133
Apr 14 16:52:02 mark-linux kernel: [14295.244286] ata5: EH complete
Apr 14 18:02:06 mark-linux kernel: [18500.172587] ata5.00: exception Emask
0x0 SAct 0x7fff SErr 0x0 action 0x6 frozen
Apr 14 18:02:06 mark-linux kernel: [18500.172601] ata5.00: failed command:
WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172617] ata5.00: cmd
61/c8:00:17:0c:c0/00:00:5a:00:00/40 tag 0 ncq dma 102400 out
Apr 14 18:02:06 mark-linux kernel: [18500.172617] res
40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
Apr 14 18:02:06 mark-linux kernel: [18500.172625] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172631] ata5.00: failed command:
WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172643] ata5.00: cmd
61/a0:08:af:39:c7/01:00:5a:00:00/40 tag 1 ncq dma 212992 out
Apr 14 18:02:06 mark-linux kernel: [18500.172643] res
40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 14 18:02:06 mark-linux kernel: [18500.172650] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172655] ata5.00: failed command:
WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172667] ata5.00: cmd
61/30:10:6f:17:f2/00:00:5b:00:00/40 tag 2 ncq dma 24576 out
Apr 14 18:02:06 mark-linux kernel: [18500.172667] res
40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Apr 14 18:02:06 mark-linux kernel: [18500.172673] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172678] ata5.00: failed command:
WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172689] ata5.00: cmd
61/18:18:67:a4:25/00:00:62:00:00/40 tag 3 ncq dma 12288 out
Apr 14 18:02:06 mark-linux kernel: [18500.172689] res
40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Apr 14 18:02:06 mark-linux kernel: [18500.172696] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172701] ata5.00: failed command:
WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172712] ata5.00: cmd
61/20:20:b7:b7:25/00:00:62:00:00/40 tag 4 ncq dma 16384 out
Apr 14 18:02:06 mark-linux kernel: [18500.172712] res
40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 14 18:02:06 mark-linux kernel: [18500.172719] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172723] ata5.00: failed command:
WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172735] ata5.00: cmd
61/30:28:5f:d6:25/00:00:62:00:00/40 tag 5 ncq dma 24576 out
Apr 14 18:02:06 mark-linux kernel: [18500.172735] res
40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 14 18:02:06 mark-linux kernel: [18500.172741] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172746] ata5.00: failed command:
WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172758] ata5.00: cmd
61/08:30:17:8a:92/00:00:49:00:00/40 tag 6 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel:
[Kernel-packages] [Bug 1683341] Re: gstreamer-plugins-ugly-i386 dependency error
** 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/1683341 Title: gstreamer-plugins-ugly-i386 dependency error Status in linux package in Ubuntu: Confirmed Bug description: Attempting to install this gives the following: The following packages have unmet dependencies: gstreamer1.0-plugins-ugly:i386: Depends: gstreamer1.0-plugins-ugly-amr (= 1.8.3-1ubuntu1) but 1.8.3-1ubuntu1 is to be installed Depends: libc6 (>= 2.7) but 2.24-3ubuntu2 is to be installed Depends: libdvdread4 (>= 4.1.3) but 5.0.3-1 is to be installed Depends: libgcc1 (>= 1:3.0) but 1:6.2.0-5ubuntu12 is to be installed Depends: libglib2.0-0 (>= 2.40) but 2.50.2-2ubuntu1 is to be installed Depends: liborc-0.4-0 (>= 1:0.4.25) but 1:0.4.26-1 is to be installed Depends: libstdc++6 (>= 5) but 6.2.0-5ubuntu12 is to be installed The libc6 dependency is wrong, I would guess this should be 2.17 not 2.7 which doesn't exist. cat version.log Ubuntu 4.8.0-46.49-generic 4.8.17 --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 4535 F pulseaudio /dev/snd/controlC3: mark 4535 F pulseaudio /dev/snd/controlC2: mark 4535 F pulseaudio /dev/snd/controlC0: mark 4535 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=3e34a9fd-33a3-4027-86ff-5151122c5379 InstallationDate: Installed on 2010-03-14 (2590 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=bf8502af-6555-4b4c-a93f-11ee7121da7d ro quiet nosplash libata.force=noncq ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-46-generic N/A linux-backports-modules-4.8.0-46-generic N/A linux-firmware1.161.1 RfKill: Tags: yakkety Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout floppy fuse libvirt libvirtd lpadmin netdev plugdev powerdev sambashare scanner tape video _MarkForUpload: True dmi.bios.date: 03/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A87TD/USB3 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.:bvr2001:bd03/08/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A87TD/USB3: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/1683341/+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 1683376] Re: gstreamer-plugins-bad-i386 dependency error
** 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/1683376 Title: gstreamer-plugins-bad-i386 dependency error Status in linux package in Ubuntu: Confirmed Bug description: The problem here seems to be that the package is dependent upon itself. All the dependencies below are met and most are already installed including the last two. The following packages have unmet dependencies: gstreamer1.0-plugins-bad:i386: Depends: libc6 (>= 2.15) but 2.24-3ubuntu2 is to be installed Depends: libcurl3-gnutls (>= 7.16.2) but 7.50.1-1ubuntu1.1 is to be installed Depends: libdvdnav4 (>= 4.1.3) but 5.0.3-1 is to be installed Depends: libdvdread4 (>= 4.1.3) but 5.0.3-1 is to be installed Depends: libgcc1 (>= 1:3.0) but 1:6.2.0-5ubuntu12 is to be installed Depends: libglib2.0-0 (>= 2.40) but 2.50.2-2ubuntu1 is to be installed Depends: libgstreamer-plugins-bad1.0-0 (= 1.8.3-1ubuntu1.1) but 1.8.3-1ubuntu1.1 is to be installed Depends: libgtk-3-0 (>= 3.16.2) but 3.20.9-1ubuntu2.1 is to be installed Depends: libgudev-1.0-0 (>= 146) but 1:230-3 is to be installed Depends: libilmbase12 (>= 2.2.0) but 2.2.0-11ubuntu2 is to be installed Depends: libjpeg8 (>= 8c) but 8c-2ubuntu8 is to be installed Depends: libmodplug1 (>= 1:0.8.8.5) but 1:0.8.8.5-2 is to be installed Depends: libopenal1 (>= 1.14) but 1:1.17.2-1 is to be installed Depends: libopenjp2-7 (>= 2.0.0) but 2.1.1-1ubuntu0.1 is to be installed Depends: liborc-0.4-0 (>= 1:0.4.25) but 1:0.4.26-1 is to be installed Depends: librsvg2-2 (>= 2.36.2) but 2.40.16-1 is to be installed Depends: librtmp1 (>= 2.3) but 2.4+20151223.gitfa8646d.1-1 is to be installed Depends: libsoundtouch1 (>= 1.9.2) but 1.9.2-2 is to be installed Depends: libstdc++6 (>= 5.2) but 6.2.0-5ubuntu12 is to be installed Depends: libusb-1.0-0 (>= 2:1.0.8) but 2:1.0.20-1 is to be installed Depends: libwayland-client0 (>= 1.9.91) but 1.11.0-2 is to be installed Depends: libx265-79 (>= 1.9) but 1.9-3 is to be installed Depends: libxml2 (>= 2.9.0) but 2.9.4+dfsg1-2ubuntu0.1 is to be installed Depends: gstreamer1.0-plugins-bad-videoparsers (= 1.8.3-1ubuntu1.1) but 1.8.3-1ubuntu1.1 is to be installed Depends: gstreamer1.0-plugins-bad-faad (= 1.8.3-1ubuntu1.1) but 1.8.3-1ubuntu1.1 is to be installed cat version.log Ubuntu 4.8.0-46.49-generic 4.8.17 ubuntu 16.10 --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 4322 F pulseaudio /dev/snd/controlC3: mark 4322 F pulseaudio /dev/snd/controlC2: mark 4322 F pulseaudio /dev/snd/controlC0: mark 4322 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=3e34a9fd-33a3-4027-86ff-5151122c5379 InstallationDate: Installed on 2010-03-14 (2590 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=bf8502af-6555-4b4c-a93f-11ee7121da7d ro quiet nosplash libata.force=noncq ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-46-generic N/A linux-backports-modules-4.8.0-46-generic N/A linux-firmware1.161.1 RfKill: Tags: yakkety Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout floppy fuse libvirt libvirtd lpadmin netdev plugdev powerdev sambashare scanner tape video _MarkForUpload: True dmi.bios.date: 03/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A87TD/USB3 dmi.board.vendor: ASUSTeK Computer INC.
[Kernel-packages] [Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel
The screenshot above is from traffic between the two RPis, which run Raspbian (RPi + Debian). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686099 Title: connection flood to port 445 on mounting cifs volume under kernel Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: This is identical to the bug reported on the Debian kernel list, only I'm running 4.4.0, not 4.[89].0 After about 15 mintues, the cifsd daemon starts flooding echo requests on port 445 to the windows server causing a constant 1MB/s load (around 10,000 packets per second) that eventually leads to system instability that forces a reboot to correct. This is repeatable and as far as I know started about a week ago (possibly with the installation of 4.4.0-75). https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1686099/+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 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel
I've got the same flood here, on port 445, across my LAN. If I block that port, I get a flood instead via port 139. There was 1MB/s upload/download between my Windows 10 machine and a Raspberry Pi 3 (4.9.24-v7+). I blocked that and had the same flood between two Raspberry Pi 3s. The same thing happened if I fired up my Lubuntu boxes (I can't remember if it was the 4.4.0-75-generic or the 4.8.0-29-generic, and I can't re- enable Samba right now on the network, as it's "live" and I don't want to disrupt the web service). Have had to temporarily block all 139/445 Samba traffic on all networked machines, just allowing 139 and 445 from my Windows 10 machine, which is tolerable, as I need to be able to access network shared folders. I've attached a screenshot from Wireshark, and I also have the .pcapng capture file if needed. ** Attachment added: "Screenshot of Wireshark live capture" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686099/+attachment/4869996/+files/wireshark-screenshot.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686099 Title: connection flood to port 445 on mounting cifs volume under kernel Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: This is identical to the bug reported on the Debian kernel list, only I'm running 4.4.0, not 4.[89].0 After about 15 mintues, the cifsd daemon starts flooding echo requests on port 445 to the windows server causing a constant 1MB/s load (around 10,000 packets per second) that eventually leads to system instability that forces a reboot to correct. This is repeatable and as far as I know started about a week ago (possibly with the installation of 4.4.0-75). https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1686099/+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 1687256] 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/1687256 Title: byd touchpad no longer detected Status in linux package in Ubuntu: Confirmed Bug description: When running on kernel 4.8.0-34 my Lafite byd touchpad is recognised correctly and shows with xinput --list as BYDPS/2 BYD Touchpad. If I use any higher upgrade, eg 4.8.0-46 in 16.10 then touchpad is only identified as ImPS/2 Generic Wheel Mouse. The same applies if I try 17.04 from an external drive, touchpad does not work and cursor remains in top rh corner of screen. This could be related to the changelog https://launchpad.net/ubuntu/+source/linux/+changelog 4.8.0-36.38 in yakkety-proposed * Yakkety update to v4.8.13 stable release (LP: #1650581) ... - Input: psmouse - disable automatic probing of BYD touchpads Any thought on what has changed and how to resolve issue so that I can upgrade to later version? Thanks --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 3590 F pulseaudio /dev/snd/controlC1: dave 3590 F pulseaudio DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0b7a1f56-4391-4d9d-90ed-d0f5f5d76c90 InstallationDate: Installed on 2015-05-17 (714 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Intel Corporation SharkBay Platform Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 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.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: Fab2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/27/2015:svnIntelCorporation:pnSharkBayPlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrFab2:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.: dmi.product.name: SharkBay Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687256/+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 1687256] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1687256/+attachment/4869956/+files/WifiSyslog.txt ** 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/1687256 Title: byd touchpad no longer detected Status in linux package in Ubuntu: New Bug description: When running on kernel 4.8.0-34 my Lafite byd touchpad is recognised correctly and shows with xinput --list as BYDPS/2 BYD Touchpad. If I use any higher upgrade, eg 4.8.0-46 in 16.10 then touchpad is only identified as ImPS/2 Generic Wheel Mouse. The same applies if I try 17.04 from an external drive, touchpad does not work and cursor remains in top rh corner of screen. This could be related to the changelog https://launchpad.net/ubuntu/+source/linux/+changelog 4.8.0-36.38 in yakkety-proposed * Yakkety update to v4.8.13 stable release (LP: #1650581) ... - Input: psmouse - disable automatic probing of BYD touchpads Any thought on what has changed and how to resolve issue so that I can upgrade to later version? Thanks --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 3590 F pulseaudio /dev/snd/controlC1: dave 3590 F pulseaudio DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0b7a1f56-4391-4d9d-90ed-d0f5f5d76c90 InstallationDate: Installed on 2015-05-17 (714 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Intel Corporation SharkBay Platform Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 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.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: Fab2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/27/2015:svnIntelCorporation:pnSharkBayPlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrFab2:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.: dmi.product.name: SharkBay Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687256/+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 1687256] [NEW] byd touchpad no longer detected
You have been subscribed to a public bug: When running on kernel 4.8.0-34 my Lafite byd touchpad is recognised correctly and shows with xinput --list as BYDPS/2 BYD Touchpad. If I use any higher upgrade, eg 4.8.0-46 in 16.10 then touchpad is only identified as ImPS/2 Generic Wheel Mouse. The same applies if I try 17.04 from an external drive, touchpad does not work and cursor remains in top rh corner of screen. This could be related to the changelog https://launchpad.net/ubuntu/+source/linux/+changelog 4.8.0-36.38 in yakkety-proposed * Yakkety update to v4.8.13 stable release (LP: #1650581) ... - Input: psmouse - disable automatic probing of BYD touchpads Any thought on what has changed and how to resolve issue so that I can upgrade to later version? Thanks --- ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dave 3590 F pulseaudio /dev/snd/controlC1: dave 3590 F pulseaudio DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0b7a1f56-4391-4d9d-90ed-d0f5f5d76c90 InstallationDate: Installed on 2015-05-17 (714 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Intel Corporation SharkBay Platform Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 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.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 Tags: yakkety Uname: Linux 4.8.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: Fab2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/27/2015:svnIntelCorporation:pnSharkBayPlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrFab2:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.: dmi.product.name: SharkBay Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bot-comment yakkety -- byd touchpad no longer detected https://bugs.launchpad.net/bugs/1687256 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 1650581] Re: Yakkety update to v4.8.13 stable release
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1650581 Title: Yakkety update to v4.8.13 stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.8.13 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.8.13 stable release shall be applied: libata-scsi: Fixup ata_gen_passthru_sense() scsi: hpsa: use bus '3' for legacy HBA devices scsi: libfc: fix seconds_since_last_reset miscalculation ARC: mm: PAE40: Fix crash at munmap ARC: Don't use "+l" inline asm constraint mm, thp: propagation of conditional compilation in khugepaged.c thp: fix corner case of munlock() of PTE-mapped THPs zram: fix unbalanced idr management at hot removal kasan: update kasan_global for gcc 7 mm: fix false-positive WARN_ON() in truncate/invalidate for hugetlb Input: change KEY_DATA from 0x275 to 0x277 Input: psmouse - disable automatic probing of BYD touchpads rcu: Fix soft lockup for rcu_nocb_kthread mm: workingset: fix NULL ptr in count_shadow_nodes PCI: Export pcie_find_root_port PCI: Set Read Completion Boundary to 128 iff Root Port supports it (_HPX) mwifiex: printk() overflow with 32-byte SSIDs KVM: arm/arm64: vgic: Don't notify EOI for non-SPIs drm/i915: Don't touch NULL sg on i915_gem_object_get_pages_gtt() error drm/i915: drop the struct_mutex when wedged or trying to reset drm/amdgpu: fix power state when port pm is unavailable drm/radeon: fix power state when port pm is unavailable (v2) drm/amdgpu: fix check for port PM availability drm/radeon: fix check for port PM availability arm64: dts: juno: fix cluster sleep state entry latency on all SoC versions KVM: use after free in kvm_ioctl_create_device() pwm: Fix device reference leak drm/mediatek: fix null pointer dereference perf/x86: Restore TASK_SIZE check on frame pointer clk: sunxi: Fix M factor computation for APB1 batman-adv: Detect missing primaryif during tp_send as error arm64: cpufeature: Schedule enable() calls instead of calling them via IPI arm64: mm: Set PSTATE.PAN from the cpu_enable_pan() call arm64: suspend: Reconfigure PSTATE after resume from idle Linux 4.8.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650581/+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 1687267] 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/1687267 Title: kernel BUG at /build/linux- 2NWldV/linux-4.10.0/include/linux/swapops.h:129! Status in linux package in Ubuntu: Confirmed Bug description: First traceback looks to be the cause. The second traceback is the effect that followed (repeatedly). Don't think it's specific to system76. Apr 30 09:56:10 galago kernel: [97085.090114] [ cut here ] Apr 30 09:56:10 galago kernel: [97085.090137] kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129! Apr 30 09:56:10 galago kernel: [97085.090157] invalid opcode: [#1] SMP Apr 30 09:56:10 galago kernel: [97085.090167] Modules linked in: nls_iso8859_1 uas usb_storage ccm rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc aufs ec_sys cmac bnep arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_via ghash_clmulni_intel snd_hda_codec_generic pcbc snd_hda_intel snd_hda_codec iwlmvm snd_hda_core snd_hwdep aesni_intel snd_pcm uvcvideo mac80211 aes_x86_64 snd_seq_midi videobuf2_vmalloc crypto_simd snd_seq_midi_event glue_helper videobuf2_memops cryptd videobuf2_v4l2 btusb snd_rawmidi videobuf2_core btrtl snd_seq btbcm intel_cstate videodev btintel Apr 30 09:56:10 galago kernel: [97085.090334] bluetooth snd_seq_device media intel_rapl_perf iwlwifi snd_timer joydev input_leds cfg80211 rtsx_pci_ms snd memstick mei_me soundcore mei lpc_ich shpchp serio_raw tpm_infineon mac_hid binfmt_misc cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper psmouse e1000e syscopyarea sysfillrect ahci sysimgblt fb_sys_fops libahci drm ptp rtsx_pci pps_core wmi fjes video Apr 30 09:56:10 galago kernel: [97085.090439] CPU: 0 PID: 3534 Comm: JS Helper Not tainted 4.10.0-20-generic #22-Ubuntu Apr 30 09:56:10 galago kernel: [97085.090457] Hardware name: System76, Inc. Galago UltraPro/W740SU , BIOS 4.6.5 12/12/2013 Apr 30 09:56:10 galago kernel: [97085.090481] task: 9003eb142d00 task.stack: a0fb83c34000 Apr 30 09:56:10 galago kernel: [97085.090499] RIP: 0010:__migration_entry_wait+0x16a/0x180 Apr 30 09:56:10 galago kernel: [97085.090512] RSP: :a0fb83c37d68 EFLAGS: 00010246 Apr 30 09:56:10 galago kernel: [97085.090525] RAX: 000fc0048078 RBX: faefcf1c69f0 RCX: faefcf1c69f0 Apr 30 09:56:10 galago kernel: [97085.090542] RDX: 0001 RSI: 9003c71a7800 RDI: faefc2f44000 Apr 30 09:56:10 galago kernel: [97085.090559] RBP: a0fb83c37d80 R08: 9003ebb38000 R09: 9003ebb38000 Apr 30 09:56:10 galago kernel: [97085.090576] R10: 7fc0379000c8 R11: 0206 R12: faefc2f44000 Apr 30 09:56:10 galago kernel: [97085.090592] R13: 3e0bd100 R14: a0fb83c37e30 R15: 9003d0b80898 Apr 30 09:56:10 galago kernel: [97085.090609] FS: 7fc01b3fa700() GS:90041fa0() knlGS: Apr 30 09:56:10 galago kernel: [97085.090628] CS: 0010 DS: ES: CR0: 80050033 Apr 30 09:56:10 galago kernel: [97085.090642] CR2: 7fc004700018 CR3: 0003c70f9000 CR4: 001406f0 Apr 30 09:56:10 galago kernel: [97085.090658] Call Trace: Apr 30 09:56:10 galago kernel: [97085.090667] migration_entry_wait+0x74/0x80 Apr 30 09:56:10 galago kernel: [97085.090680] do_swap_page+0x5b3/0x770 Apr 30 09:56:10 galago kernel: [97085.090691] handle_mm_fault+0x873/0x1360 Apr 30 09:56:10 galago kernel: [97085.090703] __do_page_fault+0x23e/0x4e0 Apr 30 09:56:10 galago kernel: [97085.090715] do_page_fault+0x22/0x30 Apr 30 09:56:10 galago kernel: [97085.090726] page_fault+0x28/0x30 Apr 30 09:56:10 galago kernel: [97085.090735] RIP: 0033:0x56520e6072b4 Apr 30 09:56:10 galago kernel: [97085.090744] RSP: 002b:7fc01b3f9c40 EFLAGS: 00010203 Apr 30 09:56:10 galago kernel: [97085.090757] RAX: RBX: 7fc037900040 RCX: 7fc037b7b137 Apr 30 09:56:10 galago kernel: [97085.090774] RDX: 0008 RSI: 2000 RDI: 7fc0047ba000 Apr 30 09:56:10 galago kernel: [97085.090790] RBP: 7fc00470 R08: 7fc0379000c8 R09: Apr 30 09:56:10 galago kernel: [97085.090807] R10: 7fc0379000c8 R11: 0206 R12: 0080 Apr 30 09:56:10 galago kernel: [97085.090824] R13: 7fc0379000c8 R14: 00b9 R15: 0002 Apr 30 09:56:10 galago
[Kernel-packages] [Bug 1687267] [NEW] kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129!
Public bug reported: First traceback looks to be the cause. The second traceback is the effect that followed (repeatedly). Don't think it's specific to system76. Apr 30 09:56:10 galago kernel: [97085.090114] [ cut here ] Apr 30 09:56:10 galago kernel: [97085.090137] kernel BUG at /build/linux-2NWldV/linux-4.10.0/include/linux/swapops.h:129! Apr 30 09:56:10 galago kernel: [97085.090157] invalid opcode: [#1] SMP Apr 30 09:56:10 galago kernel: [97085.090167] Modules linked in: nls_iso8859_1 uas usb_storage ccm rfcomm ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc aufs ec_sys cmac bnep arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_via ghash_clmulni_intel snd_hda_codec_generic pcbc snd_hda_intel snd_hda_codec iwlmvm snd_hda_core snd_hwdep aesni_intel snd_pcm uvcvideo mac80211 aes_x86_64 snd_seq_midi videobuf2_vmalloc crypto_simd snd_seq_midi_event glue_helper videobuf2_memops cryptd videobuf2_v4l2 btusb snd_rawmidi videobuf2_core btrtl snd_seq btbcm intel_cstate videodev btintel Apr 30 09:56:10 galago kernel: [97085.090334] bluetooth snd_seq_device media intel_rapl_perf iwlwifi snd_timer joydev input_leds cfg80211 rtsx_pci_ms snd memstick mei_me soundcore mei lpc_ich shpchp serio_raw tpm_infineon mac_hid binfmt_misc cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper psmouse e1000e syscopyarea sysfillrect ahci sysimgblt fb_sys_fops libahci drm ptp rtsx_pci pps_core wmi fjes video Apr 30 09:56:10 galago kernel: [97085.090439] CPU: 0 PID: 3534 Comm: JS Helper Not tainted 4.10.0-20-generic #22-Ubuntu Apr 30 09:56:10 galago kernel: [97085.090457] Hardware name: System76, Inc. Galago UltraPro/W740SU , BIOS 4.6.5 12/12/2013 Apr 30 09:56:10 galago kernel: [97085.090481] task: 9003eb142d00 task.stack: a0fb83c34000 Apr 30 09:56:10 galago kernel: [97085.090499] RIP: 0010:__migration_entry_wait+0x16a/0x180 Apr 30 09:56:10 galago kernel: [97085.090512] RSP: :a0fb83c37d68 EFLAGS: 00010246 Apr 30 09:56:10 galago kernel: [97085.090525] RAX: 000fc0048078 RBX: faefcf1c69f0 RCX: faefcf1c69f0 Apr 30 09:56:10 galago kernel: [97085.090542] RDX: 0001 RSI: 9003c71a7800 RDI: faefc2f44000 Apr 30 09:56:10 galago kernel: [97085.090559] RBP: a0fb83c37d80 R08: 9003ebb38000 R09: 9003ebb38000 Apr 30 09:56:10 galago kernel: [97085.090576] R10: 7fc0379000c8 R11: 0206 R12: faefc2f44000 Apr 30 09:56:10 galago kernel: [97085.090592] R13: 3e0bd100 R14: a0fb83c37e30 R15: 9003d0b80898 Apr 30 09:56:10 galago kernel: [97085.090609] FS: 7fc01b3fa700() GS:90041fa0() knlGS: Apr 30 09:56:10 galago kernel: [97085.090628] CS: 0010 DS: ES: CR0: 80050033 Apr 30 09:56:10 galago kernel: [97085.090642] CR2: 7fc004700018 CR3: 0003c70f9000 CR4: 001406f0 Apr 30 09:56:10 galago kernel: [97085.090658] Call Trace: Apr 30 09:56:10 galago kernel: [97085.090667] migration_entry_wait+0x74/0x80 Apr 30 09:56:10 galago kernel: [97085.090680] do_swap_page+0x5b3/0x770 Apr 30 09:56:10 galago kernel: [97085.090691] handle_mm_fault+0x873/0x1360 Apr 30 09:56:10 galago kernel: [97085.090703] __do_page_fault+0x23e/0x4e0 Apr 30 09:56:10 galago kernel: [97085.090715] do_page_fault+0x22/0x30 Apr 30 09:56:10 galago kernel: [97085.090726] page_fault+0x28/0x30 Apr 30 09:56:10 galago kernel: [97085.090735] RIP: 0033:0x56520e6072b4 Apr 30 09:56:10 galago kernel: [97085.090744] RSP: 002b:7fc01b3f9c40 EFLAGS: 00010203 Apr 30 09:56:10 galago kernel: [97085.090757] RAX: RBX: 7fc037900040 RCX: 7fc037b7b137 Apr 30 09:56:10 galago kernel: [97085.090774] RDX: 0008 RSI: 2000 RDI: 7fc0047ba000 Apr 30 09:56:10 galago kernel: [97085.090790] RBP: 7fc00470 R08: 7fc0379000c8 R09: Apr 30 09:56:10 galago kernel: [97085.090807] R10: 7fc0379000c8 R11: 0206 R12: 0080 Apr 30 09:56:10 galago kernel: [97085.090824] R13: 7fc0379000c8 R14: 00b9 R15: 0002 Apr 30 09:56:10 galago kernel: [97085.090840] Code: ff ff ff 4c 89 e7 e8 96 a2 f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb Apr 30 09:56:10 galago kernel: [97085.090897] RIP: __migration_entry_wait+0x16a/0x180 RSP: a0fb83c37d68 Apr 30 09:56:10 galago kernel: [97085.096483] ---[ end trace 03fb86cf3cfe64f3 ]--- Apr 30 09:56:25 galago kernel: [97100.371032]
[Kernel-packages] [Bug 1687262] 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/1687262 Title: 16.10, 17.04 Wired connection stopped working RTL 8111/8168/8411 Status in linux package in Ubuntu: Confirmed Bug description: This is a regression. Upon upgrading 16.04 -> 16.10. Wired connection provided by "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" has stopped working. Quickly looked around for possible solution, and decided to go on with upgrade to 17.04, since it was my initial upgrade target anyway, and wireless on the system continued to function. So, ended up in this situation: running 17.04, wireless adapter is working, while wired does not work any more. Extra observation: I've also tried live session from USB based on 17.04 ISO-image, wired network adapter just works in the live session. Conclusion: it is a software issue. Note that similar problem was reported be other user on the forum: https://ubuntuforums.org/showthread.php?t=2354675 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-generic 4.10.0.20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1894 F pulseaudio /dev/snd/controlC0: alexei 1894 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sun Apr 30 09:33:01 2017 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (479 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-23 (6 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687262/+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 1687262] [NEW] 16.10, 17.04 Wired connection stopped working RTL 8111/8168/8411
Public bug reported: This is a regression. Upon upgrading 16.04 -> 16.10. Wired connection provided by "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" has stopped working. Quickly looked around for possible solution, and decided to go on with upgrade to 17.04, since it was my initial upgrade target anyway, and wireless on the system continued to function. So, ended up in this situation: running 17.04, wireless adapter is working, while wired does not work any more. Extra observation: I've also tried live session from USB based on 17.04 ISO-image, wired network adapter just works in the live session. Conclusion: it is a software issue. Note that similar problem was reported be other user on the forum: https://ubuntuforums.org/showthread.php?t=2354675 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-generic 4.10.0.20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1894 F pulseaudio /dev/snd/controlC0: alexei 1894 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sun Apr 30 09:33:01 2017 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (479 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-23 (6 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1687262 Title: 16.10, 17.04 Wired connection stopped working RTL 8111/8168/8411 Status in linux package in Ubuntu: New Bug description: This is a regression. Upon upgrading 16.04 -> 16.10. Wired connection provided by "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" has stopped working. Quickly looked around for possible solution, and decided to go on with upgrade to 17.04, since it was my initial upgrade target anyway, and wireless on the system continued to function. So, ended up in this situation: running 17.04, wireless adapter is working, while wired does not work any more. Extra observation: I've also tried live session from USB based on 17.04 ISO-image, wired network adapter just works in the live session. Conclusion: it is a software issue. Note that similar problem was reported be other user on the forum: https://ubuntuforums.org/showthread.php?t=2354675 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-generic 4.10.0.20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 1894 F pulseaudio /dev/snd/controlC0: alexei 1894 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sun Apr 30 09:33:01 2017 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (479 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A
[Kernel-packages] [Bug 1676070] Re: Wrong button's map for Logitech M560
I have also have a Logitech m560 and found this page useful https://blogs.ethz.ch/daesters/2015/10/24/customize-mouse-m560-on-linux/ If you want to use the sideways movement of the wheel for browser forward and back, instead of the lateral buttons, just replace the 10 and 11 with 6 and 7. One small thing to note is that the author made a typo - where they have written xbindkeys --defaults ~/.xbindkeysrc it should say xbindkeys --defaults > ~/.xbindkeysrc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1676070 Title: Wrong button's map for Logitech M560 Status in linux package in Ubuntu: Incomplete Bug description: I opened this bug a long time ago for Ubuntu 15.10. Now I installed a fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for this mouse and still use the wrong codes. Some mouses come with buttons on the wheel, so you can move the wheel to left and right and the mouse execute clicks. The problem is: to this clicks work on browser as back and forward functions, the buttons need to produce the codes 8 (back) and 9 (forward). I know that because I also have a Logitech M325 mouse which has buttons on wheel's side and works out-of-the-box on the browser, emitting codes 8 and 9. The Logitech M560 mouse has this buttons on wheel's side, but produces codes 6 (left side) and 7 (right side). So out-of-the-box, this wheel's side buttons just work to scroll for left and right. Even this is less useful than "back" and "forward" browser's buttons, I could agree if the lateral buttons (code 10 and 11), do the "back" forward" functions, but I think the best option is to remap the wheel's side buttons to code 8 and 9, to work as back and forward. My kernel version is: Ubuntu 4.10.0-14.16-generic 4.10.3 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcos26749 F pulseaudio CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Dell Inc. Vostro 1520 NonfreeKernelModules: nvidia_uvm nvidia wl Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 RelatedPackageVersions: linux-restricted-modules-4.10.0-13-generic N/A linux-backports-modules-4.10.0-13-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/05/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0T808J dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A: dmi.product.name: Vostro 1520 dmi.product.version: Null dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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
