[Kernel-packages] [Bug 1516733] Re: linux: 3.13.0-70.113 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- 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/1516733 Title: linux: 3.13.0-70.113 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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 package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.13.0-70.113 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:Monday, 16. November 2015 17:55 UTC kernel-stable-Prepare-package-end:Tuesday, 17. November 2015 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 17. November 2015 01:04 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 17. November 2015 16:54 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 17. November 2015 18:01 UTC kernel-stable-Verification-testing-start:Tuesday, 17. November 2015 18:01 UTC kernel-stable-Certification-testing-start:Tuesday, 17. November 2015 18:01 UTC kernel-stable-Security-signoff-start:Tuesday, 17. November 2015 18:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 17. November 2015 18:01 UTC kernel-stable-Security-signoff-end:Wednesday, 18. November 2015 09:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1516733/+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 1516943] Re: linux-lts-utopic: 3.16.0-55.74~14.04.1 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- 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/1516943 Title: linux-lts-utopic: 3.16.0-55.74~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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-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-55.74~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:Tuesday, 17. November 2015 09:42 UTC kernel-stable-Prepare-package-end:Tuesday, 17. November 2015 19:02 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 17. November 2015 19:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 17. November 2015 19:43 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 17. November 2015 21:03 UTC kernel-stable-Verification-testing-start:Tuesday, 17. November 2015 21:03 UTC kernel-stable-Certification-testing-start:Tuesday, 17. November 2015 21:03 UTC kernel-stable-Security-signoff-start:Tuesday, 17. November 2015 21:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 17. November 2015 21:03 UTC kernel-stable-Security-signoff-end:Wednesday, 18. November 2015 09:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1516943/+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 1518855] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1518855 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/1518855 Title: Backport better suspend/resume function for pinctrl-cherryview Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On some platforms the touchpad relies on pinctrl devices to provide GPIO interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and will lose the config after suspend/resume, then touchpad can't be used. [Fix] There's a commit in 4.0-rc1 to add suspend/resume for pinctrl-cherryview: commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e Refs: [HEAD] Author: Mika Westerberg Date: Thu Dec 4 12:32:50 2014 +0200 pinctrl: cherryview: Save and restore pin configs over system sle which can be clean cherry-picked [Test] 3.19.0-33 -> failed 4.2-> passed 4.0, 4.1 -> Can't suspend due to graphic driver failed so can't use to test 3.19.0-33 + patched module -> passed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1518855/+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 1518855] [NEW] Backport better suspend/resume function for pinctrl-cherryview
Public bug reported: [Impact] On some platforms the touchpad relies on pinctrl devices to provide GPIO interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and will lose the config after suspend/resume, then touchpad can't be used. [Fix] There's a commit in 4.0-rc1 to add suspend/resume for pinctrl-cherryview: commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e Refs: [HEAD] Author: Mika Westerberg Date: Thu Dec 4 12:32:50 2014 +0200 pinctrl: cherryview: Save and restore pin configs over system sle which can be clean cherry-picked [Test] 3.19.0-33 -> failed 4.2-> passed 4.0, 4.1 -> Can't suspend due to graphic driver failed so can't use to test 3.19.0-33 + patched module -> passed ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Phidias (phidias-chiang) Status: New ** Tags: 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/1518855 Title: Backport better suspend/resume function for pinctrl-cherryview Status in linux package in Ubuntu: New Bug description: [Impact] On some platforms the touchpad relies on pinctrl devices to provide GPIO interrupt, but in 3.19.0 pinctrl-cherryview doesn't support suspend well and will lose the config after suspend/resume, then touchpad can't be used. [Fix] There's a commit in 4.0-rc1 to add suspend/resume for pinctrl-cherryview: commit 9eb457b547cc731bc2fc251bd79891a60c64fc3e Refs: [HEAD] Author: Mika Westerberg Date: Thu Dec 4 12:32:50 2014 +0200 pinctrl: cherryview: Save and restore pin configs over system sle which can be clean cherry-picked [Test] 3.19.0-33 -> failed 4.2-> passed 4.0, 4.1 -> Can't suspend due to graphic driver failed so can't use to test 3.19.0-33 + patched module -> passed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518855/+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 1491484] Re: Anker keyboard doesn't send key events to krillin
Fixes landed with latest device tarball for krillin/vegetahd. ** Changed in: bluez (Ubuntu) Status: In Progress => Fix Released ** Changed in: canonical-devices-system-image Status: Confirmed => Fix Committed -- 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/1491484 Title: Anker keyboard doesn't send key events to krillin Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Fix Released Bug description: I have an Anker BT keyboard which seems to work fine on the Nexus 4 with Android, but when I use it with Krillin and Ubuntu it doesn't seem to receive keypresses. In fact I have used a hack boot.img to get it to even connect. The exact model is : http://www.amazon.co.uk /Compact-Wireless-Bluetooth-Keyboard- Rechargeable/dp/B00PIMRCFG/ref=sr_1_2?ie=UTF8&qid=1441209196&sr=8-2&keywords=anker+bluetooth+keyboard phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 114 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-02 08:01:15 version version: 114 version ubuntu: 20150902 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491484/+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 1398193] Re: The bluetooth headset can not control the video playback
First changes for this landed in the touch images but still a bit buggy. Needs further work. -- 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/1398193 Title: The bluetooth headset can not control the video playback Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Status in media-hub package in Ubuntu: Invalid Status in media-hub package in Ubuntu RTM: Invalid Bug description: [Preconditions] 1.The DUT pair with bluetooth headset [Procedures] 1.Play a video using the mediaplayer-app 2.Play/pause video by bluetooth headset [Expect results] The bluetooth headset can play/pause video [Actual results] The bluetooth headset can not control the video playback. [Reproduce] Always To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+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 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Released ** Changed in: ofono (Ubuntu) Status: In Progress => Fix Released ** Changed in: ofono (Ubuntu RTM) Status: Fix Committed => Fix Released ** Changed in: canonical-devices-system-image Status: Confirmed => Fix Committed -- 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/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Fix Released Status in ofono package in Ubuntu: Fix Released Status in ofono package in Ubuntu RTM: Fix Released Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+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 1390532] Re: [Bluetooth] Attempt to pair using default pin of 0000 before prompting the user
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Released ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Fix Committed ** Changed in: canonical-devices-system-image 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/1390532 Title: [Bluetooth] Attempt to pair using default pin of before prompting the user Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: Per the design at https://wiki.ubuntu.com/Bluetooth#phone If the device is of a type that usually has the PIN “” (a headset, keyboard, or mouse), Ubuntu should try this first. If that doesn’t work, or for any other kind of device, a ‘PIN for “{headset name}”’ or ‘Passkey for “{headset name}”’ dialog should appear, with a PIN/passkey field that uses a number-based keyboard. It is not clear whether the input field should still display To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390532/+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 1499789] Re: BLUEZ5: Connecting a keyboard shows no pin popup
** Changed in: bluez (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/1499789 Title: BLUEZ5: Connecting a keyboard shows no pin popup Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Fix Released Bug description: You can not connect to a pin required keyboard as the dialogue is not shown. This means that the device for all intents and purposes looks to be connected, but if you disconnect from it you can not reconnect and the device doesn't actually type anything because although it looks connected it actually isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1499789/+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 1492764] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)
Update :- After using Kernel 3.19 for a while I received a Kernel Update to Kernel 4.2 Now I am running kernel 4.2.0-18-generic Now everything seems to work. I have the same hardware as Benedikt . Lenovo z50-70 Laptop. I am running Ubuntu 15.10. I have had no success with Kernel 4.3. Now with Kernel 4.2.0-18-generic all seems to work. May I request all to check out this Kernel Update and see if it fixes issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492764 Title: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Status in linux package in Ubuntu: Incomplete Bug description: System: Kubuntu 15.10 Since kernel version 4.2 I have a few of this errors: Sep 06 16:16:35 benediktZ50-70 kernel: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Sep 06 16:16:35 benediktZ50-70 kernel: [ cut here ] Sep 06 16:16:35 benediktZ50-70 kernel: WARNING: CPU: 0 PID: 187 at /build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 check_crtc_state+0x2c5/0x440 [i915]() Sep 06 16:16:35 benediktZ50-70 kernel: pipe state doesn't match! Sep 06 16:16:35 benediktZ50-70 kernel: Modules linked in: rtsx_usb_sdmmc rtsx_usb i915 i2c_algo_bit drm_kms_helper psmouse ahci drm libahci r8169 mii sdhci_acpi video sdhci i2c_hid hid Sep 06 16:16:35 benediktZ50-70 kernel: CPU: 0 PID: 187 Comm: plymouthd Tainted: GW 4.2.0-7-generic #7-Ubuntu Sep 06 16:16:35 benediktZ50-70 kernel: Hardware name: LENOVO 20354/Lancer 5A5, BIOS 9BCN91WW 07/21/2015 Sep 06 16:16:35 benediktZ50-70 kernel: c023f1e8 8802413277e8 817b0465 Sep 06 16:16:35 benediktZ50-70 kernel: 880241327838 880241327828 81076536 880241327858 Sep 06 16:16:35 benediktZ50-70 kernel: 8802413278c0 880241152000 0001 880241152350 Sep 06 16:16:35 benediktZ50-70 kernel: Call Trace: Sep 06 16:16:35 benediktZ50-70 kernel: [] dump_stack+0x45/0x57 Sep 06 16:16:35 benediktZ50-70 kernel: [] warn_slowpath_common+0x86/0xc0 Sep 06 16:16:35 benediktZ50-70 kernel: [] warn_slowpath_fmt+0x46/0x50 Sep 06 16:16:35 benediktZ50-70 kernel: [] ? intel_pipe_config_compare+0xb31/0xc60 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] check_crtc_state+0x2c5/0x440 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] intel_modeset_check_state+0x20e/0x6b0 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] intel_crtc_set_config+0x4c7/0x580 [i915] Sep 06 16:16:35 benediktZ50-70 kernel: [] ? drm_mode_create+0x25/0x60 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_mode_set_config_internal+0x66/0x100 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_mode_setcrtc+0x3a8/0x4c0 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] drm_ioctl+0x125/0x610 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] Sep 06 16:16:35 benediktZ50-70 kernel: [] do_vfs_ioctl+0x285/0x470 Sep 06 16:16:35 benediktZ50-70 kernel: [] ? do_munmap+0x349/0x480 Sep 06 16:16:35 benediktZ50-70 kernel: [] SyS_ioctl+0x79/0x90 Sep 06 16:16:35 benediktZ50-70 kernel: [] entry_SYSCALL_64_fastpath+0x16/0x75 Sep 06 16:16:35 benediktZ50-70 kernel: ---[ end trace 724377a3c01e4270 ]--- I will check next week if these errors have any impact on my system. This is a Nvidia Optimus System with the Intel graphic card activated by default. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-7-generic 4.2.0-7.7 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benedikt 1550 F pulseaudio /dev/snd/controlC1: benedikt 1550 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 6 16:22:48 2015 HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf InstallationDate: Installed on 2014-12-21 (259 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141218) MachineType: LENOVO 20354 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-7-generic N/A linux-backports-modules-4.2.0-7-generic N/A linux-firmware 1.147 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN91WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.t
[Kernel-packages] [Bug 1330076] Re: USB modem cannot be used if removed then reattached
[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/1330076 Title: USB modem cannot be used if removed then reattached Status in linux package in Ubuntu: Expired Bug description: The problem is produced as follows: * Attach the USB modem to the laptop * Connect to the internet using the modem * Disconnect from the internet * Remove USB modem * Attach USB modem It doesn't get detected by the system, and I get kernel oops, [26528.139666] BUG: unable to handle kernel NULL pointer dereference at 0068 [26528.139753] IP: [] usb_wwan_write+0x12f/0x2e0 [usb_wwan] [26528.139809] PGD 658b4067 PUD 65e7b067 PMD 0 [26528.139844] Oops: [#1] SMP [26528.139871] Modules linked in: ctr ccm ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables ppp_deflate bsd_comp ppp_async crc_ccitt cryptoloop nls_utf8 isofs pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) cuse huawei_cdc_ncm cdc_wdm cdc_ncm usbnet option usb_wwan mii usbserial rfcomm bnep nfsd auth_rpcgss nfs_acl binfmt_misc nfs lockd sunrpc fscache btusb bluetooth snd_hda_codec_hdmi snd_hda_codec_idt usb_storage gpio_ich dell_wmi sparse_keymap dell_laptop dcdbas arc4 coretemp kvm_intel snd_hda_intel kvm snd_hda_codec snd_hwdep snd_pcm pcmcia snd_page_alloc pcspkr snd_seq_midi snd_seq_midi_event snd_rawmidi joydev b43 serio_raw bcma mac80211 snd_seq cfg80211 snd_seq_device snd_timer yenta_socket pcmcia_rsrc pcmcia_core lpc_ich snd soundcore mac_hid wmi parport_pc ppdev lp parport i915 video drm_kms_helper drm i2c_algo_bit hid_generic usbhid hid psmouse firewire_ohci tg3 sdhci_pci ahci sdhci libahci firewi re_core crc_itu_t ptp pps_core ssb [26528.142710] CPU: 0 PID: 938 Comm: ModemManager Tainted: GF O 3.13.0-29-generic #53-Ubuntu [26528.143497] Hardware name: Dell Inc. Latitude E5500 /0DW634, BIOS A11 04/15/2009 [26528.143497] task: 8800753147d0 ti: 880065a02000 task.ti: 880065a02000 [26528.143497] RIP: 0010:[] [] usb_wwan_write+0x12f/0x2e0 [usb_wwan] [26528.143497] RSP: 0018:880065a03d58 EFLAGS: 00010283 [26528.143497] RAX: RBX: 0001 RCX: 0001 [26528.143497] RDX: RSI: 00220020 RDI: 0202 [26528.143497] RBP: 880065a03dd0 R08: R09: [26528.143497] R10: 88007a401500 R11: 0293 R12: 1000 [26528.143497] R13: R14: R15: 880064eb3500 [26528.143497] FS: 7fddcb75a840() GS:88007d00() knlGS: [26528.143497] CS: 0010 DS: ES: CR0: 80050033 [26528.143497] CR2: 0068 CR3: 65892000 CR4: 07f0 [26528.143497] Stack: [26528.143497] 8800069762e8 880064eb3500 00018144d209 880064eb3590 [26528.143497] dead00100100 880006976000 1c0465e6aa28 880065e68000 [26528.143497] 880064eb3580 88004ee492e0 88004ebdbc00 880006976000 [26528.143497] Call Trace: [26528.143497] [] serial_write+0x4d/0xb0 [usbserial] [26528.143497] [] n_tty_write+0x32d/0x500 [26528.143497] [] ? wake_up_state+0x20/0x20 [26528.143497] [] tty_write+0x148/0x2a0 [26528.143497] [] ? process_echoes+0x70/0x70 [26528.143497] [] vfs_write+0xb4/0x1f0 [26528.143497] [] SyS_write+0x49/0xa0 [26528.143497] [] tracesys+0xe1/0xe6 [26528.143497] Code: 04 0f 85 28 01 00 00 48 8b 45 b0 48 8b 00 48 8b 78 10 e8 55 4b f6 e0 85 c0 0f 88 bd 00 00 00 81 fb 00 10 00 00 41 bc 00 10 00 00 <49> 8b 7d 68 44 0f 4e e3 48 8b 75 c0 49 63 c4 48 89 c2 48 89 45 [26528.143497] RIP [] usb_wwan_write+0x12f/0x2e0 [usb_wwan] [26528.143497] RSP [26528.143497] CR2: 0068 [26528.212077] ---[ end trace 8b88787e2b327dca ]--- [26528.238437] option1 ttyUSB0: option_instat_callback: error -108 [26528.238629] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [26528.238651] option 2-1:1.0: device disconnected [26528.240035] option1 ttyUSB1: option_instat_callback: error -108 This time I got the following usb_modeswitch error, then when I removed/reattached the modem I got the kernel oops: [26402.536135] usb 2-1: new high-speed USB device number 16 using ehci-pci [26403.068210] usb 2-1: device not accepting address 16, error -71 [26403.180050] usb 2-1: new high-speed USB device number 17 using ehci-pci [26403.304270] usb 2-1: device descriptor read/64, error -71 [26403.944211] usb 2-1: device not accepting address 17, error -71 [26404.060139] usb 2-1: new high-speed USB device number 18 using ehci-pci
[Kernel-packages] [Bug 1467376] Re: Stuttering looping sound when not touching mouse/keyboard
[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/1467376 Title: Stuttering looping sound when not touching mouse/keyboard Status in linux package in Ubuntu: Expired Bug description: When not touching mouse and keyboard audio stuttering appears. Stuttering appears when CPU load become slow down. In task manager i have seen normal cpu load approx 20-30 % and 3% when audio stuttering comes. When did not touch keyboard and mouse audio stuttering appears at 4 or 8 or 2 sec. and continues 4 - 5 sec. and this effect looping. I have tried kernells: 3.19.0-15; 3.19.0-21; 4.1.0-040100rc8. Sound cards recognized by the system: 00:07.0 Audio device [0403]: NVIDIA Corporation MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio [10de:0774] (rev a1) Sound cards recognized by ALSA: 00:07.0 Audio device [0403]: NVIDIA Corporation MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio [10de:0774] (rev a1) Sound cards recognized by ALSA, and activated: 00:07.0 Audio device [0403]: NVIDIA Corporation MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio [10de:0774] (rev a1) 00-00: ALC662 rev1 Analog : ALC662 rev1 Analog : playback 1 : capture 1 00-01: ALC662 rev1 Digital : ALC662 rev1 Digital : playback 1 00-02: ALC662 rev1 Alt Analog : ALC662 rev1 Alt Analog : capture 1 00-03: HDMI 0 : HDMI 0 : playback 1 alsactl version 1.0.29 or 1.0.28 - same effect. 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux dmesg --level=err,warn: http://paste.debian.net/250409/ lspci http://paste.debian.net/250778/ lspci -vhttp://paste.debian.net/250779/ --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-21 (1 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: linux (not installed) Tags: vivid Uname: Linux 4.1.0-040100rc8-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1467376/+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 1496262] Re: [Samsung NP530U3B-A01IT] Random hangs / freezes
[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/1496262 Title: [Samsung NP530U3B-A01IT] Random hangs / freezes Status in linux package in Ubuntu: Expired Bug description: Since the latest kernel upgrade I'm experiencing random system freezes. Sadly I couldn't find debug informations ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic 3.19.0.29.28 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxxer 2482 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 16 09:15:01 2015 HibernationDevice: RESUME=UUID=eb9511be-fc9f-4d11-ab64-5a842aa39dad InstallationDate: Installed on 2015-04-04 (164 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 03XK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 530U3BI/530U4BI/530U4BH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr03XK:bd01/04/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3BI/530U4BI/530U4BH dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496262/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
Okay, PPA is ready: https://launchpad.net/~inaddy/+archive/ubuntu/lp1505564/+packages Please upgrade kernel to: linux-lts-vivid - 3.19.0-36.41~14.04.1hf00090138v20151122b1 By doing: $ sudo add-apt-repository ppa:inaddy/lp1505564 $ sudo apt-get update $ sudo apt-get install linux-image-3.19.0-36-generic linux-image-extra-3.19.0-36-generic linux-headers-3.19.0-36-generic And make sure packages are being installed from PPA. Then reboot server using the hotfixed kernel. I'm looking forward on hearing feedback if this kernel mitigated the issues. Cheers Rafael Tinoco -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1518816] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1518816 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/1518816 Title: xhci: Workaround to get Intel xHCI reset working more reliably Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: On all of Intel's shipping xHCI platforms, including both servers and clients, the controller can cause the shutdown process to hang. This is because existing Intel xHCI controllers require a delay of 1 mS,after setting the CMD_RESET bit in command register, before accessing any HC registers. This allows the HC to complete the reset operation and be ready for HC register access. Fix: Patch in 4.4-rc2 commit a5964396190d0c40dd549c23848c282fffa5d1f2 Author: Rajmohan Mani Date: Wed Nov 18 10:48:20 2015 +0200 xhci: Workaround to get Intel xHCI reset working more reliably Regression Potential: Just add a 1ms delay for xhci_reset, so regressions are very unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518816/+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 1518816] [NEW] xhci: Workaround to get Intel xHCI reset working more reliably
Public bug reported: SRU Justification: On all of Intel's shipping xHCI platforms, including both servers and clients, the controller can cause the shutdown process to hang. This is because existing Intel xHCI controllers require a delay of 1 mS,after setting the CMD_RESET bit in command register, before accessing any HC registers. This allows the HC to complete the reset operation and be ready for HC register access. Fix: Patch in 4.4-rc2 commit a5964396190d0c40dd549c23848c282fffa5d1f2 Author: Rajmohan Mani Date: Wed Nov 18 10:48:20 2015 +0200 xhci: Workaround to get Intel xHCI reset working more reliably Regression Potential: Just add a 1ms delay for xhci_reset, so regressions are very unlikely. ** 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/1518816 Title: xhci: Workaround to get Intel xHCI reset working more reliably Status in linux package in Ubuntu: New Bug description: SRU Justification: On all of Intel's shipping xHCI platforms, including both servers and clients, the controller can cause the shutdown process to hang. This is because existing Intel xHCI controllers require a delay of 1 mS,after setting the CMD_RESET bit in command register, before accessing any HC registers. This allows the HC to complete the reset operation and be ready for HC register access. Fix: Patch in 4.4-rc2 commit a5964396190d0c40dd549c23848c282fffa5d1f2 Author: Rajmohan Mani Date: Wed Nov 18 10:48:20 2015 +0200 xhci: Workaround to get Intel xHCI reset working more reliably Regression Potential: Just add a 1ms delay for xhci_reset, so regressions are very unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518816/+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 1478799] Re: bluetooth not working in 15.10
I have no sound, no connection to jambox, Blueman reports: Connection Failed: DBusFailedError: No such file or directory -- 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/1478799 Title: bluetooth not working in 15.10 Status in Linux: Unknown Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 15.10 Wily No bluetooth indicator visible. I can't activate bluetooth in the bluetooth system-settings. Bluetooth mouse not working (I can't pair it). syslog: Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Starting SDP server Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: DIS cannot start: GATT is disabled Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init deviceinfo plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init proximity plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init time plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init alert plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init thermometer plugin Jul 28 10:44:51 norbert-Aspire-5737Z NetworkManager[647]: VPN: loaded org.freedesktop.NetworkManager.pptp Jul 28 10:44:51 norbert-Aspire-5737Z NetworkManager[647]: DNS: loaded plugin dnsmasq Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Starting SDP server Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: DIS cannot start: GATT is disabled Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed to init deviceinfo plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed to init proximity plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed to init time plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed to init alert plugin Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed to init thermometer plugin Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Successfully called chroot(). Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Successfully dropped remaining capabilities. Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: No service file found in /etc/avahi/services. Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Network interface enumeration completed. Jul 28 10:44:51 norbert-Aspire-5737Z systemd[1]: Started Avahi mDNS/DNS-SD Stack. Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Registering HINFO record with values 'X86_64'/'LINUX'. Jul 28 10:44:51 norbert-Aspire-5737Z systemd[1]: Started Bluetooth service. hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:15:83:15:A3:0B ACL MTU: 672:4 SCO MTU: 48:1 DOWN RX bytes:445 acl:0 sco:0 events:15 errors:0 TX bytes:63 acl:0 sco:0 commands:15 errors:0 rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1478799/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
Hello Junien, Based on my previous feedbacks, I've created the following PPA: https://launchpad.net/~inaddy/+archive/ubuntu/lp1505564 With a Trusty HWE kernel (vivid) + 2 patches: nbd: Restructure debugging prints nbd: Fix timeout detection For you to use and provide me feedback. I've done minor tests and it looks like there are no regressions. Hopefully these patches will address the problem. If they do, I'll work on fixing Trusty, Vivid, Wily and Xenial. Cheers Rafael Tinoco PS: I'm still finishing kernel compilation and will copy packages to the PPA as soon as it is ready (it might take a few min/hours). -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1517726] Re: wireless card – Broadcom Corporation Device [14e4:43ec](BCM4356) needs firmware
** Changed in: hwe-next Status: New => Fix Committed ** Changed in: hwe-next Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1517726 Title: wireless card – Broadcom Corporation Device [14e4:43ec](BCM4356) needs firmware Status in HWE Next: Fix Committed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Trusty: Fix Committed Status in linux-firmware source package in Vivid: Fix Committed Status in linux-firmware source package in Wily: Fix Committed Status in linux-firmware source package in Xenial: Fix Released Bug description: Steps: 1. Install ubuntu linux vivid. 2. Log in system and check network interfaces. Actual result: No wireless network is available Expect result: Wireless network is available To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1517726/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
Testing patches I have attached above: inaddy@sf00090138trusty(~)$ sudo qemu-img create -f qcow2 -o preallocation=metadata ./test.qcow2 1G Formatting './test.qcow2', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 preallocation='metadata' lazy_refcounts=off inaddy@sf00090138trusty(~)$ sudo qemu-nbd --connect=/dev/nbd0 ./test.qcow2 [ 34.348125] nbd: registered device at major 43 [ 317.034493] nbd0: unknown partition table inaddy@sf00090138trusty(~)$ sudo fdisk /dev/nbd0 Device Boot Start End Blocks Id System /dev/nbd0p12048 2097151 1047552 83 Linux inaddy@sf00090138trusty(~)$ sudo mkfs.ext3 /dev/nbd0p1 inaddy@sf00090138trusty(~)$ sudo mkfs.ext3 /dev/nbd0p1 inaddy@sf00090138trusty(~)$ sudo mount /dev/nbd0p1 /mnt inaddy@sf00090138trusty(/mnt)$ dd if=/dev/zero of=./teste bs=1M count=256 oflag=direct 256+0 records in 256+0 records out 268435456 bytes (268 MB) copied, 1.15586 s, 232 MB/s Hopefully they won't cause any regression the PPA to be provided soon. -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1510570] Re: BLE pairing fail
I have been working with a Microsoft Designer Mouse (also a BLA device). I went to AskUbuntu to try to find out why I could not use it with Ubuntu 15.10. [I have a Microsoft Surface Pro3 and am using a home-built kernel but the kernel does not seem to affect this problem.] I have followed the instructions in comment #9 and find that the mouse works...for 10 minutes. Apparently each use of the mouse resets a 10-minute watchdog timer and the mouse is disconnected if ever this timer expires. It won't come back on its own. To reconnect it, you must "remove" the mouse using Blueman or the Gnome Bluetooth Manager (I use the former), search it out again, and set it up again. Usually this works the first time but sometimes you have to go through it again. Despite the fact that the mouse works it is reported as of type "unknown" or "All types." I have attached a chunk of syslog showing the full cycle. I removed the old and reconnected it at 19:19. I used the mouse for about 4 minutes and then turned it upside down at 19:23. It disconnected 10 minutes later at 19:33. This sequence is repeatable and invariant. Is this the right bug for this our should another be started? Thanks, Keith ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+attachment/4523863/+files/syslog -- 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/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
** Tags added: patch -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1515776] Re: 1002:68a0 After suspend-resume graphics are sluggish and input lags with displayport connected
Bug report: https://bugs.freedesktop.org/show_bug.cgi?id=93073 ** Bug watch added: freedesktop.org Bugzilla #93073 https://bugs.freedesktop.org/show_bug.cgi?id=93073 -- 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/1515776 Title: 1002:68a0 After suspend-resume graphics are sluggish and input lags with displayport connected Status in linux package in Ubuntu: Triaged Bug description: After resuming from suspend-to-ram, graphics on displayport connected Dell U2415 monitor are sluggish and input has lag. Examples: - transition from unity greeter login locked status to unlocked status: 6 seconds (normal 1 second) - transition from clicking dash and getting window: 2-3 seconds (normal <1 second) - starting gedit: 4 seconds (normal <1 second) - mouse lags, sometimes the pointer is still on the left side of the screen, while it should be on the right - input from keyboard lags, about 1-2 seconds (normal no lag) When unplugging the Displayport cable all lag is gone. When plugging displayport back in again lag is back, same as before. After a reboot, response of graphics and input is normal. So two options to get rid of the lag: unplug DP or reboot. Further investigation: Did a mainline kernel bisect: From 3.13.11-ckt27 (good) to v4.3-wily (bad) First bad is v4.0-rc1-vivid Did a kernel commit bisect: From 3.19 (good) to 4.0-rc1 (bad) first bad commit: [e55bca26188e45f209597abf986c87cc5a49894a] radeon/audio: enable DP audio Commit bisect log is attached WORKAROUND: radeon.audio=0 However, I'm not able to use audio over Displayport. 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-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michiel1788 F pulseaudio /dev/snd/controlC1: michiel1788 F pulseaudio CurrentDesktop: Unity Date: Thu Nov 12 22:08:27 2015 HibernationDevice: RESUME=UUID=d0de679a-8c90-4a25-a84a-8d3c25eb0a10 InstallationDate: Installed on 2015-10-31 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Hewlett-Packard HP EliteBook 8740w ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@wily/boot/vmlinuz-4.2.0-18-generic root=UUID=f16430cd-a447-4cf2-8f8b-ce233e03d462 ro rootflags=subvol=@wily quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.1 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: 07/07/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CAD Ver. F.50 dmi.board.name: 1520 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 33.31 dmi.chassis.asset.tag: CNU1152Q9W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CADVer.F.50:bd07/07/2014:svnHewlett-Packard:pnHPEliteBook8740w:pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.31:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8740w dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515776/+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 1255700] Re: [HP EliteBook 8740w] suspend/resume failure
In the initial report the parameter radeon.dpm=1 was used. However in newer kernels this setting is default, so dpm is enabled by default. Nevertheless tested latest kernel v4.3 with parameter radeon.dpm=0, no effect Also tested with parameter pcie_aspm=force and pcie_aspm=off, no effect pm-suspend with several combinations of quircks --quirk-s3-bios --quirk-vbe-post --quirk-vbemode-restore, no effect. -- 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/1255700 Title: [HP EliteBook 8740w] suspend/resume failure Status in linux package in Ubuntu: Incomplete Bug description: Put system in suspend. Quickly wake it up via sleep button on the keyboard. (within about 3 to 5 seconds) System goes on briefly (about 3 to 5 seconds), crashes and reboots. This crash happened with the lid closed all the time and a separate keyboard connected. This issue also happens with the lid open, but mostly I don't have a separate keyboard connected. In that case it will only wake up by pushing the power button. Lid opening doesn't trigger a wake, but I guess I will have to file a separate bug report for that. WORKAROUND: If I wait much longer (say a minute or longer) before waking the system, resume works perfectly. WORKAROUND: Press power button instead of suspend button. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michiel2740 F pulseaudio /dev/snd/controlC0: michiel2740 F pulseaudio Date: Wed Nov 27 22:04:05 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=9d9a11d9-b882-4b87-9926-e8da9e04d900 InstallationDate: Installed on 2013-10-27 (31 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.3 MachineType: Hewlett-Packard HP EliteBook 8740w MarkForUpload: True PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash radeon.dpm=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 SourcePackage: linux Title: [Hewlett-Packard HP EliteBook 8740w] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/13/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CAD Ver. F.22 dmi.board.name: 1520 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 33.31 dmi.chassis.asset.tag: CNU1152Q9W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CADVer.F.22:bd06/13/2012:svnHewlett-Packard:pnHPEliteBook8740w:pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.31:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8740w dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255700/+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 1515776] Re: 1002:68a0 After suspend-resume graphics are sluggish and input lags with displayport connected
Michiel Janssens, given you haven't heard anything on the list, feel free to post this bug to https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/Radeon . ** Description changed: - This bug could be related to 1412730 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412730 - - Description of the issue: - Booting up with displayport connected to Dell U2415 monitor, graphics and input is responsive, also after logging in. - However after resuming from suspend-to-ram, graphics are sluggish and input has lag. + After resuming from suspend-to-ram, graphics on displayport connected Dell U2415 monitor are sluggish and input has lag. Examples: - transition from unity greeter login locked status to unlocked status: 6 seconds (normal 1 second) - transition from clicking dash and getting window: 2-3 seconds (normal <1 second) - starting gedit: 4 seconds (normal <1 second) - mouse lags, sometimes the pointer is still on the left side of the screen, while it should be on the right - input from keyboard lags, about 1-2 seconds (normal no lag) - When unplugging the Displayport cable: - all lag is gone + When unplugging the Displayport cable all lag is gone. - When plugging displayport back in again: - lag is back, same as before + When plugging displayport back in again lag is back, same as before. - This issue only happens after suspend-resume. - After a reboot, response of graphics and input is normal - So two options to get rid of the lag: unplug DP or reboot. + After a reboot, response of graphics and input is normal. So two options + to get rid of the lag: unplug DP or reboot. Further investigation: Did a mainline kernel bisect: From 3.13.11-ckt27 (good) to v4.3-wily (bad) First bad is v4.0-rc1-vivid Did a kernel commit bisect: From 3.19 (good) to 4.0-rc1 (bad) first bad commit: [e55bca26188e45f209597abf986c87cc5a49894a] radeon/audio: enable DP audio Commit bisect log is attached - My daily baseline is 14.04.3 with HWE-Vivid. - But because in the current HWE-Vivid this issue isn't present I'm reporting it via Wily as you can see in the logs. - I repeated testing of last good and first bad kernels on both 14.04.3 with HWE-Vivid and 15.10. - Exactly the same behaviour. - I mention this because if this bug wont be fixed, it will still be there in the upcoming HWE-Wily also. - And if thats the case, I won't be able to suspend my laptop without this issue. + WORKAROUND: radeon.audio=0 + However, I'm not able to use audio over Displayport. 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-0ubuntu4 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: michiel1788 F pulseaudio - /dev/snd/controlC1: michiel1788 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: michiel1788 F pulseaudio + /dev/snd/controlC1: michiel1788 F pulseaudio CurrentDesktop: Unity Date: Thu Nov 12 22:08:27 2015 HibernationDevice: RESUME=UUID=d0de679a-8c90-4a25-a84a-8d3c25eb0a10 InstallationDate: Installed on 2015-10-31 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Hewlett-Packard HP EliteBook 8740w ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@wily/boot/vmlinuz-4.2.0-18-generic root=UUID=f16430cd-a447-4cf2-8f8b-ce233e03d462 ro rootflags=subvol=@wily quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.2.0-18-generic N/A - linux-backports-modules-4.2.0-18-generic N/A - linux-firmware1.149.1 + linux-restricted-modules-4.2.0-18-generic N/A + linux-backports-modules-4.2.0-18-generic N/A + linux-firmware1.149.1 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: 07/07/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CAD Ver. F.50 dmi.board.name: 1520 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 33.31 dmi.chassis.asset.tag: CNU1152Q9W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CADVer.F.50:bd07/07/2014:svnHewlett-Packard:pnHPEliteBook8740w:pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.31:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8740w dmi.sys.vendor: Hewlett-Packard -- 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/1515776 Title: 1002:68a0 After suspend-resume graphics are sluggish and input lags with displayport connected Status in linux package in Ubuntu: Triaged Bug de
[Kernel-packages] [Bug 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
** Patch added: "vivid-nbd-fix-timeout-detection.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+attachment/4523782/+files/vivid-nbd-fix-timeout-detection.patch -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1516370] Re: Vendor backlight on Lenovo Z580 having random hotkeys issues
Neale Upstone: >" This bug is with Lenovo vendor backlight" The bug is not with the Lenovo vendor backlight. It's either a bug in the linux kernel (likely), or a bug in the BIOS. >"The guidance on investigating backlight issues..." As is noticed in the guidance, it doesn't tell you to use it forever, but as a debugging step to see if that allows one to change the backlight if one is having an issue with it. This information tells developers where to look within the code to search for a bug depending on the outcome. Also, you don't need to advise on the contents of the article, given I've contributed towards it as per https://wiki.ubuntu.com/Kernel/Debugging/Backlight?action=info . Hence, could you please answer the question asked in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516370/comments/9 ? ** Tags added: needs-bisect regression-update -- 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/1516370 Title: Vendor backlight on Lenovo Z580 having random hotkeys issues Status in linux package in Ubuntu: Incomplete Bug description: I've taken a bold guess in the title of this bug. While investigating why on 14.04 LTS, I have working backlight on the latest 3.13 kernel, but not on the 3.16, I tried acpi_backlight=vendor. With default boot parameters, I just get /sys/class/backlight/intel_backlight/, and the backlight works correctly on 3.13, but does not change the brightness on 3.16 (the OSD does show that the hotkeys are trying to change the brightness). With acpi_backlight=vendor, I get both intel and /lenovo/. The key point for this bug report is what happens with the lenovo one: The hotkeys work and make the backlight change, but not consistently. Repeatedly using the hotkey to increase the brightness causes the level to increase, but then occasionally reset to zero (including resetting as shown in the OSD - i.e. the OSD is always showing the level that the backlight actually is). Occasionally the OSD shows the "enable touchpad" icon when pressing the increase brightness hotkey repeatedly. The same action also causes the wifi to enable/disable randomly. If I press the hotkey with pauses in between, things behave normally. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-67-generic 3.13.0-67.110 ProcVersionSignature: Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27 Uname: Linux 3.13.0-67-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neale 3106 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 15 11:16:55 2015 HibernationDevice: RESUME=UUID=1fd50851-1727-4432-a99c-d0be8aafc983 InstallationDate: Installed on 2013-10-23 (752 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO IdeaPad Z580 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-67-generic root=UUID=d66417de-a540-485b-b469-aabd51a8844b ro quiet splash acpi_backlight=vendor RelatedPackageVersions: linux-restricted-modules-3.13.0-67-generic N/A linux-backports-modules-3.13.0-67-generic N/A linux-firmware 1.127.18 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-03-17 (607 days ago) dmi.bios.date: 12/25/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 5FCN95WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z580 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr5FCN95WW:bd12/25/2012:svnLENOVO:pnIdeaPadZ580:pvrLenovoZ580:rvnLENOVO:rnLenovo:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoZ580: dmi.product.name: IdeaPad Z580 dmi.product.version: Lenovo Z580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516370/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
** Patch added: "vivid-nbd-restructure-debugging-prints.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+attachment/4523781/+files/vivid-nbd-restructure-debugging-prints.patch -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with: block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/+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 1424261] Re: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.
Jarl, as requested in #5, please provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date ** 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/1424261 Title: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card. Status in linux package in Ubuntu: Incomplete Bug description: Using a 64GB microSDXC card in a usb sd card reader gives wrong SD card size (32GB). When putting the same microSDXC card in a a SD adapter it correctly gives 64GB size. Hardware: sdCard: SanDisk Extreme microSDXC UHS-I (http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB) USB card reader: Kingston FCR-MRG2 (http://www.kingston.com/us/support/technical/products?model=fcr-mrg2) SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY) Here is the output from terminal: Accessing it through USB card reader: $ sudo fdisk -l /dev/sdb Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Accessing it through sd card adapter and the built-int sd card reader: $ sudo fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x My conclussion is that the driver for the usb card-reader. I will attach the output of lsusb -v -d 090c:6200 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-30-generic 3.16.0-30.40 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 4339 F pulseaudio CurrentDesktop: KDE Date: Sat Feb 21 21:27:53 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2 InstallationDate: Installed on 2013-11-27 (450 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU01143H6 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424261/+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 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
** Description changed: - Hi, + Some of our nova compute hosts regularly freeze, sometimes for a few + hours, with kern.log getting spammed with: - Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with : block nbdX: Attempted send on closed socket - and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : + and a few "CPU soft lockup" messages (see attached log). This clears up + when the queue gets cleared, eg : + block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. - - Note that timestamps from kern.log appears to be wrong, it looks like - the messages are being held, and then all delivered at once when the - kernel unfreezes. - - Attaching apport files from 2 hosts below. - --- - AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Oct 9 13:14 seq - crw-rw 1 root audio 116, 33 Oct 9 13:14 timer - AplayDevices: Error: [Errno 2] No such file or directory - ApportVersion: 2.14.1-0ubuntu3.15 - Architecture: amd64 - ArecordDevices: Error: [Errno 2] No such file or directory - AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: - DistroRelease: Ubuntu 14.04 - IwConfig: Error: [Errno 2] No such file or directory - MachineType: HP ProLiant DL385 G7 - Package: linux (not installed) - PciMultimedia: - - ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash - ProcFB: 0 radeondrmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=1bd039df-c419-4cb7-b1ad-fe004d55ccd4 ro console=tty0 console=ttyS1,38400 nosplash - ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 - RelatedPackageVersions: - linux-restricted-modules-3.19.0-30-generic N/A - linux-backports-modules-3.19.0-30-generic N/A - linux-firmware 1.127.15 - RfKill: Error: [Errno 2] No such file or directory - Tags: trusty uec-images - Uname: Linux 3.19.0-30-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: - - _MarkForUpload: True - dmi.bios.date: 12/08/2012 - dmi.bios.vendor: HP - dmi.bios.version: A18 - dmi.chassis.type: 23 - dmi.chassis.vendor: HP - dmi.modalias: dmi:bvnHP:bvrA18:bd12/08/2012:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: - dmi.product.name: ProLiant DL385 G7 - dmi.sys.vendor: HP - --- - AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Oct 9 12:37 seq - crw-rw 1 root audio 116, 33 Oct 9 12:37 timer - AplayDevices: Error: [Errno 2] No such file or directory - ApportVersion: 2.14.1-0ubuntu3.15 - Architecture: amd64 - ArecordDevices: Error: [Errno 2] No such file or directory - AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: - DistroRelease: Ubuntu 14.04 - IwConfig: Error: [Errno 2] No such file or directory - MachineType: HP ProLiant DL360p Gen8 - Package: linux (not installed) - PciMultimedia: - - ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash - ProcFB: 0 VESA VGA - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=f3c6cae8-09dc-4607-8675-c9123ea9c9fd ro console=tty0 console=ttyS1,38400 nosplash - ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 - RelatedPackageVersions: - linux-restricted-modules-3.19.0-30-generic N/A - linux-backports-modules-3.19.0-30-generic N/A - linux-firmware 1.127.15 - RfKill: Error: [Errno 2] No such file or directory - StagingDrivers: visorchannel visorutil - Tags: trusty uec-images staging - Uname: Linux 3.19.0-30-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: - - _MarkForUpload: True - dmi.bios.date: 11/14/2013 - dmi.bios.vendor: HP - dmi.bios.version: P71 - dmi.chassis.type: 23 - dmi.chassis.vendor: HP - dmi.modalias: dmi:bvnHP:bvrP71:bd11/14/2013:svnHP:pnProLiantDL360pGen8:pvr:cvnHP:ct23:cvr: - dmi.product.name: ProLiant DL360p Gen8 - dmi.sys.vendor: HP - --- - AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Oct 28 13:07 seq - crw-rw 1 root audio 116, 33 Oct 28 13:07 timer - AplayDevices: Error: [Errno 2] No such file or directory - ApportVersion: 2.14.1-0ubuntu3.16 - Architecture: amd64 - ArecordDevices: Error: [Errno 2] No such file or directory - AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: - DistroRelease: Ubuntu 14.04 - IwConfig: Error: [Errno 2] No such file or directory - MachineType: HP ProLiant DL360p Gen8 - Package: linux (not installed) - PciMultimedia: - - ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash - ProcFB: 0 VESA VGA - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=46ac2c1e-5f16-45bd-
[Kernel-packages] [Bug 1490130] Re: Elantech touchpad stops working after suspend
Wladimir Mutel, it will help immensely if you filed a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. -- 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/1490130 Title: Elantech touchpad stops working after suspend Status in linux package in Ubuntu: Incomplete Bug description: i have asus a455ld i5 5200u running kubuntu 15.04 with kernel 4.0.8-040008-generic. touchpad is recognized as elantech version 4. everything was fine until my notebook go to suspend and resume without touchpad working. I tried : modprobe -r psmouse modprobe psmouse it only work before suspend. execute those commands after resume from suspend is not working. the last thing i tried is this. when i use this command before suspend : insmod /lib/modules/4.0.8-040008-generic/kernel/drivers/input/mouse/psmouse.ko these appear in the dmesg: [ 820.207105] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x381f00) [ 820.70] psmouse serio1: elantech: Synaptics capabilities query result 0x10, 0x14, 0x0e. [ 820.294698] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input146 but when i use the command after suspend, there is nothing any output in the dmesg. i tried all ubuntu varian and opensuse 13.2 live usb, the result is the same. but in windows 10, touchpad still active after suspend. --- ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-20 (69 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: linux (not installed) Tags: vivid Uname: Linux 4.0.8-040008-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blackhole 1460 F pulseaudio /dev/snd/controlC1: blackhole 1460 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=668506c6-5b13-4a29-9c34-956c6c34a45a InstallationDate: Installed on 2015-06-20 (129 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X455LDB Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=4318cf1f-564c-47ff-8b0c-f3acf77aa34f ro quiet splash i915.enable_ips=0 vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X455LDB.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X455LDB 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.:bvrX455LDB.206:bd02/12/2015:svnASUSTeKCOMPUTERINC.:pnX455LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X455LDB 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/1490130/+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 1517882] Re: Excessive logging and problems with brcmsmac: bcma0:1: START: tid 1 is not agg'able
alphac, to clarify the Bug Description: + Are the disconnections intentional (you clicked to disconnect)? + Is the reconnection problem limited to one access point? + What is the access point manufacturer, model, and firmware version? + What wireless version are you using (G, N, etc.)? ** Tags added: kernel-bug-exists-upstream-4.3 ** Summary changed: - Excessive logging and problems with brcmsmac: bcma0:1: START: tid 1 is not agg'able + 14e4:4727 unable to reconnect to AP after disconnection ** Description changed: - Hello I have lots of logs with this message, like 15mb a day. Also the - module randomly loses ability to connect an AP after a disconnection, - the only resolution is a reboot, more than one if necessary. The latter - happens also with the proprietary Broadcom driver. - - brcmsmac bcma0:1: START: tid 1 is not agg'able + The module randomly loses ability to connect to an AP after a + disconnection, the only resolution is a reboot, more than one if + necessary. 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: USERPID ACCESS COMMAND /dev/snd/controlC0: alphac 1565 F pulseaudio CurrentDesktop: Unity Date: Thu Nov 19 13:36:22 2015 InstallationDate: Installed on 2015-09-05 (74 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 2232:1001 Silicon Motion Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. QX310/QX410/QX510/SF310/SF410/SF510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=7a190443-4e56-4ea8-98a8-296841ad7a95 ro quiet splash vt.handoff=7 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 SourcePackage: linux UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-31 (18 days ago) dmi.bios.date: 05/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 05MX.M008.20110525.SCY dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: QX310/QX410/QX510/SF310/SF410/SF510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 05MX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr05MX.M008.20110525.SCY:bd05/25/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnQX310/QX410/QX510/SF310/SF410/SF510:pvr05MX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnQX310/QX410/QX510/SF310/SF410/SF510:rvr05MX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: QX310/QX410/QX510/SF310/SF410/SF510 dmi.product.version: 05MX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. -- 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/1517882 Title: 14e4:4727 unable to reconnect to AP after disconnection Status in linux package in Ubuntu: Incomplete Bug description: The module randomly loses ability to connect to an AP after a disconnection, the only resolution is a reboot, more than one if necessary. 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: USERPID ACCESS COMMAND /dev/snd/controlC0: alphac 1565 F pulseaudio CurrentDesktop: Unity Date: Thu Nov 19 13:36:22 2015 InstallationDate: Installed on 2015-09-05 (74 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 2232:1001 Silicon Motion Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. QX310/QX410/QX510/SF310/SF410/SF510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=7a190443-4e56-4ea8-98a8-296841ad7a95 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-bac
[Kernel-packages] [Bug 1510134] Re: [Dell Latitude E5440] ALPS touchpad and buttons work only in a single window after resume from suspend.
** Tags added: xenial ** 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/1510134 Title: [Dell Latitude E5440] ALPS touchpad and buttons work only in a single window after resume from suspend. Status in linux package in Ubuntu: Confirmed Bug description: ALPS touchpad and buttons work only in a single window. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-31-generic 3.19.0-31.36 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jsum 1861 F pulseaudio /dev/snd/controlC1: jsum 1861 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 26 16:57:30 2015 HibernationDevice: RESUME=UUID=13c66e6a-58e2-431a-9f1b-15248ae2fbd0 InstallationDate: Installed on 2015-06-08 (140 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. MachineType: Dell Inc. Latitude E5440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-31-generic N/A linux-backports-modules-3.19.0-31-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 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/1510134/+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 1514052] Re: erratic fan speed and little control kernel 4.2
Yuriy Vidineev, you need to use the default Ubuntu kernel (not the third party mainline one). -- 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/1514052 Title: erratic fan speed and little control kernel 4.2 Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to Ubuntu 15.10 and almost immediately my CPU fan started speeding and slowing without good reason even when the PC is idle. I tried various things but then found that if I leave the computer off for a long time and let everything cool down then when I boot from cold the CPU fan is stable. To test my theory of cold start out I then ran sudo cpupower frequency-set -g powersave followed by sudo cpupower frequency-set -g ondemand The final mode is the initial mode. Almost immediately as soon as I moved to powersave mode the erratic fan speed started. It did not stop when I returned to ondemand. Temp fix for this behaviour is - go and have a cup of coffee and let the computer cool down when you restart: shutdown then start from cold. $ uname -a Linux HomeMegaUbuntu 4.2.0-17-generic #21-Ubuntu SMP Fri Oct 23 19:56:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.10 Release: 15.10 Codename: wily $ cpupower frequency-info analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.20 GHz - 2.80 GHz available frequency steps: 2.80 GHz, 2.80 GHz, 2.67 GHz, 2.53 GHz, 2.40 GHz, 2.27 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 GHz, 1.20 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.20 GHz and 2.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.20 GHz. cpufreq stats: 2.80 GHz:11.93%, 2.80 GHz:0.00%, 2.67 GHz:0.40%, 2.53 GHz:0.44%, 2.40 GHz:0.51%, 2.27 GHz:0.55%, 2.13 GHz:0.35%, 2.00 GHz:0.72%, 1.87 GHz:0.84%, 1.73 GHz:1.00%, 1.60 GHz:2.16%, 1.47 GHz:4.61%, 1.33 GHz:16.83%, 1.20 GHz:59.65% (29241) boost state support: Supported: yes Active: yes 25500 MHz max turbo 4 active cores 25500 MHz max turbo 3 active cores 25500 MHz max turbo 2 active cores 25500 MHz max turbo 1 active cores Tried intel_pstate but it is not supported for some reason on my machine ie the following does not work and I am left with driver: acpi-cpufreq GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=enable" Could not see ACPI Thermal Zones reported in dmesg $ dmesg | grep ACPI [0.00] BIOS-e820: [mem 0xbd78-0xbd78dfff] ACPI data [0.00] BIOS-e820: [mem 0xbd78e000-0xbd7c] ACPI NVS [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000F9B40 24 (v02 ACPIAM) [0.00] ACPI: XSDT 0xBD780100 6C (v01 DELL FX09 20101113 MSFT 0097) [0.00] ACPI: FACP 0xBD780290 F4 (v04 DELL FX09 20101113 MSFT 0097) [0.00] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 128/64 (20150619/tbfadt-623) [0.00] ACPI: DSDT 0xBD780660 005B02 (v02 1 1000 INTL 20051117) [0.00] ACPI: FACS 0xBD78E000 40 [0.00] ACPI: FACS 0xBD78E000 40 [0.00] ACPI: APIC 0xBD780390 8C (v02 DELL FX09 20101113 MSFT 0097) [0.00] ACPI: MCFG 0xBD780420 3C (v01 DELL OEMMCFG 20101113 MSFT 0097) [0.00] ACPI: SLIC 0xBD780460 000176 (v01 DELL FX09 20101113 MSFT 0097) [0.00] ACPI: OSFR 0xBD7805E0 80 (v01 DELL FX09 20101113 MSFT 0097) [0.00] ACPI: OEMB 0xBD78E040 72 (v01 DELL FX09 20101113 MSFT 0097) [0.00] ACPI: HPET 0xBD78A660 38 (v01 DELL OEMHPET 20101113 MSFT 0097) [0.00] ACPI: ASF! 0xBD78A6A0 99 (v32 LEGEND I865PASF 0001 INTL 20051117) [0.00] ACPI: SSDT 0xBD78F800 000363 (v01 DpgPmm CpuPm 0012 INTL 20051117) [0.00] ACPI: Local APIC address 0xfee0 [0.00] ACPI: PM-Timer IO Port: 0x808 [0.00] ACPI: Local APIC address 0xfee0 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] ACPI: IRQ0 used by override. [0.00] ACP
[Kernel-packages] [Bug 1515157] kili (amd64) - tests ran: 1, failed: 1
tests ran: 1, failed: 1; http://kernel.ubuntu.com/testing/4.2.0-19.23/kili__4.2.0-19.23__2015-11-22_18-09-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/1515157 Title: linux: 4.2.0-19.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-19.23 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, 11. November 2015 09:48 UTC kernel-stable-Prepare-package-end:Thursday, 12. November 2015 10:04 UTC kernel-stable-Promote-to-proposed-start:Thursday, 12. November 2015 10:04 UTC kernel-stable-Promote-to-proposed-end:Thursday, 12. November 2015 20:41 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 12. November 2015 22:03 UTC kernel-stable-Verification-testing-start:Thursday, 12. November 2015 22:03 UTC kernel-stable-Certification-testing-start:Thursday, 12. November 2015 22:03 UTC kernel-stable-Security-signoff-start:Thursday, 12. November 2015 22:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 12. November 2015 22:03 UTC kernel-stable-Security-signoff-end:Friday, 13. November 2015 09:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1515157/+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 1518767] 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/1518767 Title: Macbook Air 6.2 brightness buttons stopped working after 3.13.0-63 Status in linux package in Ubuntu: Confirmed Bug description: Buttons for brightness do not work after resume if kernels fresher than 3.13.0-63 are used (I tested with -65 ... -68, don't know about -64). If I reboot it with kernel -63, everything is back to normal. Any hints about this one? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-68-generic 3.13.0-68.111 ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bostjan2559 F pulseaudio /dev/snd/controlC0: bostjan2559 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 22 22:16:04 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-18 (553 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Apple Inc. MacBookAir6,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic.efi.signed root=UUID=13301a20-3c5b-4176-b193-c4a27d8b0910 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-68-generic N/A linux-backports-modules-3.13.0-68-generic N/A linux-firmware 1.127.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2014 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B09.1402071141 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B09.1402071141:bd02/07/2014:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.name: MacBookAir6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518767/+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 1518767] Re: Macbook Air 6.2 brightness buttons stopped working after 3.13.0-63
Also, doing this fixes the issue: sudo rmmod mba6x_bl sudo modprobe mba6x_bl -- 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/1518767 Title: Macbook Air 6.2 brightness buttons stopped working after 3.13.0-63 Status in linux package in Ubuntu: Confirmed Bug description: Buttons for brightness do not work after resume if kernels fresher than 3.13.0-63 are used (I tested with -65 ... -68, don't know about -64). If I reboot it with kernel -63, everything is back to normal. Any hints about this one? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-68-generic 3.13.0-68.111 ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bostjan2559 F pulseaudio /dev/snd/controlC0: bostjan2559 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 22 22:16:04 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-18 (553 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Apple Inc. MacBookAir6,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic.efi.signed root=UUID=13301a20-3c5b-4176-b193-c4a27d8b0910 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-68-generic N/A linux-backports-modules-3.13.0-68-generic N/A linux-firmware 1.127.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2014 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B09.1402071141 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B09.1402071141:bd02/07/2014:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.name: MacBookAir6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518767/+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 1518767] Re: Macbook Air 6.2 brightness buttons stopped working after 3.13.0-63
Additional info: the buttons themselves work as expected, I can see the brightness bar adjusting up/down, just brightness itself does not change and stays at 100%. -- 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/1518767 Title: Macbook Air 6.2 brightness buttons stopped working after 3.13.0-63 Status in linux package in Ubuntu: New Bug description: Buttons for brightness do not work after resume if kernels fresher than 3.13.0-63 are used (I tested with -65 ... -68, don't know about -64). If I reboot it with kernel -63, everything is back to normal. Any hints about this one? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-68-generic 3.13.0-68.111 ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bostjan2559 F pulseaudio /dev/snd/controlC0: bostjan2559 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 22 22:16:04 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-18 (553 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Apple Inc. MacBookAir6,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic.efi.signed root=UUID=13301a20-3c5b-4176-b193-c4a27d8b0910 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-68-generic N/A linux-backports-modules-3.13.0-68-generic N/A linux-firmware 1.127.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2014 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B09.1402071141 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B09.1402071141:bd02/07/2014:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.name: MacBookAir6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518767/+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 1518767] [NEW] Macbook Air 6.2 brightness buttons stopped working after 3.13.0-63
Public bug reported: Buttons for brightness do not work after resume if kernels fresher than 3.13.0-63 are used (I tested with -65 ... -68, don't know about -64). If I reboot it with kernel -63, everything is back to normal. Any hints about this one? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-68-generic 3.13.0-68.111 ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bostjan2559 F pulseaudio /dev/snd/controlC0: bostjan2559 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 22 22:16:04 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-18 (553 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Apple Inc. MacBookAir6,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic.efi.signed root=UUID=13301a20-3c5b-4176-b193-c4a27d8b0910 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-68-generic N/A linux-backports-modules-3.13.0-68-generic N/A linux-firmware 1.127.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2014 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B09.1402071141 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B09.1402071141:bd02/07/2014:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.name: MacBookAir6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** 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/1518767 Title: Macbook Air 6.2 brightness buttons stopped working after 3.13.0-63 Status in linux package in Ubuntu: New Bug description: Buttons for brightness do not work after resume if kernels fresher than 3.13.0-63 are used (I tested with -65 ... -68, don't know about -64). If I reboot it with kernel -63, everything is back to normal. Any hints about this one? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-68-generic 3.13.0-68.111 ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bostjan2559 F pulseaudio /dev/snd/controlC0: bostjan2559 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 22 22:16:04 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-05-18 (553 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Apple Inc. MacBookAir6,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic.efi.signed root=UUID=13301a20-3c5b-4176-b193-c4a27d8b0910 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-68-generic N/A linux-backports-modules-3.13.0-68-generic N/A linux-firmware 1.127.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2014 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B09.1402071141 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B09.1402071141:bd02/07/2014:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.name: MacBookAir6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518767/+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 1518737] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1518737 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/1518737 Title: can not re-enable touchpad Status in linux package in Ubuntu: Incomplete Bug description: I am running Ubuntu 15.10 (32-bit edition but I know it is also a problem on 64-bit edition) on an Acer Aspire 5738 laptop which has a physical button next to the touchpad that can toggle the device. When I hit the button a desktop notification appears, informing me that the device has been disabled (an icon of a touchpad with an x in the bottom-right-hand-corner) and I am no longer able to use the touchpad for anything, as expected. When I press the button again to re-enable the touchpad, a desktop notification appears, informing me that the device has been enabled (an icon of a touchpad with no x in the bottom-right-hand-corner) but the touchpad remains disabled, i.e I can use it for absolutely nothing. (clicking, scrolling, pointing, ...) Logging in and out or restarting the PC enables the touchpad, but I can also use modprobe to remove and insert psmouse module, which will also cause it to enable. When I use the button physically next to the touchpad to enable/disable the touchpad, it does not affect the toggle switch in the "Mouse and Touchpad" settings, but if I use that setting (the toggle switch) I can correctly enable and disable the touchpad. xinput lists the device under "Virtual core pointer" as an "AlpsPS/2 ALPS GlidePoint". BIOS is updated as of today. If I can be of help in patching the bug, I would love to, but I just have no idea where to look. I altered the psmouse kernel module to print information to the logs about various activity (resetting, deactivating) but none of it was very informative (again, I don't know where to look). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518737/+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 1518737] Re: can not re-enable touchpad
I am fairly certain this is a hardware / device driver bug and as such it does not originate in any repository package but in the kernel. ** 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/1518737 Title: can not re-enable touchpad Status in linux package in Ubuntu: New Bug description: I am running Ubuntu 15.10 (32-bit edition but I know it is also a problem on 64-bit edition) on an Acer Aspire 5738 laptop which has a physical button next to the touchpad that can toggle the device. When I hit the button a desktop notification appears, informing me that the device has been disabled (an icon of a touchpad with an x in the bottom-right-hand-corner) and I am no longer able to use the touchpad for anything, as expected. When I press the button again to re-enable the touchpad, a desktop notification appears, informing me that the device has been enabled (an icon of a touchpad with no x in the bottom-right-hand-corner) but the touchpad remains disabled, i.e I can use it for absolutely nothing. (clicking, scrolling, pointing, ...) Logging in and out or restarting the PC enables the touchpad, but I can also use modprobe to remove and insert psmouse module, which will also cause it to enable. When I use the button physically next to the touchpad to enable/disable the touchpad, it does not affect the toggle switch in the "Mouse and Touchpad" settings, but if I use that setting (the toggle switch) I can correctly enable and disable the touchpad. xinput lists the device under "Virtual core pointer" as an "AlpsPS/2 ALPS GlidePoint". BIOS is updated as of today. If I can be of help in patching the bug, I would love to, but I just have no idea where to look. I altered the psmouse kernel module to print information to the logs about various activity (resetting, deactivating) but none of it was very informative (again, I don't know where to look). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518737/+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 1515776] Re: 1002:68a0 After suspend-resume graphics are sluggish and input lags with displayport connected
Workaround: Adding kernel parameter radeon.audio=0 resolves the issue. However with that setting, not able to use audio over Displayport in that case off course -- 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/1515776 Title: 1002:68a0 After suspend-resume graphics are sluggish and input lags with displayport connected Status in linux package in Ubuntu: Triaged Bug description: This bug could be related to 1412730 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412730 Description of the issue: Booting up with displayport connected to Dell U2415 monitor, graphics and input is responsive, also after logging in. However after resuming from suspend-to-ram, graphics are sluggish and input has lag. Examples: - transition from unity greeter login locked status to unlocked status: 6 seconds (normal 1 second) - transition from clicking dash and getting window: 2-3 seconds (normal <1 second) - starting gedit: 4 seconds (normal <1 second) - mouse lags, sometimes the pointer is still on the left side of the screen, while it should be on the right - input from keyboard lags, about 1-2 seconds (normal no lag) When unplugging the Displayport cable: all lag is gone When plugging displayport back in again: lag is back, same as before This issue only happens after suspend-resume. After a reboot, response of graphics and input is normal So two options to get rid of the lag: unplug DP or reboot. Further investigation: Did a mainline kernel bisect: From 3.13.11-ckt27 (good) to v4.3-wily (bad) First bad is v4.0-rc1-vivid Did a kernel commit bisect: From 3.19 (good) to 4.0-rc1 (bad) first bad commit: [e55bca26188e45f209597abf986c87cc5a49894a] radeon/audio: enable DP audio Commit bisect log is attached My daily baseline is 14.04.3 with HWE-Vivid. But because in the current HWE-Vivid this issue isn't present I'm reporting it via Wily as you can see in the logs. I repeated testing of last good and first bad kernels on both 14.04.3 with HWE-Vivid and 15.10. Exactly the same behaviour. I mention this because if this bug wont be fixed, it will still be there in the upcoming HWE-Wily also. And if thats the case, I won't be able to suspend my laptop without this issue. 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-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michiel1788 F pulseaudio /dev/snd/controlC1: michiel1788 F pulseaudio CurrentDesktop: Unity Date: Thu Nov 12 22:08:27 2015 HibernationDevice: RESUME=UUID=d0de679a-8c90-4a25-a84a-8d3c25eb0a10 InstallationDate: Installed on 2015-10-31 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Hewlett-Packard HP EliteBook 8740w ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@wily/boot/vmlinuz-4.2.0-18-generic root=UUID=f16430cd-a447-4cf2-8f8b-ce233e03d462 ro rootflags=subvol=@wily quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.1 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: 07/07/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CAD Ver. F.50 dmi.board.name: 1520 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 33.31 dmi.chassis.asset.tag: CNU1152Q9W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CADVer.F.50:bd07/07/2014:svnHewlett-Packard:pnHPEliteBook8740w:pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.31:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8740w dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1515776/+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 1516370] Re: Vendor backlight on Lenovo Z580 having random hotkeys issues
I meant "If neither that" btw. I curse twitter because I cannot correct typos. Launchpad seems as painful. -- 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/1516370 Title: Vendor backlight on Lenovo Z580 having random hotkeys issues Status in linux package in Ubuntu: Incomplete Bug description: I've taken a bold guess in the title of this bug. While investigating why on 14.04 LTS, I have working backlight on the latest 3.13 kernel, but not on the 3.16, I tried acpi_backlight=vendor. With default boot parameters, I just get /sys/class/backlight/intel_backlight/, and the backlight works correctly on 3.13, but does not change the brightness on 3.16 (the OSD does show that the hotkeys are trying to change the brightness). With acpi_backlight=vendor, I get both intel and /lenovo/. The key point for this bug report is what happens with the lenovo one: The hotkeys work and make the backlight change, but not consistently. Repeatedly using the hotkey to increase the brightness causes the level to increase, but then occasionally reset to zero (including resetting as shown in the OSD - i.e. the OSD is always showing the level that the backlight actually is). Occasionally the OSD shows the "enable touchpad" icon when pressing the increase brightness hotkey repeatedly. The same action also causes the wifi to enable/disable randomly. If I press the hotkey with pauses in between, things behave normally. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-67-generic 3.13.0-67.110 ProcVersionSignature: Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27 Uname: Linux 3.13.0-67-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neale 3106 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 15 11:16:55 2015 HibernationDevice: RESUME=UUID=1fd50851-1727-4432-a99c-d0be8aafc983 InstallationDate: Installed on 2013-10-23 (752 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO IdeaPad Z580 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-67-generic root=UUID=d66417de-a540-485b-b469-aabd51a8844b ro quiet splash acpi_backlight=vendor RelatedPackageVersions: linux-restricted-modules-3.13.0-67-generic N/A linux-backports-modules-3.13.0-67-generic N/A linux-firmware 1.127.18 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-03-17 (607 days ago) dmi.bios.date: 12/25/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 5FCN95WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z580 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr5FCN95WW:bd12/25/2012:svnLENOVO:pnIdeaPadZ580:pvrLenovoZ580:rvnLENOVO:rnLenovo:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoZ580: dmi.product.name: IdeaPad Z580 dmi.product.version: Lenovo Z580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516370/+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 1516370] Re: Vendor backlight on Lenovo Z580 having random hotkeys issues
Let's not confuse things. This bug is with Lenovo vendor backlight, and is present on the latest kernel. The guidance on investigating backlight issues recommends using acpi_backlight=vendor. If neither than nor nvidia or nouveau work, then it really doesn't help the situation. Let's see if we can get what appears to be a relatively simple issue fixed - or else, why bother having the vendor option at all :-| -- 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/1516370 Title: Vendor backlight on Lenovo Z580 having random hotkeys issues Status in linux package in Ubuntu: Incomplete Bug description: I've taken a bold guess in the title of this bug. While investigating why on 14.04 LTS, I have working backlight on the latest 3.13 kernel, but not on the 3.16, I tried acpi_backlight=vendor. With default boot parameters, I just get /sys/class/backlight/intel_backlight/, and the backlight works correctly on 3.13, but does not change the brightness on 3.16 (the OSD does show that the hotkeys are trying to change the brightness). With acpi_backlight=vendor, I get both intel and /lenovo/. The key point for this bug report is what happens with the lenovo one: The hotkeys work and make the backlight change, but not consistently. Repeatedly using the hotkey to increase the brightness causes the level to increase, but then occasionally reset to zero (including resetting as shown in the OSD - i.e. the OSD is always showing the level that the backlight actually is). Occasionally the OSD shows the "enable touchpad" icon when pressing the increase brightness hotkey repeatedly. The same action also causes the wifi to enable/disable randomly. If I press the hotkey with pauses in between, things behave normally. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-67-generic 3.13.0-67.110 ProcVersionSignature: Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27 Uname: Linux 3.13.0-67-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neale 3106 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 15 11:16:55 2015 HibernationDevice: RESUME=UUID=1fd50851-1727-4432-a99c-d0be8aafc983 InstallationDate: Installed on 2013-10-23 (752 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO IdeaPad Z580 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-67-generic root=UUID=d66417de-a540-485b-b469-aabd51a8844b ro quiet splash acpi_backlight=vendor RelatedPackageVersions: linux-restricted-modules-3.13.0-67-generic N/A linux-backports-modules-3.13.0-67-generic N/A linux-firmware 1.127.18 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-03-17 (607 days ago) dmi.bios.date: 12/25/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 5FCN95WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z580 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr5FCN95WW:bd12/25/2012:svnLENOVO:pnIdeaPadZ580:pvrLenovoZ580:rvnLENOVO:rnLenovo:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoZ580: dmi.product.name: IdeaPad Z580 dmi.product.version: Lenovo Z580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516370/+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 1518737] [NEW] can not re-enable touchpad
You have been subscribed to a public bug: I am running Ubuntu 15.10 (32-bit edition but I know it is also a problem on 64-bit edition) on an Acer Aspire 5738 laptop which has a physical button next to the touchpad that can toggle the device. When I hit the button a desktop notification appears, informing me that the device has been disabled (an icon of a touchpad with an x in the bottom-right-hand-corner) and I am no longer able to use the touchpad for anything, as expected. When I press the button again to re-enable the touchpad, a desktop notification appears, informing me that the device has been enabled (an icon of a touchpad with no x in the bottom-right-hand-corner) but the touchpad remains disabled, i.e I can use it for absolutely nothing. (clicking, scrolling, pointing, ...) Logging in and out or restarting the PC enables the touchpad, but I can also use modprobe to remove and insert psmouse module, which will also cause it to enable. When I use the button physically next to the touchpad to enable/disable the touchpad, it does not affect the toggle switch in the "Mouse and Touchpad" settings, but if I use that setting (the toggle switch) I can correctly enable and disable the touchpad. xinput lists the device under "Virtual core pointer" as an "AlpsPS/2 ALPS GlidePoint". BIOS is updated as of today. If I can be of help in patching the bug, I would love to, but I just have no idea where to look. I altered the psmouse kernel module to print information to the logs about various activity (resetting, deactivating) but none of it was very informative (again, I don't know where to look). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- can not re-enable touchpad https://bugs.launchpad.net/bugs/1518737 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 1490130] Re: Elantech touchpad stops working after suspend
some records from my dmesg : model code and BIOS version : DMI: ASUSTeK COMPUTER INC. X302LA/X302LA, BIOS X302LA.203 04/20/2015 i8042/serio/psmouse/elantech lines : i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x381f00) psmouse serio1: elantech: Synaptics capabilities query result 0x10, 0x14, 0x0e. psmouse serio1: elantech: Elan sample query result 00, 23, 64 input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input5 after manual mod-reprobe without pm-suspend : psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x381f00) psmouse serio1: elantech: Synaptics capabilities query result 0x10, 0x14, 0x0e. psmouse serio1: elantech: Elan sample query result 00, 23, 64 input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input292 (then touchpad dies off) $ ls -l /etc/pm/sleep.d/05_elantech -rwxr-xr-x 1 root root 128 лис 22 20:33 /etc/pm/sleep.d/05_elantech $ cat /etc/pm/sleep.d/05_elantech #!/bin/sh case "$1" in suspend|hibernate) modprobe -r psmouse ;; resume|thaw) modprobe psmouse ;; esac after initial boot and pm-suspend : touchpad dies off, no records about its re-detection appear in dmesg now preparing to try a patch posted to linux-input mail list referred to at #8 -- 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/1490130 Title: Elantech touchpad stops working after suspend Status in linux package in Ubuntu: Incomplete Bug description: i have asus a455ld i5 5200u running kubuntu 15.04 with kernel 4.0.8-040008-generic. touchpad is recognized as elantech version 4. everything was fine until my notebook go to suspend and resume without touchpad working. I tried : modprobe -r psmouse modprobe psmouse it only work before suspend. execute those commands after resume from suspend is not working. the last thing i tried is this. when i use this command before suspend : insmod /lib/modules/4.0.8-040008-generic/kernel/drivers/input/mouse/psmouse.ko these appear in the dmesg: [ 820.207105] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x381f00) [ 820.70] psmouse serio1: elantech: Synaptics capabilities query result 0x10, 0x14, 0x0e. [ 820.294698] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input146 but when i use the command after suspend, there is nothing any output in the dmesg. i tried all ubuntu varian and opensuse 13.2 live usb, the result is the same. but in windows 10, touchpad still active after suspend. --- ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-20 (69 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: linux (not installed) Tags: vivid Uname: Linux 4.0.8-040008-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blackhole 1460 F pulseaudio /dev/snd/controlC1: blackhole 1460 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=668506c6-5b13-4a29-9c34-956c6c34a45a InstallationDate: Installed on 2015-06-20 (129 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X455LDB Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=4318cf1f-564c-47ff-8b0c-f3acf77aa34f ro quiet splash i915.enable_ips=0 vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom
[Kernel-packages] [Bug 1490130] Re: Elantech touchpad stops working after suspend
I have Asus X302LA notebook, and 'modprobe -r psmouse' followed by 'modprobe psmouse' makes its touchpad die off even without doing pm-suspend Also I see in dmesg that ETPS/2 Elantech touchpad is initially created as /devices/platform/i8042/serio1/input/input5, and after module reload, it is recreated as .../input292 (but only after first module re-probe, next times nothing happens at all) The script in /etc/pm/sleep.d apparently does not do anything (probably need to re-test it after a fresh boot) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490130 Title: Elantech touchpad stops working after suspend Status in linux package in Ubuntu: Incomplete Bug description: i have asus a455ld i5 5200u running kubuntu 15.04 with kernel 4.0.8-040008-generic. touchpad is recognized as elantech version 4. everything was fine until my notebook go to suspend and resume without touchpad working. I tried : modprobe -r psmouse modprobe psmouse it only work before suspend. execute those commands after resume from suspend is not working. the last thing i tried is this. when i use this command before suspend : insmod /lib/modules/4.0.8-040008-generic/kernel/drivers/input/mouse/psmouse.ko these appear in the dmesg: [ 820.207105] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x381f00) [ 820.70] psmouse serio1: elantech: Synaptics capabilities query result 0x10, 0x14, 0x0e. [ 820.294698] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input146 but when i use the command after suspend, there is nothing any output in the dmesg. i tried all ubuntu varian and opensuse 13.2 live usb, the result is the same. but in windows 10, touchpad still active after suspend. --- ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-06-20 (69 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: linux (not installed) Tags: vivid Uname: Linux 4.0.8-040008-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blackhole 1460 F pulseaudio /dev/snd/controlC1: blackhole 1460 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=668506c6-5b13-4a29-9c34-956c6c34a45a InstallationDate: Installed on 2015-06-20 (129 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X455LDB Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=4318cf1f-564c-47ff-8b0c-f3acf77aa34f ro quiet splash i915.enable_ips=0 vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X455LDB.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X455LDB 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.:bvrX455LDB.206:bd02/12/2015:svnASUSTeKCOMPUTERINC.:pnX455LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X455LDB 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/1490130/+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 1424261] Re: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card.
I have now (finally) updated the BIOS to the latest F.20 (mentioned in comment #5). I have further upgraded to the latest ubuntu 15.10 with kernel Linux hermes 4.2.0-18-generic #22-Ubuntu SMP Fri Nov 6 18:25:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The hardware, the symptoms and the problem is still the same. ** Changed in: linux (Ubuntu) Status: Expired => 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/1424261 Title: usb microSD card reader report incorrect size (32gb instead of 64GB) of microSD card. Status in linux package in Ubuntu: Confirmed Bug description: Using a 64GB microSDXC card in a usb sd card reader gives wrong SD card size (32GB). When putting the same microSDXC card in a a SD adapter it correctly gives 64GB size. Hardware: sdCard: SanDisk Extreme microSDXC UHS-I (http://www.sandisk.com/products/memory-cards/microsd/extreme-uhs-i-action-cameras/?capacity=64GB) USB card reader: Kingston FCR-MRG2 (http://www.kingston.com/us/support/technical/products?model=fcr-mrg2) SD adapter: Kingston (http://www.kingston.com/en/flash/microsd_cards#MBLY) Here is the output from terminal: Accessing it through USB card reader: $ sudo fdisk -l /dev/sdb Disk /dev/sdb: 27.5 GiB, 29504831488 bytes, 57626624 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x Accessing it through sd card adapter and the built-int sd card reader: $ sudo fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x My conclussion is that the driver for the usb card-reader. I will attach the output of lsusb -v -d 090c:6200 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-30-generic 3.16.0-30.40 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarl 4339 F pulseaudio CurrentDesktop: KDE Date: Sat Feb 21 21:27:53 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e45150b2-5a68-4250-918d-8b731fcb17a2 InstallationDate: Installed on 2013-11-27 (450 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=21aea9ee-02ab-46d0-8314-468f69a333c0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2015-01-22 (30 days ago) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU01143H6 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424261/+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 1518457] Re: kswapd0 100% CPU usage
same issue here: root@orangepi:/var/log# uname -a Linux orangepi 3.4.39 #2 SMP PREEMPT Mon Oct 12 12:03:03 CEST 2015 armv7l armv7l armv7l GNU/Linux root@orangepi:/var/log# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.10 DISTRIB_CODENAME=wily DISTRIB_DESCRIPTION="Ubuntu 15.10" also echo 1 > /proc/sys/vm/drop_caches temporary solve issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1518457 Title: kswapd0 100% CPU usage Status in linux package in Ubuntu: Confirmed Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 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 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' 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: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+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 1489820] Re: NVIDIA GM108M [10de:1341] got frozen screen with kernel 3.19
I'm checking in if there is any progress on this. I tried installing the Nvidia drivers point to the nVidia website in the link above. The installation went fine but it's not using the nVidia driver. I followed the instruction of running nvidia-xconfig but it doesn't change anything. I would love to be able to use the drivers that comes with Mint or Ubuntu but any attempt in installing a distro that uses a kernel higher than 3.18 gives similar issues. Thanks -- 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/1489820 Title: NVIDIA GM108M [10de:1341] got frozen screen with kernel 3.19 Status in linux package in Ubuntu: Confirmed Bug description: ~ $ uname -a Linux user-Aspire-VN7-571G 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Linux Mint 17.2 Rafaela Release: 17.2 I installed kernel 3.19 to solve the problems which are reported under https://bugs.launchpad.net/bugs/1383184. At least I could solve this. Since that time it occurs from time to time, that the screen freezes no matter which application I am just running. The only way out is to press the power bottom and to restart the computer. ubuntu-bug linux shows: ProblemType: Bug ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Fri Aug 28 12:07:10 2015 Dependencies: adduser 3.113+nmu3ubuntu3 apt-utils 1.0.1ubuntu2.10 base-passwd 3.5.33 busybox-initramfs 1:1.21.0-1ubuntu1 coreutils 8.21-1ubuntu5.1 cpio 2.11+dfsg-1ubuntu1.1 dbus 1.6.18-0ubuntu4.3 debconf 1.5.51ubuntu2 debconf-i18n 1.5.51ubuntu2 debianutils 4.4 dmsetup 2:1.02.77-6ubuntu2 dpkg 1.17.5ubuntu5.4 [modified: sbin/start-stop-daemon] e2fslibs 1.42.9-3ubuntu1.2 e2fsprogs 1.42.9-3ubuntu1.2 findutils 4.4.2-7 gcc-4.8-base 4.8.4-2ubuntu1~14.04 gcc-4.9-base 4.9.1-0ubuntu1 gettext-base 0.18.3.1-1ubuntu3 grub-common 2.02~beta2-9ubuntu1.3 grub-gfxpayload-lists 0.6 grub-pc 2.02~beta2-9ubuntu1.3 grub-pc-bin 2.02~beta2-9ubuntu1.3 grub2-common 2.02~beta2-9ubuntu1.3 ifupdown 0.7.47.2ubuntu4.1 initramfs-tools 0.103ubuntu4.2 initramfs-tools-bin 0.103ubuntu4.2 initscripts 2.88dsf-41ubuntu6.2 insserv 1.14.0-5ubuntu2 iproute2 3.12.0-2ubuntu1 isc-dhcp-client 4.2.4-7ubuntu12.3 isc-dhcp-common 4.2.4-7ubuntu12.3 klibc-utils 2.0.3-0ubuntu1 kmod 15-0ubuntu6 libacl1 2.2.52-1 libapparmor1 2.8.95~2430-0ubuntu5.3 libapt-inst1.5 1.0.1ubuntu2.10 libapt-pkg4.12 1.0.1ubuntu2.10 libasprintf0c2 0.18.3.1-1ubuntu3 libattr1 1:2.4.47-1ubuntu1 libaudit-common 1:2.3.2-2ubuntu1 libaudit1 1:2.3.2-2ubuntu1 libblkid1 2.20.1-5.1ubuntu20.6 libbz2-1.0 1.0.6-5 libc6 2.19-0ubuntu6.6 libcap2 1:2.24-0ubuntu2 libcgmanager0 0.24-0ubuntu7.3 libcomerr2 1.42.9-3ubuntu1.2 libdb5.3 5.3.28-3ubuntu3 libdbus-1-3 1.6.18-0ubuntu4.3 libdebconfclient0 0.187ubuntu1 libdevmapper1.02.1 2:1.02.77-6ubuntu2 libdrm2 2.4.60-2~ubuntu14.04.1 libexpat1 2.1.0-4ubuntu1 libfreetype6 2.5.2-1ubuntu2.4 libfuse2 2.9.2-4ubuntu4.14.04.1 libgcc1 1:4.9.1-0ubuntu1 libgpm2 1.20.4-6.1 libjson-c2 0.11-3ubuntu1.2 libjson0 0.11-3ubuntu1.2 libklibc 2.0.3-0ubuntu1 libkmod2 15-0ubuntu6 liblocale-gettext-perl 1.05-7build3 liblzma5 5.1.1alpha+20120614-2ubuntu2 libmount1 2.20.1-5.1ubuntu20.6 libncurses5 5.9+20140118-1ubuntu1 libncursesw5 5.9+20140118-1ubuntu1 libnih-dbus1 1.0.3-4ubuntu25 libnih1 1.0.3-4ubuntu25 libpam-modules 1.1.8-1ubuntu2 libpam-modules-bin 1.1.8-1ubuntu2 libpam-runtime 1.1.8-1ubuntu2 libpam-systemd 204-5ubuntu20.13 libpam0g 1.1.8-1ubuntu2 libpcre3 1:8.31-2ubuntu2.1 libplymouth2 0.8.8-0ubuntu17.1 libpng12-0 1.2.50-1ubuntu2 libprocps3 1:3.3.9-1ubuntu2.2 libselinux1 2.2.2-1ubuntu0.1 libsemanage-common 2.2-1 libsemanage1 2.2-1 libsepol1 2.2-1ubuntu0.1 libslang2 2.2.4-15ubuntu1 libss2 1.42.9-3ubuntu1.2 libstdc++6 4.8.4-2ubuntu1~14.04 libsystemd-daemon0 204-5ubuntu20.13 libsystemd-login0 204-5ubuntu20.13 libtext-charwidth-perl 0.04-7build3 libtext-iconv-perl 1.7-5build2 libtext-wrapi18n-perl 0.06-7 libtinfo5 5.9+20140118-1ubuntu1 libudev1 204-5ubuntu20.13 libustr-1.0-1 1.0.4-3ubuntu2 libuuid1 2.20.1-5.1ubuntu20.6 libxtables10 1.4.21-1ubuntu1 lsb-base 4.1+Debian11ubuntu6mint1 [origin: linuxmint] makedev 2.3.1-93ubuntu1 module-init-tools 15-0ubuntu6 mount 2.20.1-5.1ubuntu20.6 mountall 2.53 multiarch-support 2.19-0ubuntu6.6 netbase 5.2 os-prober 1.63ubuntu1 passwd 1:4.1.5.1-1ubuntu9.1 perl-base 5.18.2-2ubuntu1 plymouth 0.8.8-0ubuntu17.1 plymouth-theme-ubuntu-text 0.8.8-0ubuntu17.1 procps 1:3.3.9-1ubuntu2.2 psmisc 22.20-1ubuntu2 sensible-utils 0.0.9 systemd-services 204-5ubuntu20.1
[Kernel-packages] [Bug 1499089] Re: Please enable kconfig X86_LEGACY_VM86 for i386
Don't worry about my last question - I found in the diff that it's been applied, thanks! -- 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/1499089 Title: Please enable kconfig X86_LEGACY_VM86 for i386 Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Released Bug description: In order for dosemu to reach maximum performance (a > 10x speedup) please enable kconfig X86_LEGACY_VM86 in the kernel. As of this commit http://www.spinics.net/lists/linux-tip-commits/msg30360.html the overzealous kconfig message that seemed to suggest that the vm86() syscall was a security hazard in itself has been revised to reflect reality. Also please note that even if this kconfig option is enabled the runtime default is still off as vm86 is only actually enabled if the sysctl vm.mmap_min_addr is set to 0. That said, allowing vm.mmap_min_addr=0 is a known security risk and enabling the vm86() syscall to operate additionally would add little value to any potential attacker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499089/+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 1499089] Re: Please enable kconfig X86_LEGACY_VM86 for i386
Tested on Trusty via the Wily LTS enablement package. # dpkg -l linux-image-generic-lts-wily Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-=-= ii linux-image-generic-lts-wily 4.2.0.19.14 i386 Generic Linux kernel image dpkg -l dosemu Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-=-= ii dosemu 1.4.0.7+20130105+b028 i386 DOS Emulator for Linux This allowed the dosemu 1.4.0 package to start up MS-DOS 6.22 Microsoft(R) MS-DOS(R) Version 6.22 (C)Copyright Microsoft Corp 1981-1994. C:\> C:\> C:\>dir Volume in drive C is mu/drives/c Directory of C:\ MSDOSSYS38,138 05-14-14 7:40p COMMAND COM54,645 05-14-14 7:40p DOSEMU11-12-15 3:51p IO SYS40,774 05-14-14 7:40p 4 file(s)133,557 bytes 2,147,450,880 bytes free Have you applied the fix http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=2459ee8651dc5ab72790c2ffa99af288c7641b64 I'm sure it's needed 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/1499089 Title: Please enable kconfig X86_LEGACY_VM86 for i386 Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Released Bug description: In order for dosemu to reach maximum performance (a > 10x speedup) please enable kconfig X86_LEGACY_VM86 in the kernel. As of this commit http://www.spinics.net/lists/linux-tip-commits/msg30360.html the overzealous kconfig message that seemed to suggest that the vm86() syscall was a security hazard in itself has been revised to reflect reality. Also please note that even if this kconfig option is enabled the runtime default is still off as vm86 is only actually enabled if the sysctl vm.mmap_min_addr is set to 0. That said, allowing vm.mmap_min_addr=0 is a known security risk and enabling the vm86() syscall to operate additionally would add little value to any potential attacker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499089/+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 1499089] Re: Please enable kconfig X86_LEGACY_VM86 for i386
** Tags removed: verification-needed-wily ** Tags added: verification-done-wily -- 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/1499089 Title: Please enable kconfig X86_LEGACY_VM86 for i386 Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Released Bug description: In order for dosemu to reach maximum performance (a > 10x speedup) please enable kconfig X86_LEGACY_VM86 in the kernel. As of this commit http://www.spinics.net/lists/linux-tip-commits/msg30360.html the overzealous kconfig message that seemed to suggest that the vm86() syscall was a security hazard in itself has been revised to reflect reality. Also please note that even if this kconfig option is enabled the runtime default is still off as vm86 is only actually enabled if the sysctl vm.mmap_min_addr is set to 0. That said, allowing vm.mmap_min_addr=0 is a known security risk and enabling the vm86() syscall to operate additionally would add little value to any potential attacker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499089/+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 1517882] Re: Excessive logging and problems with brcmsmac: bcma0:1: START: tid 1 is not agg'able
Ok, sorry. Bug remains in 4.3.0-040300-generic however messages are less frequent On Sun, Nov 22, 2015 at 5:31 PM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > alphac, to advise, you don't need to apport-collect further unless > specifically requested to do so. > > ** Attachment removed: "WifiSyslog.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523272/+files/WifiSyslog.txt > > ** Attachment removed: "UdevDb.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523271/+files/UdevDb.txt > > ** Attachment removed: "RfKill.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523270/+files/RfKill.txt > > ** Attachment removed: "ProcModules.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523269/+files/ProcModules.txt > > ** Attachment removed: "ProcInterrupts.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523268/+files/ProcInterrupts.txt > > ** Attachment removed: "ProcCpuinfo.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523267/+files/ProcCpuinfo.txt > > ** Attachment removed: "Lsusb.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523266/+files/Lsusb.txt > > ** Attachment removed: "Lspci.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523265/+files/Lspci.txt > > ** Attachment removed: "JournalErrors.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523264/+files/JournalErrors.txt > > ** Attachment removed: "IwConfig.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523263/+files/IwConfig.txt > > ** Attachment removed: "CurrentDmesg.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523262/+files/CurrentDmesg.txt > > ** Attachment removed: "CRDA.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523261/+files/CRDA.txt > > ** Attachment removed: "AlsaInfo.txt" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523260/+files/AlsaInfo.txt > > ** Description changed: > > Hello I have lots of logs with this message, like 15mb a day. Also the > module randomly loses ability to connect an AP after a disconnection, > the only resolution is a reboot, more than one if necessary. The latter > happens also with the proprietary Broadcom driver. > > brcmsmac bcma0:1: START: tid 1 is not agg'able > > 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: > - USERPID ACCESS COMMAND > - /dev/snd/controlC0: alphac 1565 F pulseaudio > + USERPID ACCESS COMMAND > + /dev/snd/controlC0: alphac 1565 F pulseaudio > CurrentDesktop: Unity > Date: Thu Nov 19 13:36:22 2015 > InstallationDate: Installed on 2015-09-05 (74 days ago) > InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) > Lsusb: > - Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching > Hub > - Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > - Bus 001 Device 003: ID 2232:1001 Silicon Motion > - Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching > Hub > - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > + Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching > Hub > + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > + Bus 001 Device 003: ID 2232:1001 Silicon Motion > + Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching > Hub > + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: SAMSUNG ELECTRONICS CO., LTD. > QX310/QX410/QX510/SF310/SF410/SF510 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic > root=UUID=7a190443-4e56-4ea8-98a8-296841ad7a95 ro quiet splash vt.handoff=7 > 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 > + linux-restricted-modules-4.2.0-18-generic N/A > + linux-backports-modules-4.2.0-18-generic N/A > + linux-firmware1.149.2 > SourcePackage: linux > UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev' > UpgradeStatus: Upgraded to wily on 2015-10-31 (18 days ago) > dmi.bios.date: 05/25/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 05MX.M008.20110525.SCY > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: QX310/QX410/QX510/SF310/SF410/SF510 > dmi.board.vendor: SAMSUNG ELECTRONI
[Kernel-packages] [Bug 1518642] Re: rtl8192cu kernel driver not working
Vincent Thiele, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. 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-3603 ** 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/1518642 Title: rtl8192cu kernel driver not working Status in linux package in Ubuntu: Incomplete Bug description: Connection is dropped after some time. Workaround install patched dkms driver. Should work out of the box for "normal users" 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 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vincent1352 F pulseaudio /dev/snd/controlC0: vincent1352 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 22 00:58:18 2015 HibernationDevice: RESUME=UUID=2dfaf257-b29b-4238-b562-b7769b0aaa49 InstallationDate: Installed on 2015-11-21 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed root=UUID=23870d18-dac9-4325-be37-c76e2a75da2e ro quiet splash vt.handoff=7 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] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Maximus IV GENE-Z dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusIVGENE-Z:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518642/+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 1515157] kili (amd64) - tests ran: 87, failed: 42
tests ran: 87, failed: 42; http://kernel.ubuntu.com/testing/4.2.0-19.23/kili__4.2.0-19.23__2015-11-22_14-18-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/1515157 Title: linux: 4.2.0-19.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: New Bug description: This bug is for tracking the 4.2.0-19.23 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, 11. November 2015 09:48 UTC kernel-stable-Prepare-package-end:Thursday, 12. November 2015 10:04 UTC kernel-stable-Promote-to-proposed-start:Thursday, 12. November 2015 10:04 UTC kernel-stable-Promote-to-proposed-end:Thursday, 12. November 2015 20:41 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 12. November 2015 22:03 UTC kernel-stable-Verification-testing-start:Thursday, 12. November 2015 22:03 UTC kernel-stable-Certification-testing-start:Thursday, 12. November 2015 22:03 UTC kernel-stable-Security-signoff-start:Thursday, 12. November 2015 22:03 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 12. November 2015 22:03 UTC kernel-stable-Security-signoff-end:Friday, 13. November 2015 09:01 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1515157/+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 1517882] Re: Excessive logging and problems with brcmsmac: bcma0:1: START: tid 1 is not agg'able
alphac, to advise, you don't need to apport-collect further unless specifically requested to do so. ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523272/+files/WifiSyslog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523271/+files/UdevDb.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523270/+files/RfKill.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523269/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523268/+files/ProcInterrupts.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523267/+files/ProcCpuinfo.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523266/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523265/+files/Lspci.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523264/+files/JournalErrors.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523263/+files/IwConfig.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523262/+files/CurrentDmesg.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523261/+files/CRDA.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517882/+attachment/4523260/+files/AlsaInfo.txt ** Description changed: Hello I have lots of logs with this message, like 15mb a day. Also the module randomly loses ability to connect an AP after a disconnection, the only resolution is a reboot, more than one if necessary. The latter happens also with the proprietary Broadcom driver. brcmsmac bcma0:1: START: tid 1 is not agg'able 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: - USERPID ACCESS COMMAND - /dev/snd/controlC0: alphac 1565 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: alphac 1565 F pulseaudio CurrentDesktop: Unity Date: Thu Nov 19 13:36:22 2015 InstallationDate: Installed on 2015-09-05 (74 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: - Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub - Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 003: ID 2232:1001 Silicon Motion - Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 003: ID 2232:1001 Silicon Motion + Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. QX310/QX410/QX510/SF310/SF410/SF510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=7a190443-4e56-4ea8-98a8-296841ad7a95 ro quiet splash vt.handoff=7 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 + linux-restricted-modules-4.2.0-18-generic N/A + linux-backports-modules-4.2.0-18-generic N/A + linux-firmware1.149.2 SourcePackage: linux UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-31 (18 days ago) dmi.bios.date: 05/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 05MX.M008.20110525.SCY dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: QX310/QX410/QX510/SF310/SF410/SF510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 05MX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr05MX.M008.20110525.SCY:bd05/25/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnQX310/QX410/QX510/SF310/SF410/SF510:pvr05MX:r
[Kernel-packages] [Bug 1514052] Re: erratic fan speed and little control kernel 4.2
Hello Christopher, Unfortunately I can't do it for now: "The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again." I use 4.3.0-040300-generic. Looks like simplest way to do it for me - download 16.04 daily build and test on it. I'll try it soon BTW rmmod dell_smm_hwmon fixes problem for me -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1514052 Title: erratic fan speed and little control kernel 4.2 Status in linux package in Ubuntu: Incomplete Bug description: I have just upgraded to Ubuntu 15.10 and almost immediately my CPU fan started speeding and slowing without good reason even when the PC is idle. I tried various things but then found that if I leave the computer off for a long time and let everything cool down then when I boot from cold the CPU fan is stable. To test my theory of cold start out I then ran sudo cpupower frequency-set -g powersave followed by sudo cpupower frequency-set -g ondemand The final mode is the initial mode. Almost immediately as soon as I moved to powersave mode the erratic fan speed started. It did not stop when I returned to ondemand. Temp fix for this behaviour is - go and have a cup of coffee and let the computer cool down when you restart: shutdown then start from cold. $ uname -a Linux HomeMegaUbuntu 4.2.0-17-generic #21-Ubuntu SMP Fri Oct 23 19:56:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.10 Release: 15.10 Codename: wily $ cpupower frequency-info analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.20 GHz - 2.80 GHz available frequency steps: 2.80 GHz, 2.80 GHz, 2.67 GHz, 2.53 GHz, 2.40 GHz, 2.27 GHz, 2.13 GHz, 2.00 GHz, 1.87 GHz, 1.73 GHz, 1.60 GHz, 1.47 GHz, 1.33 GHz, 1.20 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.20 GHz and 2.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.20 GHz. cpufreq stats: 2.80 GHz:11.93%, 2.80 GHz:0.00%, 2.67 GHz:0.40%, 2.53 GHz:0.44%, 2.40 GHz:0.51%, 2.27 GHz:0.55%, 2.13 GHz:0.35%, 2.00 GHz:0.72%, 1.87 GHz:0.84%, 1.73 GHz:1.00%, 1.60 GHz:2.16%, 1.47 GHz:4.61%, 1.33 GHz:16.83%, 1.20 GHz:59.65% (29241) boost state support: Supported: yes Active: yes 25500 MHz max turbo 4 active cores 25500 MHz max turbo 3 active cores 25500 MHz max turbo 2 active cores 25500 MHz max turbo 1 active cores Tried intel_pstate but it is not supported for some reason on my machine ie the following does not work and I am left with driver: acpi-cpufreq GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=enable" Could not see ACPI Thermal Zones reported in dmesg $ dmesg | grep ACPI [0.00] BIOS-e820: [mem 0xbd78-0xbd78dfff] ACPI data [0.00] BIOS-e820: [mem 0xbd78e000-0xbd7c] ACPI NVS [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000F9B40 24 (v02 ACPIAM) [0.00] ACPI: XSDT 0xBD780100 6C (v01 DELL FX09 20101113 MSFT 0097) [0.00] ACPI: FACP 0xBD780290 F4 (v04 DELL FX09 20101113 MSFT 0097) [0.00] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 128/64 (20150619/tbfadt-623) [0.00] ACPI: DSDT 0xBD780660 005B02 (v02 1 1000 INTL 20051117) [0.00] ACPI: FACS 0xBD78E000 40 [0.00] ACPI: FACS 0xBD78E000 40 [0.00] ACPI: APIC 0xBD780390 8C (v02 DELL FX09 20101113 MSFT 0097) [0.00] ACPI: MCFG 0xBD780420 3C (v01 DELL OEMMCFG 20101113 MSFT 0097) [0.00] ACPI: SLIC 0xBD780460 000176 (v01 DELL FX09 20101113 MSFT 0097) [0.00] ACPI: OSFR 0xBD7805E0 80 (v01 DELL FX09 20101113 MSFT 0097) [0.00] ACPI: OEMB 0xBD78E040 72 (v01 DELL FX09 20101113 MSFT 0097) [0.00] ACPI: HPET 0xBD78A660 38 (v01 DELL OEMHPET 20101113 MSFT 0097) [0.00] ACPI: ASF! 0xBD78A6A0 99 (v32 LEGEND I865PASF 0001 INTL 20051117) [0.00] ACPI: SSDT 0xBD78F800 000363 (v01 DpgPmm CpuPm 0012 INTL 20051117) [0.00] ACPI: Local APIC address 0xfee0 [0.00] ACPI: PM-Timer IO Port: 0x808
[Kernel-packages] [Bug 1510134] Re: [Dell Latitude E5440] ALPS touchpad and buttons work only in a single window after resume from suspend.
Christopher M. Penalver, the daily image boots, and exposes the same behaviour as the others. Please let me know if there is something I could contribute with. Thank you for your patience and guidance. -- 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/1510134 Title: [Dell Latitude E5440] ALPS touchpad and buttons work only in a single window after resume from suspend. Status in linux package in Ubuntu: Incomplete Bug description: ALPS touchpad and buttons work only in a single window. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-31-generic 3.19.0-31.36 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jsum 1861 F pulseaudio /dev/snd/controlC1: jsum 1861 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 26 16:57:30 2015 HibernationDevice: RESUME=UUID=13c66e6a-58e2-431a-9f1b-15248ae2fbd0 InstallationDate: Installed on 2015-06-08 (140 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. MachineType: Dell Inc. Latitude E5440 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-31-generic N/A linux-backports-modules-3.19.0-31-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 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/1510134/+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 1507909] Re: WARNING: CPU: 1 PID: 54 at /build/linux-qOmAV7/linux-3.19.0/sound/pci/hda/hda_i915.c:115 snd_hdac_i915_register_notifier+0x35/0x40 [snd_hda_intel]()
affect the same way: [4.266325] [ cut here ] [4.266339] WARNING: CPU: 0 PID: 68 at /build/linux-TgZcQQ/linux-3.19.0/sound/pci/hda/hda_i915.c:115 snd_hdac_i915_register_notifier+0x35/0x40 [snd_hda_intel]() [4.266341] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_intel_sst_acpi snd_intel_sst_core snd_soc_sst_mfld_platform snd_hda_intel snd_soc_core snd_hda_controller snd_hda_codec snd_compress intel_rapl snd_pcm_dmaengine snd_hwdep intel_powerclamp snd_pcm coretemp snd_seq_midi kvm_intel snd_seq_midi_event kvm snd_rawmidi i915 crct10dif_pclmul snd_seq crc32_pclmul ghash_clmulni_intel cryptd snd_seq_device snd_timer drm_kms_helper drm snd serio_raw joydev lpc_ich soundcore i2c_algo_bit shpchp mei_txe mei iosf_mbi snd_soc_sst_acpi video 8250_fintek mac_hid tpm_infineon crystalhd(OE) parport_pc ppdev lp parport sunrpc autofs4 pata_acpi hid_generic usbhid hid psmouse pata_jmicron r8169 mii ahci libahci [4.266395] CPU: 0 PID: 68 Comm: kworker/0:1 Tainted: G OE 3.19.0-33-generic #38-Ubuntu [4.266397] Hardware name: ASUS All Series/J1900I-C, BIOS 0805 09/16/2015 [4.266402] Workqueue: events azx_probe_work [snd_hda_intel] [4.266405] c0582838 8801787dbbf8 817c4f9f 0007 [4.266409] 8801787dbc38 81076a8a 8801787dbc08 [4.266413] c05b3b28 88017a20 88017834b800 [4.266417] Call Trace: [4.266428] [] dump_stack+0x45/0x57 [4.266434] [] warn_slowpath_common+0x8a/0xc0 [4.266438] [] warn_slowpath_null+0x1a/0x20 [4.266443] [] snd_hdac_i915_register_notifier+0x35/0x40 [snd_hda_intel] [4.266450] [] patch_generic_hdmi+0x58d/0x6c0 [snd_hda_codec_hdmi] [4.266457] [] ? __kmalloc_track_caller+0x1a5/0x260 [4.266476] [] ? snd_hda_codec_configure+0x409/0x5a0 [snd_hda_codec] [4.266484] [] snd_hda_codec_configure+0x202/0x5a0 [snd_hda_codec] [4.266491] [] ? azx_bus_reset+0xb0/0xb0 [snd_hda_controller] [4.266496] [] ? azx_halt+0x40/0x40 [snd_hda_controller] [4.266500] [] ? azx_pcm_prepare+0x510/0x510 [snd_hda_controller] [4.266505] [] ? azx_pcm_hw_params+0xa0/0xa0 [snd_hda_controller] [4.266510] [] azx_codec_configure+0x38/0x60 [snd_hda_controller] [4.266515] [] azx_probe_continue+0x4f4/0x810 [snd_hda_intel] [4.266520] [] azx_probe_work+0x15/0x20 [snd_hda_intel] [4.266525] [] process_one_work+0x158/0x430 [4.266529] [] worker_thread+0x5b/0x530 [4.266533] [] ? rescuer_thread+0x3a0/0x3a0 [4.266537] [] kthread+0xc9/0xe0 [4.266541] [] ? kthread_create_on_node+0x1c0/0x1c0 [4.266545] [] ret_from_fork+0x58/0x90 [4.266550] [] ? kthread_create_on_node+0x1c0/0x1c0 [4.266552] ---[ end trace ec56967dba95c3e0 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1507909 Title: WARNING: CPU: 1 PID: 54 at /build/linux- qOmAV7/linux-3.19.0/sound/pci/hda/hda_i915.c:115 snd_hdac_i915_register_notifier+0x35/0x40 [snd_hda_intel]() Status in bcmwl package in Ubuntu: Confirmed Bug description: I have found this warning in dmesg at each start, even if sound seems to work properly : [ 11.127798] sound hdaudioC0D0: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 11.127805] sound hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 11.127808] sound hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 11.127811] sound hdaudioC0D0:mono: mono_out=0x0 [ 11.127813] sound hdaudioC0D0:inputs: [ 11.127817] sound hdaudioC0D0: Mic=0x19 [ 11.127820] sound hdaudioC0D0: Internal Mic=0x12 [ 11.155157] intel_soc_dts_thermal: request_threaded_irq ret -22 [ 11.170699] intel_soc_dts_thermal: request_threaded_irq ret -22 [ 11.190674] intel_rapl: Found RAPL domain package [ 11.190680] intel_rapl: Found RAPL domain core [ 11.324236] [ cut here ] [ 11.324247] WARNING: CPU: 1 PID: 54 at /build/linux-qOmAV7/linux-3.19.0/sound/pci/hda/hda_i915.c:115 snd_hdac_i915_register_notifier+0x35/0x40 [snd_hda_intel]() [ 11.324250] Modules linked in: snd_hda_codec_hdmi intel_rapl snd_hda_codec_realtek snd_hda_codec_generic intel_powerclamp hp_wmi(+) sparse_keymap coretemp snd_hda_intel snd_hda_controller rfkill_gpio kvm_intel uvcvideo kvm crct10dif_pclmul crc32_pclmul videobuf2_vmalloc videobuf2_memops ghash_clmulni_intel videobuf2_core v4l2_common videodev media cryptd joydev serio_raw arc4 btusb bluetooth rtl8723be(OE) rtsx_pci_ms memstick btcoexist(OE) rtl_pci(OE) rtlwifi(OE) mac80211 cfg80211 snd_intel_sst_acpi snd_intel_sst_core snd_soc_sst_mfld_platform snd_hda_codec snd_soc_core wmi snd_compress hp_accel snd_hwdep snd_pcm_dmaengine lis3lv02d i915 snd_pcm input_polldev 8250_fintek dw_dmac dw_dmac_core vi
[Kernel-packages] [Bug 1514785] Re: kernel 3.16.0.52+53 - ip rule repeats all default rules (messing up rule table)
seems to be Ubutu specific, as it did not occur on my pure Debian and CentOS systems so far. -- 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/1514785 Title: kernel 3.16.0.52+53 - ip rule repeats all default rules (messing up rule table) Status in linux-lts-utopic package in Ubuntu: Confirmed Bug description: PBR routing is broken using some kernel versions. Problem occurs on KVM guests and Desktop. lsb_release: Ubutu 14.04.3 LTS Release 14.04 Expected: To have the normal rule table when using 'ip rule show' 0: from all lookup local 32766: from all lookup main 32767: from all lookup default Instead: The 'ip rule show' command is messed up showing lots of repeated rules for local/main/default (did not count them - simply too much) It seems like it stucks within a loop adding/displaying and adding/displaying... but the system is not blocked. A sec prob in my case as it is making policy based routing useless if you need to grep whether your rule exists already. Workaraound: I went back to the 3.16.0.51 series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1514785/+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 1514785] Re: kernel 3.16.0.52+53 - ip rule repeats all default rules (messing up rule table)
I have the same problem in 3.16.0-53. I filed bug #1518715 which may be the same thing. -- 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/1514785 Title: kernel 3.16.0.52+53 - ip rule repeats all default rules (messing up rule table) Status in linux-lts-utopic package in Ubuntu: Confirmed Bug description: PBR routing is broken using some kernel versions. Problem occurs on KVM guests and Desktop. lsb_release: Ubutu 14.04.3 LTS Release 14.04 Expected: To have the normal rule table when using 'ip rule show' 0: from all lookup local 32766: from all lookup main 32767: from all lookup default Instead: The 'ip rule show' command is messed up showing lots of repeated rules for local/main/default (did not count them - simply too much) It seems like it stucks within a loop adding/displaying and adding/displaying... but the system is not blocked. A sec prob in my case as it is making policy based routing useless if you need to grep whether your rule exists already. Workaraound: I went back to the 3.16.0.51 series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1514785/+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 1318111] Re: Adds more and more copies of ‘crashkernel=384M-:128M’ in /etc/default/grub when upgrading or reinstalling grub-pc
replace the content of /etc/default/grub.d/kexec-tools.cfg with: KEXEC_TOAPPEND="crashkernel=384M-:128M" case "$GRUB_CMDLINE_LINUX_DEFAULT" in *$KEXEC_TOAPPEND*) ;; *) GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT $KEXEC_TOAPPEND" ;; esac -- 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/1318111 Title: Adds more and more copies of ‘crashkernel=384M-:128M’ in /etc/default/grub when upgrading or reinstalling grub-pc Status in kexec-tools package in Ubuntu: Confirmed Bug description: # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M" # apt-get install --reinstall grub-pc … # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M crashkernel=384M-:128M" # apt-get install --reinstall grub-pc … # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M" # apt-get install --reinstall grub-pc … # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M" ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: kexec-tools 1:2.0.6-0ubuntu2 Uname: Linux 3.15.0-031500rc4-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.14.2-0ubuntu2 Architecture: amd64 Date: Fri May 9 22:39:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2010-12-05 (1251 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202) SourcePackage: kexec-tools UpgradeStatus: Upgraded to utopic on 2013-10-31 (190 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1318111/+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 1514808] kili (i386) - tests ran: 87, failed: 80
tests ran: 87, failed: 80; http://kernel.ubuntu.com/testing/3.2.0-95.135/kili__3.2.0-95.135__2015-11-12_21-41-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/1514808 Title: linux: 3.2.0-95.135 -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-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta 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: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-95.135 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, 10. November 2015 12:07 UTC kernel-stable-Prepare-package-end:Tuesday, 10. November 2015 19:03 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 10. November 2015 19:03 UTC kernel-stable-Promote-to-proposed-end:Thursday, 12. November 2015 20:40 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Thursday, 12. November 2015 22:00 UTC kernel-stable-Verification-testing-start:Thursday, 12. November 2015 22:00 UTC kernel-stable-Certification-testing-start:Thursday, 12. November 2015 22:00 UTC kernel-stable-Security-signoff-start:Thursday, 12. November 2015 22:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Thursday, 12. November 2015 22:00 UTC kernel-stable-Security-signoff-end:Friday, 13. November 2015 01:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1514808/+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 1499421] Re: kernel panic on boot after upgrade to ubuntu 15.10
Ubuntu Wily crashes on several occasions but intermittantly during boot on my Acer Aspire V15 Nitro. I have the F12 boot menu enabled. This problem also exists when booting from DVD or USB-pendrive. I had these problems from the firsts attempts to run the Live USB or installing a fresh new system. ***No such problems with 15.04.*** What happens is that the boot process ends and the system reboots itself. When not quick enough pressing F12, the system will boot into M$-Windows. Otherwise the F12 boot menu comes up. Today, at the 4th or 5th attempt, Ubuntu came up at last. Some last red lines in syslog.log: Nov 22 11:44:09 jupiter com.canonical.Unity.Scope.Home[1352]: (unity-scope-home:2547): unity-scope-home-WARNING **: platform-info.vala:112: Unable to read SIM properties: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Nov 22 11:44:09 jupiter com.canonical.Unity.Scope.LocalFiles[1352]: (process:2563): unity-files-daemon-WARNING **: folder.vala:65: Failed to read favorites: Failed to open file '/home/theo/.gtk-bookmarks': No such file or directory Nov 22 11:44:10 jupiter com.canonical.Unity.Scope.Home[1352]: (unity-scope-home:2547): Json-CRITICAL **: json_object_get_object_member: assertion 'node != NULL' failed Nov 22 11:44:10 jupiter com.canonical.Unity.Scope.Home[1352]: message repeated 9 times: [ (unity-scope-home:2547): Json-CRITICAL **: json_object_get_object_member: assertion 'node != NULL' failed] Nov 22 11:44:10 jupiter com.canonical.Unity.Scope.Home[1352]: (unity-scope-home:2547): libunity-WARNING **: unity-aggregator-scope.vala:145: Error serializing GVariant with type string 'mv' to the D-Bus wire format Nov 22 11:44:11 jupiter com.canonical.Unity.Scope.Home[1352]: (unity-scope-home:2547): unity-scope-home-WARNING **: scope.vala:849: Remote search failed: Request failed with error 6 Nov 22 11:44:11 jupiter com.canonical.Unity.Scope.Home[1352]: (unity-scope-home:2547): Json-CRITICAL **: json_object_get_object_member: assertion 'node != NULL' failed Nov 22 11:44:11 jupiter com.canonical.Unity.Scope.Home[1352]: message repeated 9 times: [ (unity-scope-home:2547): Json-CRITICAL **: json_object_get_object_member: assertion 'node != NULL' failed] Nov 22 11:44:30 jupiter systemd[1]: Stopping User Manager for UID 119... Nov 22 11:44:30 jupiter systemd[1029]: Stopped target Default. Nov 22 11:44:30 jupiter systemd[1029]: Stopped target Basic System. Nov 22 11:44:30 jupiter systemd[1029]: Stopped target Sockets. Nov 22 11:44:30 jupiter systemd[1029]: Stopped target Paths. Nov 22 11:44:30 jupiter systemd[1029]: Stopped target Timers. Nov 22 11:44:30 jupiter systemd[1029]: Reached target Shutdown. Nov 22 11:44:30 jupiter systemd[1029]: Starting Exit the Session... Nov 22 11:44:30 jupiter systemd[1029]: Received SIGRTMIN+24 from PID 2720 (kill). Nov 22 11:44:30 jupiter systemd[1]: Stopped User Manager for UID 119. Nov 22 11:44:30 jupiter systemd[1]: Removed slice user-119.slice. Attached: a file with kern.log and syslog.log output. ** Attachment added: "Kern.log + Syslog.log files" https://bugs.launchpad.net/ubuntu/wily/+source/linux/+bug/1499421/+attachment/4523480/+files/kern-syslog.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/1499421 Title: kernel panic on boot after upgrade to ubuntu 15.10 Status in linux package in Ubuntu: Confirmed Status in linux source package in Wily: Confirmed Bug description: the installed Kernel in the release upgrade to the development line of ubuntu 15.10 creates a kernel panic on my Lenovo yoga 2 pro the previously isntalled ubuntu 15.04 Kernel does still boot. Ubuntu Release: Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 Expected: Clean Upgrade to 150.10 development branch reboot happend instead: system got updated but dropped to a non responding cmd after a reboot i have a blinking caps lock after selecting an old kernel (and not the 4.2) it boots... ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.6 ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Thu Sep 24 16:55:16 2015 InstallationDate: Installed on 2015-04-25 (152 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-09-24 (0 days ago) To manage notifications about this bug go to: htt
[Kernel-packages] [Bug 1507959] Re: Regression: Kernel update breaks all lxc-containers lxc-start failing with (apparmor="DENIED" operation="mount")
*** This bug is a duplicate of bug 1504781 *** https://bugs.launchpad.net/bugs/1504781 This has been resolved as per suggestion of tapczan in lxc (1.0.7-0ubuntu0.10) on 2015-11-03. ** Package changed: linux (Ubuntu) => lxc (Ubuntu) ** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1507959 Title: Regression: Kernel update breaks all lxc-containers lxc-start failing with (apparmor="DENIED" operation="mount") Status in lxc package in Ubuntu: Fix Released Bug description: Hello, The following recent kernel update completely break our lxc-start usage on precise both with precise original kernel 3.2 + also the trusty-lts-stack using 3.13 After installing those new kernel updates all lxc-start of a container fail with: "Permission denied - mount failed '/dev/pts/ptmx'->'/dev/ptmx'" with strace pointing to: 13695 mount("/dev/pts/ptmx", "/dev/ptmx", 0x7f4d68c85d37, MS_BIND, NULL) = -1 EACCES (Permission denied) and dmesg showing: Oct 20 10:59:00 titan226 kernel: [ 663.508664] type=1400 audit(1445331540.807:29): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="/usr/bin/lxc-start" name="/dev/ptmx" pid=2897 comm="lxc-start" srcname="/dev/pts/ptmx" flags="rw, bind" After downgrading kernel version the problem immediately dissappeared and the lxc-start for containers works again as before. Bad versions: ii linux-image-3.13.0-66-generic3.13.0-66.108~precise1Linux kernel image for version 3.13.0 on 64 bit x86 SMP ii linux-image-3.2.0-92-generic 3.2.0-92.130 Linux kernel image for version 3.2.0 on 64 bit x86 SMP Good versions: ii linux-image-3.13.0-61-generic3.13.0-61.100~precise1Linux kernel image for version 3.13.0 on 64 bit x86 SMP ii linux-image-3.2.0-88-generic 3.2.0-88.126 Linux kernel image for version 3.2.0 on 64 bit x86 SMP From kernel changelog maybe this other issue here maybe causing it but not verified: * SAUCE: (no-up) apparmor: fix mount not handling disconnected paths - LP: #1496430 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-61-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ee5d3bc2-531d-4fbf-ba3f-033c27498274 IwConfig: Error: [Errno 2] No such file or directory MachineType: FUJITSU PRIMERGY MX130 S1 MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-61-generic root=UUID=8c11de07-6403-46cf-994b-15750a7404ba ro rootdelay=80 ProcVersionSignature: Ubuntu 3.13.0-61.100~precise1-generic 3.13.11-ckt22 RelatedPackageVersions: linux-restricted-modules-3.13.0-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.79.18 RfKill: Error: [Errno 2] No such file or directory Tags: precise Uname: Linux 3.13.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/18/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.01.2974.A1 dmi.board.asset.tag: - dmi.board.name: D2974 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D2974-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.chassis.version: MX130S1F dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00R1.01.2974.A1:bd01/18/2011:svnFUJITSU:pnPRIMERGYMX130S1:pvr:rvnFUJITSU:rnD2974:rvrS26361-D2974-A1:cvnFUJITSU:ct3:cvrMX130S1F: dmi.product.name: PRIMERGY MX130 S1 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1507959/+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 1518623] Re: Letters missing in most programs
At some point in previous versions I was thinking it might be caused by having little memory that makes something crash (I had 4GB and Firefox goes to creating Swap very fast if it is used for a while), but now I have 8 GB of memory and I see the bug. Must be some other cause but it is a very bad one. -- 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/1518623 Title: Letters missing in most programs Status in linux package in Ubuntu: Confirmed Bug description: I thought this bug was fixed in Ubuntu 15.04, but now I am having it. It is a nasty bug making Ubuntu useless, I must restart (at least this is how it worked in previous version of Ubuntu) to get my computer back. I do not know if there is a coincidence, but I started Firefox and then the bug was triggered. 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: USERPID ACCESS COMMAND /dev/snd/controlC0: florin 1332 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 21 23:20:15 2015 HibernationDevice: RESUME=UUID=dd1e181e-9b0d-4f4c-ba33-b263484b28ab InstallationDate: Installed on 2015-10-26 (26 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite C650 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=a7de0130-0393-481e-981f-d950f6cc614a ro persistent quiet splash vt.handoff=7 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 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/09/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 2.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.10:bd11/09/2011:svnTOSHIBA:pnSatelliteC650:pvrPSC14E-00400MG5:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite C650 dmi.product.version: PSC14E-00400MG5 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518623/+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