[Kernel-packages] [Bug 1539852] [NEW] Ubuntu detects no bluetooth devices, Windows 10 on same laptop detects dozen
Public bug reported: Ubuntu detects no bluetooth devices, Windows 10 on same laptop detects dozen which is probably all bluetooth devices on this floor of this apartment house. I have no idea what Bluetooth chipset I have, the only information I found with googling and various system information tools is "realtek". I am hoping that either Apport includes that information or you could tell me how do I dig out that information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-7-generic 4.3.0-7.18 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikaela1961 F pulseaudio /dev/snd/controlC1: mikaela1961 F pulseaudio CurrentDesktop: MATE Date: Sat Jan 30 09:38:26 2016 HibernationDevice: RESUME=UUID=431ec214-73ef-4058-b283-5721bb5a45d2 InstallationDate: Installed on 2015-12-12 (48 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151212) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 002: ID 13d3:3414 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic.efi.signed root=UUID=ab0e7270-40bc-4a68-a541-59fd96690354 ro rw acpi_osi= RelatedPackageVersions: linux-restricted-modules-4.3.0-7-generic N/A linux-backports-modules-4.3.0-7-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JX.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550JX.209:bd10/31/2015:svnASUSTeKCOMPUTERINC.:pnX550JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bluetooth 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/1539852 Title: Ubuntu detects no bluetooth devices, Windows 10 on same laptop detects dozen Status in linux package in Ubuntu: New Bug description: Ubuntu detects no bluetooth devices, Windows 10 on same laptop detects dozen which is probably all bluetooth devices on this floor of this apartment house. I have no idea what Bluetooth chipset I have, the only information I found with googling and various system information tools is "realtek". I am hoping that either Apport includes that information or you could tell me how do I dig out that information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-7-generic 4.3.0-7.18 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikaela1961 F pulseaudio /dev/snd/controlC1: mikaela1961 F pulseaudio CurrentDesktop: MATE Date: Sat Jan 30 09:38:26 2016 HibernationDevice: RESUME=UUID=431ec214-73ef-4058-b283-5721bb5a45d2 InstallationDate: Installed on 2015-12-12 (48 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151212) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 002: ID 13d3:3414 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic.efi.signed root=UUID=ab0e7270-40bc-4a68-a541-59fd96690354 ro rw acpi_osi= RelatedPackageVersions: linux-restricted-modules-4.3.0-7-generic N/A linux-backports-modules-4.3.0-7-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JX.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: AT
[Kernel-packages] [Bug 1539843] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1539843 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1539843 Title: External microphone does not work Status in linux package in Ubuntu: Incomplete Bug description: Asus N551JM In this laptop is combined jack for microphone and headphone. I use headset A4Tech Bloody G500 that nice work in Windows. But in Linux Mint 17.3 and ubuntu 14.04/15.10 they do not work (work only as headphone). System don't see that i connected headset and in pavucontrol i see only embeded in laptop microphone. http://www.alsa-project.org/db/?f=c3414b326df60a869d448dc437d40a9cbe888dbc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539843/+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 1539843] [NEW] External microphone does not work
Public bug reported: Asus N551JM In this laptop is combined jack for microphone and headphone. I use headset A4Tech Bloody G500 that nice work in Windows. But in Linux Mint 17.3 and ubuntu 14.04/15.10 they do not work (work only as headphone). System don't see that i connected headset and in pavucontrol i see only embeded in laptop microphone. http://www.alsa-project.org/db/?f=c3414b326df60a869d448dc437d40a9cbe888dbc ** Affects: linux (Ubuntu) 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/1539843 Title: External microphone does not work Status in linux package in Ubuntu: New Bug description: Asus N551JM In this laptop is combined jack for microphone and headphone. I use headset A4Tech Bloody G500 that nice work in Windows. But in Linux Mint 17.3 and ubuntu 14.04/15.10 they do not work (work only as headphone). System don't see that i connected headset and in pavucontrol i see only embeded in laptop microphone. http://www.alsa-project.org/db/?f=c3414b326df60a869d448dc437d40a9cbe888dbc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539843/+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 1520774] Re: btrfs kernel panic in 4.2.0-18-generic
[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/1520774 Title: btrfs kernel panic in 4.2.0-18-generic Status in linux package in Ubuntu: Expired Bug description: lsb_release -rd Description: Ubuntu 15.10 Release: 15.10 apt-cache policy linux-image-generic linux-image-generic: Installiert: 4.2.0.18.20 Installationskandidat: 4.2.0.18.20 Versionstabelle: *** 4.2.0.18.20 0 500 http://de.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ wily-security/main amd64 Packages 100 /var/lib/dpkg/status 4.2.0.16.18 0 500 http://de.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Nov 28 13:27:37 2015 HibernationDevice: RESUME=UUID=980993fc-6c0b-4081-b7db-803bf1c95cb9 InstallationDate: Installed on 2015-09-10 (79 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. PowerEdge 2950 ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 XDG_RUNTIME_DIR= ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-18-generic root=UUID=5fc5358f-103a-409e-9d07-2489c35ddf66 ro rootflags=subvol=@ RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.2 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-04 (23 days ago) dmi.bios.date: 10/30/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.7.0 dmi.board.name: 0H603H dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.7.0:bd10/30/2010:svnDellInc.:pnPowerEdge2950:pvr:rvnDellInc.:rn0H603H:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge 2950 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520774/+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 1520090] Re: unable to handle kernel NULL pointer dereference; IP: [] gen8_ppgtt_insert_entries+0x46/0x230 [i915]
[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/1520090 Title: unable to handle kernel NULL pointer dereference; IP: [] gen8_ppgtt_insert_entries+0x46/0x230 [i915] Status in linux package in Ubuntu: Expired Bug description: System crashed second day in a row and only poweroff is possible. Ubuntu 15.10 from syslog: Nov 26 11:46:47 hofvarpnir kernel: [13250.527059] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! Nov 26 11:46:47 hofvarpnir kernel: [13250.527473] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! Nov 26 11:46:47 hofvarpnir kernel: [13250.528514] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! Nov 26 11:46:47 hofvarpnir kernel: [13250.529439] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! Nov 26 11:46:47 hofvarpnir kernel: [13250.529853] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! Nov 26 11:46:47 hofvarpnir kernel: [13250.530895] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! Nov 26 11:46:47 hofvarpnir kernel: [13250.531821] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! Nov 26 11:46:47 hofvarpnir kernel: [13250.532140] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! Nov 26 11:46:47 hofvarpnir kernel: [13250.532310] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! Nov 26 11:46:47 hofvarpnir kernel: [13250.532479] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! Nov 26 11:46:48 hofvarpnir kernel: [13251.485121] [ cut here ] Nov 26 11:46:48 hofvarpnir kernel: [13251.485146] WARNING: CPU: 3 PID: 5314 at /build/linux-d3RvQM/linux-4.2.0/drivers/gpu/drm/i915/i915_gem_gtt.c:523 gen8_ppgtt_clear_range+0x1ee/0x230 [i915]() Nov 26 11:46:48 hofvarpnir kernel: [13251.485147] WARN_ON(!pd->page_table[pde]) Nov 26 11:46:48 hofvarpnir kernel: [13251.485148] Modules linked in: vhost_net vhost macvtap macvlan usb_serial_simple usbserial rfcomm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables binfmt_misc bnep arc4 intel_rapl iosf_mbi iwlmvm x86_pkg_temp_thermal intel_powerclamp coretemp input_leds serio_raw mac80211 joydev cdc_mbim cdc_wdm cdc_ncm snd_usb_audio lpc_ich snd_usbmidi_lib cdc_acm snd_seq_midi snd_seq_midi_event usbnet rtsx_pci_ms snd_rawmidi iwlwifi mii uvcvideo videobuf2_vmalloc videobuf2_memops snd_seq thinkpad_acpi cfg80211 memstick videobuf2_core nvram v4l2_common snd_hda_codec_realtek videodev snd_seq_device snd_hda_codec_generic media snd_hda_codec_hdmi btusb btrtl btbcm btintel bluetooth snd_hda_intel snd_hda_codec snd_hda_core snd _hwdep shpchp mei_me mei snd_pcm snd_timer snd soundcore mac_hid kvm_intel kvm parport_pc ppdev lp parport autofs4 btrfs drbg ansi_cprng algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear hid_generic usbhid hid rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse i2c_algo_bit ahci drm_kms_helper libahci e1000e rtsx_pci drm ptp pps_core wmi video Nov 26 11:46:48 hofvarpnir kernel: [13251.485218] CPU: 3 PID: 5314 Comm: kscreenlocker_g Tainted: GW 4.2.0-17-generic #21-Ubuntu Nov 26 11:46:48 hofvarpnir kernel: [13251.485219] Hardware name: LENOVO 20BX002KRT/20BX002KRT, BIOS JBET51WW (1.16 ) 07/08/2015 Nov 26 11:46:48 hofvarpnir kernel: [13251.485220] af8b4627 88024eebf2c8 817e8c09 Nov 26 11:46:48 hofvarpnir kernel: [13251.485223] 88024eebf320 88024eebf308 8107b3c6 Nov 26 11:46:48 hofvarpnir kernel: [13251.485224] ea000662af80 359e5083 002b 8801b72dc000 Nov 26 11:46:48 hofvarpnir kernel: [13251.485226] Call Trace: Nov 26 11:46:48 hofvarpnir kernel: [13251.485231] [] dump_stack+0x45/0x57 Nov 26 11:46:48 hofvarpnir kernel: [13251.485234] [] warn_slowpath_common+0x86/0xc0 Nov 26 11:46:48 hofvarpnir kernel: [13251.485236] [] warn_slowpath_fmt+0x55/0x70 Nov 26 11:46:48 hofvarpnir kernel: [13251.485251] [] ? i915_gem_object_put_pages_gtt+0x129/0x1d0 [i915] Nov 26 11:46:48 hofvarpnir kernel: [13251.485261] [] gen8_ppgtt_clear_range+0x1ee/0x230 [i915
[Kernel-packages] [Bug 1521189] Re: Ubuntu 15.10 installer crash in kvm unable to mount root fs
[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/1521189 Title: Ubuntu 15.10 installer crash in kvm unable to mount root fs Status in linux package in Ubuntu: Expired Bug description: qemu-system-x86_64 -hda ubuntu-sda.img -cdrom ubuntu-15.10-desktop- amd64.iso Where ubuntu-sda.img is 8 GB file filled with zeros, and iso is the Ubuntu iso It starts booting, shows the pink image (from boot loader?) then switches to text mode and after few seconds it crashes each time. The KVM is run on Debian 8 amd64. sha256 is: cc991993e3d9f57f27199877ac416157228fe6896212968d6e8c5aebd74e7ab0 ubuntu-15.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521189/+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 1539750] Re: usb headset causes "retire_playback_urb ... callbacks suppressed"
Mark Fraser, thank you for reporting this and helping make Ubuntu better. To clarify, are you having an issue with the USB headset in anyway that would correlate to the log entries you posted? ** Tags added: bios-outdated-2101 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1539750 Title: usb headset causes "retire_playback_urb ... callbacks suppressed" Status in linux package in Ubuntu: Incomplete Bug description: Whilst the USB headset is plugged in, I'm seeing usb headset causes "retire_playback_urb ... callbacks suppressed" messages in /var/log/syslog along with: Jan 29 18:58:03 Woody kernel: [35533.838345] usb 8-1: reset full-speed USB device number 2 using ohci-pci Jan 29 18:58:03 Woody pulseaudio[1826]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Jan 29 18:58:03 Woody pulseaudio[1826]: [pulseaudio] source.c: Default and alternate sample rates are the same. Jan 29 18:58:06 Woody kernel: [35537.212732] retire_capture_urb: 4164 callbacks suppressed ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-47-generic 3.19.0-47.53 ProcVersionSignature: Ubuntu 3.19.0-47.53-generic 3.19.8-ckt10 Uname: Linux 3.19.0-47-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC3D0c', '/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jan 29 19:39:15 2016 HibernationDevice: RESUME=UUID=588ca909-5d63-43e0-9878-7128eeb408e0 InstallationDate: Installed on 2014-05-01 (638 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic root=UUID=9c702c78-504f-45bc-bfa2-f41fa24221dd ro clocksource=acpi_pm quiet splash nomodeset video=uvesafb:mode_option=1680x1050-24@60,mtrr=3,scroll=ywrap PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-47-generic N/A linux-backports-modules-3.19.0-47-generic N/A linux-firmware 1.143.7 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-10-24 (97 days ago) dmi.bios.date: 11/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd11/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x: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/1539750/+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 1539729] Re: amd_freq_sensitivity cannot be loaded
** Changed in: linux (Ubuntu) Importance: Undecided => Low -- 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/1539729 Title: amd_freq_sensitivity cannot be loaded Status in linux package in Ubuntu: Confirmed Bug description: Hardware: AMD Phenom(tm) II X6 1100T amd_freq_sensitivity.ko driver cannot be loaded nor automatically upon boot, neither manually: $ modprobe amd_freq_sensitivity modprobe: ERROR: could not insert 'amd_freq_sensitivity': No such device $ sudo modprobe -f amd_freq_sensitivity modprobe: ERROR: could not insert 'amd_freq_sensitivity': Exec format error ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-76-generic 3.13.0-76.120 ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30 Uname: Linux 3.13.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrey 4173 F pulseaudio /dev/snd/controlC2: andrey 4173 F pulseaudio /dev/snd/controlC0: andrey 4173 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 29 20:31:35 2016 HibernationDevice: RESUME=UUID=af49e02b-30c7-4695-9748-f78bc942f31d InstallationDate: Installed on 2012-05-13 (1355 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic root=UUID=e073ef69-1057-4c6b-801b-5d5fa762340f ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-76-generic N/A linux-backports-modules-3.13.0-76-generic N/A linux-firmware 1.127.20 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (641 days ago) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539729/+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 1539729] Re: amd_freq_sensitivity cannot be loaded
** Tags added: bios-outdated-1604 -- 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/1539729 Title: amd_freq_sensitivity cannot be loaded Status in linux package in Ubuntu: Confirmed Bug description: Hardware: AMD Phenom(tm) II X6 1100T amd_freq_sensitivity.ko driver cannot be loaded nor automatically upon boot, neither manually: $ modprobe amd_freq_sensitivity modprobe: ERROR: could not insert 'amd_freq_sensitivity': No such device $ sudo modprobe -f amd_freq_sensitivity modprobe: ERROR: could not insert 'amd_freq_sensitivity': Exec format error ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-76-generic 3.13.0-76.120 ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30 Uname: Linux 3.13.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrey 4173 F pulseaudio /dev/snd/controlC2: andrey 4173 F pulseaudio /dev/snd/controlC0: andrey 4173 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 29 20:31:35 2016 HibernationDevice: RESUME=UUID=af49e02b-30c7-4695-9748-f78bc942f31d InstallationDate: Installed on 2012-05-13 (1355 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic root=UUID=e073ef69-1057-4c6b-801b-5d5fa762340f ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-76-generic N/A linux-backports-modules-3.13.0-76-generic N/A linux-firmware 1.127.20 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (641 days ago) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539729/+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 1539349] Re: sleep from invalid context in aa_move_mount
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1539349 Title: sleep from invalid context in aa_move_mount Status in linux package in Ubuntu: Incomplete Bug description: In xenial master-next, when I cp /bin/mount /home/ubuntu/mount, define the following policy: #include /home/ubuntu/mount { #include #include capability, network, mount, /** mkrwixr, } And then run the following script under sudo from ~/ubuntu: #!/bin/sh apparmor_parser -r /home/ubuntu/mount.aa umount -l a/b umount -l a/a umount -l a rm -rf a mkdir a mount --bind a a mount --make-slave a mkdir a/a a/b mount -t tmpfs tmpfs a/a /home/ubuntu/mount --move a/a a/b I get the following kernel warning: Jan 29 02:36:06 seth kernel: audit: type=1400 audit(1454034966.022:15): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/home/ubuntu/mount" pid=1179 comm="apparmor_parser" Jan 29 02:36:06 seth kernel: BUG: sleeping function called from invalid context at mm/slub.c:1287 Jan 29 02:36:06 seth kernel: in_atomic(): 1, irqs_disabled(): 0, pid: 1189, name: mount Jan 29 02:36:06 seth kernel: no locks held by mount/1189. Jan 29 02:36:06 seth kernel: CPU: 0 PID: 1189 Comm: mount Not tainted 4.4.0+ #4 Jan 29 02:36:06 seth kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 Jan 29 02:36:06 seth kernel: a02414bf 88007784fc28 81449309 Jan 29 02:36:06 seth kernel: 880079129580 88007784fc50 810b5789 81ce0e60 Jan 29 02:36:06 seth kernel: 0507 88007784fc78 810b5889 Jan 29 02:36:06 seth kernel: Call Trace: Jan 29 02:36:06 seth kernel: [] dump_stack+0x4b/0x72 Jan 29 02:36:06 seth kernel: [] ___might_sleep+0x179/0x230 Jan 29 02:36:06 seth kernel: [] __might_sleep+0x49/0x80 Jan 29 02:36:06 seth kernel: [] ? getname_kernel+0x34/0x120 Jan 29 02:36:06 seth kernel: [] kmem_cache_alloc+0x1db/0x2a0 Jan 29 02:36:06 seth kernel: [] getname_kernel+0x34/0x120 Jan 29 02:36:06 seth kernel: [] kern_path+0x16/0x30 Jan 29 02:36:06 seth kernel: [] aa_move_mount+0x17c/0x320 Jan 29 02:36:06 seth kernel: [] apparmor_sb_mount+0x233/0x2d0 Jan 29 02:36:06 seth kernel: [] security_sb_mount+0x57/0x80 Jan 29 02:36:06 seth kernel: [] do_mount+0xb1/0xe60 Jan 29 02:36:06 seth kernel: [] ? __might_fault+0x96/0xa0 Jan 29 02:36:06 seth kernel: [] ? memdup_user+0x53/0x80 Jan 29 02:36:06 seth kernel: [] SyS_mount+0x9f/0x100 Jan 29 02:36:06 seth kernel: [] entry_SYSCALL_64_fastpath+0x16/0x76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539349/+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 1538773] Re: Default WoL settings override BIOS and cause battery drain while powered off.
** Description changed: - Similar issue and same fix as : http://akuederle.com/fix-battery-drain/ - Wake on lan is disabled in BIOS yet Ubuntu default shutdown forces it enabled, causing unintended battery drain while powered off + + WORKAROUND: echo "ethtool -s eth0 wol d" >> /etc/rc.local.shutdown ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ethtool 1:3.16-1 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 27 17:11:08 2016 Dependencies: - gcc-5-base 5.2.1-22ubuntu2 - libc6 2.21-0ubuntu4 - libgcc1 1:5.2.1-22ubuntu2 + gcc-5-base 5.2.1-22ubuntu2 + libc6 2.21-0ubuntu4 + libgcc1 1:5.2.1-22ubuntu2 InstallationDate: Installed on 2016-01-20 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: - LANGUAGE=en_US - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: ethtool UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: linux (Ubuntu) Importance: Undecided => Low -- 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/1538773 Title: Default WoL settings override BIOS and cause battery drain while powered off. Status in linux package in Ubuntu: Incomplete Bug description: Wake on lan is disabled in BIOS yet Ubuntu default shutdown forces it enabled, causing unintended battery drain while powered off WORKAROUND: echo "ethtool -s eth0 wol d" >> /etc/rc.local.shutdown ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ethtool 1:3.16-1 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 27 17:11:08 2016 Dependencies: gcc-5-base 5.2.1-22ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-22ubuntu2 InstallationDate: Installed on 2016-01-20 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ethtool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538773/+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 1539642] Re: Integrate zfcp HBA API library 2.1.1
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1539642 Title: Integrate zfcp HBA API library 2.1.1 Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Heinz-Werner Seeck - 2016-01-29 03:25:26 == Please integrate this package into Ubuntu 16.04. This is a prerequisite for e.g. Tivoli Storage Manager.. Here you can find the location for downloading: http://www.ibm.com/developerworks/linux/linux390/zfcp-hbaapi-2.1.1.html It is available under the Common Public License Version 1.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539642/+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 1538684] Re: BUG: Bad page map in process renderer_crash_ pte:800000009af93865 pmd:c6abb067
*** This bug is a duplicate of bug 1538683 *** https://bugs.launchpad.net/bugs/1538683 ** This bug has been marked a duplicate of bug 1538683 BUG: Bad page map in process renderer_crash_ pte:80009af93865 pmd:c6abb067 -- 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/1538684 Title: BUG: Bad page map in process renderer_crash_ pte:80009af93865 pmd:c6abb067 Status in linux package in Ubuntu: Confirmed Bug description: suddenly the error originated Ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-7-generic 4.3.0-7.18 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rmarquez 2220 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 27 13:41:34 2016 HibernationDevice: RESUME=UUID=28ea2be7-6648-492b-957e-252c9384d2fd InstallationDate: Installed on 2016-01-20 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) IwConfig: enp3s0no wireless extensions. lono wireless extensions. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic root=UUID=a9ea17d8-cbf3-4240-9b7c-5cedf41ee185 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.3.0-7-generic N/A linux-backports-modules-4.3.0-7-generic N/A linux-firmware 1.155 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: RQG4110H.86A.0017.2011.0322.1523 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41RQ dmi.board.vendor: Intel Corporation dmi.board.version: AAE54511-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0017.2011.0322.1523:bd03/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-201:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538684/+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 1538683] Re: BUG: Bad page map in process renderer_crash_ pte:800000009af93865 pmd:c6abb067
WindTux, thank you for reporting this and helping make Ubuntu better. In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following: 1) The one to test is at the very top line at the top of the page (not the daily folder). 2) The release names are irrelevant. 3) The folder time stamps aren't indicative of when the kernel actually was released upstream. 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . If testing on your main install would be inconvenient, one may: 1) Install Ubuntu to a different partition and then test this there. 2) Backup, or clone the primary install. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: latest-bios-0017 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1538683 Title: BUG: Bad page map in process renderer_crash_ pte:80009af93865 pmd:c6abb067 Status in linux package in Ubuntu: Incomplete Bug description: suddenly the error originated Ubuntu 16.04 ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-7-generic 4.3.0-7.18 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rmarquez 2220 F pulseaudio Date: Wed Jan 27 13:39:53 2016 Failure: oops HibernationDevice: RESUME=UUID=28ea2be7-6648-492b-957e-252c9384d2fd InstallationDate: Installed on 2016-01-20 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) IwConfig: enp3s0no wireless extensions. lono wireless extensions. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic root=UUID=a9ea17d8-cbf3-4240-9b7c-5cedf41ee185 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9 RfKill: SourcePackage: linux Title: BUG: Bad page map in process renderer_crash_ pte:80009af93865 pmd:c6abb067 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: RQG4110H.86A.0017.2011.0322.1523 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41RQ dmi.board.vendor: Intel Corporation dmi.board.version: AAE54511-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0017.2011.0322.1523:bd03/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-201:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538683/+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 1520457] Re: Telemetry Enabling for Broxton-P
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1520457 Title: Telemetry Enabling for Broxton-P Status in intel: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Intel PM Telemetry is a software mechanism via various SoC PM and performance related parameters like PM counters, firmware trace verbosity, the status of different devices inside the SoC, can be monitored and analyzed. HW: Apollo Lake Scheduler: Kernel: 4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1520457/+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 1461360] Re: [Feature]Knights Landing PMU (Performance Monitoring Unit) support
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1461360 Title: [Feature]Knights Landing PMU (Performance Monitoring Unit) support Status in intel: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Add PMU support to the perf event subsystem for Knights Landing Schedule: 4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1461360/+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 1538404] Re: logitech wireless keyboard (K270) and trackball (M570) laggy with latest kernels
TIm, thank you for reporting this and helping make Ubuntu better. In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following: 1) The one to test is at the very top line at the top of the page (not the daily folder). 2) The release names are irrelevant. 3) The folder time stamps aren't indicative of when the kernel actually was released upstream. 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . If testing on your main install would be inconvenient, one may: 1) Install Ubuntu to a different partition and then test this there. 2) Backup, or clone the primary install. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: latest-bios-f9 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1538404 Title: logitech wireless keyboard (K270) and trackball (M570) laggy with latest kernels Status in linux package in Ubuntu: Incomplete Bug description: Recently inputs from my logitech wireless keyboard and trackball, became very laggy, and dropping out at times. This is a regression since 4.3.0-2.11 works perfectly 4.3.0-5.16 is really bad, with devices often dropping out completely or loosing all input for over 30secs at times 4.3.0.7.8 seems better, but still very slow at times, sometimes is like typing 1 character per second or noticable lag on mouse input. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-7-generic 4.3.0-7.18 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darkness 8233 F pulseaudio /dev/snd/controlC0: darkness 8233 F pulseaudio CurrentDesktop: GNOME Date: Wed Jan 27 16:14:55 2016 InstallationDate: Installed on 2012-09-23 (1221 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic root=UUID=71eeb904-068b-41c2-9d34-59365ca4c3ad ro quiet splash init=/lib/systemd/systemd nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.3.0-7-generic N/A linux-backports-modules-4.3.0-7-generic N/A linux-firmware 1.155 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: P67A-UD3R-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67A-UD3R-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538404/+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 1527462] Re: [Feature]Skylake GT4e support
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1527462 Title: [Feature]Skylake GT4e support Status in intel: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Add PCIID for SKL GT4e in graphic statck. Hardware: Greenlow or SKL-H 4+4e upstream: kernel: 4.5 drm: 2.4.66 xf86-video-intel: TBD mesa: mesa-11.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1527462/+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 1533035] Re: [BugFix] Skylake intel-lpss fix
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1533035 Title: [BugFix] Skylake intel-lpss fix Status in intel: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Canonical found several I2C touchpad couldn't work on OEM SKL machines once they enable intel-lpss driver. This entry is used to track such fix made by Intel. So that these fix could enter into 16.04 release. The following bugs are reported by Canonical for i2c touchpad failure. [LP1496306] Monet][Redwood][dino2] touchpad doesn't work after Canonical back port LPSS patch set from 4.3 kernel into 15.04 kernel. [LP 1505913] Re: [monet] touchpad doesn't work with Ubuntu kernel 3.19.0-29.31 [LP 1505914] [pandora] [vangogh] touchpad doesn't work with Ubuntu kernel 3.19.0-29.31 [LP 1505910] Re: [dino2] touchpad doesn't work with Ubuntu kernel 3.19.0-29.31 [LP 1505917] Re: [maple] touchpad doesn't work with Ubuntu kernel 3.19.0-29.31 [LP 1505919] Re: [iris] touchpad doesn't work with Ubuntu kernel 3.19.0-29.31 upstream schedule: 4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1533035/+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 1398274] Re: [Feature] TPM2.0 kernel support
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1398274 Title: [Feature] TPM2.0 kernel support Status in intel: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: This entry will track TPM2.0 kernel work. Intel schedule: basic device driver:4.0 device driver improvement: 4.5 trusted keys: 4.5 sysfs attributes: 4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1398274/+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 1538202] Re: Reboot then waking up after suspend on Acer Asprire 7540
MrRomanze, thank you for reporting this and helping make Ubuntu better. To clarify: 1) Do you require the use of the lowlatency kernel? 2) If so, while using it if you remove the following non-default kernel boot parameters is it still reproducible: acpi_sleep=nonvs quiet splash acpi_sleep=nonvs ** Tags added: latest-bios-1.11 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1538202 Title: Reboot then waking up after suspend on Acer Asprire 7540 Status in linux package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 15.10. Then I wake up computer after suspend, it just reboots. This happens with X.org ATI driver only, but with fglrx I'm greeted with a black screen (even backlights are turned off) and I have to reboot anyway. (but whatever, fglrx works horrible, I would never install it back) ALSO, computer wakes up normally on latest upstream kernel (4.5.0-040500rc1-generic) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-25-lowlatency 4.2.0-25.30 ProcVersionSignature: Ubuntu 4.2.0-25.30-lowlatency 4.2.6 Uname: Linux 4.2.0-25-lowlatency x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: potato 2548 F pulseaudio /dev/snd/controlC1: potato 2548 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 26 20:19:24 2016 HibernationDevice: RESUME=UUID=2277e00a-0411-4136-b180-2892752df2e0 InstallationDate: Installed on 2016-01-17 (9 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire 7540 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-lowlatency root=UUID=ae6c8d51-38da-4c25-9281-6b9ceac5b2ca ro quiet splash acpi_sleep=nonvs quiet splash acpi_sleep=nonvs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-25-lowlatency N/A linux-backports-modules-4.2.0-25-lowlatency N/A linux-firmware 1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.11 dmi.board.name: JV71TR dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone: dmi.product.name: Aspire 7540 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538202/+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 1538205] Re: Touchpad lock button locks mouse completely on Acer Aspire 7540
MrRomanze, thank you for reporting this and helping make Ubuntu better. To clarify, is this reproducible with the generic kernel? ** Tags added: latest-bios-1.11 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1538205 Title: Touchpad lock button locks mouse completely on Acer Aspire 7540 Status in linux package in Ubuntu: Incomplete Bug description: Then I click touchpad lock button, it works, button glows, notification shows up, mouse locks. However, then I press it again, it wouldn't unlock the touchpad. (but button stops to glow and notifications shows up again too) The only solution is to reboot. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-25-lowlatency 4.2.0-25.30 ProcVersionSignature: Ubuntu 4.2.0-25.30-lowlatency 4.2.6 Uname: Linux 4.2.0-25-lowlatency x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: potato 2548 F pulseaudio /dev/snd/controlC1: potato 2548 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 26 20:29:28 2016 HibernationDevice: RESUME=UUID=2277e00a-0411-4136-b180-2892752df2e0 InstallationDate: Installed on 2016-01-17 (9 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire 7540 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-lowlatency root=UUID=ae6c8d51-38da-4c25-9281-6b9ceac5b2ca ro quiet splash acpi_sleep=nonvs quiet splash acpi_sleep=nonvs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-25-lowlatency N/A linux-backports-modules-4.2.0-25-lowlatency N/A linux-firmware 1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.11 dmi.board.name: JV71TR dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone: dmi.product.name: Aspire 7540 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538205/+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 1454892] Re: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host
I built a Trusty test kernel. Sorry for the delay, it required backporting 20 other commits. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1454892/trusty/ Can you test this kernel and see if it resolves this bug? Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1454892 Title: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux-lts-utopic package in Ubuntu: Won't Fix Status in linux-lts-trusty source package in Precise: In Progress Status in linux source package in Trusty: In Progress Status in linux-lts-utopic source package in Trusty: Won't Fix Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Bug description: hv_netvsc: Use the xmit_more skb flag to optimize signaling the host Based on the information given to this driver (via the xmit_more skb flag), we can defer signaling the host if more packets are on the way. This will help make the host more efficient since it can potentially process a larger batch of packets. Implement this optimization. Upstream commit: https://git.kernel.org/cgit/linux/kernel/git/davem /net-next.git/commit/?id=82fa3c776e5abba7ed6e4b4f4983d14731c37d6a This commit may imply other commits previously requested, for example https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452074 Requested for all typical Hyper-V targets: 15.10, 15.04, 14.10, 14.04, 14.04 HWE, 12.02, and 12.02 HWE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454892/+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 1537918] Re: Kernel doesn't support UDF
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1537918 Title: Kernel doesn't support UDF Status in linux package in Ubuntu: Confirmed Bug description: I was pulling my hair out for the last six months trying to figure out why the heck some DVDs (encrypted, pressed, burned, it doesn't matter) just will not be recognized. In the GNOME Disk Utility, the disks show up as X.X GB Unknown, and will not mount. I have to manually go into a terminal, type sudo mount /dev/sr0 /mnt and just deal with it. This is a real pain, and I just recently figured out why. According to this: http://superuser.com/questions/730130/how-to-get-ubuntu-12-04-to- recognize-the-udf-filesystem in addition to this: http://www.linuxquestions.org/questions/linux-desktop-74/some-udf- dvds-will-not-mount-unknown-filesystem-4175550577/ I deduced that the kernel was not compiled with UDF support. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ihatewindows 28002 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 22 13:55:28 2016 HibernationDevice: RESUME=UUID=2f0f1d7c-4117-40df-9314-f2556c82fc3b InstallationDate: Installed on 2015-11-12 (71 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E5420 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-22-generic N/A linux-backports-modules-4.2.0-22-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd11/30/2011:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 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/1537918/+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 1536474] Re: [Feature] Update i40e and i40evf driver in 16.04
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1536474 Title: [Feature] Update i40e and i40evf driver in 16.04 Status in intel: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: In order to sync with Intel ethernet drivers on Sourceforge, i40e and i40evf driver in 16.04 should be updated. Upstream schedule: 3.15 later To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1536474/+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 1537666] Re: ISST-LTE: Ubuntu 14.04.4 LPAR interrupts at check_and_cede_processor
** Changed in: linux (Ubuntu) Status: New => Triaged -- 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/1537666 Title: ISST-LTE: Ubuntu 14.04.4 LPAR interrupts at check_and_cede_processor Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - YUECHANG E. MEI - 2015-12-11 17:19:07 == ---Problem Description--- We have an Ubuntu 14.04.4 LPAR, conelp2. It is running stress test: base, io, and tcp. When checking "dmesg", we see this interruption: [Fri Dec 11 13:58:50 2015] --- interrupt: 501 at plpar_hcall_norets+0x1c/0x28 [Fri Dec 11 13:58:50 2015] LR = check_and_cede_processor+0x34/0x50 In the previous test, conelp2 stopped all the stress tests by itself because it ran out of memory. Is the out of memory issue relating to the interruption? Contact Information = Yuechang (Erin) Mei /ye...@us.ibm.com, Raja Sunkari /rajas...@in.ibm.com ---uname output--- Linux conelp2 4.2.0-21-generic #25~14.04.1-Ubuntu SMP Thu Dec 3 13:55:42 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = EUH Alpine 8408-E8E ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install Ubuntu 14.04.4 in a LPAR, then update to the latest 14.04.4 kernel by using this workaround: echo "deb http://software.linux.ibm.com/pub/ubuntu-ppc64el-repository/ trusty-proposed main restricted universe multiverse" >> /etc/apt/sources.list apt-get update apt-get install linux-image-generic-lts-wily 2. Setup the Stress test, and start base,io, tcp 3. After an hour, check dmesg, then you will see the message about the interruption Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com, Raja Sunkari /rajas...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. == Comment: #1 - YUECHANG E. MEI - 2015-12-11 17:23:00 == == Comment: #3 - YUECHANG E. MEI - 2015-12-14 15:23:33 == == Comment: #4 - MAMATHA INAMDAR - 2015-12-15 03:56:14 == dmrsg show page allocation failure [Fri Dec 11 13:45:38 2015] swapper/127: page allocation failure: order:0, mode:0x120 [Fri Dec 11 13:45:38 2015] CPU: 127 PID: 0 Comm: swapper/127 Not tainted 4.2.0-21-generic #25~14.04.1-Ubuntu [Fri Dec 11 13:45:38 2015] Call Trace: [Fri Dec 11 13:45:38 2015] [c0027fbc3890] [c0a805ec] dump_stack+0x90/0xbc (unreliable) [Fri Dec 11 13:45:38 2015] [c0027fbc38c0] [c021c118] warn_alloc_failed+0x118/0x160 [Fri Dec 11 13:45:38 2015] [c0027fbc3960] [c0221114] __alloc_pages_nodemask+0x834/0xa60 [Fri Dec 11 13:45:38 2015] [c0027fbc3b10] [c0221404] __alloc_page_frag+0xc4/0x190 [Fri Dec 11 13:45:38 2015] [c0027fbc3b50] [c08f6d20] netdev_alloc_frag+0x50/0x80 [Fri Dec 11 13:45:38 2015] [c0027fbc3b80] [c0764e80] tg3_alloc_rx_data+0xa0/0x2c0 [Fri Dec 11 13:45:38 2015] [c0027fbc3be0] [c0767344] tg3_poll_work+0x484/0x1070 [Fri Dec 11 13:45:38 2015] [c0027fbc3ce0] [c0767f8c] tg3_poll_msix+0x5c/0x210 [Fri Dec 11 13:45:38 2015] [c0027fbc3d30] [c090ebb8] net_rx_action+0x2d8/0x430 [Fri Dec 11 13:45:38 2015] [c0027fbc3e40] [c00ba124] __do_softirq+0x174/0x390 [Fri Dec 11 13:45:38 2015] [c0027fbc3f40] [c00ba6c8] irq_exit+0xc8/0x100 [Fri Dec 11 13:45:38 2015] [c0027fbc3f60] [c00111ec] __do_irq+0x8c/0x190 [Fri Dec 11 13:45:38 2015] [c0027fbc3f90] [c0024278] call_do_irq+0x14/0x24 [Fri Dec 11 13:45:38 2015] [c002763a39b0] [c0011390] do_IRQ+0xa0/0x120 [Fri Dec 11 13:45:38 2015] [c002763a3a10] [c00099b0] restore_check_irq_replay+0x2c/0x70 [Fri Dec 11 13:45:38 2015] --- interrupt: 501 at plpar_hcall_norets+0x1c/0x28 [Fri Dec 11 13:45:38 2015] LR = check_and_cede_processor+0x34/0x50 [Fri Dec 11 13:45:38 2015] [c002763a3d00] [c08a8d90] check_and_cede_processor+0x20/0x50 (unreliable) [Fri Dec 11 13:45:38 2015] [c002763a3d60] [c08a8fb8] shared_cede_loop+0x68/0x170 [Fri Dec 11 13:45:38 2015] [c002763a3da0] [c08a615c] cpuidle_enter_state+0xbc/0x350 [Fri Dec 11 13:45:38 2015] [c002763a3e00] [c0110f3c] call_cpuidle+0x7c/0xd0 [Fri Dec 11 13:45:38 2015] [c002763a3e40] [c01112d0] cpu_startup_entry+0x340/0x450 [Fri Dec 11 13:45:38 2015] [c002763a3f10] [c0044ab4] start_secondary+0x364/0x3a0 [Fri Dec 11 13:45:38 2015] [c002763a3f90] [c0008b6c] start_secondary_prolog+0x10/0x14 [Fri Dec 11 13:45:38 2015] Mem-Info: [Fri Dec 11 13:45:38 2015] active_anon:714 inactive_anon:2255 i
[Kernel-packages] [Bug 1536327] Re: [Lenovo G50-30] freezes
Marko Lazic, to clarify, are you referring to when you are using 4.5-rc1? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1536327 Title: [Lenovo G50-30] freezes Status in linux package in Ubuntu: Incomplete Bug description: My computer freezes. The best one and most reliable that i found was kernel 4.1.13-realtime however it has wifi bugs and system freezes as well. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marko 1224 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=8c1be7c0-8725-4999-b281-2c800eb41898 InstallationDate: Installed on 2016-01-13 (7 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-26-generic root=UUID=b02421be-8ad3-4413-8476-bf02e076581d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-26.31-generic 4.2.8-ckt1 RelatedPackageVersions: linux-restricted-modules-4.2.0-26-generic N/A linux-backports-modules-4.2.0-26-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN48WW:bd08/03/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536327/+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 1529232] Re: Scanner not detected over wifi since after 3.13.0-68
Lucas Partridge, to see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Tags added: needs-reverse-bisect ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1529232 Title: Scanner not detected over wifi since after 3.13.0-68 Status in linux package in Ubuntu: Incomplete Bug description: Please see http://ubuntuforums.org/showthread.php?t=2306464 for details. I'm running 64-bit 14.04 LTS ubuntu. When I boot my PC into 3.13.0-68-generic (via the 'ubuntu advanced' menu item in grub) I can detect my scanner over wifi using scangearmp. However since 3.13.0-70-generic I have not been able to detect my scanner over wifi. My current kernel is 3.13.0-74-generic. Therefore I suspect a regression has occurred between 3.13.0-68-generic and 3.13.0-70-generic: Scanner *is* detected by scangearmp over wifi and it scans documents as expected in this version: uname -a Linux zorro 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux But scanner is *not* detected by scangearmp in this version or later: Linux zorro 3.13.0-70-generic #113-Ubuntu SMP Mon Nov 16 18:34:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Note that this happened before some time ago. i.e., The scanner was detected over wifi, then not, then it was again some time later. Then this latest break occurred again. I suspect successive updates are fixing or breaking the detection accordingly. $ dpkg -l | grep scangear ii scangearmp-common 2.20-1 amd64ScanGear MP for Linux. ii scangearmp-mg7100series 2.20-1 amd64ScanGear MP for Linux. Device is Canon Pixma MG7150 (combined printer, scanner, copier). Note the printer works fine over wifi; only the scanner is affected. I can see from the changelog at http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_3.13.0-74.118/changelog that many changes went into 3.13.0-69.112 but it's not obvious to me which of these might have caused the regression. --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lucas 1604 F pulseaudio /dev/snd/controlC2: lucas 1604 F pulseaudio /dev/snd/controlC0: lucas 1604 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0140e677-b732-4571-a80a-fc5d7c00359c InstallationDate: Installed on 2014-12-05 (387 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7528 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic root=UUID=941f5e44-f02e-42f2-ac78-5f6b4b9e98e9 ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 RelatedPackageVersions: linux-restricted-modules-3.13.0-74-generic N/A linux-backports-modules-3.13.0-74-generic N/A linux-firmware 1.127.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G31M3-F(MS-7528) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd06/19/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7528:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-F(MS-7528):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7528 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529232/+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 1430625] Re: ACPI PCC probe failed.
More painful when it comes up during installation process. IDK about when a true fix to code might happen but... a NOPCC option would nice for initial installations where newer users are not yet building their own kernels. Better yet to help true noobs and expedite things everyone wanting to do a quick and dirty install before recompiling... couldn't options for MOBO architecture be set automatically based on a quick examination of BIOS date? For instance the hardware for PCC simply did not exist before a certain date. So that code ideally should be automatically turned off if the BIOS date is not later than that. Not a complete or perfect solution of course. But I suspect the volume of problem reports would be dramatically reduced as many newer Linux inductees tend to either start with well used older hardware or brand new hardware. -- 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/1430625 Title: ACPI PCC probe failed. Status in One Hundred Papercuts: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: systemd message in RED dmesg: [1.068627] ACPI PCC probe failed. In kernel 4.0-rc3 Not red ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-7-generic 3.19.0-7.7 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 3118 F...m pulseaudio /dev/snd/controlC0: caravena 3118 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 11 01:13:11 2015 InstallationDate: Installed on 2014-09-25 (167 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-7-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ 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.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1430625/+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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
I meant OTA-9 BTW -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Upgraded to OTA-0 and still not working with my E4.5 and Toyota Avensis. I have access to phones running the following OS: 1. Symbian 2.Android 3.iOS 4. Firefox OS 5. Ubuntu All of them connect to the car bluetooth without issue, except Ubuntu. It's been an issue for a year now. Can we have a big push to sort this please? I can help with testing. -- 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/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1539102] Re: EPOW related RTAS event messages in kernel logs
** Also affects: linux (Ubuntu Xenial) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Wily) Status: New => In Progress ** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) -- 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/1539102 Title: EPOW related RTAS event messages in kernel logs Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: In Progress Status in linux source package in Xenial: Fix Committed Bug description: Problem Description === EPOW related RTAS event messages in kernel logs Machine Type = POWER8 Steps to Reproduce = 1) Install Ubuntu14.04 on a Power VM LPAR. 2) Post reboot following events are logged into dmesg & /var/log/syslog [216112.739470] Non critical power or cooling issue cleared [216122.992606] RTAS: event: 187589, Type: EPOW, Severity: 1 [216122.992609] Non critical power or cooling issue cleared [216129.240731] RTAS: event: 187590, Type: EPOW, Severity: 1 [216129.240733] Non critical power or cooling issue cleared [216141.612689] RTAS: event: 187591, Type: EPOW, Severity: 1 [216141.612691] Non critical power or cooling issue cleared [216147.830578] RTAS: event: 187592, Type: EPOW, Severity: 1 [216147.830580] Non critical power or cooling issue cleared [216158.334408] RTAS: event: 187593, Type: EPOW, Severity: 1 [216158.334410] Non critical power or cooling issue cleared [216199.883138] RTAS: event: 187594, Type: EPOW, Severity: 1 [216199.883140] Non critical power or cooling issue cleared [216244.596335] RTAS: event: 187595, Type: EPOW, Severity: 1 [216244.596337] Non critical power or cooling issue cleared [216250.853514] RTAS: event: 187596, Type: EPOW, Severity: 1 [216250.853516] Non critical power or cooling issue cleared [216263.319986] RTAS: event: 187597, Type: EPOW, Severity: 1 [216263.319989] Non critical power or cooling issue cleared [216271.438925] RTAS: event: 187598, Type: EPOW, Severity: 1 The log is filled with several such messages along with RTAS: event: 13884, Type: Platform Error, Severity: 2 RTAS: event: 13885, Type: Platform Error, Severity: 2 RTAS: event: 13886, Type: Platform Error, Severity: 2 RTAS: event: 13887, Type: Platform Error, Severity: 2 RTAS: event: 13888, Type: Platform Error, Severity: 2 RTAS: event: 13889, Type: Platform Error, Severity: 2 RTAS: event: 13890, Type: Platform Error, Severity: 2 RTAS: event: 13891, Type: Platform Error, Severity: 2 Regrads Praveen == Comment: #2 - VASANT HEGDE - == Below upstream patch fixes this issue..I believe this will apply cleanly on top of Ubuntu 14.04.04 kernel. commit b4af279a7cba5cc1f665485e8ecdf272f1ba0cc5 Author: Vipin K Parashar Date: Tue Dec 1 16:43:42 2015 +0530 powerpc/pseries: Limit EPOW reset event warnings Kernel prints respective warnings about various EPOW events for user information/action after parsing EPOW interrupts. At times below EPOW reset event warning is seen to be flooding kernel log over a period of time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539102/+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 1539750] 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/1539750 Title: usb headset causes "retire_playback_urb ... callbacks suppressed" Status in linux package in Ubuntu: Confirmed Bug description: Whilst the USB headset is plugged in, I'm seeing usb headset causes "retire_playback_urb ... callbacks suppressed" messages in /var/log/syslog along with: Jan 29 18:58:03 Woody kernel: [35533.838345] usb 8-1: reset full-speed USB device number 2 using ohci-pci Jan 29 18:58:03 Woody pulseaudio[1826]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Jan 29 18:58:03 Woody pulseaudio[1826]: [pulseaudio] source.c: Default and alternate sample rates are the same. Jan 29 18:58:06 Woody kernel: [35537.212732] retire_capture_urb: 4164 callbacks suppressed ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-47-generic 3.19.0-47.53 ProcVersionSignature: Ubuntu 3.19.0-47.53-generic 3.19.8-ckt10 Uname: Linux 3.19.0-47-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC3D0c', '/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jan 29 19:39:15 2016 HibernationDevice: RESUME=UUID=588ca909-5d63-43e0-9878-7128eeb408e0 InstallationDate: Installed on 2014-05-01 (638 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic root=UUID=9c702c78-504f-45bc-bfa2-f41fa24221dd ro clocksource=acpi_pm quiet splash nomodeset video=uvesafb:mode_option=1680x1050-24@60,mtrr=3,scroll=ywrap PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-47-generic N/A linux-backports-modules-3.19.0-47-generic N/A linux-firmware 1.143.7 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-10-24 (97 days ago) dmi.bios.date: 11/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd11/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x: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/1539750/+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 1502781] Re: Bluetooth 0930:021c not working in Ubuntu 15.10
hey folks - got it to work finally! awesome! :-D i got the key insight here: https://bugzilla.kernel.org/attachment.cgi?id=197861&action=diff but thanks to you - since without your notes, i would not have guessed the issue was with that file btusb.c Many many thanks! thomas -- 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/1502781 Title: Bluetooth 0930:021c not working in Ubuntu 15.10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: Ubuntu detects the bluetooth hardware (it shows the bluetooth icon in the status bar), and I can turn it on or off and set the visibility and such. However, it is never able to find any bluetooth device. "lsusb" shows: Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012 Bluetooth "rfkill list" output: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no "hciconfig -a" output: hci0: Type: BR/EDR Bus: USB BD Address: 18:CF:5E:09:55:43 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING RX bytes:1313 acl:0 sco:0 events:88 errors:0 TX bytes:3200 acl:0 sco:0 commands:87 errors:0 Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x8f Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Name: 'lucas-Leon' Class: 0x0c010c Service Classes: Rendering, Capturing Device Class: Computer, Laptop HCI Version: 4.1 (0x7) Revision: 0x1102 LMP Version: 4.0 (0x6) Subversion: 0x1 Manufacturer: Atheros Communications, Inc. (69) Thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lucas 1143 F pulseaudio /dev/snd/controlC1: lucas 1143 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 5 09:19:20 2015 HibernationDevice: RESUME=UUID=58bcbcd9-672f-4530-b8b5-775f76fc9187 InstallationDate: Installed on 2015-10-04 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012 Bluetooth Bus 001 Device 002: ID 04f2:b433 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Toshiba Leon ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-14-generic root=UUID=a107b544-64af-4e74-89a7-2c0e9fe8ce8d ro rootflags=subvol=@ tpm_tis.interrupts=0 modprobe.blacklist=ehci_pci quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.148 SourcePackage: linux UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Toshiba dmi.modalias: dmi:bvncoreboot:bvr:bd08/26/2014:svnToshiba:pnLeon:pvr1.0:cvnToshiba:ct3:cvr: dmi.product.name: Leon dmi.product.version: 1.0 dmi.sys.vendor: Toshiba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502781/+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 1502781] Re: Bluetooth 0930:021c not working in Ubuntu 15.10
btw, my headsets seem to work now too! not sure how why - but i added a whole bunch of alsa stuff and i upgraded to kernel 4.4 i guess i would need to try the other kernels etc to see what made it work, but i am afraid - all i care about - is exactly that - it works! :-D -- 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/1502781 Title: Bluetooth 0930:021c not working in Ubuntu 15.10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: Ubuntu detects the bluetooth hardware (it shows the bluetooth icon in the status bar), and I can turn it on or off and set the visibility and such. However, it is never able to find any bluetooth device. "lsusb" shows: Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012 Bluetooth "rfkill list" output: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no "hciconfig -a" output: hci0: Type: BR/EDR Bus: USB BD Address: 18:CF:5E:09:55:43 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING RX bytes:1313 acl:0 sco:0 events:88 errors:0 TX bytes:3200 acl:0 sco:0 commands:87 errors:0 Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x8f Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Name: 'lucas-Leon' Class: 0x0c010c Service Classes: Rendering, Capturing Device Class: Computer, Laptop HCI Version: 4.1 (0x7) Revision: 0x1102 LMP Version: 4.0 (0x6) Subversion: 0x1 Manufacturer: Atheros Communications, Inc. (69) Thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lucas 1143 F pulseaudio /dev/snd/controlC1: lucas 1143 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 5 09:19:20 2015 HibernationDevice: RESUME=UUID=58bcbcd9-672f-4530-b8b5-775f76fc9187 InstallationDate: Installed on 2015-10-04 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012 Bluetooth Bus 001 Device 002: ID 04f2:b433 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Toshiba Leon ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-14-generic root=UUID=a107b544-64af-4e74-89a7-2c0e9fe8ce8d ro rootflags=subvol=@ tpm_tis.interrupts=0 modprobe.blacklist=ehci_pci quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.148 SourcePackage: linux UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Toshiba dmi.modalias: dmi:bvncoreboot:bvr:bd08/26/2014:svnToshiba:pnLeon:pvr1.0:cvnToshiba:ct3:cvr: dmi.product.name: Leon dmi.product.version: 1.0 dmi.sys.vendor: Toshiba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502781/+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 1536327] Re: [Lenovo G50-30] freezes
I am sad to say that freezing bug still persists, only it takes longer for freeze to occur. -- 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/1536327 Title: [Lenovo G50-30] freezes Status in linux package in Ubuntu: Incomplete Bug description: My computer freezes. The best one and most reliable that i found was kernel 4.1.13-realtime however it has wifi bugs and system freezes as well. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marko 1224 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=8c1be7c0-8725-4999-b281-2c800eb41898 InstallationDate: Installed on 2016-01-13 (7 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 80G0 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-26-generic root=UUID=b02421be-8ad3-4413-8476-bf02e076581d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-26.31-generic 4.2.8-ckt1 RelatedPackageVersions: linux-restricted-modules-4.2.0-26-generic N/A linux-backports-modules-4.2.0-26-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN48WW:bd08/03/2015:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536327/+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 1529535] Re: Atheros AR3012 USB Bluetooth adapter not recognized
I got it to work! I just changed the file as sugested here!! https://bugzilla.kernel.org/attachment.cgi?id=197861&action=diff awesome. :-D -- 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/1529535 Title: Atheros AR3012 USB Bluetooth adapter not recognized Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 15.10 Fresh install. gellenburg@usatlll01:~$ lspci 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) 00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3) 00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3) 00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03) 00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) 03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) gellenburg@usatlll01:~$ lsusb Bus 003 Device 002: ID 8087:8001 Intel Corp. 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 003: ID 058f:3822 Alcor Micro Corp. Bus 001 Device 002: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub gellenburg@usatlll01:~$ usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=11 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=04.02 S: Manufacturer=Linux 4.2.0-22-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=04ca ProdID=300d Rev=00.01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none) I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none) T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 3 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=058f ProdID=3822 Rev=05.00 S: Product=USB 2.0 Camera C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=200mA I: If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo I: If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 4 D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1 P: Vendor=1d6b ProdID=0003 Rev=04.02 S: Manufacturer=Linux 4.2.0-22-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 2 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=04.02 S: Manufacturer=Linux 4.2.0-22-generic ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1d.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 8 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=8001 Rev=00.03 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub gellenburg@usatlll01:~$ uname -a Linux usatlll01 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux gellenburg@usatlll01:~$ rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no gellenburg@usatlll01:~$ gellenburg@usatlll01:~$ dmesg | grep -i blue [ 18.543198] Bluetooth: Core ver 2.20 [ 18.543213] Bluetooth: HCI device and connection manager i
[Kernel-packages] [Bug 1539750] [NEW] usb headset causes "retire_playback_urb ... callbacks suppressed"
Public bug reported: Whilst the USB headset is plugged in, I'm seeing usb headset causes "retire_playback_urb ... callbacks suppressed" messages in /var/log/syslog along with: Jan 29 18:58:03 Woody kernel: [35533.838345] usb 8-1: reset full-speed USB device number 2 using ohci-pci Jan 29 18:58:03 Woody pulseaudio[1826]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Jan 29 18:58:03 Woody pulseaudio[1826]: [pulseaudio] source.c: Default and alternate sample rates are the same. Jan 29 18:58:06 Woody kernel: [35537.212732] retire_capture_urb: 4164 callbacks suppressed ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-47-generic 3.19.0-47.53 ProcVersionSignature: Ubuntu 3.19.0-47.53-generic 3.19.8-ckt10 Uname: Linux 3.19.0-47-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC3D0c', '/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jan 29 19:39:15 2016 HibernationDevice: RESUME=UUID=588ca909-5d63-43e0-9878-7128eeb408e0 InstallationDate: Installed on 2014-05-01 (638 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic root=UUID=9c702c78-504f-45bc-bfa2-f41fa24221dd ro clocksource=acpi_pm quiet splash nomodeset video=uvesafb:mode_option=1680x1050-24@60,mtrr=3,scroll=ywrap PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-47-generic N/A linux-backports-modules-3.19.0-47-generic N/A linux-firmware 1.143.7 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-10-24 (97 days ago) dmi.bios.date: 11/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd11/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1539750 Title: usb headset causes "retire_playback_urb ... callbacks suppressed" Status in linux package in Ubuntu: New Bug description: Whilst the USB headset is plugged in, I'm seeing usb headset causes "retire_playback_urb ... callbacks suppressed" messages in /var/log/syslog along with: Jan 29 18:58:03 Woody kernel: [35533.838345] usb 8-1: reset full-speed USB device number 2 using ohci-pci Jan 29 18:58:03 Woody pulseaudio[1826]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Jan 29 18:58:03 Woody pulseaudio[1826]: [pulseaudio] source.c: Default and alternate sample rates are the same. Jan 29 18:58:06 Woody kernel: [35537.212732] retire_capture_urb: 4164 callbacks suppressed ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-47-generic 3.19.0-47.53 ProcVersionSignature: Ubuntu 3.19.0-47.53-generic 3.19.8-ckt10 Uname: Linux 3.19.0-47-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC3D0c', '/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Jan 29 19:39:15 2016 HibernationDevice: RESUME=UUID=588ca909-5d63-43e0-9878-7128eeb408e0 InstallationDate: Installed on 2014-05-01
[Kernel-packages] [Bug 1539729] 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/1539729 Title: amd_freq_sensitivity cannot be loaded Status in linux package in Ubuntu: Confirmed Bug description: Hardware: AMD Phenom(tm) II X6 1100T amd_freq_sensitivity.ko driver cannot be loaded nor automatically upon boot, neither manually: $ modprobe amd_freq_sensitivity modprobe: ERROR: could not insert 'amd_freq_sensitivity': No such device $ sudo modprobe -f amd_freq_sensitivity modprobe: ERROR: could not insert 'amd_freq_sensitivity': Exec format error ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-76-generic 3.13.0-76.120 ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30 Uname: Linux 3.13.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrey 4173 F pulseaudio /dev/snd/controlC2: andrey 4173 F pulseaudio /dev/snd/controlC0: andrey 4173 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 29 20:31:35 2016 HibernationDevice: RESUME=UUID=af49e02b-30c7-4695-9748-f78bc942f31d InstallationDate: Installed on 2012-05-13 (1355 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic root=UUID=e073ef69-1057-4c6b-801b-5d5fa762340f ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-76-generic N/A linux-backports-modules-3.13.0-76-generic N/A linux-firmware 1.127.20 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (641 days ago) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539729/+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 1529535] Re: Atheros AR3012 USB Bluetooth adapter not recognized
I am in the same situation and this is definitely not working for me - anything i should try? many thanks thomas -- 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/1529535 Title: Atheros AR3012 USB Bluetooth adapter not recognized Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 15.10 Fresh install. gellenburg@usatlll01:~$ lspci 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) 00:1c.2 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3) 00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3) 00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03) 00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) 03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) gellenburg@usatlll01:~$ lsusb Bus 003 Device 002: ID 8087:8001 Intel Corp. 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 003: ID 058f:3822 Alcor Micro Corp. Bus 001 Device 002: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub gellenburg@usatlll01:~$ usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=11 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=04.02 S: Manufacturer=Linux 4.2.0-22-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=04ca ProdID=300d Rev=00.01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none) I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none) T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 3 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=058f ProdID=3822 Rev=05.00 S: Product=USB 2.0 Camera C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=200mA I: If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo I: If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 4 D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1 P: Vendor=1d6b ProdID=0003 Rev=04.02 S: Manufacturer=Linux 4.2.0-22-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 2 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=04.02 S: Manufacturer=Linux 4.2.0-22-generic ehci_hcd S: Product=EHCI Host Controller S: SerialNumber=:00:1d.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 8 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=8001 Rev=00.03 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub gellenburg@usatlll01:~$ uname -a Linux usatlll01 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux gellenburg@usatlll01:~$ rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no gellenburg@usatlll01:~$ gellenburg@usatlll01:~$ dmesg | grep -i blue [ 18.543198] Bluetooth: Core ver 2.20 [ 18.543213] Bluetooth: HCI device and connection manager initialized [ 18.54321
[Kernel-packages] [Bug 1506521] Re: [Hyper-V] hv_set_ifconfig issues on Wily 15.10
Hi Joe, One issue I'm seeing with the new script is that it seems to be ignoring the netmask parameter. In our test network the dhcp assigned is a /23, and that is set on the Ubuntu 15.10 VM. When we simulate the IP injection, although the network configuration changes and we still have connectivity, the netmask gets 'reset' to 255.0.0.0. I'm not seeing anything in the logs or manually running the hv_set_ifconfig script. In the generated ifcfg-eth0 file there is the NETMASK0 field with the right one we're trying to parse, however the script seems to be ignoring it, as it doesn't get in the interfaces config file. Are you seeing the same behavior? -- 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/1506521 Title: [Hyper-V] hv_set_ifconfig issues on Wily 15.10 Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: Confirmed Status in linux source package in Xenial: In Progress Bug description: Hello, It seems that during the Wily development, some changes have occurred that broke the hv_set_ifconfig script. Please see the below details and update the script accordingly. From my understanding the changes in python versioning on 15.10 are causing this, and when running hv_set_ifconfig with Python v3, it will give some code errors. This has been verified with the daily build from Oct 12, kernel 4.2.0-16-generic and the matching linux-cloud-tools/common are installed. # whereis hv_set_ifconfig hv_set_ifconfig: /usr/sbin/hv_set_ifconfig # /usr/sbin/hv_set_ifconfig /usr/bin/env: python: No such file or directory Indeed there is no python executable by default, only python3. Modifying the header for hv_set_ifconfig to use python3, returns the below: ~# /usr/sbin/hv_set_ifconfig File "/usr/sbin/hv_set_ifconfig", line 130 print "===" ^ SyntaxError: Missing parentheses in call to 'print' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506521/+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 1539729] [NEW] amd_freq_sensitivity cannot be loaded
Public bug reported: Hardware: AMD Phenom(tm) II X6 1100T amd_freq_sensitivity.ko driver cannot be loaded nor automatically upon boot, neither manually: $ modprobe amd_freq_sensitivity modprobe: ERROR: could not insert 'amd_freq_sensitivity': No such device $ sudo modprobe -f amd_freq_sensitivity modprobe: ERROR: could not insert 'amd_freq_sensitivity': Exec format error ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-76-generic 3.13.0-76.120 ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30 Uname: Linux 3.13.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrey 4173 F pulseaudio /dev/snd/controlC2: andrey 4173 F pulseaudio /dev/snd/controlC0: andrey 4173 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 29 20:31:35 2016 HibernationDevice: RESUME=UUID=af49e02b-30c7-4695-9748-f78bc942f31d InstallationDate: Installed on 2012-05-13 (1355 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic root=UUID=e073ef69-1057-4c6b-801b-5d5fa762340f ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-76-generic N/A linux-backports-modules-3.13.0-76-generic N/A linux-firmware 1.127.20 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (641 days ago) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1539729 Title: amd_freq_sensitivity cannot be loaded Status in linux package in Ubuntu: New Bug description: Hardware: AMD Phenom(tm) II X6 1100T amd_freq_sensitivity.ko driver cannot be loaded nor automatically upon boot, neither manually: $ modprobe amd_freq_sensitivity modprobe: ERROR: could not insert 'amd_freq_sensitivity': No such device $ sudo modprobe -f amd_freq_sensitivity modprobe: ERROR: could not insert 'amd_freq_sensitivity': Exec format error ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-76-generic 3.13.0-76.120 ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30 Uname: Linux 3.13.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrey 4173 F pulseaudio /dev/snd/controlC2: andrey 4173 F pulseaudio /dev/snd/controlC0: andrey 4173 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 29 20:31:35 2016 HibernationDevice: RESUME=UUID=af49e02b-30c7-4695-9748-f78bc942f31d InstallationDate: Installed on 2012-05-13 (1355 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic root=UUID=e073ef69-1057-4c6b-801b-5d5fa762340f ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-76-generic N/A linux-backports-modules-3.13.0-76-generic N/A linux-firmware 1.127.20 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (641 days ago) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis
[Kernel-packages] [Bug 1537013] Re: linux-lts-vivid: 3.19.0-49.55~14.04.1 -proposed tracker
** Description changed: This bug is for tracking the 3.19.0-49.55~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 kernel-stable-Prepare-package-start:Friday, 22. January 2016 10:41 UTC kernel-stable-master-bug:1536775 kernel-stable-Prepare-package-end:Friday, 22. January 2016 22:57 UTC kernel-stable-Promote-to-proposed-start:Friday, 22. January 2016 22:57 UTC kernel-stable-Promote-to-proposed-end:Monday, 25. January 2016 20:47 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 25. January 2016 22:01 UTC kernel-stable-Verification-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Certification-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Security-signoff-start:Monday, 25. January 2016 22:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Security-signoff-end:Tuesday, 26. January 2016 09:02 UTC + kernel-stable-Certification-testing-end:Friday, 29. January 2016 18:02 UTC -- 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/1537013 Title: linux-lts-vivid: 3.19.0-49.55~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: Fix Released 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: In Progress 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-49.55~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 kernel-stable-Prepare-package-start:Friday, 22. January 2016 10:41 UTC kernel-stable-master-bug:1536775 kernel-stable-Prepare-package-end:Friday, 22. January 2016 22:57 UTC kernel-stable-Promote-to-proposed-start:Friday, 22. January 2016 22:57 UTC kernel-stable-Promote-to-proposed-end:Monday, 25. January 2016 20:47 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 25. January 2016 22:01 UTC kernel-stable-Verification-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Certification-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Security-signoff-start:Monday, 25. January 2016 22:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Security-signoff-end:Tuesday, 26. January 2016 09:02 UTC kernel-stable-Certification-testing-end:Friday, 29. January 2016 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1537013/+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 1529232] Re: Scanner not detected over wifi since after 3.13.0-68
OK. The machine had since updated to 3.13.0-76-generic but still had the problem with the scanner not being detected over wifi by scangearmp. As per the instructions at https://wiki.ubuntu.com/Kernel/MainlineBuilds#Preparing_to_install_an_upstream_kernel I switched from the proprietary NVidia binary driver (v340.96 for GeForce GT430) to the open source X.Org X server Nouveau driver. I rebooted then installed the upstream kernel v4.5-rc1-wily from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc1-wily/ These were the files I used: linux-headers-4.5.0-040500rc1_4.5.0-040500rc1.201601241731_all.deb linux-headers-4.5.0-040500rc1-generic_4.5.0-040500rc1.201601241731_amd64.deb linux-image-4.5.0-040500rc1-generic_4.5.0-040500rc1.201601241731_amd64.deb I rebooted into it from the GRUB menu. scangearmp *was* then able to find my Canon MG7150 scanner over wifi. So it's fixed in the upstream kernel and I've added the tags you requested. -- 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/1529232 Title: Scanner not detected over wifi since after 3.13.0-68 Status in linux package in Ubuntu: Confirmed Bug description: Please see http://ubuntuforums.org/showthread.php?t=2306464 for details. I'm running 64-bit 14.04 LTS ubuntu. When I boot my PC into 3.13.0-68-generic (via the 'ubuntu advanced' menu item in grub) I can detect my scanner over wifi using scangearmp. However since 3.13.0-70-generic I have not been able to detect my scanner over wifi. My current kernel is 3.13.0-74-generic. Therefore I suspect a regression has occurred between 3.13.0-68-generic and 3.13.0-70-generic: Scanner *is* detected by scangearmp over wifi and it scans documents as expected in this version: uname -a Linux zorro 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux But scanner is *not* detected by scangearmp in this version or later: Linux zorro 3.13.0-70-generic #113-Ubuntu SMP Mon Nov 16 18:34:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Note that this happened before some time ago. i.e., The scanner was detected over wifi, then not, then it was again some time later. Then this latest break occurred again. I suspect successive updates are fixing or breaking the detection accordingly. $ dpkg -l | grep scangear ii scangearmp-common 2.20-1 amd64ScanGear MP for Linux. ii scangearmp-mg7100series 2.20-1 amd64ScanGear MP for Linux. Device is Canon Pixma MG7150 (combined printer, scanner, copier). Note the printer works fine over wifi; only the scanner is affected. I can see from the changelog at http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_3.13.0-74.118/changelog that many changes went into 3.13.0-69.112 but it's not obvious to me which of these might have caused the regression. --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lucas 1604 F pulseaudio /dev/snd/controlC2: lucas 1604 F pulseaudio /dev/snd/controlC0: lucas 1604 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0140e677-b732-4571-a80a-fc5d7c00359c InstallationDate: Installed on 2014-12-05 (387 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7528 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic root=UUID=941f5e44-f02e-42f2-ac78-5f6b4b9e98e9 ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 RelatedPackageVersions: linux-restricted-modules-3.13.0-74-generic N/A linux-backports-modules-3.13.0-74-generic N/A linux-firmware 1.127.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G31M3-F(MS-7528) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd06/19/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7528:pvr1.0:rvnMICRO
[Kernel-packages] [Bug 1502781] Re: Bluetooth 0930:021c not working in Ubuntu 15.10
Not much more progress it seems... :-(( still the same "no bluetooth adapters found" issue output is a little changed, obviously: uname -a yields Alienware-17-R2 4.3.0-040300-generic #201511020949 SMP Mon Nov 2 14:50:44 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i blue [4.707040] Bluetooth: Core ver 2.20 [4.707049] Bluetooth: HCI device and connection manager initialized [4.707051] Bluetooth: HCI socket layer initialized [4.707053] Bluetooth: L2CAP socket layer initialized [4.707056] Bluetooth: SCO socket layer initialized [6.801535] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu [6.801536] Bluetooth: Loading patch file failed [ 10.313101] Modules linked in: bbswitch(OE) ath3k binfmt_misc arc4 nls_iso8859_1 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_wmi mxm_wmi sparse_keymap nvidia(POE) kvm ath10k_pci ath10k_core crct10dif_pclmul crc32_pclmul ath aesni_intel mac80211 aes_x86_64 lrw gf128mul uvcvideo glue_helper ablk_helper videobuf2_vmalloc hid_multitouch btusb videobuf2_memops cryptd snd_hda_codec_hdmi btrtl videobuf2_core btbcm cfg80211 snd_soc_rt5640 input_leds btintel v4l2_common joydev snd_soc_rl6231 snd_soc_ssm4567 videodev bluetooth snd_soc_core snd_hda_codec_ca0132 media serio_raw snd_compress ac97_bus rtsx_pci_ms snd_hda_intel snd_pcm_dmaengine snd_hda_codec memstick snd_hda_core snd_hwdep mei_me snd_pcm mei shpchp lpc_ich snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer [ 11.729089] Modules linked in: bbswitch(OE) ath3k binfmt_misc arc4 nls_iso8859_1 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_wmi mxm_wmi sparse_keymap nvidia(POE) kvm ath10k_pci ath10k_core crct10dif_pclmul crc32_pclmul ath aesni_intel mac80211 aes_x86_64 lrw gf128mul uvcvideo glue_helper ablk_helper videobuf2_vmalloc hid_multitouch btusb videobuf2_memops cryptd snd_hda_codec_hdmi btrtl videobuf2_core btbcm cfg80211 snd_soc_rt5640 input_leds btintel v4l2_common joydev snd_soc_rl6231 snd_soc_ssm4567 videodev bluetooth snd_soc_core snd_hda_codec_ca0132 media serio_raw snd_compress ac97_bus rtsx_pci_ms snd_hda_intel snd_pcm_dmaengine snd_hda_codec memstick snd_hda_core snd_hwdep mei_me snd_pcm mei shpchp lpc_ich snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer [ 11.966179] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.966182] Bluetooth: BNEP filters: protocol multicast [ 11.966190] Bluetooth: BNEP socket layer initialized lsmod |grep blue bluetooth 512000 10 bnep,ath3k,btbcm,btrtl,btusb,btintel lsusb shows: Bus 001 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Not quite clear what to do... while i am at it, the headphones don't work either... ;-p looks like i am not the only one and extensive google didn't help - all solutions didn't seem to work for me. have a nice week-end all. thomas -- 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/1502781 Title: Bluetooth 0930:021c not working in Ubuntu 15.10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: Ubuntu detects the bluetooth hardware (it shows the bluetooth icon in the status bar), and I can turn it on or off and set the visibility and such. However, it is never able to find any bluetooth device. "lsusb" shows: Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012 Bluetooth "rfkill list" output: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no "hciconfig -a" output: hci0: Type: BR/EDR Bus: USB BD Address: 18:CF:5E:09:55:43 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING RX bytes:1313 acl:0 sco:0 events:88 errors:0 TX bytes:3200 acl:0 sco:0 commands:87 errors:0 Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x8f Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Name: 'lucas-Leon' Class: 0x0c010c Service Classes: Rendering, Capturing Device Class: Computer, Laptop HCI Version: 4.1 (0x7) Revision: 0x1102 LMP Version: 4.0 (0x6) Subversion: 0x1 Manufacturer: Atheros Communications, Inc. (69) Thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInU
[Kernel-packages] [Bug 1535879] Re: It looks to be the (expired ) bug #1451632 drm:intel fifo
Great. With upstream version below, carlos@carlosLT:~$ uname -a Linux carlosLT 4.5.0-040500rc1-generic #201601241731 SMP Sun Jan 24 22:33:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux and I have three errors now: carlos@carlosLT:~$ dmesg | grep ERROR [ 39.837796] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A [ 39.837809] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [ 39.837834] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [ 39.837843] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun I will continue testing upstream and inform ... Thanks, Carlos -- 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/1535879 Title: It looks to be the (expired ) bug #1451632 drm:intel fifo Status in linux package in Ubuntu: Incomplete Bug description: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1451632/+activity dmesg | grep drm:intel [1.441536] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [1.441575] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun Returned back (https://bugzilla.kernel.org/show_bug.cgi?id=79261). It seamed to be fixed up-stream but not for all. Effects on my DELL Precision E6530: without notice it switches from nouveau to nvidia. Switching back to nouveau it hangs (need restart) and OK. Using optimus: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GF108GLM [NVS 5200M] (rev ff) I'll try to use the upstream kernels and inform ... ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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: Tue Jan 19 20:32:03 2016 DistUpgraded: 2015-10-12 20:30:48,655 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0535] NVIDIA Corporation GF108GLM [NVS 5200M] [10de:0dfc] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-05-19 (610 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E6530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-10-12 (99 days ago) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jan 19 18:32:11 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5553 vendor CMN xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-pack
[Kernel-packages] [Bug 1529232] Re: Scanner not detected over wifi since after 3.13.0-68
OK. The machine had since updated to 3.13.0-76-generic but still had the problem with the scanner not being detected over wifi by scangearmp. As per the instructions at https://wiki.ubuntu.com/Kernel/MainlineBuilds#Preparing_to_install_an_upstream_kernel I switched from the proprietary NVidia binary driver (v340.96 for GeForce GT430) to the open source X.Org X server Nouveau driver. I rebooted then installed the upstream kernel v4.5-rc1-wily from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc1-wily/ These were the files I used: linux-headers-4.5.0-040500rc1_4.5.0-040500rc1.201601241731_all.deb linux-headers-4.5.0-040500rc1-generic_4.5.0-040500rc1.201601241731_amd64.deb linux-image-4.5.0-040500rc1-generic_4.5.0-040500rc1.201601241731_amd64.deb I rebooted into it from the GRUB menu. scangearmp *was* then able to find my Canon MG7150 scanner over wifi. So it's fixed in the upstream kernel and I've added the tags you requested. ** 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/1529232 Title: Scanner not detected over wifi since after 3.13.0-68 Status in linux package in Ubuntu: Confirmed Bug description: Please see http://ubuntuforums.org/showthread.php?t=2306464 for details. I'm running 64-bit 14.04 LTS ubuntu. When I boot my PC into 3.13.0-68-generic (via the 'ubuntu advanced' menu item in grub) I can detect my scanner over wifi using scangearmp. However since 3.13.0-70-generic I have not been able to detect my scanner over wifi. My current kernel is 3.13.0-74-generic. Therefore I suspect a regression has occurred between 3.13.0-68-generic and 3.13.0-70-generic: Scanner *is* detected by scangearmp over wifi and it scans documents as expected in this version: uname -a Linux zorro 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux But scanner is *not* detected by scangearmp in this version or later: Linux zorro 3.13.0-70-generic #113-Ubuntu SMP Mon Nov 16 18:34:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Note that this happened before some time ago. i.e., The scanner was detected over wifi, then not, then it was again some time later. Then this latest break occurred again. I suspect successive updates are fixing or breaking the detection accordingly. $ dpkg -l | grep scangear ii scangearmp-common 2.20-1 amd64ScanGear MP for Linux. ii scangearmp-mg7100series 2.20-1 amd64ScanGear MP for Linux. Device is Canon Pixma MG7150 (combined printer, scanner, copier). Note the printer works fine over wifi; only the scanner is affected. I can see from the changelog at http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_3.13.0-74.118/changelog that many changes went into 3.13.0-69.112 but it's not obvious to me which of these might have caused the regression. --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lucas 1604 F pulseaudio /dev/snd/controlC2: lucas 1604 F pulseaudio /dev/snd/controlC0: lucas 1604 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0140e677-b732-4571-a80a-fc5d7c00359c InstallationDate: Installed on 2014-12-05 (387 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7528 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic root=UUID=941f5e44-f02e-42f2-ac78-5f6b4b9e98e9 ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 RelatedPackageVersions: linux-restricted-modules-3.13.0-74-generic N/A linux-backports-modules-3.13.0-74-generic N/A linux-firmware 1.127.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G31M3-F(MS-7528) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd
[Kernel-packages] [Bug 1529232] Re: Scanner not detected over wifi since after 3.13.0-68
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.5-rc1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1529232 Title: Scanner not detected over wifi since after 3.13.0-68 Status in linux package in Ubuntu: Incomplete Bug description: Please see http://ubuntuforums.org/showthread.php?t=2306464 for details. I'm running 64-bit 14.04 LTS ubuntu. When I boot my PC into 3.13.0-68-generic (via the 'ubuntu advanced' menu item in grub) I can detect my scanner over wifi using scangearmp. However since 3.13.0-70-generic I have not been able to detect my scanner over wifi. My current kernel is 3.13.0-74-generic. Therefore I suspect a regression has occurred between 3.13.0-68-generic and 3.13.0-70-generic: Scanner *is* detected by scangearmp over wifi and it scans documents as expected in this version: uname -a Linux zorro 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux But scanner is *not* detected by scangearmp in this version or later: Linux zorro 3.13.0-70-generic #113-Ubuntu SMP Mon Nov 16 18:34:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Note that this happened before some time ago. i.e., The scanner was detected over wifi, then not, then it was again some time later. Then this latest break occurred again. I suspect successive updates are fixing or breaking the detection accordingly. $ dpkg -l | grep scangear ii scangearmp-common 2.20-1 amd64ScanGear MP for Linux. ii scangearmp-mg7100series 2.20-1 amd64ScanGear MP for Linux. Device is Canon Pixma MG7150 (combined printer, scanner, copier). Note the printer works fine over wifi; only the scanner is affected. I can see from the changelog at http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_3.13.0-74.118/changelog that many changes went into 3.13.0-69.112 but it's not obvious to me which of these might have caused the regression. --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lucas 1604 F pulseaudio /dev/snd/controlC2: lucas 1604 F pulseaudio /dev/snd/controlC0: lucas 1604 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0140e677-b732-4571-a80a-fc5d7c00359c InstallationDate: Installed on 2014-12-05 (387 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7528 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic root=UUID=941f5e44-f02e-42f2-ac78-5f6b4b9e98e9 ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 RelatedPackageVersions: linux-restricted-modules-3.13.0-74-generic N/A linux-backports-modules-3.13.0-74-generic N/A linux-firmware 1.127.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G31M3-F(MS-7528) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd06/19/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7528:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-F(MS-7528):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7528 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529232/+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 1502781] Re: Bluetooth 0930:021c not working in Ubuntu 15.10
sorry to bother, tried to follow religiously the steps provided, but it didn't work for me. I am using ubuntu 15.10 Alienware-17-R2 4.2.0-25-generic #30-Ubuntu SMP Mon Jan 18 12:31:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep -i blue [3.751610] Bluetooth: Core ver 2.20 [3.751621] Bluetooth: HCI device and connection manager initialized [3.751624] Bluetooth: HCI socket layer initialized [3.751626] Bluetooth: L2CAP socket layer initialized [3.751629] Bluetooth: SCO socket layer initialized [5.064855] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu [5.064857] Bluetooth: Loading patch file failed [ 10.482926] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.482929] Bluetooth: BNEP filters: protocol multicast [ 10.482933] Bluetooth: BNEP socket layer initialized lsmod |grep blue bluetooth 516096 10 bnep,ath3k,btbcm,btrtl,btusb,btintel so everything is similar in my system, it seems... so i simply followed: sudo add-apt-repository ppa:hanipouspilot/bluetooth sudo apt-get update sudo apt-get install btusb-lp1502781-dkms and In order to fix this bug in kernel 4.2 (use attached files) : 1- Install btusb-lp1502781-dkms_0.1_all.deb 2- Copy btbcm.h, btintel.h and btrtl.h to "/var/lib/dkms/btusb- lp1502781/0.1/build" 3- sudo make sudo make install 4- Reboot the computer. Shutting down instead, and restarting and i have made no progress. :-(( I am now trying to install kernel 4.3 to see if better... many thanks thomas -- 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/1502781 Title: Bluetooth 0930:021c not working in Ubuntu 15.10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: Ubuntu detects the bluetooth hardware (it shows the bluetooth icon in the status bar), and I can turn it on or off and set the visibility and such. However, it is never able to find any bluetooth device. "lsusb" shows: Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012 Bluetooth "rfkill list" output: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no "hciconfig -a" output: hci0: Type: BR/EDR Bus: USB BD Address: 18:CF:5E:09:55:43 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING RX bytes:1313 acl:0 sco:0 events:88 errors:0 TX bytes:3200 acl:0 sco:0 commands:87 errors:0 Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x8f Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Name: 'lucas-Leon' Class: 0x0c010c Service Classes: Rendering, Capturing Device Class: Computer, Laptop HCI Version: 4.1 (0x7) Revision: 0x1102 LMP Version: 4.0 (0x6) Subversion: 0x1 Manufacturer: Atheros Communications, Inc. (69) Thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lucas 1143 F pulseaudio /dev/snd/controlC1: lucas 1143 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 5 09:19:20 2015 HibernationDevice: RESUME=UUID=58bcbcd9-672f-4530-b8b5-775f76fc9187 InstallationDate: Installed on 2015-10-04 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer Bus 001 Device 003: ID 0930:021c Toshiba Corp. Atheros AR3012 Bluetooth Bus 001 Device 002: ID 04f2:b433 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Toshiba Leon ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-14-generic root=UUID=a107b544-64af-4e74-89a7-2c0e9fe8ce8d ro rootflags=subvol=@ tpm_tis.interrupts=0 modprobe.blacklist=ehci_pci quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.148 SourcePackage: linux UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2014 dmi.bios.vendor: corebo
[Kernel-packages] [Bug 1537013] Re: linux-lts-vivid: 3.19.0-49.55~14.04.1 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/trusty/3.19.0-49.55~14.04.1/trusty-3.19-proposed-frozen.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- 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/1537013 Title: linux-lts-vivid: 3.19.0-49.55~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: Fix Released 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: In Progress 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-49.55~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 kernel-stable-Prepare-package-start:Friday, 22. January 2016 10:41 UTC kernel-stable-master-bug:1536775 kernel-stable-Prepare-package-end:Friday, 22. January 2016 22:57 UTC kernel-stable-Promote-to-proposed-start:Friday, 22. January 2016 22:57 UTC kernel-stable-Promote-to-proposed-end:Monday, 25. January 2016 20:47 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 25. January 2016 22:01 UTC kernel-stable-Verification-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Certification-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Security-signoff-start:Monday, 25. January 2016 22:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Security-signoff-end:Tuesday, 26. January 2016 09:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1537013/+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 1535660] Re: Certain Bluetooth mice do not pair with Ubuntu
This bug was fixed in the package ubuntu-system-settings - 0.3+16.04.20160128-0ubuntu1 --- ubuntu-system-settings (0.3+16.04.20160128-0ubuntu1) xenial; urgency=medium * Allow pairing regardless of type (LP: #1535660, #1534221) * Exposed adapterAddress in the bluetooth plugin to be used to get the address in the about plugin (LP: #1537029) -- Ken VanDine Thu, 28 Jan 2016 14:23:03 + ** Changed in: ubuntu-system-settings (Ubuntu) Status: In Progress => Fix Released -- 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/1535660 Title: Certain Bluetooth mice do not pair with Ubuntu Status in The Avila project: Confirmed Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: I have a Microsoft Arc Mouse Surface Edition, and tried to pair it with my Ubuntu (trusty) desktop. It shows up in the pairing gui with a little mouse icon, but the UI offers no option to pair to the device. On Ubuntu touch, system settings never shows the device as something that can be paired to. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1535660/+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 1535879] Re: It looks to be the (expired ) bug #1451632 drm:intel fifo
OK. I'll do that now ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1535879 Title: It looks to be the (expired ) bug #1451632 drm:intel fifo Status in linux package in Ubuntu: Incomplete Bug description: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1451632/+activity dmesg | grep drm:intel [1.441536] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [1.441575] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun Returned back (https://bugzilla.kernel.org/show_bug.cgi?id=79261). It seamed to be fixed up-stream but not for all. Effects on my DELL Precision E6530: without notice it switches from nouveau to nvidia. Switching back to nouveau it hangs (need restart) and OK. Using optimus: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GF108GLM [NVS 5200M] (rev ff) I'll try to use the upstream kernels and inform ... ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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: Tue Jan 19 20:32:03 2016 DistUpgraded: 2015-10-12 20:30:48,655 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0535] NVIDIA Corporation GF108GLM [NVS 5200M] [10de:0dfc] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-05-19 (610 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E6530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-10-12 (99 days ago) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jan 19 18:32:11 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5553 vendor CMN xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535879/+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 1539688] [NEW] Bluetooth stops working after the OTA9 update
Public bug reported: After the OTA9 update, the system stops working with Kenwood KCA-BT200 Bluetooth car radio adapter (handsfree+audio streaming): please check attached file for further details. Build name: OTA9 Ubuntu image part 20160123.1 Ubuntu build description: ubuntu 15.04 - armhf (20160123-115651) device image part : 20160108-ef-c96d8 device build description: VEGETA01.A-S23A_BQ_L100EN_2009_160123 Customization image part: 2016011-926-36-vivid available for further test and to supply additional details. Thanks and Regards D ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth handsfree ** Attachment added: "detailed description before/after" https://bugs.launchpad.net/bugs/1539688/+attachment/4559299/+files/160129_%20Bluetooth%20after%20the%20OTA9%20update.pdf -- 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/1539688 Title: Bluetooth stops working after the OTA9 update Status in bluez package in Ubuntu: New Bug description: After the OTA9 update, the system stops working with Kenwood KCA-BT200 Bluetooth car radio adapter (handsfree+audio streaming): please check attached file for further details. Build name: OTA9 Ubuntu image part 20160123.1 Ubuntu build description: ubuntu 15.04 - armhf (20160123-115651) device image part : 20160108-ef-c96d8 device build description: VEGETA01.A-S23A_BQ_L100EN_2009_160123 Customization image part: 2016011-926-36-vivid available for further test and to supply additional details. Thanks and Regards D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539688/+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 1535660] Re: Certain Bluetooth mice do not pair with Ubuntu
** Changed in: ubuntu-system-settings (Ubuntu) Status: New => In Progress ** Changed in: canonical-devices-system-image Assignee: John McAleely (john.mcaleely) => Bill Filler (bfiller) ** Changed in: canonical-devices-system-image Status: Confirmed => In Progress -- 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/1535660 Title: Certain Bluetooth mice do not pair with Ubuntu Status in The Avila project: Confirmed Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: I have a Microsoft Arc Mouse Surface Edition, and tried to pair it with my Ubuntu (trusty) desktop. It shows up in the pairing gui with a little mouse icon, but the UI offers no option to pair to the device. On Ubuntu touch, system settings never shows the device as something that can be paired to. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1535660/+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 1531539] Comment bridged from LTC Bugzilla
--- Comment From gpicc...@br.ibm.com 2016-01-29 10:40 EDT--- I noticed Ubuntu's 16.04 kernel 4.4 is available now, right? Doing a git log between the latest Canonical 4.4 and the upstream kernel (4.5-rc1), I found the following commits are missing from Ubuntu's kernel. Can you cherry-pick them? Thanks in advance, Guilherme List of commits to be added in Ubuntu 16.04 kernel: 779ff7561709 NVMe: Export NVMe attributes to sysfs group a5cdb68c2c10 NVMe: Shutdown controller only for power-off db3cbfff5bcc NVMe: IO queue deletion re-write 25646264e15a NVMe: Remove queue freezing on resets 1d49c38c4865 NVMe: Use a retryable error code on reset e3e9d50cd6ed NVMe: Fix admin queue ring wrap 4490733250b8 nvme: make SG_IO support optional bfd8947194b2 nvme: fixes for NVME_IOCTL_IO_CMD on the char device 69d3b8ac15a5 nvme: synchronize access to ctrl->namespaces 363c9aacb6c5 nvme: Move nvme_freeze/unfreeze_queues to nvme core ca5927e7ab53 lightnvm: introduce mlc lower page table mappings 22513215b83d lightnvm: return the get_bb_tbl return value 91276162de94 lightnvm: refactor end_io functions for sync 2b9b6e86bca7 NVMe: Export namespace attributes to sysfs a0a3408ee614 NVMe: Add pci error handlers f4800d6d1548 nvme: merge iod and cmd_info bf68405705bd nvme: meta_sg doesn't have to be an array eee417b06978 nvme: properly free resources for cancelled command aae239e1910e nvme: simplify completion handling adf68f21c155 nvme: special case AEN requests e7a2a87d5938 nvme: switch abort to blk_execute_rq_nowait d8f32166a9c5 nvme: switch delete SQ/CQ to blk_execute_rq_nowait 7688faa6dd2c nvme: factor out a few helpers from req_completion 4680072003df nvme: fix admin queue depth 4b9d5b151046 NVMe: Simplify metadata setup 53029b0441bb NVMe: Remove device management handles on remove 92f7a1624bbc NVMe: Use unbounded work queue for all work 540c801c65eb NVMe: Implement namespace list scanning 6bf25d16410d nvme: switch abort_limit to an atomic_t 5c8809e65077 nvme: remove dead controllers from a work item fd634f414286 nvme: merge probe_work and reset_work e1569a16180a nvme: do not restart the request timeout if we're resetting the controller 846cc05f95d5 nvme: simplify resets 297465c873ae nvme: add NVME_SC_CANCELLED 31c7c7d2c9f1 nvme: merge nvme_abort_req and nvme_timeout 4c9f748f0ee8 nvme: don't take the I/O queue q_lock in nvme_timeout 77bf25ea7020 nvme: protect against simultaneous shutdown invocations 7385014c0732 nvme: only add a controller to dev_list after it's been fully initialized 749941f2365d nvme: only ignore hardware errors in nvme_create_io_queues 8c0b39155048 nvme: precedence bug in nvme_pr_clear() d1ea7be5f755 nvme: fix another 32-bit build warning ac02dddec633 NVMe: fix build with CONFIG_NVM enabled 06c1e3902aa7 blk-integrity: empty implementation when disabled 9a0be7abb62f nvme: refactor set_queue_count f3ca80fc11c3 nvme: move chardev and sysfs interface to common code 5bae7f73d378 nvme: move namespace scanning to common code ce4541f40a94 nvme: move the call to nvme_init_identify earlier 7fd8930f26be nvme: add a common helper to read Identify Controller data 5fd4ce1b005b nvme: move nvme_{enable,disable,shutdown}_ctrl to common code 1b2eb374651f nvme: move remaining CC setup into nvme_enable_ctrl 106198edb74c nvme: add explicit quirk handling 1673f1f08c88 nvme: move block_device_operations and ns/ctrl freeing to common code 0b7f1f26f95a nvme: use the block layer for userspace passthrough metadata 4160982e7594 nvme: split __nvme_submit_sync_cmd 22944e9981db nvme: move nvme_setup_flush and nvme_setup_rw to common code 15a190f7f57a nvme: move nvme_error_status to common code d4f6c3aba5b4 nvme: factor out a nvme_unmap_data helper ba1ca37ea4e3 nvme: refactor nvme_queue_rq 69d2b571746d nvme: simplify nvme_setup_prps calling convention 1c63dc66580d nvme: split a new struct nvme_ctrl out of struct nvme_dev 01fec28a6f3b nvme: use vendor it from identify bf7d3ebbd219 nvme: split nvme_trans_device_id_page 7a67cbea653e nvme: use offset instead of a struct for registers 21d34711e1b5 nvme: split command submission helpers out of pci.c 71bd150c7107 nvme: move struct nvme_iod to pci.c 6f3b0e8bcf3c blk-mq: add a flags parameter to blk_mq_alloc_request -- 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/1531539 Title: [Ubuntu 16.04] Enable nvme block driver on Power Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Bug description: This is a feature to cherry pick some nvme commits into 16.04 kernel. Guilherme is going to specify which commits are being required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1537666] Comment bridged from LTC Bugzilla
--- Comment From ye...@us.ibm.com 2016-01-29 10:45 EDT--- (In reply to comment #19) > (In reply to comment #18) > > (In reply to comment #17) > > > It is still not clear to me what needs to be documented exactly. I am the > > > owner for the https://wiki.ubuntu.com/ppc64el/Recommendations, and anyone > > > can update there. > > > > > > So, if there is a text I can share there, I would be glad to help > > > > Hi Breno, > > > > The default value of min_free_kbytes doesn't work fine because there are > > lots of "interrupt: 501 at plpar_hcall_norets+0x1c/0x2" created when we run > > with the default value. If we increase min_free_kbytes to 365536 (356 MB), > > it will eliminate the fault. So we want to document this information for > > future reference. > > > > Yuechang > > Ok. Just documented it at > https://wiki.ubuntu.com/ppc64el/ > Recommendations#Min_free_kbytes_kernel_configuration Thank you, Breno! -- 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/1537666 Title: ISST-LTE: Ubuntu 14.04.4 LPAR interrupts at check_and_cede_processor Status in linux package in Ubuntu: New Bug description: == Comment: #0 - YUECHANG E. MEI - 2015-12-11 17:19:07 == ---Problem Description--- We have an Ubuntu 14.04.4 LPAR, conelp2. It is running stress test: base, io, and tcp. When checking "dmesg", we see this interruption: [Fri Dec 11 13:58:50 2015] --- interrupt: 501 at plpar_hcall_norets+0x1c/0x28 [Fri Dec 11 13:58:50 2015] LR = check_and_cede_processor+0x34/0x50 In the previous test, conelp2 stopped all the stress tests by itself because it ran out of memory. Is the out of memory issue relating to the interruption? Contact Information = Yuechang (Erin) Mei /ye...@us.ibm.com, Raja Sunkari /rajas...@in.ibm.com ---uname output--- Linux conelp2 4.2.0-21-generic #25~14.04.1-Ubuntu SMP Thu Dec 3 13:55:42 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = EUH Alpine 8408-E8E ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install Ubuntu 14.04.4 in a LPAR, then update to the latest 14.04.4 kernel by using this workaround: echo "deb http://software.linux.ibm.com/pub/ubuntu-ppc64el-repository/ trusty-proposed main restricted universe multiverse" >> /etc/apt/sources.list apt-get update apt-get install linux-image-generic-lts-wily 2. Setup the Stress test, and start base,io, tcp 3. After an hour, check dmesg, then you will see the message about the interruption Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com, Raja Sunkari /rajas...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. == Comment: #1 - YUECHANG E. MEI - 2015-12-11 17:23:00 == == Comment: #3 - YUECHANG E. MEI - 2015-12-14 15:23:33 == == Comment: #4 - MAMATHA INAMDAR - 2015-12-15 03:56:14 == dmrsg show page allocation failure [Fri Dec 11 13:45:38 2015] swapper/127: page allocation failure: order:0, mode:0x120 [Fri Dec 11 13:45:38 2015] CPU: 127 PID: 0 Comm: swapper/127 Not tainted 4.2.0-21-generic #25~14.04.1-Ubuntu [Fri Dec 11 13:45:38 2015] Call Trace: [Fri Dec 11 13:45:38 2015] [c0027fbc3890] [c0a805ec] dump_stack+0x90/0xbc (unreliable) [Fri Dec 11 13:45:38 2015] [c0027fbc38c0] [c021c118] warn_alloc_failed+0x118/0x160 [Fri Dec 11 13:45:38 2015] [c0027fbc3960] [c0221114] __alloc_pages_nodemask+0x834/0xa60 [Fri Dec 11 13:45:38 2015] [c0027fbc3b10] [c0221404] __alloc_page_frag+0xc4/0x190 [Fri Dec 11 13:45:38 2015] [c0027fbc3b50] [c08f6d20] netdev_alloc_frag+0x50/0x80 [Fri Dec 11 13:45:38 2015] [c0027fbc3b80] [c0764e80] tg3_alloc_rx_data+0xa0/0x2c0 [Fri Dec 11 13:45:38 2015] [c0027fbc3be0] [c0767344] tg3_poll_work+0x484/0x1070 [Fri Dec 11 13:45:38 2015] [c0027fbc3ce0] [c0767f8c] tg3_poll_msix+0x5c/0x210 [Fri Dec 11 13:45:38 2015] [c0027fbc3d30] [c090ebb8] net_rx_action+0x2d8/0x430 [Fri Dec 11 13:45:38 2015] [c0027fbc3e40] [c00ba124] __do_softirq+0x174/0x390 [Fri Dec 11 13:45:38 2015] [c0027fbc3f40] [c00ba6c8] irq_exit+0xc8/0x100 [Fri Dec 11 13:45:38 2015] [c0027fbc3f60] [c00111ec] __do_irq+0x8c/0x190 [Fri Dec 11 13:45:38 2015] [c0027fbc3f90] [c0024278] call_do_irq+0x14/0x24 [Fri Dec 11 13:45:38 2015] [c002763a39b0] [c0011390] do_IRQ+0xa0/0x120 [Fri Dec 11 13:45:38 2015] [c002763a3a10] [c00099b0] restore_check_irq_replay+0x2c/0x70 [Fri Dec 11 13:45:38 2015] --- interrupt: 501 at plpar_hcall_norets+0x1c/0x28 [Fri Dec 1
[Kernel-packages] [Bug 1505948] Re: Memory arena corruption with FUSE (was Memory allocation failure crashes kernel hard, presumably related to FUSE)
The bug triggers with the debug kernel, however there is no message like "fuse_direct_IO: io->reg would have gone negative" in the journal: Jan 29 16:22:18 ubuntu dnsmasq-dhcp[896]: DHCPREQUEST(virbr0) 192.168.122.93 52:54:00:45:1c:61 Jan 29 16:22:18 ubuntu dnsmasq-dhcp[896]: DHCPACK(virbr0) 192.168.122.93 52:54:00:45:1c:61 Jan 29 16:22:51 ubuntu kernel: BUG: unable to handle kernel paging request at 8800904b06c0 Jan 29 16:22:51 ubuntu kernel: IP: [] __kmalloc+0x94/0x250 Jan 29 16:22:51 ubuntu kernel: PGD 1ff0067 PUD 3738b6063 PMD 0 Jan 29 16:22:51 ubuntu kernel: Oops: [#1] SMP Jan 29 16:22:51 ubuntu kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables nls_iso8859_1 ipmi_ssif ipmi_devintf gpio_ich coretemp kvm_intel serio_raw kvm input_leds cdc_ether usbnet mii lpc_ich i7core_edac ioatdma edac_core i5500_temp shpchp dca 8250_fintek ipmi_si mac_hid ipmi_msghandler sunrpc autofs4 hid_generic mptsas mptscsih usbhid mptbase psmouse hid pata_acpi scsi_transport_sas bnx2 Jan 29 16:22:51 ubuntu kernel: CPU: 4 PID: 21954 Comm: qemu-system-x86 Tainted: G I 4.2.0-27-generic #32lp1505948v201601281755 Jan 29 16:22:51 ubuntu kernel: Hardware name: IBM System x3550 M2 -[794654G]-/49Y6512 , BIOS -[D6E131CUS-1.05]- 11/25/2009 Jan 29 16:22:51 ubuntu kernel: task: 880380e98c80 ti: 8803811d4000 task.ti: 8803811d4000 Jan 29 16:22:51 ubuntu kernel: RIP: 0010:[] [] __kmalloc+0x94/0x250 Jan 29 16:22:51 ubuntu kernel: RSP: 0018:8803811d79c8 EFLAGS: 00010286 Jan 29 16:22:51 ubuntu kernel: RAX: RBX: 00d0 RCX: 0009d36e Jan 29 16:22:51 ubuntu kernel: RDX: 0009d36d RSI: RDI: 00019aa0 Jan 29 16:22:51 ubuntu kernel: RBP: 8803811d7a08 R08: 88067fc19aa0 R09: 812f8d56 Jan 29 16:22:51 ubuntu kernel: R10: 8800904b06c0 R11: 081a R12: 00d0 Jan 29 16:22:51 ubuntu kernel: R13: 0058 R14: 8803738037c0 R15: 8803738037c0 Jan 29 16:22:51 ubuntu kernel: FS: 7f384a78eb00() GS:88067fc0() knlGS: Jan 29 16:22:51 ubuntu kernel: CS: 0010 DS: ES: CR0: 8005003b Jan 29 16:22:51 ubuntu kernel: CR2: 8800904b06c0 CR3: 0002da9d5000 CR4: 26e0 Jan 29 16:22:51 ubuntu kernel: Stack: Jan 29 16:22:51 ubuntu kernel: 8803811d7a18 812f8d56 880371e2b200 8805993ae0d0 Jan 29 16:22:51 ubuntu kernel: 000b 00d0 0058 8805993ae210 Jan 29 16:22:51 ubuntu kernel: 8803811d7a58 812f8d56 8803811d7a38 8805993ae0d0 Jan 29 16:22:51 ubuntu kernel: Call Trace: Jan 29 16:22:51 ubuntu kernel: [] ? __fuse_request_alloc+0x56/0xd0 Jan 29 16:22:51 ubuntu kernel: [] __fuse_request_alloc+0x56/0xd0 Jan 29 16:22:51 ubuntu kernel: [] __fuse_get_req+0x1d6/0x280 Jan 29 16:22:51 ubuntu kernel: [] ? wake_atomic_t_function+0x60/0x60 Jan 29 16:22:51 ubuntu kernel: [] fuse_get_req+0x10/0x20 Jan 29 16:22:51 ubuntu kernel: [] fuse_direct_io+0x4fd/0x5c0 Jan 29 16:22:51 ubuntu kernel: [] ? fuse_getxattr+0x12f/0x160 Jan 29 16:22:51 ubuntu kernel: [] ? kmem_cache_alloc_trace+0x187/0x1f0 Jan 29 16:22:51 ubuntu kernel: [] ? fuse_direct_IO+0xff/0x3b0 Jan 29 16:22:51 ubuntu kernel: [] fuse_direct_IO+0x193/0x3b0 Jan 29 16:22:51 ubuntu kernel: [] generic_file_direct_write+0xb9/0x180 Jan 29 16:22:51 ubuntu kernel: [] fuse_file_write_iter+0x15c/0x2e0 Jan 29 16:22:51 ubuntu kernel: [] ? security_file_permission+0x3d/0xc0 Jan 29 16:22:51 ubuntu kernel: [] ? fuse_perform_write+0x540/0x540 Jan 29 16:22:51 ubuntu kernel: [] aio_run_iocb+0x27f/0x2e0 Jan 29 16:22:51 ubuntu kernel: [] ? fsnotify+0x316/0x4a0 Jan 29 16:22:51 ubuntu kernel: [] ? __fget_light+0x25/0x60 Jan 29 16:22:51 ubuntu kernel: [] do_io_submit+0x24b/0x4f0 Jan 29 16:22:51 ubuntu kernel: [] ? wake_up_q+0x70/0x70 Jan 29 16:22:51 ubuntu kernel: [] SyS_io_submit+0x10/0x20 Jan 29 16:22:51 ubuntu kernel: [] entry_SYSCALL_64_fastpath+0x16/0x75 Jan 29 16:22:51 ubuntu kernel: Code: 08 65 4c 03 05 36 af e2 7e 49 83 78 10 00 4d 8b 10 0f 84 36 01 00 00 4d 85 d2 0f 84 2d 01 00 00 49 63 46 20 48 8d 4a 01 49 8b 3e <49> 8b 1c 02 4c 89 d0 65 48 0f c7 0f 0f 94 c0 84 c0 74 bb 49 63 Jan 29 16:22:51 ubuntu kernel: RIP [] __kmalloc+0x94/0x250 Jan 29 16:22:51 ubuntu kernel: RSP Jan 29 16:22:51 ubuntu kernel: CR2: 8800904b06c0 Jan 29 16:22:51 ubuntu kernel: ---[ end trace 1ebba465731d9933 ]--- Jan 29 16:22:52 ubuntu kernel: BUG: unable to handle kernel paging request at 8800904b06c0 Jan 29 16:22:52 ubuntu kernel: IP: [] kmem_cache_alloc_trace+0x7a/0x1f0 Jan 29 16:22:52 ubuntu kernel: PGD 1ff0067 PUD 3738b6063 PMD 0 Jan 29
[Kernel-packages] [Bug 1539642] Re: Integrate zfcp HBA API library 2.1.1
** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Skipper Bug Screeners (skipper-screen-team) ** Tags added: packaging ** Description changed: == Comment: #0 - Heinz-Werner Seeck - 2016-01-29 03:25:26 == Please integrate this package into Ubuntu 16.04. This is a prerequisite for e.g. Tivoli Storage Manager.. Here you can find the location for downloading: http://www.ibm.com/developerworks/linux/linux390/zfcp-hbaapi-2.1.1.html + + It is available under the Common Public License Version 1.0. ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Foundations Team (canonical-foundations) -- 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/1539642 Title: Integrate zfcp HBA API library 2.1.1 Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Heinz-Werner Seeck - 2016-01-29 03:25:26 == Please integrate this package into Ubuntu 16.04. This is a prerequisite for e.g. Tivoli Storage Manager.. Here you can find the location for downloading: http://www.ibm.com/developerworks/linux/linux390/zfcp-hbaapi-2.1.1.html It is available under the Common Public License Version 1.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539642/+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 1539642] Re: Integrate zfcp HBA API library 2.1.1
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1539642 Title: Integrate zfcp HBA API library 2.1.1 Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Heinz-Werner Seeck - 2016-01-29 03:25:26 == Please integrate this package into Ubuntu 16.04. This is a prerequisite for e.g. Tivoli Storage Manager.. Here you can find the location for downloading: http://www.ibm.com/developerworks/linux/linux390/zfcp-hbaapi-2.1.1.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539642/+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 1538909] Re: OPRASHB:Habanero:EEH: Opal not calling out slot number for failing adapter behind plx switch
** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) -- 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/1538909 Title: OPRASHB:Habanero:EEH: Opal not calling out slot number for failing adapter behind plx switch Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: New Status in linux source package in Wily: New Status in linux source package in Xenial: Fix Committed Bug description: == Comment: #0 - MAMATHA INAMDAR - 2016-01-14 04:51:41 == ---Problem Description--- Working with Chad (IO team) we were able to inject an EEH recoverable error to the broadcom network adapter (PE #2) behind the PLX switch. Looks like OPAL calls out the Backplane PLX ( Planar ) instead of the adapter slot. We want to primarily focus on why the adapter slot ( behind PLX ) didn't get called out using this defect. Problem: >> Working with Chad (IO team) we were able to inject an EEH recoverable error >> to the broadcom network adapter (PE #2) and noticed that we are not getting >> the adapter slot called out, instead we get the location pointing to the >> backplane PLX. > >If what you injected is a PCIe error message, I think those cause the >switch leg to freeze, but I will need Gavin to confirm. > >> Per Chad: >> ?? >> ?They're logging the right PE (#2--which corresponds to the Broadcom?? >> ?adapter)--they're just not pointing to its slot explicitly.?? >> ?? >> >> >> >> Here is a snippet the /var/log/messages: >> >> ?? >> ?Nov 11 12:17:18 habmc8p01 kernel: EEH: Frozen PHB#1-PE#2 detected >> ?Nov 11 12:17:18 habmc8p01 kernel: bnx2x: [bnx2x_timer:5750(net0)]MFW seems??? >> ?hanged: drv_pulse (0x1c1) != mcp_pulse (0x7fff)?? >> ?Nov 11 12:17:18 habmc8p01 kernel: EEH: PE location: Backplane PLX, PHB location: >> ?Backplane PLX >> ?? >> >> >> >> >> injection: >> setpci -s 0001:0c:00.2 COMMAND >> ??? >> ?setpci -s??0001:0c:00.2??? >> ?COMMAND=0540?? >> ??? It seems you're disabling memory BAR and then issue MMIO load, which results in "unsupported request" returned from the adapter. In response to that, the PE#2 as shown in the kernel log is put to frozen state. Nothing wrong at this point. I think the only question would be: the location code isn't making sense. Contact Information = - ---uname output--- 3.19.0-43-generic Machine Type = ---Debugger--- A debugger is not configured ---Steps to Reproduce--- This bug is follow up of bug 133061. This bug is opened to backport the kernel patch which is available to fix the issue for bug 133061 on Ubuntu. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for -: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. Firestone server ( Ubuntu Host ) = I have built the Ubuntu kernel with patch and created *.deb files. Please find the same in the following path for installing and testing your test case State: Assigned by: thalerj on 13 January 2016 12:10:58 The patched kernel is working great for both firestone and Habanero. It resolves the issue and all slot numbers are called out properly. == Comment: #1 - MAMATHA INAMDAR - 2016-01-28 01:02:23 == Patch is now available in the following branch https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=7e56f627768da4e6480986b5145dc3422bc448a5 == Comment: #3 - MAMATHA INAMDAR - 2016-01-28 01:09:14 == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538909/+subscriptions -- Mailing list: https://launchpad.net
[Kernel-packages] [Bug 1526683] Re: 10ec:8821 rtl8821ae loses connection occasionally on 2.4 GHz network requiring hardware button to be toggled twice for connection to be re-established
I think this has been mistakenly forgotten as "incomplete", but if that is not the case, please tell me what you want me to do. ** 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/1526683 Title: 10ec:8821 rtl8821ae loses connection occasionally on 2.4 GHz network requiring hardware button to be toggled twice for connection to be re- established Status in linux package in Ubuntu: Confirmed Bug description: rtl8821ae loses connection occasionally connected to 802.11n 2.4 GHz ASUS Wireless Router RT-AC51U (firmware 3.0.0.4.378_9135-gac2b2c2on). This requires WiFi hardware button to be toggled twice for connection to be re-established. WORKAROUND: Set router to "legacy" mode (i.e. 802.11g). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-2-generic 4.3.0-2.11 [modified: boot/vmlinuz-4.3.0-2-generic] ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikaela1361 F pulseaudio /dev/snd/controlC1: mikaela1361 F pulseaudio CurrentDesktop: MATE Date: Wed Dec 16 11:35:09 2015 HibernationDevice: RESUME=UUID=431ec214-73ef-4058-b283-5721bb5a45d2 InstallationDate: Installed on 2015-12-12 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151212) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 006: ID 13d3:3414 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic.efi.signed root=UUID=ab0e7270-40bc-4a68-a541-59fd96690354 ro rw acpi_osi= RelatedPackageVersions: linux-restricted-modules-4.3.0-2-generic N/A linux-backports-modules-4.3.0-2-generic N/A linux-firmware 1.154 SourcePackage: linux UdevLog: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JX.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550JX.204:bd05/07/2015:svnASUSTeKCOMPUTERINC.:pnX550JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JX 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/1526683/+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 1539642] [NEW] Integrate zfcp HBA API library 2.1.1
You have been subscribed to a public bug: == Comment: #0 - Heinz-Werner Seeck - 2016-01-29 03:25:26 == Please integrate this package into Ubuntu 16.04. This is a prerequisite for e.g. Tivoli Storage Manager.. Here you can find the location for downloading: http://www.ibm.com/developerworks/linux/linux390/zfcp-hbaapi-2.1.1.html ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-136235 severity-high targetmilestone-inin1604 -- Integrate zfcp HBA API library 2.1.1 https://bugs.launchpad.net/bugs/1539642 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1506521] Re: [Hyper-V] hv_set_ifconfig issues on Wily 15.10
I've tested it and everything goes fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1506521 Title: [Hyper-V] hv_set_ifconfig issues on Wily 15.10 Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: Confirmed Status in linux source package in Xenial: In Progress Bug description: Hello, It seems that during the Wily development, some changes have occurred that broke the hv_set_ifconfig script. Please see the below details and update the script accordingly. From my understanding the changes in python versioning on 15.10 are causing this, and when running hv_set_ifconfig with Python v3, it will give some code errors. This has been verified with the daily build from Oct 12, kernel 4.2.0-16-generic and the matching linux-cloud-tools/common are installed. # whereis hv_set_ifconfig hv_set_ifconfig: /usr/sbin/hv_set_ifconfig # /usr/sbin/hv_set_ifconfig /usr/bin/env: python: No such file or directory Indeed there is no python executable by default, only python3. Modifying the header for hv_set_ifconfig to use python3, returns the below: ~# /usr/sbin/hv_set_ifconfig File "/usr/sbin/hv_set_ifconfig", line 130 print "===" ^ SyntaxError: Missing parentheses in call to 'print' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506521/+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 1492934] Re: Kernel sometimes won't boot to login screen
** No longer affects: linux (Ubuntu) ** Package changed: xserver-xorg-video-nouveau (Mandriva) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Critical => Undecided ** Changed in: linux (Ubuntu) Status: Confirmed => New ** Changed in: linux (Ubuntu) Remote watch: bugs.mageia.org/ #16245 => None ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492934 Title: Kernel sometimes won't boot to login screen Status in linux package in Ubuntu: Incomplete Bug description: I'm using 3.19.0-26-generic as kernel. Ubuntu version is: Description: Ubuntu 15.04 Release: 15.04 Version of the nouveau driver is: Installed: 1:1.0.11-1ubuntu2build1 Candidate:1:1.0.11-1ubuntu2build1 Version table: *** 1:1.0.11-1ubuntu2build1 0 500 http://ftp.acc.umu.se/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status I expected the module to be able to work without freezing the entire system. This issue prevents me from getting to the login session. I have installed Ubuntu on my brand new laptop which is a Asus N550JK. It has Hybrid Graphics (Intel 4th Generation + nVidia GeForce GTX 850M so I was told to nvidia-prime for Optimus. Sometimes when I boot the kernel it stops before I see the login window and the computer is completely frozen. However if I switch to the proprietary driver for nouveau the computer doesn't lock completely anymore. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 7 09:19:38 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-26-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-26-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] InstallationDate: Installed on 2015-09-05 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed root=UUID=28c2cc37-e8b5-4f1d-8a4a-33f26e77b390 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UdevLog: Error: [Errno 2] Filen eller katalogen finns inte: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK 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.:bvrN550JK.208:bd09/26/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Sep 7 09:16:28 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: intel(G1): [drm] failed to set drm interface version: Permission denied [13]. intel(G1): Failed to claim DRM device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
[Kernel-packages] [Bug 1533602] Re: Click issue after resume
Christophe H, live environments are available to test via http://releases.ubuntu.com/ . -- 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/1533602 Title: Click issue after resume Status in linux package in Ubuntu: Incomplete Bug description: Hello I have a fujitsu laptop with Intel i915 since migration to 13.04 suspend causes issues: click disappear from both trackpad and USB mouse and bluetooth mouse some information 4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux I have this kind of event inside my logs ACPI: Waking up from system sleep state S3 Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: System wakeup disabled by ACPI Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: System wakeup disabled by ACPI Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: System wakeup disabled by ACPI Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of devices complete after 17.130 msecs Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of devices complete after 0.223 msecs Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: System wakeup disabled by ACPI Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System wakeup disabled by ACPI and also PM: Finishing wakeup. Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: Allocating resources Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: Allocating resources Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: Allocating resources Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: Allocating resources Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: Allocating resources Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment for info I am running a OCZ Vertez 3 240 GB SSD later on I have this Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in libQt5Sql.so.5.4.2[7f48eda6a000+3f000] and the results of cat /proc/acpi/wakeup Device S-state Status Sysfs node UAR1 S3*disabled pnp:00:06 EHC1 S3*enabled pci::00:1d.0 EHC2 S3*enabled pci::00:1a.0 HDEF S4*disabled pci::00:1b.0 PCE1 S4*disabled PCE3 S3*disabled pci::00:1c.3 PCE4 S4*disabled pci::00:1c.4 GLAN S4*enabled pci::00:19.0 LID S4*enabled platform:PNP0C0D:00 Hope that helps...do not hesitate if you need more info Thanks --- ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1556 F pulseaudio CasperVersion: 1.366 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126) MachineType: FUJITSU LIFEBOOK S761 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-7-generic N/A linux-backports-modules-4.3.0-7-generic N/A linux-firmware 1.155 Tags: xenial UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.3.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2011 dmi.bios.vendor: FUJITSU // Phoenix Technolog
[Kernel-packages] [Bug 1492934] [NEW] Kernel sometimes won't boot to login screen
You have been subscribed to a public bug: I'm using 3.19.0-26-generic as kernel. Ubuntu version is: Description:Ubuntu 15.04 Release:15.04 Version of the nouveau driver is: Installed: 1:1.0.11-1ubuntu2build1 Candidate:1:1.0.11-1ubuntu2build1 Version table: *** 1:1.0.11-1ubuntu2build1 0 500 http://ftp.acc.umu.se/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status I expected the module to be able to work without freezing the entire system. This issue prevents me from getting to the login session. I have installed Ubuntu on my brand new laptop which is a Asus N550JK. It has Hybrid Graphics (Intel 4th Generation + nVidia GeForce GTX 850M so I was told to nvidia-prime for Optimus. Sometimes when I boot the kernel it stops before I see the login window and the computer is completely frozen. However if I switch to the proprietary driver for nouveau the computer doesn't lock completely anymore. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 7 09:19:38 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-26-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-26-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] InstallationDate: Installed on 2015-09-05 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed root=UUID=28c2cc37-e8b5-4f1d-8a4a-33f26e77b390 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UdevLog: Error: [Errno 2] Filen eller katalogen finns inte: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK 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.:bvrN550JK.208:bd09/26/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Sep 7 09:16:28 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: intel(G1): [drm] failed to set drm interface version: Permission denied [13]. intel(G1): Failed to claim DRM device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16971 vendor SDC xserver.version: 2:1.17.1-0ubuntu3 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug latest-bios-208 ubuntu vivid -- Kernel sometimes won't boot to login screen https://bugs.launchpad.net/bugs/1492934 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1533602] Re: Click issue after resume
Hello Christopher I don't think I understand what to do... I don't remember if it was working with 13.04 or even 13.10... So if you want me to go back to this ubuntu version how can I do it...the wiki is not totally clear for me. This is my 'only' laptop and don't want to screw it up Kind Regards -- 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/1533602 Title: Click issue after resume Status in linux package in Ubuntu: Incomplete Bug description: Hello I have a fujitsu laptop with Intel i915 since migration to 13.04 suspend causes issues: click disappear from both trackpad and USB mouse and bluetooth mouse some information 4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux I have this kind of event inside my logs ACPI: Waking up from system sleep state S3 Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: System wakeup disabled by ACPI Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: System wakeup disabled by ACPI Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: System wakeup disabled by ACPI Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of devices complete after 17.130 msecs Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of devices complete after 0.223 msecs Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: System wakeup disabled by ACPI Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System wakeup disabled by ACPI and also PM: Finishing wakeup. Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: Allocating resources Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: Allocating resources Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: Allocating resources Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: Allocating resources Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: Allocating resources Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment for info I am running a OCZ Vertez 3 240 GB SSD later on I have this Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in libQt5Sql.so.5.4.2[7f48eda6a000+3f000] and the results of cat /proc/acpi/wakeup Device S-state Status Sysfs node UAR1 S3*disabled pnp:00:06 EHC1 S3*enabled pci::00:1d.0 EHC2 S3*enabled pci::00:1a.0 HDEF S4*disabled pci::00:1b.0 PCE1 S4*disabled PCE3 S3*disabled pci::00:1c.3 PCE4 S4*disabled pci::00:1c.4 GLAN S4*enabled pci::00:19.0 LID S4*enabled platform:PNP0C0D:00 Hope that helps...do not hesitate if you need more info Thanks --- ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1556 F pulseaudio CasperVersion: 1.366 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126) MachineType: FUJITSU LIFEBOOK S761 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 RelatedPackageVersions: linux-restricted-modules-4.3.0-7-generic N/A linux-backports-modules-4.3.0-7-generic N/A linux-firmware 1.155 Tags: xenial UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.3.0-7-generic x86_64 Upgrad
[Kernel-packages] [Bug 1539102] Re: EPOW related RTAS event messages in kernel logs
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin14044 -- 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/1539102 Title: EPOW related RTAS event messages in kernel logs Status in linux package in Ubuntu: Triaged Bug description: Problem Description === EPOW related RTAS event messages in kernel logs Machine Type = POWER8 Steps to Reproduce = 1) Install Ubuntu14.04 on a Power VM LPAR. 2) Post reboot following events are logged into dmesg & /var/log/syslog [216112.739470] Non critical power or cooling issue cleared [216122.992606] RTAS: event: 187589, Type: EPOW, Severity: 1 [216122.992609] Non critical power or cooling issue cleared [216129.240731] RTAS: event: 187590, Type: EPOW, Severity: 1 [216129.240733] Non critical power or cooling issue cleared [216141.612689] RTAS: event: 187591, Type: EPOW, Severity: 1 [216141.612691] Non critical power or cooling issue cleared [216147.830578] RTAS: event: 187592, Type: EPOW, Severity: 1 [216147.830580] Non critical power or cooling issue cleared [216158.334408] RTAS: event: 187593, Type: EPOW, Severity: 1 [216158.334410] Non critical power or cooling issue cleared [216199.883138] RTAS: event: 187594, Type: EPOW, Severity: 1 [216199.883140] Non critical power or cooling issue cleared [216244.596335] RTAS: event: 187595, Type: EPOW, Severity: 1 [216244.596337] Non critical power or cooling issue cleared [216250.853514] RTAS: event: 187596, Type: EPOW, Severity: 1 [216250.853516] Non critical power or cooling issue cleared [216263.319986] RTAS: event: 187597, Type: EPOW, Severity: 1 [216263.319989] Non critical power or cooling issue cleared [216271.438925] RTAS: event: 187598, Type: EPOW, Severity: 1 The log is filled with several such messages along with RTAS: event: 13884, Type: Platform Error, Severity: 2 RTAS: event: 13885, Type: Platform Error, Severity: 2 RTAS: event: 13886, Type: Platform Error, Severity: 2 RTAS: event: 13887, Type: Platform Error, Severity: 2 RTAS: event: 13888, Type: Platform Error, Severity: 2 RTAS: event: 13889, Type: Platform Error, Severity: 2 RTAS: event: 13890, Type: Platform Error, Severity: 2 RTAS: event: 13891, Type: Platform Error, Severity: 2 Regrads Praveen == Comment: #2 - VASANT HEGDE - == Below upstream patch fixes this issue..I believe this will apply cleanly on top of Ubuntu 14.04.04 kernel. commit b4af279a7cba5cc1f665485e8ecdf272f1ba0cc5 Author: Vipin K Parashar Date: Tue Dec 1 16:43:42 2015 +0530 powerpc/pseries: Limit EPOW reset event warnings Kernel prints respective warnings about various EPOW events for user information/action after parsing EPOW interrupts. At times below EPOW reset event warning is seen to be flooding kernel log over a period of time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539102/+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 1539090] Re: linux: 4.4.0-2.16 -proposed tracker
Here's the relevant information: xenial linux 4.4.0-2.16 REGR summary Please verify test results in http://people.canonical.com/~kernel/status /adt-matrix/overall.txt ** Changed in: kernel-development-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1539090 Title: linux: 4.4.0-2.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-2.16 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 kernel-Prepare-package-start:Thursday, 28. January 2016 13:56 UTC kernel-phase-changed:Thursday, 28. January 2016 13:56 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 28. January 2016 14:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1539090/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Milestone: None => ww08-2016 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: New Status in bluez package in Ubuntu: Confirmed Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1538618] Re: flashcache: build failures against kernel 4.4
This bug was fixed in the package flashcache - 3.1.3+git20150701-2ubuntu1 --- flashcache (3.1.3+git20150701-2ubuntu1) xenial; urgency=low * Merge from Debian unstable. Remaining changes (LP: #1539063): - ensure we fill in the BIO error code when ending an IO * d/p/switch-to-using-prepare_ioctl-and-target_ioctl.patch: - switch to the new prepare_ioctl and target_ioctl calls (LP: #1538618) flashcache (3.1.3+git20150701-2) unstable; urgency=medium * Fix build error on linux 4.3 flashcache (3.1.3+git20150701-1) unstable; urgency=medium * New upstream release * Switch to kmod(Closes: #733702) * Bump standards version to 3.9.6 -- Andy Whitcroft Mon, 25 Jan 2016 13:13:52 + ** Changed in: flashcache (Ubuntu) Status: In Progress => 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/1538618 Title: flashcache: build failures against kernel 4.4 Status in flashcache package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Bug description: We are seeing build failures against 4.4 kernels introduced by the change to device mapper ioctl interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashcache/+bug/1538618/+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 1528101] Re: ISST-LTE: kdump failed: second kernel booting hangs after /scripts/init-bottom when large min_free_kbytes value being set
Yes, I have started to work on a possible solution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1528101 Title: ISST-LTE: kdump failed: second kernel booting hangs after /scripts /init-bottom when large min_free_kbytes value being set Status in kexec-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Ping Tian Han - 2015-07-15 04:21:23 == ---Problem Description--- kdump can be triggered by "echo c > /proc/sysrq-trigger', but the second kernel hangs here: ... [7.311129] sd 0:2:4:0: alua: rtpg failed with 8070002 [7.311232] sd 0:2:4:0: alua: port group 1dc state A preferred supports TOlUSNA done. Begin: Running /scripts/local-premount ... done. [ 12.894379] EXT4-fs (dm-12): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. [ 13.463955] init: plymouth-upstart-bridge main process (1681) terminated with status 1 [ 13.463996] init: plymouth-upstart-bridge main process ended, respawning [ 13.471552] init: plymouth-upstart-bridge main process (1691) terminated with status 1 [ 13.471586] init: plymouth-upstart-bridge main process ended, respawning [ 13.479547] init: plymouth-upstart-bridge main process (1694) terminated with status 1 [ 13.479580] init: plymouth-upstart-bridge main process ended, respawning [ 13.487503] init: plymouth-upstart-bridge main process (1696) terminated with status 1 [ 13.487536] init: plymouth-upstart-bridge main process ended, respawning [ 13.496113] init: plymouth-upstart-bridge main process (1698) terminated with status 1 [ 13.496146] init: plymouth-upstart-bridge main process ended, respawning [ 13.504363] init: plymouth-upstart-bridge main process (1700) terminated with status 1 [ 13.504397] init: plymouth-upstart-bridge main process ended, respawning [ 13.512840] init: plymouth-upstart-bridge main process (1702) terminated with status 1 [ 13.512873] init: plymouth-upstart-bridge main process ended, respawning [ 13.521159] init: plymouth-upstart-bridge main process (1704) terminated with status 1 [ 13.521196] init: plymouth-upstart-bridge main process ended, respawning [ 13.531934] init: plymouth-upstart-bridge main process (1706) terminated with status 1 [ 13.531968] init: plymouth-upstart-bridge main process ended, respawning [ 13.548264] init: plymouth-upstart-bridge main process (1708) terminated with status 1 [ 13.548301] init: plymouth-upstart-bridge main process ended, respawning [ 14.774719] EXT4-fs (dm-12): re-mounted. Opts: errors=remount-ro <--- and no vmcore dumpped. Contact Information = Ping Tian Han/pt...@cn.ibm.com, Mikhail Afanasiev/afana...@us.ibm.com ---uname output--- Linux dilllp1 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---System Hang--- the booting process of the second kernel hangs. We have to reboot the system. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. install ubuntu on dilllp1, which root device is on a mpath device 2. sudo apt-get install linux-crashdump 3. change the crashkerenl= parameter in /boot/grub/grub.cfg to 'crashkernel=768M', then reboot 4. trigger kdump by 'echo c > /proc/sysrq-trigger' Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit == Comment: #8 - Ping Tian Han - 2015-12-09 02:09:30 == We can reproduce this bug with kernel 4.2.0-19. == Comment: #12 - Hari Krishna Bathini - 2015-12-09 08:22:27 == Is the issue only seen with sysctl configuration "vm.min_free_kbytes = 312721" ? Thanks Hari == Comment: #13 - Ping Tian Han - 2015-12-09 21:08:54 == (In reply to comment #12) > Is the issue only seen with sysctl configuration > "vm.min_free_kbytes = 312721" ? > Yes, I just found that if use the default min_free_kbytes value then kdump works just fine! == Comment: #14 - Hari Krishna Bathini - 2015-12-10 00:51:43 == (In reply to comment #13) > (In reply to comment #12) > > Is the issue only seen with sysctl configuration > > "vm.min_free_kbytes = 312721" ? > > > > Yes, I just found that if use the default min_free_kbytes value then kdump > works just fine! It is blocking kdump from utilising the memory needed to boot. So, crashkernel=768M with min_free_kbytes configured to 312721 translates to ~450 MB for second kernel boot (kdump) which doesn't seem to be sufficient for booting. How to handle this: 1. Reserve memory for crashkernel, that augments it by min_free_kbytes OR 2. Use default min_free_kbytes Thanks Hari == Co
[Kernel-packages] [Bug 1539090] Re: linux: 4.4.0-2.16 -proposed tracker
** Changed in: kernel-development-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-development-workflow/prepare-package-meta Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) ** Changed in: kernel-development-workflow/prepare-package-signed Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) -- 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/1539090 Title: linux: 4.4.0-2.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Confirmed Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-2.16 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 kernel-Prepare-package-start:Thursday, 28. January 2016 13:56 UTC kernel-phase-changed:Thursday, 28. January 2016 13:56 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 28. January 2016 14:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1539090/+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 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)
Sorry for the formatting : the ppa is ppa:louis-bouchard/makedumpfile-tests -- 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/1536904 Title: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal) Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Wily: Confirmed Bug description: == Comment: #0 - == ---Problem Description--- Kdump fails on Ubuntu 16.04 with Austin adapter(tg3) Contact Information = hathy...@in.ibm.com, iranna.an...@in.ibm.com,mputt...@in.ibm.com ---uname output--- linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Machine details: 9.47.67.156 (root/ltcnetdd) Machine Type = 8247-22L ---System Hang--- The system hangs after triggering a crash. Need to reboot to bring it up and functional. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Steps to follow: 1. apt-get install linux-crashdump 2. apt-get install kdump-tools 3. Edit /etc/default/kdump-tools and change the following: USE_KDUMP=0 to 1 4. Change the size of the crash kernel in /boot/grub/grub.cfg to crashkernel=4096M-:4096M 5. Load the kdump config file: kdump-config load 6. echo 1 > /proc/sys/kernel/sysrq 7. echo c > /proc/sysrq-trigger Things to look at to cross-check are: After loading the kdump-config file, check for it's status root@ltciofvtr-s822l1:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: SSH: root@35.35.35.36 SSH_KEY: /root/.ssh/id_rsa HOSTTAG: ip current state:ready to kdump kexec command: /sbin/kexec -p --args-linux --command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic root@ltciofvtr-s822l1:~# kdump-config status * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to /boot/vmlinuz-4.3.0-5-generic current state : ready to kdump root@ltciofvtr-s822l1:~# cat /proc/cmdline root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash crashkernel=4096M-:4096M root@ltciofvtr-s822l1:~# dmesg| grep -i crash [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System RAM: 131072MB) [0.00] Kernel command line: root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash crashkernel=4096M-:4096M Observations: 1. Kdump-config status command reports that there is a broken symbloic link suggesting that kdump-config file is unable to handle the symbolic link. 2. Trace observed on console: root@ltciofvtr-s822l1:~# echo c | tee /proc/sysrq-trigger c [ 238.872102] sysrq: SysRq : Trigger a crash [ 238.872179] Unable to handle kernel paging request for data at address 0x [ 238.872256] Faulting instruction address: 0xc0646534 [ 238.872322] Oops: Kernel access of bad area, sig: 11 [#1] [ 238.872373] SMP NR_CPUS=2048 NUMA PowerNV [ 238.872427] Modules linked in: dm_round_robin dm_service_time ipmi_powernv ipmi_msghandler leds_powernv uio_pdrv_genirq powernv_rng uio dm_multipath sunrpc bonding autofs4 btrfs xor raid6_pq mlx4_en ses enclosure bnx2x mlx4_core lpfc qla2xxx mdio libcrc32c be2net e1000e vxlan ipr ip6_udp_tunnel udp_tunnel scsi_transport_fc [ 238.872895] CPU: 121 PID: 3861 Comm: tee Not tainted 4.3.0-5-generic #16-Ubuntu [ 238.872973] task: c00fe01ce860 ti: c00fe022c000 task.ti: c00fe022c000 [ 238.873049] NIP: c0646534 LR: c06475f8 CTR: c0646500 [ 238.873125] REGS: c00fe022f990 TRAP: 0300 Not tainted (4.3.0-5-generic) [ 238.873200] MSR: 90009033 CR: 28004222 XER: 2000 [ 238.873392] CFAR: c0008468 DAR: DSISR: 4200 SOFTE: 1 GPR00: c06475f8 c00fe022fc10 c155e400 0063 GPR04: c007fc648450 c007fc659cf0 c01fff83 0792 GPR08: 0007 0001 c01fff861780 GPR12: c0646500 c7b87d80 GPR16: GPR20: 10009d88 0001 GPR24: 10009d88 3fffe7b210b0 c14a5cb0 0004 GPR28: c14a6070 0063 c1460de4 [ 238.875062] NIP [c0646534] sysrq_handle_crash+0x34/0x50 [ 238.875178] LR [c06475f8] __handle_sysrq+0xe8/0x280 [ 238.875270] Call Trace: [ 238.8
[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)
Hello, You can find the upcoming version in the following PPA : ppa:louis- bouchard/makedumpfile-tests. Here is the changelog : * Allow for symlinks to be created for vmlinux files : On Power8 architecture, systems are booting from a vmlinux file. The symlink /var/lib/kdump/vmlinuz has to point to this file. (LP: #1536904) * Add functionality to create symlinks for older kernels : If kdump is installed on systems with more than one kernel package, the smaller initrd.img file will only be created for the latest kernel. Adding the 'symlinks' functionality will allow for the creation of symlinks to older kernels. If the smaller initrd.img file is missing in /var/lib/kdump it will be created beforehand. This will be preempted if kdump is already loaded. (LP: #1537714) * Fix kdump-config manpage : add documentation for the propagate option. (LP: #1538148) * Improve manpage for kdump-config -- 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/1536904 Title: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal) Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Wily: Confirmed Bug description: == Comment: #0 - == ---Problem Description--- Kdump fails on Ubuntu 16.04 with Austin adapter(tg3) Contact Information = hathy...@in.ibm.com, iranna.an...@in.ibm.com,mputt...@in.ibm.com ---uname output--- linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Machine details: 9.47.67.156 (root/ltcnetdd) Machine Type = 8247-22L ---System Hang--- The system hangs after triggering a crash. Need to reboot to bring it up and functional. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Steps to follow: 1. apt-get install linux-crashdump 2. apt-get install kdump-tools 3. Edit /etc/default/kdump-tools and change the following: USE_KDUMP=0 to 1 4. Change the size of the crash kernel in /boot/grub/grub.cfg to crashkernel=4096M-:4096M 5. Load the kdump config file: kdump-config load 6. echo 1 > /proc/sys/kernel/sysrq 7. echo c > /proc/sysrq-trigger Things to look at to cross-check are: After loading the kdump-config file, check for it's status root@ltciofvtr-s822l1:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: SSH: root@35.35.35.36 SSH_KEY: /root/.ssh/id_rsa HOSTTAG: ip current state:ready to kdump kexec command: /sbin/kexec -p --args-linux --command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" --initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic root@ltciofvtr-s822l1:~# kdump-config status * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to /boot/vmlinuz-4.3.0-5-generic current state : ready to kdump root@ltciofvtr-s822l1:~# cat /proc/cmdline root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash crashkernel=4096M-:4096M root@ltciofvtr-s822l1:~# dmesg| grep -i crash [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System RAM: 131072MB) [0.00] Kernel command line: root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash crashkernel=4096M-:4096M Observations: 1. Kdump-config status command reports that there is a broken symbloic link suggesting that kdump-config file is unable to handle the symbolic link. 2. Trace observed on console:
[Kernel-packages] [Bug 1523108] Re: Bluetooth doesn't work on ASUS Zenbook UX301LAA
After rebooting, backlit returned, but still no reaction on Fn+F2 and no Bluetooth. This is dmesg after reboot: $ dmesg | grep -i bluetooth [8.795276] Bluetooth: Core ver 2.21 [8.795292] Bluetooth: HCI device and connection manager initialized [8.795295] Bluetooth: HCI socket layer initialized [8.795298] Bluetooth: L2CAP socket layer initialized [8.795302] Bluetooth: SCO socket layer initialized [8.829680] Bluetooth: hci0: read Intel version: 370710018002030d00 [8.831009] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq [8.907934] Bluetooth: hci0 sending Intel patch command (0xfc8e) failed (-19) [9.293108] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [9.293111] Bluetooth: BNEP filters: protocol multicast [9.293116] Bluetooth: BNEP socket layer initialized [ 10.903615] Bluetooth: hci0 command 0xfc8e tx timeout [ 10.903629] Bluetooth: hci0 sending frame failed (-19) [ 10.907603] Bluetooth: hci0: Exiting manufacturer mode failed (-110) Some more stuff in syslog: Jan 29 14:42:35 shadow-zenbook systemd[1]: Starting Bluetooth service... Jan 29 14:42:35 shadow-zenbook bluetoothd[1414]: Bluetooth daemon 5.35 Jan 29 14:42:35 shadow-zenbook bluetoothd[1414]: Starting SDP server Jan 29 14:42:35 shadow-zenbook kernel: [8.795276] Bluetooth: Core ver 2.21 Jan 29 14:42:35 shadow-zenbook kernel: [8.795292] Bluetooth: HCI device and connection manager initialized Jan 29 14:42:35 shadow-zenbook kernel: [8.795295] Bluetooth: HCI socket layer initialized Jan 29 14:42:35 shadow-zenbook kernel: [8.795298] Bluetooth: L2CAP socket layer initialized Jan 29 14:42:35 shadow-zenbook kernel: [8.795302] Bluetooth: SCO socket layer initialized Jan 29 14:42:35 shadow-zenbook kernel: [8.829680] Bluetooth: hci0: read Intel version: 370710018002030d00 Jan 29 14:42:35 shadow-zenbook kernel: [8.831009] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq Jan 29 14:42:35 shadow-zenbook kernel: [8.907934] Bluetooth: hci0 sending Intel patch command (0xfc8e) failed (-19) Jan 29 14:42:35 shadow-zenbook kernel: [9.293108] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Jan 29 14:42:35 shadow-zenbook kernel: [9.293111] Bluetooth: BNEP filters: protocol multicast Jan 29 14:42:35 shadow-zenbook kernel: [9.293116] Bluetooth: BNEP socket layer initialized Jan 29 14:42:35 shadow-zenbook bluetoothd[1414]: Bluetooth management interface 1.11 initialized Jan 29 14:42:35 shadow-zenbook systemd[1]: Started Bluetooth service. Jan 29 14:42:35 shadow-zenbook systemd[1]: Reached target Bluetooth. Jan 29 14:42:35 shadow-zenbook NetworkManager[1436]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Jan 29 14:42:36 shadow-zenbook kernel: [ 10.903615] Bluetooth: hci0 command 0xfc8e tx timeout Jan 29 14:42:36 shadow-zenbook kernel: [ 10.903629] Bluetooth: hci0 sending frame failed (-19) Jan 29 14:42:36 shadow-zenbook kernel: [ 10.907603] Bluetooth: hci0: Exiting manufacturer mode failed (-110) Jan 29 14:42:36 shadow-zenbook systemd[1]: bluetooth.target: Unit not needed anymore. Stopping. Jan 29 14:42:36 shadow-zenbook systemd[1]: Stopped target Bluetooth. -- 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/1523108 Title: Bluetooth doesn't work on ASUS Zenbook UX301LAA Status in linux package in Ubuntu: Triaged Bug description: It's not possible to make bluetooth work. Pressing Fn+F2 doesn't change anything. Sometimes a grey (inactive) bluetooth icon appears but disappears instantly after attempt to turn it on. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shadowlmd 2409 F pulseaudio /dev/snd/controlC1: shadowlmd 2409 F pulseaudio CurrentDesktop: Unity Date: Sat Dec 5 18:03:20 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=4443577b-ebf9-4f35-bd95-660448592ddb InstallationDate: Installed on 2015-10-22 (43 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=e7df807f-bc9b-4cdf-85ae-38b8a3c6f016 ro quiet splash rootfstype=ext4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/ud
[Kernel-packages] [Bug 1523108] Re: Bluetooth doesn't work on ASUS Zenbook UX301LAA
Tried, didn't help. $ cat /etc/modprobe.d/asus.conf options asus_nb_wmi wapf=4 $ sudo modprobe -r asus_nb_wmi $ sudo modprobe -v asus_nb_wmi insmod /lib/modules/4.5.0-040500rc1-generic/kernel/drivers/platform/x86/wmi.ko insmod /lib/modules/4.5.0-040500rc1-generic/kernel/drivers/input/sparse-keymap.ko insmod /lib/modules/4.5.0-040500rc1-generic/kernel/drivers/platform/x86/asus-wmi.ko insmod /lib/modules/4.5.0-040500rc1-generic/kernel/drivers/platform/x86/asus-nb-wmi.ko wapf=4 F2 key LED lighted up and BT icon disappeared from tray and I got this message in dmesg: [39333.878246] usb 2-4: USB disconnect, device number 6 This happens without this option too. Also, keyboard backlit stopped working with this option. -- 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/1523108 Title: Bluetooth doesn't work on ASUS Zenbook UX301LAA Status in linux package in Ubuntu: Triaged Bug description: It's not possible to make bluetooth work. Pressing Fn+F2 doesn't change anything. Sometimes a grey (inactive) bluetooth icon appears but disappears instantly after attempt to turn it on. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shadowlmd 2409 F pulseaudio /dev/snd/controlC1: shadowlmd 2409 F pulseaudio CurrentDesktop: Unity Date: Sat Dec 5 18:03:20 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=4443577b-ebf9-4f35-bd95-660448592ddb InstallationDate: Installed on 2015-10-22 (43 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=e7df807f-bc9b-4cdf-85ae-38b8a3c6f016 ro quiet splash rootfstype=ext4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA 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.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX301LAA 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/1523108/+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 1536803] Re: linux: 4.4.0-1.15 -proposed tracker
*** This bug is a duplicate of bug 1539090 *** https://bugs.launchpad.net/bugs/1539090 ** This bug has been marked a duplicate of bug 1539090 linux: 4.4.0-2.16 -proposed 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/1536803 Title: linux: 4.4.0-1.15 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-1.15 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 kernel-Prepare-package-start:Thursday, 21. January 2016 21:58 UTC kernel-phase-changed:Thursday, 21. January 2016 21:58 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Friday, 22. January 2016 19:23 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1536803/+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 1539090] Re: linux: 4.4.0-2.16 -proposed tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1539090 Title: linux: 4.4.0-2.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-2.16 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 kernel-Prepare-package-start:Thursday, 28. January 2016 13:56 UTC kernel-phase-changed:Thursday, 28. January 2016 13:56 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 28. January 2016 14:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1539090/+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 1536493] Re: Call/SMS Alert are not routed to bluetooth headset
I have the same problem. Device: Aquaris E5 Ubuntu Edition Version: OTA-9 When i connect the phone to my bluetooth speaker or my car radio, i can play music via bluetooth. But the handsfree function does not work. My car radio is a Sony MEX-BT2500, when i connect the phone i can see the hansfree icon on the radio flashing for a second. The music icon stays on. And i can not use the buttons or the remote on the radio to switch songs. These functions work on my old Nokia with Symbian. The same happens with my bluetooth speaker, it is a Logitech UE Mini. Music play fine but the calls are not going via the bluetooth speaker. I had the same problems on OTA-8.5 -- 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/1536493 Title: Call/SMS Alert are not routed to bluetooth headset Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Expected Result: All audio from the phone should play in the bluetooth headset when it is connected. Actual Result: The music and other audio plays on the bluetooth headset however the SMS/Call alerts are not. They are still played in the phone's speaker. This causes the user to miss the notification because you can't hear it especially when listening to music/podcast. Device: bq Aquarius E5 HD Version: OTA 8.5 Same on MX4 rc-proposed/ota 9 In addition when answering the call, the call audio is not on the headset To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536493/+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 1539090] Re: linux: 4.4.0-2.16 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) -- 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/1539090 Title: linux: 4.4.0-2.16 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-2.16 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 kernel-Prepare-package-start:Thursday, 28. January 2016 13:56 UTC kernel-phase-changed:Thursday, 28. January 2016 13:56 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Thursday, 28. January 2016 14:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1539090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1523108] Re: Bluetooth doesn't work on ASUS Zenbook UX301LAA
Try to use option "wapf=4" for asus_nb_wmi module. 2016-01-29 13:43 GMT+03:00 Vasya Pupkin <1523...@bugs.launchpad.net>: > And of course everything works like a charm under Windows 10. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1523108 > > Title: > Bluetooth doesn't work on ASUS Zenbook UX301LAA > > Status in linux package in Ubuntu: > Triaged > > Bug description: > It's not possible to make bluetooth work. Pressing Fn+F2 doesn't > change anything. Sometimes a grey (inactive) bluetooth icon appears > but disappears instantly after attempt to turn it on. > > ProblemType: Bug > DistroRelease: Ubuntu 15.10 > Package: linux-image-4.2.0-21-generic 4.2.0-21.25 > ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 > Uname: Linux 4.2.0-21-generic x86_64 > ApportVersion: 2.19.1-0ubuntu5 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: shadowlmd 2409 F pulseaudio >/dev/snd/controlC1: shadowlmd 2409 F pulseaudio > CurrentDesktop: Unity > Date: Sat Dec 5 18:03:20 2015 > EcryptfsInUse: Yes > HibernationDevice: RESUME=UUID=4443577b-ebf9-4f35-bd95-660448592ddb > InstallationDate: Installed on 2015-10-22 (43 days ago) > InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) > MachineType: ASUSTeK COMPUTER INC. UX301LAA > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed > root=UUID=e7df807f-bc9b-4cdf-85ae-38b8a3c6f016 ro quiet splash > rootfstype=ext4 vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-4.2.0-21-generic N/A >linux-backports-modules-4.2.0-21-generic N/A >linux-firmware1.149.3 > SourcePackage: linux > UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/05/2015 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX301LAA.211 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX301LAA > 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.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.name: UX301LAA > 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/1523108/+subscriptions -- 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/1523108 Title: Bluetooth doesn't work on ASUS Zenbook UX301LAA Status in linux package in Ubuntu: Triaged Bug description: It's not possible to make bluetooth work. Pressing Fn+F2 doesn't change anything. Sometimes a grey (inactive) bluetooth icon appears but disappears instantly after attempt to turn it on. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shadowlmd 2409 F pulseaudio /dev/snd/controlC1: shadowlmd 2409 F pulseaudio CurrentDesktop: Unity Date: Sat Dec 5 18:03:20 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=4443577b-ebf9-4f35-bd95-660448592ddb InstallationDate: Installed on 2015-10-22 (43 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=e7df807f-bc9b-4cdf-85ae-38b8a3c6f016 ro quiet splash rootfstype=ext4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA 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.
[Kernel-packages] [Bug 1523108] Re: Bluetooth doesn't work on ASUS Zenbook UX301LAA
Maybe the problem is not with adapter itself but with Zenbook UX301LA. Fn+F2 hotkey used to enable/disable BT and Wi-Fi doesn't work too. -- 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/1523108 Title: Bluetooth doesn't work on ASUS Zenbook UX301LAA Status in linux package in Ubuntu: Triaged Bug description: It's not possible to make bluetooth work. Pressing Fn+F2 doesn't change anything. Sometimes a grey (inactive) bluetooth icon appears but disappears instantly after attempt to turn it on. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shadowlmd 2409 F pulseaudio /dev/snd/controlC1: shadowlmd 2409 F pulseaudio CurrentDesktop: Unity Date: Sat Dec 5 18:03:20 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=4443577b-ebf9-4f35-bd95-660448592ddb InstallationDate: Installed on 2015-10-22 (43 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=e7df807f-bc9b-4cdf-85ae-38b8a3c6f016 ro quiet splash rootfstype=ext4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA 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.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX301LAA 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/1523108/+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 1523108] Re: Bluetooth doesn't work on ASUS Zenbook UX301LAA
And of course everything works like a charm under Windows 10. -- 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/1523108 Title: Bluetooth doesn't work on ASUS Zenbook UX301LAA Status in linux package in Ubuntu: Triaged Bug description: It's not possible to make bluetooth work. Pressing Fn+F2 doesn't change anything. Sometimes a grey (inactive) bluetooth icon appears but disappears instantly after attempt to turn it on. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shadowlmd 2409 F pulseaudio /dev/snd/controlC1: shadowlmd 2409 F pulseaudio CurrentDesktop: Unity Date: Sat Dec 5 18:03:20 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=4443577b-ebf9-4f35-bd95-660448592ddb InstallationDate: Installed on 2015-10-22 (43 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=e7df807f-bc9b-4cdf-85ae-38b8a3c6f016 ro quiet splash rootfstype=ext4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA 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.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX301LAA 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/1523108/+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 1535307] Re: running 'rr' make check causes kernel "hard LOCKUP"
I wrote: "PS: it's possible that that commit doesn't actually fix the underlying kernel crash, it just means that rr isn't triggering it any more, and that if you modified EFLAGS via the ptrace interface rather than r11 you'd get the crash back again." but looking at the kernel I think that is impossible, since the set_flags() function in arch/x86/kernel/ptrace.c sanitizes eflags if set via ptrace. The issue fixed by 29722cd4ef66 is that setting r11 in some situations would bypass the sanitizing. -- 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/1535307 Title: running 'rr' make check causes kernel "hard LOCKUP" Status in linux package in Ubuntu: Triaged Bug description: Running the 'rr' make check on Ubuntu Trusty causes the machine to become unusable because the kernel crashes. (rr build-and-make-check instructions: https://github.com/mozilla/rr/wiki/Building-And- Installing) This is 3.13.0-74-generic #118-Ubuntu for x86_64. This is rr bug https://github.com/mozilla/rr/issues/1614 (which includes information about a Debian Jessie kernel crash initially and also the Ubuntu crash later on in the same report), but since crashing the kernel is a kernel bug I'm reporting that part here. kern.log reports: Jan 18 12:33:12 e104462 kernel: [ 367.805326] [ cut here ] Jan 18 12:33:12 e104462 kernel: [ 367.805333] WARNING: CPU: 2 PID: 4294 at /build/linux-_xRakU/linux-3.13.0/kernel/watchdog.c:245 watchdog_overflow_callback+0x 9c/0xd0() Jan 18 12:33:12 e104462 kernel: [ 367.805334] Watchdog detected hard LOCKUP on cpu 2 Jan 18 12:33:12 e104462 kernel: [ 367.805335] Modules linked in: pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) bnep rfcomm bluetooth nfsd auth_rpcgss nfs_acl binfmt_misc nfs lockd sunrpc fscache dm_crypt snd_hda_codec_hdmi intel_rapl snd_hda_codec_realtek x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_intel snd_hda_codec kvm pl2303 usbserial snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi aesni_intel aes_x86_64 lrw snd_seq gf128mul glue_helper ablk_helper cryptd snd_seq_device serio_raw snd_timer lpc_ich snd soundcore mei_me mei shpchp mac_hid parport_pc ppdev lp parport hid_generic usbhid hid usb_storage nouveau mxm_wmi i2c_algo_bit ttm drm_kms_helper e1000e psmouse ahci drm ptp libahci pps_core video wmi Jan 18 12:33:12 e104462 kernel: [ 367.805365] CPU: 2 PID: 4294 Comm: rr:async_signal Tainted: G OX 3.13.0-74-generic #118-Ubuntu Jan 18 12:33:12 e104462 kernel: [ 367.805366] Hardware name: LENOVO 32281S1/MAHOBAY, BIOS 9SKT71AUS 07/02/2013 Jan 18 12:33:12 e104462 kernel: [ 367.805367] 0009 8804033abc78 81724b70 8804033abcc0 Jan 18 12:33:12 e104462 kernel: [ 367.805369] 8804033abcb0 810678bd 880407798000 Jan 18 12:33:12 e104462 kernel: [ 367.805370] 8804033abde0 8804033abf58 8804033abd10 Jan 18 12:33:12 e104462 kernel: [ 367.805372] Call Trace: Jan 18 12:33:12 e104462 kernel: [ 367.805376] [] dump_stack+0x45/0x56 Jan 18 12:33:12 e104462 kernel: [ 367.805379] [] warn_slowpath_common+0x7d/0xa0 Jan 18 12:33:12 e104462 kernel: [ 367.805380] [] warn_slowpath_fmt+0x4c/0x50 Jan 18 12:33:12 e104462 kernel: [ 367.805382] [] ? restart_watchdog_hrtimer+0x50/0x50 Jan 18 12:33:12 e104462 kernel: [ 367.805384] [] watchdog_overflow_callback+0x9c/0xd0 Jan 18 12:33:12 e104462 kernel: [ 367.805386] [] __perf_event_overflow+0x8e/0x250 Jan 18 12:33:12 e104462 kernel: [ 367.805389] [] ? x86_perf_event_set_period+0xe8/0x150 Jan 18 12:33:12 e104462 kernel: [ 367.805390] [] perf_event_overflow+0x14/0x20 Jan 18 12:33:12 e104462 kernel: [ 367.805392] [] intel_pmu_handle_irq+0x1ed/0x3f0 Jan 18 12:33:12 e104462 kernel: [ 367.805395] [] perf_event_nmi_handler+0x2b/0x50 Jan 18 12:33:12 e104462 kernel: [ 367.805397] [] nmi_handle.isra.2+0x88/0x180 Jan 18 12:33:12 e104462 kernel: [ 367.805399] [] do_nmi+0x1c9/0x3e0 Jan 18 12:33:12 e104462 kernel: [ 367.805400] [] nmi+0x5a/0xbf Jan 18 12:33:12 e104462 kernel: [ 367.805402] ---[ end trace 1511edbd209fafac ]--- followed a little later by Jan 18 12:33:33 e104462 kernel: [ 392.175012] BUG: soft lockup - CPU#1 stuck for 23s! [condvar_stress-:3380] Jan 18 12:33:33 e104462 kernel: [ 392.175014] Modules linked in: pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) bnep rfcomm bluetooth nfsd auth_rpcgss nfs_acl binfmt_misc nfs lockd sunrpc fscache dm_crypt snd_hda_codec_hdmi intel_rapl snd_hda_codec_realtek x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_intel snd_hda_codec kvm pl2303 usbserial snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul snd_page_alloc snd_seq_midi sn
[Kernel-packages] [Bug 1536867] Re: linux: 4.2.0-27.32 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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/1536867 Title: linux: 4.2.0-27.32 -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 verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Confirmed Bug description: This bug is for tracking the 4.2.0-27.32 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 kernel-stable-Prepare-package-start:Friday, 22. January 2016 02:11 UTC kernel-stable-Prepare-package-end:Friday, 22. January 2016 14:56 UTC kernel-stable-Promote-to-proposed-start:Friday, 22. January 2016 14:56 UTC kernel-stable-Promote-to-proposed-end:Friday, 22. January 2016 19:26 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Friday, 22. January 2016 21:02 UTC kernel-stable-Verification-testing-start:Friday, 22. January 2016 21:02 UTC kernel-stable-Certification-testing-start:Friday, 22. January 2016 21:02 UTC kernel-stable-Security-signoff-start:Friday, 22. January 2016 21:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Friday, 22. January 2016 21:03 UTC kernel-stable-Security-signoff-end:Saturday, 23. January 2016 00:01 UTC kernel-stable-Regression-testing-end:Monday, 25. January 2016 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1536867/+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 1536149] Re: linux-lts-utopic: 3.16.0-60.80~14.04.1 -proposed tracker
network configuration issue (wrong proxy setup) caused lxc tests to fail. Ignoring these failures. ** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1536149 Title: linux-lts-utopic: 3.16.0-60.80~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: Fix Released 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: In Progress Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-utopic source package in Trusty: New Bug description: This bug is for tracking the 3.16.0-60.80~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 kernel-stable-Prepare-package-start:Wednesday, 20. January 2016 11:41 UTC kernel-stable-Prepare-package-end:Wednesday, 20. January 2016 22:02 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. January 2016 22:02 UTC kernel-stable-Promote-to-proposed-end:Thursday, 21. January 2016 21:02 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Friday, 22. January 2016 19:24 UTC kernel-stable-Verification-testing-start:Friday, 22. January 2016 19:24 UTC kernel-stable-Certification-testing-start:Friday, 22. January 2016 19:24 UTC kernel-stable-Security-signoff-start:Friday, 22. January 2016 19:24 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Friday, 22. January 2016 19:24 UTC kernel-stable-Security-signoff-end:Saturday, 23. January 2016 00:00 UTC kernel-stable-Certification-testing-end:Wednesday, 27. January 2016 12:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1536149/+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 1535880] Re: linux: 3.13.0-77.121 -proposed tracker
network configuration issue (wrong proxy setup) caused lxc tests to fail. Ignoring these failures. ** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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/1535880 Title: linux: 3.13.0-77.121 -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: Fix Released 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: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-77.121 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 kernel-stable-Prepare-package-start:Tuesday, 19. January 2016 19:59 UTC kernel-stable-Prepare-package-end:Wednesday, 20. January 2016 17:22 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 20. January 2016 17:22 UTC kernel-stable-Promote-to-proposed-end:Thursday, 21. January 2016 15:01 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 21. January 2016 16:01 UTC kernel-stable-Verification-testing-start:Thursday, 21. January 2016 16:01 UTC kernel-stable-Certification-testing-start:Thursday, 21. January 2016 16:01 UTC kernel-stable-Security-signoff-start:Thursday, 21. January 2016 16:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 21. January 2016 16:02 UTC kernel-stable-Security-signoff-end:Friday, 22. January 2016 19:24 UTC kernel-stable-Certification-testing-end:Tuesday, 26. January 2016 11:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1535880/+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 1536867] onibi (i386) - tests ran: 167, failed: 0
tests ran: 167, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-27.32/onibi__4.2.0-27.32__2016-01-29_07-35-00/results-index.html -- 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/1536867 Title: linux: 4.2.0-27.32 -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 verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Wily: Confirmed Bug description: This bug is for tracking the 4.2.0-27.32 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 kernel-stable-Prepare-package-start:Friday, 22. January 2016 02:11 UTC kernel-stable-Prepare-package-end:Friday, 22. January 2016 14:56 UTC kernel-stable-Promote-to-proposed-start:Friday, 22. January 2016 14:56 UTC kernel-stable-Promote-to-proposed-end:Friday, 22. January 2016 19:26 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Friday, 22. January 2016 21:02 UTC kernel-stable-Verification-testing-start:Friday, 22. January 2016 21:02 UTC kernel-stable-Certification-testing-start:Friday, 22. January 2016 21:02 UTC kernel-stable-Security-signoff-start:Friday, 22. January 2016 21:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Friday, 22. January 2016 21:03 UTC kernel-stable-Security-signoff-end:Saturday, 23. January 2016 00:01 UTC kernel-stable-Regression-testing-end:Monday, 25. January 2016 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1536867/+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 1537013] Re: linux-lts-vivid: 3.19.0-49.55~14.04.1 -proposed tracker
network configuration issue (wrong proxy setup) caused lxc tests to fail. Ignoring these failures. ** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- 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/1537013 Title: linux-lts-vivid: 3.19.0-49.55~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: In Progress 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-49.55~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 kernel-stable-Prepare-package-start:Friday, 22. January 2016 10:41 UTC kernel-stable-master-bug:1536775 kernel-stable-Prepare-package-end:Friday, 22. January 2016 22:57 UTC kernel-stable-Promote-to-proposed-start:Friday, 22. January 2016 22:57 UTC kernel-stable-Promote-to-proposed-end:Monday, 25. January 2016 20:47 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Monday, 25. January 2016 22:01 UTC kernel-stable-Verification-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Certification-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Security-signoff-start:Monday, 25. January 2016 22:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Monday, 25. January 2016 22:01 UTC kernel-stable-Security-signoff-end:Tuesday, 26. January 2016 09:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1537013/+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 1538449] Re: CVE-2016-2070
** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux (Ubuntu Wily) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-mako (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-goldfish (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-flo (Ubuntu Vivid) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1538449 Title: CVE-2016-2070 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-lts-wily source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Invalid Status in linux-armadaxp source package in Vivid: Invalid Status in li
[Kernel-packages] [Bug 1486180] Comment bridged from LTC Bugzilla
--- Comment From shriy...@in.ibm.com 2016-01-29 04:46 EDT--- Also verified the same on Ubuntu 14.04.04 uname : 4.2.0-27-generic Call trace is not 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/1486180 Title: Kernel OOPS during DLPAR operation with Fibre Channel adapter Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: -- Problem Description -- Kernel OOPS during DLPAR operation with Fibre Channel adapter ---uname output--- 4.1.0-1-generic ---Additional Hardware Info--- Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 15.10 on a Power VM LPAR. 2) Configure and start rtas_errd daemon 3) Via HMC try to add a Fibre channel adapter via dynamic partitioning During the operation following OOPS message is observed Oops output: !!! 00E0806 Fcode, Copyright (c) 2000-2012 Emulex !!! Version 3.10x2 !!! 00E0806 Fcode, Copyright (c) 2000-2012 Emulex !!! Version 3.10x2 [ 8696.808703] PCI host bridge /pci@8002020 ranges: [ 8696.808708] MEM 0x0003ff84..0x0003ff847eff -> 0x8000 [ 8696.808716] PCI: I/O resource not set for host bridge /pci@8002020 (domain 1) [ 8696.808761] PCI host bridge to bus 0001:01 [ 8696.808765] pci_bus 0001:01: root bus resource [mem 0x3ff84-0x3ff847eff] (bus address [0x8000-0xfeff]) [ 8696.808768] pci_bus 0001:01: root bus resource [bus 01-ff] [ 8696.897390] rpaphp: Slot [U78C7.001.RCH0042-P1-C8] registered [ 8696.897395] rpadlpar_io: slot PHB 32 added [ 8696.972155] Emulex LightPulse Fibre Channel SCSI driver 10.5.0.0. [ 8696.972157] Copyright(c) 2004-2015 Emulex. All rights reserved. [ 8696.972438] lpfc 0001:01:00.1: enabling device (0140 -> 0142) [ 8696.976145] Unable to handle kernel paging request for data at address 0x000c [ 8696.976174] Faulting instruction address: 0xc0084cc4 [ 8696.976182] Oops: Kernel access of bad area, sig: 11 [#1] [ 8696.976188] SMP NR_CPUS=2048 NUMA pSeries [ 8696.976196] Modules linked in: lpfc(+) scsi_transport_fc rpadlpar_io rpaphp rtc_generic pseries_rng autofs4 [ 8696.976220] CPU: 3 PID: 1426 Comm: systemd-udevd Not tainted 4.1.0-1-generic #1~dogfoodv1-Ubuntu [ 8696.976230] task: c003857737e0 ti: c000fd08c000 task.ti: c000fd08c000 [ 8696.976239] NIP: c0084cc4 LR: c0084ca8 CTR: [ 8696.976247] REGS: c000fd08f0f0 TRAP: 0300 Not tainted (4.1.0-1-generic) [ 8696.976255] MSR: 80019033 CR: 8222 XER: 2000 [ 8696.976278] CFAR: c0008468 DAR: 000c DSISR: 4000 SOFTE: 1 GPR00: c0084ca8 c000fd08f370 c14bda00 GPR04: 0001 c000fd08f408 0003 d2c31e60 GPR08: c13bda00 c003873e6b80 d2ca7c98 GPR12: 8800 ce831b00 d29421f8 38ca4522 GPR16: c000fd08fdc0 c000fd08fe04 d2941878 c000fc8054c0 GPR20: d238 d238 d2ccff90 GPR24: c165074c c0038e17e000 c13b5e00 c0038e17e000 GPR28: c13b5e28 ca590600 c13b5df0 c13b5e20 [ 8696.976396] NIP [c0084cc4] enable_ddw+0x254/0x7b0 [ 8696.976405] LR [c0084ca8] enable_ddw+0x238/0x7b0 [ 8696.976411] Call Trace: [ 8696.976419] [c000fd08f370] [c0084ca8] enable_ddw+0x238/0x7b0 (unreliable) [ 8696.976431] [c000fd08f4b0] [c00866d8] dma_set_mask_pSeriesLP+0x218/0x2a0 [ 8696.976444] [c000fd08f540] [c0023528] dma_set_mask+0x58/0xa0 [ 8696.976474] [c000fd08f570] [d2c71280] lpfc_pci_probe_one+0xb0/0xc50 [lpfc] [ 8696.976486] [c000fd08f610] [c05987fc] local_pci_probe+0x6c/0x140 [ 8696.976497] [c000fd08f6a0] [c0598a28] pci_device_probe+0x158/0x1e0 [ 8696.976510] [c000fd08f700] [c067b744] driver_probe_device+0x1c4/0x5a0 [ 8696.976522] [c000fd08f790] [c067bcdc] __driver_attach+0x11c/0x120 [ 8696.976533] [c000fd08f7d0] [c067854c] bus_for_each_dev+0x9c/0x110 [ 8696.976544] [c000fd08f820] [c067adbc] driver_attach+0x3c/0x60 [ 8696.976555] [c000fd08f850] [c067a768] bus_add_driver+0x208/0x320 [ 8696.976565] [c000fd08f8e0] [c067c99c] driver_register+0x9c/0x180 [ 8696.976576] [c000fd08f950] [c05978ec] __pci_register_driv
[Kernel-packages] [Bug 1538428] Re: CVE-2016-2053
** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-mako (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-goldfish (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-flo (Ubuntu Vivid) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1538428 Title: CVE-2016-2053 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: New Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source pac
[Kernel-packages] [Bug 1526958] Re: CVE-2015-8569
** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1526958 Title: CVE-2015-8569 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in V
[Kernel-packages] [Bug 1530407] Re: CVE-2015-8575
** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1530407 Title: CVE-2015-8575 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in V
[Kernel-packages] [Bug 1538425] Re: CVE-2015-8785
** Changed in: linux (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1538425 Title: CVE-2015-8785 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in
[Kernel-packages] [Bug 1539001] Re: CVE-2015-8787
** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-wily (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-manta (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux-raspi2 (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux-mako (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-goldfish (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-flo (Ubuntu Vivid) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1539001 Title: CVE-2015-8787 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp
[Kernel-packages] [Bug 1530400] Re: CVE-2015-7550
** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1530400 Title: CVE-2015-7550 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: New Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: New Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: New Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: New Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: New Status in linux-raspi2 source package in Vivid: Invalid Status in linux-ti-omap4 source pack
[Kernel-packages] [Bug 1492934]
Created attachment 7386 Here's my Xorg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492934 Title: Kernel sometimes won't boot to login screen Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-nouveau package in Mandriva: Confirmed Bug description: I'm using 3.19.0-26-generic as kernel. Ubuntu version is: Description: Ubuntu 15.04 Release: 15.04 Version of the nouveau driver is: Installed: 1:1.0.11-1ubuntu2build1 Candidate:1:1.0.11-1ubuntu2build1 Version table: *** 1:1.0.11-1ubuntu2build1 0 500 http://ftp.acc.umu.se/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status I expected the module to be able to work without freezing the entire system. This issue prevents me from getting to the login session. I have installed Ubuntu on my brand new laptop which is a Asus N550JK. It has Hybrid Graphics (Intel 4th Generation + nVidia GeForce GTX 850M so I was told to nvidia-prime for Optimus. Sometimes when I boot the kernel it stops before I see the login window and the computer is completely frozen. However if I switch to the proprietary driver for nouveau the computer doesn't lock completely anymore. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 7 09:19:38 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-26-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-26-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] InstallationDate: Installed on 2015-09-05 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed root=UUID=28c2cc37-e8b5-4f1d-8a4a-33f26e77b390 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UdevLog: Error: [Errno 2] Filen eller katalogen finns inte: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK 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.:bvrN550JK.208:bd09/26/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Sep 7 09:16:28 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: intel(G1): [drm] failed to set drm interface version: Permission denied [13]. intel(G1): Failed to claim DRM device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16971 vendor SDC xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.la
[Kernel-packages] [Bug 1525570] Re: CVE-2015-8543
** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1525570 Title: CVE-2015-8543 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-lts-wily source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-raspi2 source package in V