[Kernel-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
-fno-PIE builds (Sebastian Siewior and Borislav Petkov). This is not a kernel regression, but one of the Debian gcc package. Nevertheless, it's quite annoying, so I think it should go into mainline and stable now" http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=04e36857d6747e4525e68c4292c081b795b48366 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1574982 Title: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler Status in dkms package in Ubuntu: Invalid Status in gcc-defaults package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in dkms source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Bug description: Installing the latest 4.4.0-22 kernel ends with that error logged into dkmsbuildlog (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine) https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic' arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler the latest error logged is: /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error: code model kernel does not support PIC mode Looks like it is related to the latest changes updates: gcc-6/gcc-5 5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the packages built with gcc-6) Maybe some alternatives has not been updated to take care of these changes, as asked some time ago: http://askubuntu.com/questions/26498/choose-gcc-and-g-version This has been firstly reported against a nvidia crash: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gcc 4:5.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 26 08:41:32 2016 SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem2014 F pulseaudio /dev/snd/pcmC0D0p: oem2014 F...m pulseaudio /dev/snd/controlC0: oem2014 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: ubuntu ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Tags: yakkety Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vend
[Kernel-packages] [Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume
I'm experiencing a similar issue on Thinkpad x220 running Linux Mint 18 (based on Ubuntu 16.04) with kernel 4.4.0-21. In my case, rfkill unblock needs to be called twice in order to fully enable (and soft unblock) bluetooth: # rfkill block bluetooth # rfkill list bluetooth 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no # rfkill unblock bluetooth # rfkill list bluetooth 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 5: hci0: Bluetooth Soft blocked: yes Hard blocked: no (At this stage, Bluetooth appears to be on in the Mint Bluetooth configuration dialog but can't see any devices). # rfkill unblock bluetooth # rfkill list bluetooth 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 5: hci0: Bluetooth Soft blocked: no Hard blocked: no (Now Bluetooth works fully as expected). -- 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/1603715 Title: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume Status in Bluez Utilities: New Status in bluez package in Ubuntu: Confirmed Bug description: DELL Latitude E5510 has a hardware switch to disable and enable bluetooth and wifi devices ("hard blocking" in terms of rfkill). In terms of wifi, this works great: After hard unblocking, the device resumes back to normal operation without any manual intervention. That was also working with bluetooth as of ubuntu 14.04, kernel 4.2. In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this is not working any more: After hard blocking and unblocking - bluetooth is not working at all - the applet-indicator remains gray - bluetooth cannot be enabled with the applet-indicator (see https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png). Applet-indicator remains gray - rfkill list tells me that the kernel knows about the hard unblocking (turns from "yes" to "no"): rfkill list bluetooth 2: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 8: hci0: Bluetooth Soft blocked: no Hard blocked: no The device is a sudo lsusb Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module Workaround: After a sudo service bluetooth restart the bluetooth device turns back to normal operation and the applet- indicator turns from gray to black (available). Suggested fix: Make the workaround obsolete. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Jul 17 04:00:58 2016 InstallationDate: Installed on 2014-11-29 (595 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5510 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 023HKR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1603715/+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 1606642] Re: NETDEV WATCHDOG: transmit queue 0 timed out
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1606642 Title: NETDEV WATCHDOG: transmit queue 0 timed out Status in linux package in Ubuntu: Expired Bug description: Kernel module crash: [ 3537.262585] WARNING: CPU: 2 PID: 0 at /build/linux-dcxD3m/linux-4.4.0/net/sched/sch_generic.c:306 dev_watchdog+0x237/0x240() [ 3537.262596] NETDEV WATCHDOG: wwp0s29u1u4 (qmi_wwan): transmit queue 0 timed out [ 3537.262605] Modules linked in: hid_generic hidp hid rfcomm qmi_wwan cdc_wdm usbnet mii bnep intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm qcserial usb_wwan usbserial irqbypass crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media joydev btusb btrtl btbcm btintel input_leds bluetooth serio_raw arc4 snd_hda_codec_hdmi iwldvm mac80211 snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec iwlwifi snd_hda_core snd_hwdep cfg80211 snd_pcm lpc_ich shpchp snd_seq_midi snd_seq_midi_event snd_rawmidi thinkpad_acpi snd_seq nvram snd_seq_device snd_timer snd soundcore mac_hid mei_me mei parport_pc ppdev lp parport autofs4 overlay [ 3537.262752] nls_utf8 isofs nls_iso8859_1 jfs xfs libcrc32c reiserfs dm_mirror dm_region_hash dm_log i915 i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt e1000e fb_sys_fops sdhci_pci sdhci drm ahci ptp libahci pps_core wmi fjes video [ 3537.262820] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.4.0-31-generic #50-Ubuntu [ 3537.262829] Hardware name: LENOVO 4291PR5/4291PR5, BIOS 8DET70WW (1.40 ) 05/14/2015 [ 3537.262836] 0286 a2df4eaadf32735b 88041e283d98 813f1143 [ 3537.262846] 88041e283de0 81d66c78 88041e283dd0 81081102 [ 3537.262860] 8804062b5680 0002 880405b32000 [ 3537.262868] Call Trace: [ 3537.262874][] dump_stack+0x63/0x90 [ 3537.262903] [] warn_slowpath_common+0x82/0xc0 [ 3537.262915] [] warn_slowpath_fmt+0x5c/0x80 [ 3537.262929] [] dev_watchdog+0x237/0x240 [ 3537.262944] [] ? qdisc_rcu_free+0x40/0x40 [ 3537.262958] [] call_timer_fn+0x35/0x120 [ 3537.262968] [] ? qdisc_rcu_free+0x40/0x40 [ 3537.262980] [] run_timer_softirq+0x23a/0x2f0 [ 3537.262992] [] __do_softirq+0x101/0x290 [ 3537.263003] [] irq_exit+0xa3/0xb0 [ 3537.263018] [] smp_apic_timer_interrupt+0x42/0x50 [ 3537.263027] [] apic_timer_interrupt+0x82/0x90 [ 3537.263031][] ? cpuidle_enter_state+0x10e/0x2b0 [ 3537.263052] [] cpuidle_enter+0x17/0x20 [ 3537.263063] [] call_cpuidle+0x32/0x60 [ 3537.263072] [] ? cpuidle_select+0x13/0x20 [ 3537.263081] [] cpu_startup_entry+0x290/0x350 [ 3537.263093] [] start_secondary+0x ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 6656 F pulseaudio CasperVersion: 1.376 CurrentDesktop: XFCE Date: Tue Jul 26 19:22:31 2016 LiveMediaBuild: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 4291PR5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/Ubuntu/16.04x/desktop-amd64/casper/vmlinuz.efi append noprompt boot=casper nohibernate keyboard-configuration-layoutcode=pl console-setup/layoutcode=pl userfullname=User Name username=username hostname=hostname nfsroot=usb showmounts persistent-path=/Ubuntu/16.04x/desktop-amd64 persistent iso-scan/filename=/Ubuntu/16.04x/xubuntu-16.04.1-desktop-amd64.iso RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET70WW (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291PR5 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET70WW(1.40):bd05/14/2015:svnLENOVO:pn4291PR5:pvrThinkPadX220:rvnLENOVO:rn4291PR5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4291PR5 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bu
[Kernel-packages] [Bug 732038] Re: WiFi not working (Broadcom BCM4311 )
*** This bug is a duplicate of bug 732677 *** https://bugs.launchpad.net/bugs/732677 Sorry there is mistake in comment #24.If secure boot in Bios is disabled then only i can see wifi networks.Please solve this i don't want to disable UEFI secure boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/732038 Title: WiFi not working (Broadcom BCM4311 ) Status in linux package in Ubuntu: Confirmed Bug description: After installing Natty from scratch I also installed Broadcom STA driver offered through Additional drivers but WiFi is not working. Network manager is not showing any wifi networks, and wifi light on my laptop is off. I tried to repeat procedure (stop/start Broadcome STA driver) but nothing happens. Tried also WiFi switch on laptop but still nothing. WiFi was working just fine on previous Ubuntu versions just after installing additional driver. Natty Alpha3, Broadcom BCM4311. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 4.0~b12+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Wed Mar 9 15:56:54 2011 FirefoxPackages: firefox 4.0~b12+build1+nobinonly-0ubuntu3 flashplugin-installer 10.2.152.27ubuntu1 adobe-flashplugin N/A icedtea-plugin 1.0~20110122-0ubuntu1 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302) ProcEnviron: LANGUAGE=en_GB:en LANG=en_US.UTF-8 LC_MESSAGES=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to natty on 2011-03-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/732038/+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 1623516] Re: My sylog and dmesg is full of WARN Event TRB Messages.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1623516 Title: My sylog and dmesg is full of WARN Event TRB Messages. Status in linux package in Ubuntu: Expired Bug description: Dear Support Team, Description: Ubuntu 16.04.1 LTS Release: 16.04 my dmesg and syslog is full of warn messages (see below). I get more than 10 of this messages per second. dmesg: [ 3899.166989] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 2 with no TDs queued? [ 3899.271440] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 2 with no TDs queued? [ 3899.273495] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 2 with no TDs queued? [ 3899.375906] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 2 with no TDs queued? [ 3899.480354] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 2 with no TDs queued? /var/log/syslog: Sep 14 15:36:56 workstation kernel: [ 3950.767800] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 2 with no TDs queued? Sep 14 15:36:56 workstation kernel: [ 3950.872267] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 2 with no TDs queued? Sep 14 15:36:56 workstation kernel: [ 3950.976707] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 2 with no TDs queued? Sep 14 15:36:56 workstation kernel: [ 3951.081177] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 2 with no TDs queued? Sep 14 15:36:56 workstation kernel: [ 3951.185616] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 2 with no TDs queued? Sep 14 15:36:56 workstation kernel: [ 3951.394532] xhci_hcd :00:14.0: WARN Event TRB for slot 5 ep 2 with no TDs queued? I *think* it is related to USB, but am not at all sure about this and cannot directly match it to anything direclty. Actually USB seems to be working for me, I just see these massive logs. On time of repoting this, I have the following USB devices attached: >lsusb [bo@workstation (~) Wed 3:45pm] lsusb Bus 002 Device 003: ID 8087:07da Intel Corp. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 05c8:034b Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc. VFS491 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 003: ID 1058:07a8 Western Digital Technologies, Inc. My Passport (WDBBEP), My Passport for Mac (WDBLUZ) Bus 004 Device 002: ID 0424:5534 Standard Microsystems Corp. Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] Bus 003 Device 006: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter Bus 003 Device 007: ID 1d50:6089 OpenMoko, Inc. Bus 003 Device 002: ID 0424:2134 Standard Microsystems Corp. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I hope you can help me, as it is really annoying. Thank you and best regards Boris ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bo 4087 F...m pulseaudio /dev/snd/controlC0: bo 4087 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 14 15:32:56 2016 HibernationDevice: RESUME=UUID=422c3fe4-cf87-4bfa-8415-8bd46c3ed706 InstallationDate: Installed on 2014-09-19 (726 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP EliteBook Folio 9470m ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash "acpi_osi=!Windows 2012" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-18 (27 days ago) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IBD Ver. F.47 dmi.board.name: 18DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 62.17 dmi.chassis.asset.tag: CNU412BJRP dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Pac
[Kernel-packages] [Bug 1623092] Re: Computer crashes on shutdown
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1623092 Title: Computer crashes on shutdown Status in linux package in Ubuntu: Expired Bug description: This bug has occurred twice in the past week. My motherboard is set up to turn on at 6am in the morning. The morning after this bug occurs it does not automatically start up. The bug occurs on shutdown and leaves the computer unresponsive with the text of the kernel log bug report on the screen. I've had to do a hard shutdown at this point, holding the power button until the machine powers down fully. I am happy to do whatever troubleshooting you suggest. I used `ubuntu-bug linux` to file this report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: antonios 4898 F pulseaudio /dev/snd/controlC0: antonios 4898 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 13 11:09:38 2016 HibernationDevice: RESUME=UUID=d39f2337-8ee7-4d9d-9202-41a04c955dfd InstallationDate: Installed on 2012-09-14 (1459 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) IwConfig: lono wireless extensions. docker0 no wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=50ef8abe-641b-49fd-8a81-60aca8cd440f ro RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-08 (35 days ago) dmi.bios.date: 09/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2105 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-M PRO 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.:bvr2105:bd09/06/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-MPRO: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/1623092/+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 732038] Re: WiFi not working (Broadcom BCM4311 )
*** This bug is a duplicate of bug 732677 *** https://bugs.launchpad.net/bugs/732677 If secure boot in Bios is enabled then only i can see wifi networks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/732038 Title: WiFi not working (Broadcom BCM4311 ) Status in linux package in Ubuntu: Confirmed Bug description: After installing Natty from scratch I also installed Broadcom STA driver offered through Additional drivers but WiFi is not working. Network manager is not showing any wifi networks, and wifi light on my laptop is off. I tried to repeat procedure (stop/start Broadcome STA driver) but nothing happens. Tried also WiFi switch on laptop but still nothing. WiFi was working just fine on previous Ubuntu versions just after installing additional driver. Natty Alpha3, Broadcom BCM4311. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 4.0~b12+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Wed Mar 9 15:56:54 2011 FirefoxPackages: firefox 4.0~b12+build1+nobinonly-0ubuntu3 flashplugin-installer 10.2.152.27ubuntu1 adobe-flashplugin N/A icedtea-plugin 1.0~20110122-0ubuntu1 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302) ProcEnviron: LANGUAGE=en_GB:en LANG=en_US.UTF-8 LC_MESSAGES=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to natty on 2011-03-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/732038/+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 732038] Re: WiFi not working (Broadcom BCM4311 )
*** This bug is a duplicate of bug 732677 *** https://bugs.launchpad.net/bugs/732677 I have a trouble connecting to wifi and i cant see wifi networks.I can see the wifi networks when i disable secure boot option in BIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/732038 Title: WiFi not working (Broadcom BCM4311 ) Status in linux package in Ubuntu: Confirmed Bug description: After installing Natty from scratch I also installed Broadcom STA driver offered through Additional drivers but WiFi is not working. Network manager is not showing any wifi networks, and wifi light on my laptop is off. I tried to repeat procedure (stop/start Broadcome STA driver) but nothing happens. Tried also WiFi switch on laptop but still nothing. WiFi was working just fine on previous Ubuntu versions just after installing additional driver. Natty Alpha3, Broadcom BCM4311. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 4.0~b12+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Wed Mar 9 15:56:54 2011 FirefoxPackages: firefox 4.0~b12+build1+nobinonly-0ubuntu3 flashplugin-installer 10.2.152.27ubuntu1 adobe-flashplugin N/A icedtea-plugin 1.0~20110122-0ubuntu1 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302) ProcEnviron: LANGUAGE=en_GB:en LANG=en_US.UTF-8 LC_MESSAGES=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to natty on 2011-03-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/732038/+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 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume
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/1603715 Title: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume Status in Bluez Utilities: New Status in bluez package in Ubuntu: Confirmed Bug description: DELL Latitude E5510 has a hardware switch to disable and enable bluetooth and wifi devices ("hard blocking" in terms of rfkill). In terms of wifi, this works great: After hard unblocking, the device resumes back to normal operation without any manual intervention. That was also working with bluetooth as of ubuntu 14.04, kernel 4.2. In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this is not working any more: After hard blocking and unblocking - bluetooth is not working at all - the applet-indicator remains gray - bluetooth cannot be enabled with the applet-indicator (see https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png). Applet-indicator remains gray - rfkill list tells me that the kernel knows about the hard unblocking (turns from "yes" to "no"): rfkill list bluetooth 2: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 8: hci0: Bluetooth Soft blocked: no Hard blocked: no The device is a sudo lsusb Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module Workaround: After a sudo service bluetooth restart the bluetooth device turns back to normal operation and the applet- indicator turns from gray to black (available). Suggested fix: Make the workaround obsolete. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Jul 17 04:00:58 2016 InstallationDate: Installed on 2014-11-29 (595 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5510 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 023HKR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1603715/+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 1642192] Re: i386 4.9 in -proposed fails to boot in cloud instances
No boot with any of the the available 4.9 kernels, in particular 4.9.0-1, under Lubuntu-17.04 and 16.04. Find similar lines in the console log, in particular the following which was mentioned above: Begin: Waiting for root file system ... Begin: running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. [... repeating some 50 times... ] Begin: Running /scripts/local-block ... done. done. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642192 Title: i386 4.9 in -proposed fails to boot in cloud instances Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: I noticed a forever-looping test of linuxinfo on i386 this morning. This test upgrades the kernel to 4.9 in -proposed; as soon as that reboots, the VM never comes back. nova console-log shows: [1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3) [1.582525] Write protecting the kernel text: 8300k [1.583624] Write protecting the kernel read-only data: 3344k [1.584845] NX-protecting the kernel data: 6036k [1.585921] [ cut here ] [1.586861] WARNING: CPU: 0 PID: 1 at /build/linux-UWDXbt/linux-4.9.0/arch/x86/mm/dump_pagetables.c:225 note_page+0x6a1/0x880 [1.589199] x86/mm: Found insecure W+X mapping at address c00a/0xc00a [1.590657] Modules linked in: [1.591305] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-1-generic #2-Ubuntu [1.592809] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 [1.593188] dae89e70 dc3e0b05 dae89eb4 dca47958 dae89ea0 dc07299a dca47920 dae89ed4 [1.593188] 0001 dca47958 00e1 dc068db1 00e1 dae89f34 8000 [1.593188] dae89ec0 dc072a06 0009 dae89eb4 dca47920 dae89ed4 76601e21 [1.593188] Call Trace: [1.593188] [] dump_stack+0x58/0x73 [1.593188] [] __warn+0xea/0x110 [1.593188] [] ? note_page+0x6a1/0x880 [1.593188] [] warn_slowpath_fmt+0x46/0x60 [1.593188] [] note_page+0x6a1/0x880 [1.593188] [] ptdump_walk_pgd_level_core+0x1f5/0x300 [1.593188] [] ptdump_walk_pgd_level_checkwx+0x16/0x20 [1.593188] [] mark_rodata_ro+0xfd/0x130 [1.593188] [] ? rest_init+0x70/0x70 [1.593188] [] kernel_init+0x2c/0x100 [1.593188] [] ? schedule_tail+0x11/0x50 [1.593188] [] ? rest_init+0x70/0x70 [1.593188] [] ret_from_fork+0x1b/0x28 [1.613361] ---[ end trace d63b34644638754d ]--- [1.614368] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found. ... Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. [... repeating some 50 times... ] Begin: Running /scripts/local-block ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=ac6eb865-17d6-469d-b58e-8c0d49174fe4 does not exist. Dropping to a shell! BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642192/+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 1471794] Re: Wifi slow on Intel Corporation Centrino Ultimate-N 6300
>From http://www.intel.com/content/www/us/en/support/network-and-i-o /wireless-networking/05511.html, one can conclude that this issue will probably never be fixed. The Ultimate-N 6300 is only supported for kernel 2.6.30. Obviously, it would be great for someone at Intel to confirm this. The driver persists in newer kernels, but if anybody is going to work on it to fix any problem remains to be seen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1471794 Title: Wifi slow on Intel Corporation Centrino Ultimate-N 6300 Status in linux package in Ubuntu: Confirmed Bug description: On Intel Corporation Centrino Ultimate-N 6300 who use iwlwifi, the Wifi goes approximately (in my home) to 15MB/s in up and down on Windows 7, but it goes only to 5 - 6MB/s down, and 1 - 3MB/s up on Linux. Before Ubuntu 11.04 → It was slow. After Ubuntu 11.04 → It was slow. On Ubuntu 11.04 (Only for test): The down speed is approximately 11MB/s and the up speed is approximately: 6 - 8MB/s The driver contain a regression for speed performance. Currently I use Ubuntu 14.04 LTS with Linux 3.18.1 (Vivid package) but the speed is already slow. The range of the card is reduced, and I take sometimes 2 - 5min to discover a network. Connection/disconnection to an other network can make a bug were the fastest way to change network is to disable/enable the card (if it works), or reboot the computer. It make this card absolutely not reliable because of the driver on Linux. --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: valentin 4266 F pulseaudio /dev/snd/controlC0: valentin 4266 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-11-24 (245 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E6540 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=83928b5e-863a-4f13-98b2-f288f6a095dc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 RelatedPackageVersions: linux-restricted-modules-3.13.0-46-generic N/A linux-backports-modules-3.13.0-46-generic N/A linux-firmware 1.127.14 StagingDrivers: zram Tags: trusty staging Uname: Linux 3.13.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/19/2015:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471794/+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 1630063] Re: specific USB devices disconnect and don't reconnect
I also had this problem, and found a different fix in 4.9 that fixed it (my original bug #1641052): commit a8006bd915095c40098bfcb684cc2bdfb414dc0d Merge: 965c4b7 6bad6bc Author: Linus Torvalds Date: Fri Oct 28 11:26:01 2016 -0700 Merge branch 'timers-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip Pull timer fixes from Ingo Molnar: "Fix four timer locking races: two were noticed by Linus while reviewing the code while chasing for a corruption bug, and two from fixing spurious USB timeouts" * 'timers-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: timers: Prevent base clock corruption when forwarding timers: Prevent base clock rewind when forwarding clock timers: Lock base for same bucket optimization timers: Plug locking race vs. timer migration Hide -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630063 Title: specific USB devices disconnect and don't reconnect Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: 2 USB ports randomly disconnect and don't reconnect (it's always the same two), and in dmesg all I get is " [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up [ 1276.916553] usb 3-1: USB disconnect, device number 2 [ 1277.017302] usb 3-2: USB disconnect, device number 3 " This only started happening when Yakkety went to the 4.8 branch, with 4.7 branch this doesn't occur, hence the bug report since it's unlikely that a hardware failure will only stick to one OS and one branch of the kernel for that OS. (these USB ports don't randomly die on Windows or BSD, I've tested that in the past couple of days) kernel version: 4.8.0.17.27 Ubuntu version Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: c_smith2213 F pulseaudio /dev/snd/controlC0: c_smith2213 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b InstallationDate: Installed on 2016-10-03 (0 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: GA-78LMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630063/+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 1644919] 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/1644919 Title: [fn] plus F2,F3,F4,F5,F6,F10,F11,F12 not responding - Fresh Install Status in linux package in Ubuntu: Confirmed Bug description: Gigabyte P57 laptop Fresh install, 10 days old, updated yesterday so software/kernel should be current. Some function keys work. Function plus F1 puts the machine to sleep Function plus F7, F8, F9 control the volume However, Pressing Function plus F2 does not turn off wireless Pressing Function plus F3,F4 do not change brightness Function plus F5 does not change output to LCD or Monitor Pressing Function plus F6 does not toggle touchpad (a separate bug in this machine, but the Elantech touchpad is recognised at the moment.) Function plus F10 does not turn the display off Function plus F11 does not turn off bluetooth Function plus F12 does not disable the camera Please let me know if you need any further troubleshooting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: horace 1948 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 26 07:44:13 2016 HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e InstallationDate: Installed on 2016-11-13 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05af:1050 Jing-Mold Enterprise Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE P57 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB0B dmi.board.asset.tag: Default string dmi.board.name: P57 dmi.board.vendor: GIGABYTE dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: P57 dmi.product.version: Default string dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644919/+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 1644919] [NEW] [fn] plus F2, F3, F4, F5, F6, F10, F11, F12 not responding - Fresh Install
Public bug reported: Gigabyte P57 laptop Fresh install, 10 days old, updated yesterday so software/kernel should be current. Some function keys work. Function plus F1 puts the machine to sleep Function plus F7, F8, F9 control the volume However, Pressing Function plus F2 does not turn off wireless Pressing Function plus F3,F4 do not change brightness Function plus F5 does not change output to LCD or Monitor Pressing Function plus F6 does not toggle touchpad (a separate bug in this machine, but the Elantech touchpad is recognised at the moment.) Function plus F10 does not turn the display off Function plus F11 does not turn off bluetooth Function plus F12 does not disable the camera Please let me know if you need any further troubleshooting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: horace 1948 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 26 07:44:13 2016 HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e InstallationDate: Installed on 2016-11-13 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05af:1050 Jing-Mold Enterprise Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE P57 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB0B dmi.board.asset.tag: Default string dmi.board.name: P57 dmi.board.vendor: GIGABYTE dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: P57 dmi.product.version: Default string dmi.sys.vendor: GIGABYTE ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644919 Title: [fn] plus F2,F3,F4,F5,F6,F10,F11,F12 not responding - Fresh Install Status in linux package in Ubuntu: New Bug description: Gigabyte P57 laptop Fresh install, 10 days old, updated yesterday so software/kernel should be current. Some function keys work. Function plus F1 puts the machine to sleep Function plus F7, F8, F9 control the volume However, Pressing Function plus F2 does not turn off wireless Pressing Function plus F3,F4 do not change brightness Function plus F5 does not change output to LCD or Monitor Pressing Function plus F6 does not toggle touchpad (a separate bug in this machine, but the Elantech touchpad is recognised at the moment.) Function plus F10 does not turn the display off Function plus F11 does not turn off bluetooth Function plus F12 does not disable the camera Please let me know if you need any further troubleshooting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: horace 1948 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 26 07:44:13 2016 HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e InstallationDate: Installed on 2016-11-13 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05af:1050 Jing-Mold Enterprise Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType:
[Kernel-packages] [Bug 1643165] Re: Wifi drops out regularly after upgrade to 16.04
Running 4.9.0-040900rc6, just had a drop out. Noticed that dmesg had this output: First this line, which seemed to coincide with the dropout: [ 3627.072802] wlan0: AP 00:07:26:aa:e0:45 changed bandwidth, new config is 2462 MHz, width 2 (2452/0 MHz) Then, after a minute, this and it came back: [ 3707.386740] wlan0: authenticate with 00:07:26:aa:e0:45 [ 3707.394906] wlan0: send auth to 00:07:26:aa:e0:45 (try 1/3) [ 3707.397243] wlan0: authenticated [ 3707.397828] wlan0: associate with 00:07:26:aa:e0:45 (try 1/3) [ 3707.406078] wlan0: RX AssocResp from 00:07:26:aa:e0:45 (capab=0x431 status=0 aid=1) [ 3707.413670] wlan0: associated [ 3707.447412] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 00:07:26:aa:e0:45 ** 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/1643165 Title: Wifi drops out regularly after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04, my wifi has seemed a lot more flaky, it'll drop out for 20s every few minutes then come back. network manager still thinks that it is connected, but websites will fail to load/time out. Reconnecting to the AP (by clicking on it in network-manager) seems to re-establish the connection. I typically sit 6ft from the access point so the signal is strong and much stronger than any nearby APs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaun 2212 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 19 10:39:23 2016 HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f InstallationDate: Installed on 2012-09-26 (1515 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_pstate=enable vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-25 (207 days ago) dmi.bios.date: 07/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643165/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
This script also works for me on Mint 18. Is there any way to run it automatically, after connecting with a bluetooth device? -- 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/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
@Peter > your ASPM bug I think you may opt it out, since ASPM doesn't work at Windows too (see powercfg /energy report there). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
@Alex: unfortunately not. The only 2 bugs may have to influence Fans: - your ASPM bug and - very possibly my - fans bug (powertop maybe since package does not reach lower than C3 state) on kernel bug tracker. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1627496] Re: radeon broken with kernel 4.6.0+
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627496 Title: radeon broken with kernel 4.6.0+ Status in linux package in Ubuntu: Fix Released Bug description: Hello Guys, I'm currently running an up-to-date Xenial system on amd64 (PC) platform. Whenever I launch the OS with stock kernel (4.4.X) all seems good. Whenever I launch the OS with let's say a mainline-PPA kernel whose version is above 4.6.0 inclusive (4.5.X are functional), or stock yakkety kernel nowadays (4.8.X), kernel fails to setup my graphics card, whose description is appended in a few text files I joined to this message. In hope this helps, Sincelely, Vécu P.S. : I very suspect this is a mainstream bug ; for any complimentary info. please don't hesitate to post and ask for more. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 25 15:23:08 2016 DistUpgraded: 2016-04-23 10:48:41,985 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Radeon HD 7670M [1179:fb41] InstallationDate: Installed on 2015-05-01 (512 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: TOSHIBA SATELLITE L875-10G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic root=UUID=fb0648bd-7019-4cb2-b5b3-382141e3716a ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-23 (155 days ago) dmi.bios.date: 3/25/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd3/25/2013:svnTOSHIBA:pnSATELLITEL875-10G:pvrPSKBLE-003006FR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE L875-10G dmi.product.version: PSKBLE-003006FR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs 1.0 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 25 15:10:31 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
@Peter That's may be possible since their genuine detection is not perfect, for example it passes under VirtualBox ;) So looks like there is no benefit in Dell 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/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1407313] Re: Physical buttons of touchpad do not work on Asus N53S (ETPS/2 Elantech Touchpad)
I have an Asus G752VT with the same behavior on ubuntu 16.04.1. Also tested the upstream kernel 4.8.10, but nothing has changed. The touchpad is working fine. Tap to klick is working. Also holding the left click hardware button and mark something is working. But left and right click is not working with the hardware buttons. This has to be a config issue. Can someone point me to the richt config setting to test? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1407313 Title: Physical buttons of touchpad do not work on Asus N53S (ETPS/2 Elantech Touchpad) Status in linux package in Ubuntu: Confirmed Bug description: Physical buttons for left and right button do not work at all on the touchpad of Asus N53S. I'm now on Linux Mint 17.1, but had the same issue previously on Ubuntu 13-10 (http://ubuntuforums.org/showthread.php?t=2196970). I have not found any real workaround. Plugging in a mouse all works just fine. Find attached relevant log files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1994 F pulseaudio CurrentDesktop: X-Cinnamon CurrentDmesg: [ 32.256027] nouveau E[ PDISP][:01:00.0] chid 0 mthd 0x0080 data 0x 0x00085080 Date: Sat Jan 3 18:24:37 2015 HibernationDevice: RESUME=UUID=b9874704-5718-4a69-88a4-d6d5d08715d7 InstallationDate: Installed on 2015-01-03 (0 days ago) InstallationMedia: Linux Mint 17.1 "Rebecca" - Release amd64 20141126 MachineType: ASUSTeK Computer Inc. N53SV ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=eef70fc7-ad88-4dee-abec-96153d2eb0ed ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53SV.215 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N53SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53SV.215:bd01/09/2012:svnASUSTeKComputerInc.:pnN53SV:pvr1.0:rvnASUSTeKComputerInc.:rnN53SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N53SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1407313/+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 1640786] Re: netfilter regression introducing a performance slowdown in binary arp/ip/ip6tables
I have backport the "Under Review" patches into Xenial 4.4.0-49 to test, here are the numbers : # uname -a Linux 4.4.0-49-generic #70hf121102v20161124b2-Ubuntu SMP Fri Nov 25 02:34:36 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux # iptables -F # time (./list-addrs 3000 | xargs -n1 iptables -A FORWARD -j ACCEPT -s) real 0m5.661s user 0m0.096s sys 0m0.452s So the patches have positive impact on mainline kernel and Xenial Ubuntu kernel. Once the patches are approved, I will submit it to the kernel team. Eric -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640786 Title: netfilter regression introducing a performance slowdown in binary arp/ip/ip6tables Status in linux package in Ubuntu: In Progress Bug description: Explanation : It has been brought to my attention that Ubuntu kernel 4.4 has a severe netfilter regression affecting the performance of "/sbin/iptables" command, especially when adding large number of policies. My source have documented everything here[2]. I was able to reproduce the situation on my side, and a kernel bisect identified the same offending commit[1] as my source found for this bug. Running the commit right before the offending one have proven to have expected performance : # commit [71ae0dff] <== Offending commit real 0m33.314s user 0m1.520s sys 0m26.192s # commit [d7b59742] <== Right before offending commit real 0m5.952s user 0m0.124s sys 0m0.220s Reproducer : $ iptables -F $ echo 3 > /proc/sys/vm/drop_caches $ time (./list-addrs 3000 | xargs -n1 iptables -A FORWARD -j ACCEPT -s) "list-addrs" script can be found here[3] Note : * "iptables-restore" doesn't suffer of that netfilter regression, and I'm also aware that "iptables-restore" is the favourite approach since it is way more efficient than iptables that is executed over and over, once for each policy one want to set, but since "/sbin/iptables" takes vastly longer to perform with that commit, I think this need to be address anyway. * I also tried with the latest and greatest iptables upstream code, and got the same result. Reference : [1] - https://github.com/torvalds/linux/commit/71ae0dff02d756e4d2ca710b79f2ff5390029a5f [2] - https://gist.github.com/williammartin/b75e3faf5964648299e4d985413e6c0c [3] - https://gist.github.com/williammartin/b75e3faf5964648299e4d985413e6c0c#file-list-addrs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640786/+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 1644823] 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/1644823 Title: Bluetooth not working Status in linux package in Ubuntu: Confirmed Bug description: I have Lenovo thinkpad E531 laptop. The built-in bluetooth not working. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mfawzy 1927 F pulseaudio CRDA: country EG: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (N/A, 20), (N/A) (5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS CurrentDesktop: GNOME-Flashback:Unity Date: Fri Nov 25 14:40:57 2016 HibernationDevice: RESUME=UUID=3d81c46b-d5d8-4809-8b2c-45998d99d0e7 InstallationDate: Installed on 2016-11-15 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 6885DZG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=5348a48b-8050-4470-98f1-f6b758b76ce1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: LENOVO dmi.bios.version: HEET44WW (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 6885DZG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHEET44WW(1.25):bd05/30/2014:svnLENOVO:pn6885DZG:pvrThinkPadEdgeE531:rvnLENOVO:rn6885DZG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6885DZG dmi.product.version: ThinkPad Edge E531 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644823/+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 1644804] Re: [Vostro 15-3568] Right key does not work on this clickpad
Verified with the latest mainline kernel, 4.9.0rc6, still not working. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644804 Title: [Vostro 15-3568] Right key does not work on this clickpad Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Bug description: CID: 201606-22528 Dell Vostro 15-3568 The right key on the clickpad does not work on this laptop. Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot and test the right key Result: * Not working at all ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1525 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 06:52:56 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1644804/+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 1644806] Re: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter"
Note that you can verify this issue by downgrading grub-related packages from proposed to updates: sudo apt-get install shim=0.8-0ubuntu2 shim- signed=1.19~16.04.1+0.8-0ubuntu2 grub-efi- amd64-bin=2.02~beta2-36ubuntu3.2 grub2-common=2.02~beta2-36ubuntu3.2 grub-common=2.02~beta2-36ubuntu3.2 grub-efi-amd64=2.02~beta2-36ubuntu3.2 grub-efi-amd64-signed=1.66.2+2.02~beta2-36ubuntu3.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644806 Title: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter" Status in linux package in Ubuntu: Confirmed Bug description: CID: 201606-22528 The proposed shim package will cause this laptop complain about: "Failed to set MokSBStateRT: (2) Invalid Parameter" on boot. You will see a blue screen after the Dell logo (please find the attached screenshot). Hit ok will continue to boot. BIOS setting UEFI + SecureBoot Enabled Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot to see if everything is ok 3. Enable proposed + dist-upgrade 4. Reboot, and you will see this issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-49-generic 4.4.0-49.70 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1611 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 07:03:10 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-49-generic N/A linux-backports-modules-4.4.0-49-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644806/+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 1644823] [NEW] Bluetooth not working
Public bug reported: I have Lenovo thinkpad E531 laptop. The built-in bluetooth not working. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mfawzy 1927 F pulseaudio CRDA: country EG: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (N/A, 20), (N/A) (5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS CurrentDesktop: GNOME-Flashback:Unity Date: Fri Nov 25 14:40:57 2016 HibernationDevice: RESUME=UUID=3d81c46b-d5d8-4809-8b2c-45998d99d0e7 InstallationDate: Installed on 2016-11-15 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 6885DZG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=5348a48b-8050-4470-98f1-f6b758b76ce1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: LENOVO dmi.bios.version: HEET44WW (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 6885DZG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHEET44WW(1.25):bd05/30/2014:svnLENOVO:pn6885DZG:pvrThinkPadEdgeE531:rvnLENOVO:rn6885DZG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6885DZG dmi.product.version: ThinkPad Edge E531 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644823 Title: Bluetooth not working Status in linux package in Ubuntu: New Bug description: I have Lenovo thinkpad E531 laptop. The built-in bluetooth not working. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mfawzy 1927 F pulseaudio CRDA: country EG: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 40), (N/A, 20), (N/A) (5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS CurrentDesktop: GNOME-Flashback:Unity Date: Fri Nov 25 14:40:57 2016 HibernationDevice: RESUME=UUID=3d81c46b-d5d8-4809-8b2c-45998d99d0e7 InstallationDate: Installed on 2016-11-15 (9 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 6885DZG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=5348a48b-8050-4470-98f1-f6b758b76ce1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: LENOVO dmi.bios.version: HEET44WW (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 6885DZG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHEET44WW(1.25):bd05/30/2014:svnLENOVO:pn6885DZG:pvrThinkPadEdgeE531:rvnLENOVO:rn6885DZG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6885DZG dmi.product.version: ThinkPad Edge E531 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644823/+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 1626269] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted makedumpfile into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1626269 Title: Ubuntu 16.10: kdump is not working in 4.8 kernel. Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Trusty: Confirmed Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Yakkety: Fix Committed Bug description: [SRU justification] makedumpfile fails to execute if executed on a 4.8 kernel [Impact] Unable to generate compressed kernel dumps on those platform [Fix] Backport commits 2c21d4656e8d3c2af2b1e14809d076941ae69e96 and 0c9dd01d8ee2e4ec1821a11f5e174fdba56012b8. The second commit is required since, once the initial issue is fixed, it triggers a second issue fixed on Debian by https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=842019 [Test Case] - Install kernel 4.8 along with the linux-crashdump metapackage - Reboot to enable kdump - Trigger a kernel panic with "echo c > /proc/sysrq-trigger" Without the patch, the following message will appear and makedumpfile will fail : get_mem_map: Can't distinguish the memory type. With the fix, makedumpfile completes correctly. [Regression] None expected. The modification keeps the initial structure when kernels before 4.8 are used. [Original description of the problem] == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 == ---Problem Description--- Ubuntu 16.10: kdump is not working in 4.8 kernel. ---Steps to Reproduce--- 1) apt-get install linux-crashdump 2) increase crashdump size: sudo vim /etc/default/grub.d/kexec-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M" 3) sudo update-grub ; reboot the machine 4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools 5) kdump-config show 6) echo "c" > /proc/sysrq-trigger Logs root@ubuntu:/home/ubuntu# uname -a Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@ubuntu:/home/ubuntu# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-11-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-11-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ubuntu:/home/ubuntu# cd root@ubuntu:~# echo "c" > /proc/sysrq-trigger [ 50.733424] sysrq: SysRq : Trigger a crash [ 50.733437] Unable to handle kernel paging request for data at address 0x [ 50.733441] Faulting instruction address: 0xc05af3f4 [ 50.733444] Oops: Kernel access of bad area, sig: 11 [#1] [ 50.733446] SMP NR_CPUS=2048 NUMA pSeries [ 50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic crc32c_vpmsum [ 50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic #12-Ubuntu [ 50.733480] task: c004f7906880 task.stack: c004f7898000 [ 50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: c05af3c0 [ 50.733485] REGS: c004f789b990 T
[Kernel-packages] [Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.
Hello bugproxy, or anyone else affected, Accepted makedumpfile into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.0-2ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: makedumpfile (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: makedumpfile (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1626269 Title: Ubuntu 16.10: kdump is not working in 4.8 kernel. Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Trusty: Confirmed Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Yakkety: Fix Committed Bug description: [SRU justification] makedumpfile fails to execute if executed on a 4.8 kernel [Impact] Unable to generate compressed kernel dumps on those platform [Fix] Backport commits 2c21d4656e8d3c2af2b1e14809d076941ae69e96 and 0c9dd01d8ee2e4ec1821a11f5e174fdba56012b8. The second commit is required since, once the initial issue is fixed, it triggers a second issue fixed on Debian by https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=842019 [Test Case] - Install kernel 4.8 along with the linux-crashdump metapackage - Reboot to enable kdump - Trigger a kernel panic with "echo c > /proc/sysrq-trigger" Without the patch, the following message will appear and makedumpfile will fail : get_mem_map: Can't distinguish the memory type. With the fix, makedumpfile completes correctly. [Regression] None expected. The modification keeps the initial structure when kernels before 4.8 are used. [Original description of the problem] == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 == ---Problem Description--- Ubuntu 16.10: kdump is not working in 4.8 kernel. ---Steps to Reproduce--- 1) apt-get install linux-crashdump 2) increase crashdump size: sudo vim /etc/default/grub.d/kexec-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M" 3) sudo update-grub ; reboot the machine 4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools 5) kdump-config show 6) echo "c" > /proc/sysrq-trigger Logs root@ubuntu:/home/ubuntu# uname -a Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@ubuntu:/home/ubuntu# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-11-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.8.0-11-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ubuntu:/home/ubuntu# cd root@ubuntu:~# echo "c" > /proc/sysrq-trigger [ 50.733424] sysrq: SysRq : Trigger a crash [ 50.733437] Unable to handle kernel paging request for data at address 0x [ 50.733441] Faulting instruction address: 0xc05af3f4 [ 50.733444] Oops: Kernel access of bad area, sig: 11 [#1] [ 50.733446] SMP NR_CPUS=2048 NUMA pSeries [ 50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic crc32c_vpmsum [ 50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-
[Kernel-packages] [Bug 1644771] Re: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes
Hello Louis, or anyone else affected, Accepted makedumpfile into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.0-2ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: makedumpfile (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: makedumpfile (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1644771 Title: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Yakkety: Fix Committed Bug description: [SRU justification] This fix is needed to avoid failure to load kdump-tools when one kernel boot parameter has double-quotes. [Impact] kdump functionality becomes unusable [Fix] Modify kdump-config to handle the presence of double-quotes in the cmdline [Test Case] Edit /etc/default/grub and add the following to GRUB_CMDLINE_LINUX_DEFAULT : \"acpi_osi=!Windows 2012\" $ sudo update-grub $ sudo reboot kdump-config will show the following error upon reboot : [ 11.595868] kdump-tools[1710]: Cannot open `2012 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service': No s uch file or directory [ 11.602563] kdump-tools[1710]: * failed to load kdump kernel With this fix, the kdump-config command will run successfully [Regression] None expected. Fix is already in Zesty & Debian. Only one line added to the sed statement. [Original description of the problem] kdump-tools fails to load if one of the kernel parameter has double-quotes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1644771/+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 1644771] Please test proposed package
Hello Louis, or anyone else affected, Accepted makedumpfile into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1644771 Title: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Yakkety: Fix Committed Bug description: [SRU justification] This fix is needed to avoid failure to load kdump-tools when one kernel boot parameter has double-quotes. [Impact] kdump functionality becomes unusable [Fix] Modify kdump-config to handle the presence of double-quotes in the cmdline [Test Case] Edit /etc/default/grub and add the following to GRUB_CMDLINE_LINUX_DEFAULT : \"acpi_osi=!Windows 2012\" $ sudo update-grub $ sudo reboot kdump-config will show the following error upon reboot : [ 11.595868] kdump-tools[1710]: Cannot open `2012 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service': No s uch file or directory [ 11.602563] kdump-tools[1710]: * failed to load kdump kernel With this fix, the kdump-config command will run successfully [Regression] None expected. Fix is already in Zesty & Debian. Only one line added to the sed statement. [Original description of the problem] kdump-tools fails to load if one of the kernel parameter has double-quotes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1644771/+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 1644806] 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/1644806 Title: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter" Status in linux package in Ubuntu: Confirmed Bug description: CID: 201606-22528 The proposed shim package will cause this laptop complain about: "Failed to set MokSBStateRT: (2) Invalid Parameter" on boot. You will see a blue screen after the Dell logo (please find the attached screenshot). Hit ok will continue to boot. BIOS setting UEFI + SecureBoot Enabled Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot to see if everything is ok 3. Enable proposed + dist-upgrade 4. Reboot, and you will see this issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-49-generic 4.4.0-49.70 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1611 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 07:03:10 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-49-generic N/A linux-backports-modules-4.4.0-49-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644806/+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 1644806] Re: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter"
Note that this issue can be reproduced on a Dell Inspiron 7560 (201606-22349) laptop as well. And the OEM image is affected too. ** Tags added: 201606-22349 ** Description changed: CID: 201606-22528 The proposed shim package will cause this laptop complain about: "Failed to set MokSBStateRT: (2) Invalid Parameter" on boot. You will see a blue screen after the Dell logo (please find the attached screenshot). Hit ok will continue to boot. BIOS setting UEFI + SecureBoot Enabled + Steps: + 1. Install 14.04.1 + dist-upgrade + 2. Reboot to see if everything is ok + 3. Enable proposed + dist-upgrade + 4. Reboot, and you will see this issue + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-49-generic 4.4.0-49.70 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 1611 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1611 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 07:03:10 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. - Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller - Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. + Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller + Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-49-generic N/A - linux-backports-modules-4.4.0-49-generic N/A - linux-firmware1.157.5 + linux-restricted-modules-4.4.0-49-generic N/A + linux-backports-modules-4.4.0-49-generic N/A + linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644806 Title: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter" Status in linux package in Ubuntu: New Bug description: CID: 201606-22528 The proposed shim package will cause this laptop complain about: "Failed to set MokSBStateRT: (2) Invalid Parameter" on boot. You will see a blue screen after the Dell logo (please find the attached screenshot). Hit ok will continue to boot. BIOS setting UEFI + SecureBoot Enabled Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot to see if everything is ok 3. Enable proposed + dist-upgrade 4. Reboot, and you will see this issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-49-generic 4.4.0-49.70 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1611 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 07:03:10 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 P
[Kernel-packages] [Bug 1644806] [NEW] Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter"
Public bug reported: CID: 201606-22528 The proposed shim package will cause this laptop complain about: "Failed to set MokSBStateRT: (2) Invalid Parameter" on boot. You will see a blue screen after the Dell logo (please find the attached screenshot). Hit ok will continue to boot. BIOS setting UEFI + SecureBoot Enabled Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot to see if everything is ok 3. Enable proposed + dist-upgrade 4. Reboot, and you will see this issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-49-generic 4.4.0-49.70 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1611 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 07:03:10 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-49-generic N/A linux-backports-modules-4.4.0-49-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 201606-22349 201606-22528 amd64 apport-bug package-from-proposed taipei-lab xenial ** Attachment added: "image20161125_190623046.jpg" https://bugs.launchpad.net/bugs/1644806/+attachment/4782926/+files/image20161125_190623046.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644806 Title: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter" Status in linux package in Ubuntu: New Bug description: CID: 201606-22528 The proposed shim package will cause this laptop complain about: "Failed to set MokSBStateRT: (2) Invalid Parameter" on boot. You will see a blue screen after the Dell logo (please find the attached screenshot). Hit ok will continue to boot. BIOS setting UEFI + SecureBoot Enabled Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot to see if everything is ok 3. Enable proposed + dist-upgrade 4. Reboot, and you will see this issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-49-generic 4.4.0-49.70 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1611 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 07:03:10 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-49-generic N/A linux-backports-modules-4.4.0-49-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chass
[Kernel-packages] [Bug 1644804] 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/1644804 Title: [Vostro 15-3568] Right key does not work on this clickpad Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Bug description: CID: 201606-22528 Dell Vostro 15-3568 The right key on the clickpad does not work on this laptop. Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot and test the right key Result: * Not working at all ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1525 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 06:52:56 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1644804/+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 1644804] [NEW] [Vostro 15-3568] Right key does not work on this clickpad
Public bug reported: CID: 201606-22528 Dell Vostro 15-3568 The right key on the clickpad does not work on this laptop. Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot and test the right key Result: * Not working at all ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1525 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 06:52:56 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 201606-22528 amd64 apport-bug taipei-lab xenial ** Also affects: hwe-next 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/1644804 Title: [Vostro 15-3568] Right key does not work on this clickpad Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Bug description: CID: 201606-22528 Dell Vostro 15-3568 The right key on the clickpad does not work on this laptop. Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot and test the right key Result: * Not working at all ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1525 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 06:52:56 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1644804/+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 1640621] Re: linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker
Certification-testing: LP: #1644782 may be a potential kernel regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1640621 Title: linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.19.0-75.83~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1640613 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1640621/+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 1641049] Re: NFSv4 do not invalidate cached information about deleted files
I was able to reproduce this bug in a bit different manner in vagrant VM environment. We were using 16.04 as nfs server and 14.04, 16.04 (with latest kernel and 4.9-rc6) and 16.10 as clients. For the testing we were using the script in the end of this post. Scenario is: * create 1k symlinks by A on share * ls that directory * delete symlinks on A * create them again on A * ls the directory again by B * delete everything repeat 10 times Kernels 4.4 (from 16.04) AND 4.8 (from 16.10) have errors like ls: cannot read symbolic link '/mnt/ubuntu/347': Input/output error ls: cannot read symbolic link '/mnt/ubuntu/891': Input/output error ls: cannot read symbolic link '/mnt/ubuntu/248': Input/output error ls: cannot read symbolic link '/mnt/ubuntu/872': Input/output error starting from the second ls. Kernels 3.13 (from 14.04) and upstream 4.9-rc6 do not have these errors. If you want vagrant files for vms please tell. Testing script: #!/bin/zsh a=9e0147f b=7329576 function exec_a { vagrant ssh -c "/bin/bash -c ${(q)*}" $a -- -q } function exec_b { vagrant ssh -c "/bin/bash -c ${(q)*}" $b -- -q } SHARE_ROOT=/mnt/ubuntu function iteration { exec_a "for i in {0..1000}; do ln -s /dev/null $SHARE_ROOT/\$i ; done" exec_b "ls -li $SHARE_ROOT | wc -l | paste <(echo \"first ls\") - " exec_a "find $SHARE_ROOT -type l -delete" exec_a "for i in {0..1000}; do ln -s /dev/null $SHARE_ROOT/\$i ; done" exec_b "ls -li $SHARE_ROOT | wc -l | paste <(echo \"second ls\") - " exec_a "find $SHARE_ROOT -type l -delete" } exec_a "find $SHARE_ROOT -type l -delete" for i in {0..10}; do iteration; done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Confirmed Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bv
[Kernel-packages] [Bug 1641049] Re: NFSv4 do not invalidate cached information about deleted files
** 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/1641049 Title: NFSv4 do not invalidate cached information about deleted files Status in linux package in Ubuntu: Confirmed Bug description: When using NFSv4 client in Ubuntu 16.04 the the following sequence of actions fails. You need a NFS server (S) and two clients (A and B). Let the NFS share be mounted at /nfsdata A: echo test > /nfsdata/file B: cat /nfsdata/file ===> test A: rm /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory A: echo test > /nfsdata/file B: cat /nfsdata/file ===> cat: No such file or directory (!) Doing echo 3 > proc/sys/vm/drop_caches as root makes the file visible on B. 14.04 works without any problem. I have attached log from one of our servers, 4.4.0-47 kernel does not fix this issue. Syslog contains rpcdebug -m nfs -s all output for the scenario (with different filenames). I can do full packet capture of NFS traffic if you want. Mounting nfs with lookupcache=positive do not fix this issue. NFSv4 server is CentOS 6.7 in our case. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 11 17:06:51 2016 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd02/12/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:13 seq crw-rw 1 root audio 116, 33 Nov 8 03:13 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=7b92d2e2-e481-471a-bc38-e178a9418aa1 InstallationDate: Installed on 2016-11-07 (3 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=11e697e5-38f8-41ae-863c-2755793044a6 ro
[Kernel-packages] [Bug 1643922] Re: Network installer fails to detect network on AMD Overdrive (ARM64)
Apologies about the delay - I was away from the hardware for a couple of days. Just tested the netboot images from http://cdimage.ubuntu.com/ubuntu- server/daily/current/zesty-server-arm64.iso and it works perfectly fine. Glad to hear that the fix has been propagated into the new releases, but I still need to be able to install the LTS one. If I'm just stupid and miss the point that I can use Zesty installer to install Xenial, do educate 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/1643922 Title: Network installer fails to detect network on AMD Overdrive (ARM64) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Kernel 4.4.0-31.50 used in the newest version of the network installer for Xenial: http://ports.ubuntu.com/dists/xenial-proposed/main/installer- arm64/current/images/MANIFEST.udebs does not contain amd-xgbe module. In result the installer fails to initialize eth0 and can not continue. The lack of module has been addressed by LP#1597573, so that latest available udebs 4.4.0-47.68 now contain the relevant module, but the netboot image doesn't seem to have been regenerated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643922/+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 1644783] [NEW] [201601-20489][Lenovo ThinkPad L460] cardreader does not work with proposed kernel 3.19.0-75
Public bug reported: A place holder to collect debugging information. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-75-generic 3.19.0-75.83~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-75.83~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-75-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Nov 25 18:15:19 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-larue2-trusty-amd64-20160406-0 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20160406-05:07 SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug package-from-proposed trusty ** Changed in: linux-lts-vivid (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1644783 Title: [201601-20489][Lenovo ThinkPad L460] cardreader does not work with proposed kernel 3.19.0-75 Status in linux-lts-vivid package in Ubuntu: Invalid Bug description: A place holder to collect debugging information. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-75-generic 3.19.0-75.83~14.04.1 ProcVersionSignature: Ubuntu 3.19.0-75.83~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-75-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Nov 25 18:15:19 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-larue2-trusty-amd64-20160406-0 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20160406-05:07 SourcePackage: linux-lts-vivid UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1644783/+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 1644771] Re: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes
** Description changed: - kdump-tools fails to load if one of the kernel parameter has double- - quotes + [SRU justification] + This fix is needed to avoid failure to load kdump-tools when one kernel boot parameter has double-quotes. + + [Impact] + kdump functionality becomes unusable + + [Fix] + Modify kdump-config to handle the presence of double-quotes in the cmdline + + [Test Case] + Edit /etc/default/grub and add the following to GRUB_CMDLINE_LINUX_DEFAULT : + + \"acpi_osi=!Windows 2012\" + $ sudo update-grub + $ sudo reboot + + kdump-config will show the following error upon reboot : + + [ 11.595868] kdump-tools[1710]: Cannot open `2012 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service': No s + uch file or directory + [ 11.602563] kdump-tools[1710]: * failed to load kdump kernel + + With this fix, the kdump-config command will run successfully + + [Regression] + None expected. Fix is already in Zesty & Debian. Only one line added to the sed statement. + + [Original description of the problem] + kdump-tools fails to load if one of the kernel parameter has double-quotes ** Tags added: sts-sru -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1644771 Title: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Yakkety: In Progress Bug description: [SRU justification] This fix is needed to avoid failure to load kdump-tools when one kernel boot parameter has double-quotes. [Impact] kdump functionality becomes unusable [Fix] Modify kdump-config to handle the presence of double-quotes in the cmdline [Test Case] Edit /etc/default/grub and add the following to GRUB_CMDLINE_LINUX_DEFAULT : \"acpi_osi=!Windows 2012\" $ sudo update-grub $ sudo reboot kdump-config will show the following error upon reboot : [ 11.595868] kdump-tools[1710]: Cannot open `2012 irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service': No s uch file or directory [ 11.602563] kdump-tools[1710]: * failed to load kdump kernel With this fix, the kdump-config command will run successfully [Regression] None expected. Fix is already in Zesty & Debian. Only one line added to the sed statement. [Original description of the problem] kdump-tools fails to load if one of the kernel parameter has double-quotes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1644771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
@Alex: I have SSD in M.2 so far primary used with Windows and original SSHD with Linux, I've installed it without any issue from USB key on my HDD without any modification of ISO. It started with the nice dell logo on boot and I could also see Dell repositories/drivers in Driver manager, but the problem was that the Fan was spinning crazy (about 3k rpm) also on powertop I could see the CPU did not get over C3 state because of old kernel (3.19). I am wondering that Dell did not release 16.04 LTS based update yet. But anyway I've replaced it back to Mint 18.1 because on kernel 4.8.x fans are spinning permanently but significantly slower (2k rpm) and also after fresh boot the are turning off correctly for a while, but they start to spin forever after some time of usage. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1644771] Re: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes
Debian bug for reference : https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=835600 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1644771 Title: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Yakkety: In Progress Bug description: kdump-tools fails to load if one of the kernel parameter has double- quotes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1644771/+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 1644771] [NEW] kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes
Public bug reported: kdump-tools fails to load if one of the kernel parameter has double- quotes ** Affects: makedumpfile (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: makedumpfile (Ubuntu Xenial) Importance: High Assignee: Louis Bouchard (louis-bouchard) Status: In Progress ** Affects: makedumpfile (Ubuntu Yakkety) Importance: High Assignee: Louis Bouchard (louis-bouchard) Status: In Progress ** Also affects: makedumpfile (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: makedumpfile (Ubuntu) Status: New => Fix Released ** Changed in: makedumpfile (Ubuntu Xenial) Importance: Undecided => High ** Changed in: makedumpfile (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: makedumpfile (Ubuntu Xenial) Assignee: (unassigned) => Louis Bouchard (louis-bouchard) ** Changed in: makedumpfile (Ubuntu Yakkety) Assignee: (unassigned) => Louis Bouchard (louis-bouchard) ** Changed in: makedumpfile (Ubuntu Xenial) Status: New => In Progress ** Changed in: makedumpfile (Ubuntu Yakkety) Status: New => In Progress ** Bug watch added: Debian Bug tracker #835600 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835600 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1644771 Title: kdump-tools: Fails to load kdump kernel when /proc/cmdline contains double quotes Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Yakkety: In Progress Bug description: kdump-tools fails to load if one of the kernel parameter has double- quotes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1644771/+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 1398859] Re: unmounting NTFS causes mount.ntfs process to get stuck in eternal kernel deep sleep
I also see this with exfat, so it rather seems to be related to fuse (as both ntfs-3g and exfat use fuse). Curiously I do not see this when running the tests on my laptop or on the Scalingstack cloud infra, just when I run them in QEMU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1398859 Title: unmounting NTFS causes mount.ntfs process to get stuck in eternal kernel deep sleep Status in linux package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Fix Released Bug description: Since Mid-November the udisks2 test (https://jenkins.qa.ubuntu.com/job /vivid-adt-udisks2/? shows it happened between Nov 13 and 19) exhibits a regression with NTFS: Unmounting causes the ntfs-3g process to go into kernel deep sleep and umount hangs forever. This can be reproduced with sudo apt install ntfs-3g sudo modprobe scsi_debug # check dmesg which drive this created; e. g. /dev/sda sudo mkntfs -F /dev/sda sudo mount /dev/sda /mnt Now you have a process which is happy: root 12821 0.0 0.0 15272 1948 ?Ss 15:49 0:00 /sbin/mount.ntfs /dev/sda /mnt -o rw You can work with /mnt, edit files, etc. But now unmount: sudo umount /mnt This never returns, and the process goes into uninterruptible kernel sleep ("D"): root 12928 0.0 0.0 15272 1948 ?Ds 15:55 0:00 /sbin/mount.ntfs /dev/sda /mnt -o rw The strace for the umount until the hang is ubuntu@autopkgtest:~$ sudo strace -vvtts1024 -p 12928 Process 12928 attached 15:56:17.938299 read(4, "0\0\0\0\2\0\0\0\2\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0", 135168) = 48 15:56:22.338931 read(4, "(\0\0\0&\0\0\0\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 135168) = 40 15:56:22.339637 sendto(5, "<29>Dec 3 15:56:22 ntfs-3g[12928]: Unmounting /dev/sda ()\n", 59, MSG_NOSIGNAL, NULL, 0) = 59 15:56:22.340509 fsync(3)= 0 15:56:22.341188 fcntl(3, F_SETLK, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0 15:56:22.341759 close(3 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ntfs-3g 1:2013.1.13AR.1-2ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 3 15:48:12 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-20 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141119) SourcePackage: ntfs-3g UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398859/+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 1398859] Re: unmounting NTFS causes mount.ntfs process to get stuck in eternal kernel deep sleep
> Curiously I do not see this when running the tests on my laptop And of course in the minute I write this it does happen again (I ran the test maybe 20 times today, and only just now it happened): [11359.569157] INFO: task systemd-udevd:341 blocked for more than 120 seconds. [11359.569163] Not tainted 4.8.0-29-generic #31~lp1626436ProposedWithTwoPatches [11359.569165] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [11359.569167] systemd-udevd D a31788e77ba8 0 341 1 0x0100 [11359.569173] a31788e77ba8 00ff84c71a68 a3149967 a31788e82ac0 [11359.569177] 88e77db0 a31788e78000 a317893bc070 a317893bc088 [11359.569179] a31788e77be0 a3149cf771c0 a31788e77bc0 85296905 [11359.569182] Call Trace: [11359.569190] [] schedule+0x35/0x80 [11359.569193] [] rwsem_down_read_failed+0x103/0x160 [11359.569197] [] call_rwsem_down_read_failed+0x18/0x30 [11359.569200] [] down_read+0x20/0x40 [11359.569202] [] get_super.part.7+0x95/0xd0 [11359.569204] [] get_super+0x26/0x30 [11359.569208] [] fsync_bdev+0x18/0x60 [11359.569211] [] invalidate_partition+0x24/0x50 [11359.569213] [] rescan_partitions+0x53/0x2b0 [11359.569216] [] ? security_capable+0x48/0x60 [11359.569218] [] __blkdev_reread_part+0x65/0x70 [11359.569220] [] blkdev_reread_part+0x23/0x40 [11359.569222] [] blkdev_ioctl+0x425/0x910 [11359.569225] [] ? __seccomp_filter+0x67/0x260 [11359.569228] [] block_ioctl+0x3d/0x50 [11359.569231] [] do_vfs_ioctl+0xa3/0x610 [11359.569233] [] ? __secure_computing+0x43/0xe0 [11359.569236] [] ? syscall_trace_enter+0xce/0x2f0 [11359.569239] [] SyS_ioctl+0x79/0x90 [11359.569241] [] do_syscall_64+0x5e/0xc0 [11359.569244] [] entry_SYSCALL64_slow_path+0x25/0x25 [11359.569320] INFO: task mount.ntfs:15670 blocked for more than 120 seconds. [11359.569323] Not tainted 4.8.0-29-generic #31~lp1626436ProposedWithTwoPatches [11359.569324] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [11359.569325] mount.ntfs D a314d0d1bd68 0 15670 5268 0x [11359.569329] a314d0d1bd68 00010003 a3178bef9c80 a3149967 [11359.569332] 3d862ecf a314d0d1c000 a3149cf771dc a3149967 [11359.569334] a3149cf771e0 a314d0d1bd80 85296905 [11359.569337] Call Trace: [11359.569340] [] schedule+0x35/0x80 [11359.569342] [] schedule_preempt_disabled+0xe/0x10 [11359.569344] [] __mutex_lock_slowpath+0xb9/0x130 [11359.569347] [] mutex_lock+0x1f/0x30 [11359.569350] [] blkdev_put+0x20/0x110 [11359.569352] [] blkdev_close+0x34/0x70 [11359.569354] [] __fput+0xe7/0x230 [11359.569356] [] fput+0xe/0x10 [11359.569358] [] task_work_run+0x80/0xa0 [11359.569361] [] exit_to_usermode_loop+0xc2/0xd0 [11359.569363] [] syscall_return_slowpath+0x4e/0x60 [11359.569366] [] entry_SYSCALL_64_fastpath+0xa6/0xa8 root 15670 0.0 0.0 16040 460 ?Ds 10:41 0:00 /sbin/mount.ntfs /dev/sdb /run/media/root/553BDB6430706196 -o rw,nodev,nosuid,uid=0,gid=0,uhelper=udisks2 (uninterruptible kernel deep sleep, 'D' state). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1398859 Title: unmounting NTFS causes mount.ntfs process to get stuck in eternal kernel deep sleep Status in linux package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Fix Released Bug description: Since Mid-November the udisks2 test (https://jenkins.qa.ubuntu.com/job /vivid-adt-udisks2/? shows it happened between Nov 13 and 19) exhibits a regression with NTFS: Unmounting causes the ntfs-3g process to go into kernel deep sleep and umount hangs forever. This can be reproduced with sudo apt install ntfs-3g sudo modprobe scsi_debug # check dmesg which drive this created; e. g. /dev/sda sudo mkntfs -F /dev/sda sudo mount /dev/sda /mnt Now you have a process which is happy: root 12821 0.0 0.0 15272 1948 ?Ss 15:49 0:00 /sbin/mount.ntfs /dev/sda /mnt -o rw You can work with /mnt, edit files, etc. But now unmount: sudo umount /mnt This never returns, and the process goes into uninterruptible kernel sleep ("D"): root 12928 0.0 0.0 15272 1948 ?Ds 15:55 0:00 /sbin/mount.ntfs /dev/sda /mnt -o rw The strace for the umount until the hang is ubuntu@autopkgtest:~$ sudo strace -vvtts1024 -p 12928 Process 12928 attached 15:56:17.938299 read(4, "0\0\0\0\2\0\0\0\2\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0", 135168) = 48 15:56:22.338931 read(4, "(\0\0\0&\0\0\0\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 135168) = 40 15:56:22.339637 sendto(5, "<29>Dec 3 15:56:22 ntfs-3g[12928]: Unmounting /dev/sda ()\n", 59, MSG_NOSIGNAL, NULL, 0) = 59 15:56:22.340509 fsync(3)
[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool
@filsd Thank you much! @Peter > Installed Ubuntu 14.04 from filsd (thank you for sharing that btw) on my i7 > Inspiron Just wondering on how you installed, since if your system initially came with Windows preinstalled, filsd's recovery media wouldn't allow you to install the system. See https://github.com/dell/dell-recovery/commit/e7eef25094a535c0447a039f741547cb955f818f Unless you modified the image :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602888 Title: Dell Inspiron 7559 fans do not shut off once started, even when cool Status in linux package in Ubuntu: Incomplete Bug description: Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to be an issue with the fan control. When I first boot up the machine the fans are off. However, after the laptop warms up under normal usage, the fans kick on and then never shut off again. Even when the CPU cools down to below 35c, the fans will continue to run. If I suspend the the laptop, and then immediately wake it up again then fans are once again off, until it warms up again. So essentially, once the fans start they don't seem to ever shut off. Fans seem to work normally under Windows 10. They turn on as needed, and then turn off once the laptop cools down. I've tried the various BIOS updates that Dell has released, without success. I am currently running Dell's latest BIOS for this laptop (v1.1.8) Below is the output of lm-sensors showing the fans running when the CPU is at a cool 35c dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 1925 RPM Processor Fan: 2143 RPM CPU:+35.0°C GPU: +1.0°C SODIMM: +49.0°C ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1709 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 13 19:18:45 2016 HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77 InstallationDate: Installed on 2016-07-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-28-generic N/A linux-backports-modules-4.4.0-28-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7559 dmi.product.version: 1.1.8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1644726] Re: AD5593R configurable multi-channel converter support
** Summary changed: - AD5593R configurable ADC/DAC/GPIO support + AD5593R configurable multi-channel converter support -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644726 Title: AD5593R configurable multi-channel converter support Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Bug description: Support Analog devices 8 channel configurable ADC/DAC/GPIO device in Ubuntu kernel. http://www.analog.com/media/en/technical-documentation/data- sheets/AD5593R.pdf This bug is used for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1644726/+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 1640613] Re: linux: 3.19.0-75.83 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Pierre Equoy (pierre-equoy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640613 Title: linux: 3.19.0-75.83 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-75.83 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1640613/+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 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
I've downloaded the kernel from http://kernel.ubuntu.com/~jsalisbury/lp1619918/xenial/ and https://launchpad.net/~canonical-kernel-security- team/+archive/ubuntu/ppa/+build/11038082 now. Both kernels have the same problem/regression (verified with "sudo btrfs fi show /") -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619918/+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