[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Also a test with a latest rc-proposed image and silo 22 (https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-022/) would be great from someone who experience problems here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
Attachment from "sudo thermald --no-daemon --dbus-enable --loglevel=debug | tee thermald.log". ** Attachment added: "A few minutes full load over 30% base load" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+attachment/4457110/+files/thermald-lenovo-W500-2015.09.04.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/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: In Progress Bug description: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+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 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver
I'm using Wily with kernel 4.2 so I can't use Your patch. corrado@corrado-wily2:~/Downloads$ sudo dpkg -i rtbth_3.9.3-patched-1_amd64.deb [sudo] password for corrado: Selecting previously unselected package rtbth. (Reading database ... 217656 files and directories currently installed.) Preparing to unpack rtbth_3.9.3-patched-1_amd64.deb ... Unpacking rtbth (3.9.3-patched-1) ... Setting up rtbth (3.9.3-patched-1) ... depmod: WARNING: could not open /lib/modules/3.19.0-22-generic/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/3.19.0-22-generic/modules.builtin: No such file or directory corrado@corrado-wily2:~/Downloads$ corrado@corrado-wily2:~/Downloads$ uname -a Linux corrado-wily2 4.2.0-7-generic #7-Ubuntu SMP Tue Sep 1 16:43:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux corrado@corrado-wily2:~/Downloads$ -- 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/1189721 Title: Ralink RT3290 doesn't have a bluetooth driver Status in Linux: Unknown Status in Linux Mint: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: As of Raring Ubuntu has a wifi driver for the RT3290 that works out of the box. It still does not have bluetooth support. This thread in the Ubuntu forums links to a driver that is claimed to work: http://ubuntuforums.org/showthread.php?t=2115570 --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graeme 2412 F pulseaudio CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70 InstallationDate: Installed on 2013-05-17 (144 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/06/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.32 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1189721/+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 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544
d3f180ea1a44aecba1b0dab2a253428e77f906bf linux-image-3.19.0-031900-generic_3.19.0-031900.201509032049_amd64.deb is GOOD -- 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/1491467 Title: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544 Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: On Fujitsu A544 laptop (and likely others) fitted with SSD, kworker takes 100% of one core of CPU due to GPE13 interrupt storm See upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=53071 The bug can be identified by repeatedly running cat /sys/firmware/acpi/interrupts/gpe13 where a rapidly increasing count will be seen. Workaround: sudo sh -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe13' disables it until reboot Using sudo crontab -e and adding the line @reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe13 works around for subsequent boots. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: colinl 1699 F pulseaudio /dev/snd/controlC1: colinl 1699 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 2 16:03:19 2015 InstallationDate: Installed on 2014-10-21 (316 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.147 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-08-31 (1 days ago) dmi.bios.date: 04/01/2015 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.19 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd04/01/2015:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1491467/+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 1492113] 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/1492113 Title: Screen freeze when watching video in VLC or Firefox Status in linux package in Ubuntu: Confirmed Bug description: Screen freezes when I watch video in VLC media player or viewing media on browser like Firefox. Moving mouse is of no use and Ctrl + Alt + T short cut does not launch terminal. But I Could hear the audio even after screen freeze. If I press Ctrl + Alt + F1 and wait for several minutes switches to console. I then kill the 100% cpu process (like VLC or Firefox) then switching to GUI (CTRL-ALT-F7) brings back the screen and I am able to work as usual or sometimes returns to login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-generic 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 25483 F pulseaudio /dev/snd/controlC0: john 25483 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 4 02:16:28 2015 HibernationDevice: RESUME=UUID=a2ax-f1b1-x-8bfc-5437xxx InstallationDate: Installed on 2012-11-25 (1012 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. 965P-DS3 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=e1f-8adf-4f5a--02eba23 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-08-21 (378 days ago) dmi.bios.date: 06/25/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: 965P-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/25/2009:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 965P-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492113/+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 1490785] onza (amd64) - tests ran: 180, failed: 1
tests ran: 180, failed: 1; http://kernel.ubuntu.com/testing/onza__3.19.0-28.30~14.04.1__2015-09-04_03-18-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1490785 Title: linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-28.30~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, 01. September 2015 01:02 UTC kernel-stable-master-bug:1490606 kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1490785/+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 1483320] Re: Migrate Broadwell to use i915_bpo
(+bpo2 was the first version with the 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/1483320 Title: Migrate Broadwell to use i915_bpo Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Bug description: There are several bugs affecting Broadwell generation graphics in the vivid kernel (3.19), but not found in 4.2rc which i915_bpo module is based on. In order to support our OEM partners (and other BDW users) it would make sense to migrate BDW to use i915_bpo instead. The known (public) bugs this would fix are: - screen is black after xrandr rotate command https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446979 - changing the VT causes flicker https://bugs.freedesktop.org/show_bug.cgi?id=85583 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450557 - GPU hangs on resume https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1468232 (and dupes, which I believe there are several of) - and some OEM machines can't always hotplug the HDMI output (no public bug AIUI) the migration should not be too risky, since i915_bpo is already used for Braswell which is same generation as (=based on) BDW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483320/+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 1492113] Re: Screen freeze when watching video in VLC or Firefox
** Description changed: Screen freezes when I watch video in VLC media player or viewing media on browser like Firefox. Moving mouse is of no use and Ctrl + Alt + T short cut does not launch terminal. But I Could hear the audio even after screen freeze. If I press Ctrl + Alt + F1 and wait for several minutes switches to console. I then kill the 100% cpu process (like VLC or Firefox) then switching to GUI (CTRL-ALT-F7) brings back the screen and I am able to work as usual or sometimes returns to login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-generic 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: john 25483 F pulseaudio - /dev/snd/controlC0: john 25483 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: john 25483 F pulseaudio + /dev/snd/controlC0: john 25483 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 4 02:16:28 2015 - HibernationDevice: RESUME=UUID=a2a0fdd2-f1b1-4f29-8bfc-5437d8124b13 + HibernationDevice: RESUME=UUID=a2ax-f1b1-x-8bfc-5437xxx InstallationDate: Installed on 2012-11-25 (1012 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) IwConfig: - lono wireless extensions. - - eth0 no wireless extensions. + lono wireless extensions. + + eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. 965P-DS3 ProcFB: - - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=d122ae1f-8adf-4f5a-b6c0-02eba23182e3 ro quiet splash + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=e1f-8adf-4f5a--02eba23 ro quiet splash RelatedPackageVersions: - linux-restricted-modules-3.13.0-63-generic N/A - linux-backports-modules-3.13.0-63-generic N/A - linux-firmware 1.127.15 + linux-restricted-modules-3.13.0-63-generic N/A + linux-backports-modules-3.13.0-63-generic N/A + linux-firmware 1.127.15 RfKill: - + SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-08-21 (378 days ago) dmi.bios.date: 06/25/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: 965P-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/25/2009:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 965P-DS3 dmi.sys.vendor: Gigabyte Technology 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/1492113 Title: Screen freeze when watching video in VLC or Firefox Status in linux package in Ubuntu: New Bug description: Screen freezes when I watch video in VLC media player or viewing media on browser like Firefox. Moving mouse is of no use and Ctrl + Alt + T short cut does not launch terminal. But I Could hear the audio even after screen freeze. If I press Ctrl + Alt + F1 and wait for several minutes switches to console. I then kill the 100% cpu process (like VLC or Firefox) then switching to GUI (CTRL-ALT-F7) brings back the screen and I am able to work as usual or sometimes returns to login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-generic 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 25483 F pulseaudio /dev/snd/controlC0: john 25483 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 4 02:16:28 2015 HibernationDevice: RESUME=UUID=a2ax-f1b1-x-8bfc-5437xxx InstallationDate: Installed on 2012-11-25 (1012 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. 965P-DS3 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=e1f-8adf-4f5a--02eba23 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: SourcePackage: linux
[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
Let's take this one point at a time: * fan not running at full speed in disengaged mode in a thermal emergency - as mentioned earlier, the default fan mode on the machine is to run under firmware control, in which case it runs in engaged mode with a loop feed back controller so it never exceeds a top speed of 3500 RPM. This matches the original thermal design by the manufacturer. So either they made a mistake and all machines like yours overheat (and we would see lots of owners with your machine reporting this bug) or this issue is particular to your machine * CPU not throttling in a thermal emergency (unless the frequency readings are wrong) - that needs investigation as thermald should be doing that (but as I mentioned earlier, I will examine the thermald issues later) * shutting down when supposed to suspend as a reaction to overheat, unnecessarily destroying session - when a critical thermal event occurs one has a very short time window to react. Potentially the silicon may be permanently damaged, so the kernel chooses to power down rather ran try to suspend (since this can get stuck and exacerbate the issue). Without the handling of this thermal event, the next step is for the hardware to physically shut itself down which is out of any form of operating system control, so either way, the machine is desperately trying to save itself from breaking. * destroying session in a shut down/restart cycle (I heard rumours this may be fixed later in Snappy with containers) - again, in a rush to save your silicon from becoming irreparably damaged shutdown is the fastest mechanism. Snappy containers will not help. I'd recommend reading https://en.wikipedia.org/wiki/Thermal_design_power, there is paragraph that states: "Most modern processors will cause a therm-trip only upon a catastrophic cooling failure, such as a no longer operational fan or an incorrectly mounted heatsink." So, the next step will be to see if we can see what thermald is doing. 1. Stop thermald so we can re-enable it with full debug on: sudo systemctl stop thermald (if you are using systemd) or sudo service thermald stop (if you are using upstart) 2. Run thermald for a while from the command line and capture debug output: sudo thermald --no-daemon --dbus-enable --loglevel=debug | tee thermald.log ..run this say for 5-10 minutes and use your machine, then attach the thermald.log to the bug report 3. Re-start themrald sudo systemctl start thermald (if you are using systemd) or sudo service thermald start (if you are using upstart) -- 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/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: In Progress Bug description: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware
[Kernel-packages] [Bug 1492113] [NEW] Screen freeze when watching video in VLC or Firefox
Public bug reported: Screen freezes when I watch video in VLC media player or viewing media on browser like Firefox. Moving mouse is of no use and Ctrl + Alt + T short cut does not launch terminal. But I Could hear the audio even after screen freeze. If I press Ctrl + Alt + F1 and wait for several minutes switches to console. I then kill the 100% cpu process (like VLC or Firefox) then switching to GUI (CTRL-ALT-F7) brings back the screen and I am able to work as usual or sometimes returns to login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-generic 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 25483 F pulseaudio /dev/snd/controlC0: john 25483 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 4 02:16:28 2015 HibernationDevice: RESUME=UUID=a2ax-f1b1-x-8bfc-5437xxx InstallationDate: Installed on 2012-11-25 (1012 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. 965P-DS3 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=e1f-8adf-4f5a--02eba23 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-08-21 (378 days ago) dmi.bios.date: 06/25/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: 965P-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/25/2009:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 965P-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 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/1492113 Title: Screen freeze when watching video in VLC or Firefox Status in linux package in Ubuntu: New Bug description: Screen freezes when I watch video in VLC media player or viewing media on browser like Firefox. Moving mouse is of no use and Ctrl + Alt + T short cut does not launch terminal. But I Could hear the audio even after screen freeze. If I press Ctrl + Alt + F1 and wait for several minutes switches to console. I then kill the 100% cpu process (like VLC or Firefox) then switching to GUI (CTRL-ALT-F7) brings back the screen and I am able to work as usual or sometimes returns to login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-63-generic 3.13.0-63.103 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 25483 F pulseaudio /dev/snd/controlC0: john 25483 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 4 02:16:28 2015 HibernationDevice: RESUME=UUID=a2ax-f1b1-x-8bfc-5437xxx InstallationDate: Installed on 2012-11-25 (1012 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. 965P-DS3 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=e1f-8adf-4f5a--02eba23 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-63-generic N/A linux-backports-modules-3.13.0-63-generic N/A linux-firmware 1.127.15 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-08-21 (378 days ago) dmi.bios.date: 06/25/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: 965P-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/25/2009:svnGigabyteTechnologyCo.,Ltd.:pn965P-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965P-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 965P-DS3 dmi.sys.vendor: Gigabyte Techn
[Kernel-packages] [Bug 1483320] Re: Migrate Broadwell to use i915_bpo
Tested with the test kernel -27.29+bpo2.0, the vga external only issue is fixed. -- 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/1483320 Title: Migrate Broadwell to use i915_bpo Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Bug description: There are several bugs affecting Broadwell generation graphics in the vivid kernel (3.19), but not found in 4.2rc which i915_bpo module is based on. In order to support our OEM partners (and other BDW users) it would make sense to migrate BDW to use i915_bpo instead. The known (public) bugs this would fix are: - screen is black after xrandr rotate command https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446979 - changing the VT causes flicker https://bugs.freedesktop.org/show_bug.cgi?id=85583 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450557 - GPU hangs on resume https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1468232 (and dupes, which I believe there are several of) - and some OEM machines can't always hotplug the HDMI output (no public bug AIUI) the migration should not be too risky, since i915_bpo is already used for Braswell which is same generation as (=based on) BDW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483320/+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 1483320] Re: Migrate Broadwell to use i915_bpo
commit 6fa2d197936ba0b8936e813d0adecefac160062b Author: Ander Conselvan de Oliveira Date: Mon Aug 31 11:23:28 2015 +0300 i915: Set ddi_pll_sel in DP MST path in upstream drm-intel-next-fixes fixed this regression. This is included on the -27.29+bpo2.2 build available here: http://koti.kapsi.fi/~tjaalton/skl/ -- 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/1483320 Title: Migrate Broadwell to use i915_bpo Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: In Progress Bug description: There are several bugs affecting Broadwell generation graphics in the vivid kernel (3.19), but not found in 4.2rc which i915_bpo module is based on. In order to support our OEM partners (and other BDW users) it would make sense to migrate BDW to use i915_bpo instead. The known (public) bugs this would fix are: - screen is black after xrandr rotate command https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446979 - changing the VT causes flicker https://bugs.freedesktop.org/show_bug.cgi?id=85583 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450557 - GPU hangs on resume https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1468232 (and dupes, which I believe there are several of) - and some OEM machines can't always hotplug the HDMI output (no public bug AIUI) the migration should not be too risky, since i915_bpo is already used for Braswell which is same generation as (=based on) BDW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1483320/+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 1489501] Re: [i915_bpo] Sync to v4.2-rc8
** Summary changed: - [i915_bpo] Sync to v4.2-rc6 + [i915_bpo] Sync to v4.2-rc8 -- 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/1489501 Title: [i915_bpo] Sync to v4.2-rc8 Status in linux package in Ubuntu: In Progress Bug description: A handful of fixes made it upstream. Need to revert a sauce commit first so that another revert can be applied. ed63baaf849e91c drm/i915: Avoid TP3 on CHV 5e86dfe39f54ab1 drm/i915: remove HBR2 from chv supported list 33747cc5ec03603 Revert "drm/i915: Add eDP intermediate frequencies for CHV" bf1a5fd2eccf20b Revert "drm/i915: Allow parsing of variable size child device entries from VBT" 903ecd0bb970438 drm/i915: Flag the execlists context object as dirty after every use d2944cf21305c75 drm/i915: Commit planes on each crtc separately. f0fdc55db0c6f76 drm/i915: calculate primary visibility changes instead of calling from set_config e8fa4270536de2e drm/i915: Only dither on 6bpc panels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1489501/+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 1491988] Re: 15.10: Multiple Bluetooth controllers not found
Can you please do the following to generate a more verbose output: $ sudo systemctl stop bluetooth $ MGMT_DEBUG=1 sudo bluetoothd -n -d &> bluetoothd-multiple-adapters.log In another terminal: $ bluetoothctl [bluetooth]# list Please add all output here and attach the file bluetoothd-multiple- adapters.log ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1491988 Title: 15.10: Multiple Bluetooth controllers not found Status in bluez package in Ubuntu: Incomplete Bug description: $ hcitool dev Devices: hci100:10:7A:4D:15:33 hci000:1F:3A:E0:0A:AF $ hcitool -i hci1 scan Scanning ... 00:0A:95:4B:BD:C2 Apple Wireless Keyboard $ sudo systemctl restart bluetooth $ journalctl -u bluetooth | grep adapter_service_add Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: src/adapter.c:adapter_service_add() /org/bluez/hci0 $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard [bluetooth]# list Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 728733] Re: fan only works when my acer 5315 is booted then stops
[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/728733 Title: fan only works when my acer 5315 is booted then stops Status in linux package in Ubuntu: Expired Bug description: Binary package hint: acpi fan only works when my acer 5315 is booted then stops.i have a acer aspire 5315 laptop. My fan stopped working after installing ubuntu from vista. ive changed it for a new one and still the same problem. no dust aswel. please help ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: acpi 1.5-2 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Thu Mar 3 22:18:12 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: acpi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/728733/+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 1454944] Re: [Lenovo T450] fwts high failues were found.
[Expired for linux-lts-utopic (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-lts-utopic (Ubuntu) Status: Incomplete => Expired -- 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/1454944 Title: [Lenovo T450] fwts high failues were found. Status in HWE Next: Won't Fix Status in linux-lts-utopic package in Ubuntu: Expired Bug description: CID : 201502-16842 Lenovo T450 Steps: 1. Install ubuntu14.04.2 on Lenovo T450. 2. Install Plainbox. 3. Execute canonical-certifcation-client, 4. Select test case 'firmware/fwts_desktop_diagnosis' 5. Execute the test. Actual result: There are some errors in fwts log, please refer to fwts logs in attachment. Expect result: Test case execute smoothly, there is no error in fwts log. --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1655 F pulseaudio /dev/snd/controlC0: u 1655 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=01240a83-2e9e-4951-8c40-94b759934ce3 InstallationDate: Installed on 2015-05-11 (3 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 20BUZ0BTUS Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=18c52354-b721-4d40-b110-39737086d3d1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.16.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/03/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET45WW (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BUZ0BTUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET45WW(1.10):bd02/03/2015:svnLENOVO:pn20BUZ0BTUS:pvrThinkPadT450:rvnLENOVO:rn20BUZ0BTUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BUZ0BTUS dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1454944/+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 1300557] Re: Screen resolution no longer works
Hello? Any corrections for that revisions range you wanted me to bisect? -- 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/1300557 Title: Screen resolution no longer works Status in linux package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1300557/+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 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
I can't see how that information could be helpful in fixing the problem. It doesn't matter whether there's a common hardware ailment involved in this particular overheating or not. The software is acting like an idiot and wasting all its chances to remedy the situation: -fan not running at full speed in disengaged mode in a thermal emergency -CPU not throttling in a thermal emergency (unless the frequency readings are wrong) -shutting down when supposed to suspend as a reaction to overheat, unnecessarily destroying session -destroying session in a shut down/restart cycle (I heard rumours this may be fixed later in Snappy with containers) -- 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/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: In Progress Bug description: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
@Joseph Thank you. I upgraded the production server that is most often errors out with the Wily kernel you referenced above and will report back Please be patient, an individual VM can go several days without the error. -- 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/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1490606] onza (i386) - tests ran: 170, failed: 1
tests ran: 170, failed: 1; http://kernel.ubuntu.com/testing/onza__3.19.0-28.30__2015-09-03_19-01-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/1490606 Title: linux: 3.19.0-28.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-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: 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 Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1490606/+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 1463164] Re: Broadcom bcm43xx WiFI works with Fedora, why not Ubuntu?
Update: The source of the free firmware in Fedora appears to be this package: https://apps.fedoraproject.org/packages/b43-openfwwf Would it be possible to get this marked for inclusion in 15.10? ** Also affects: firmware-nonfree (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1463164 Title: Broadcom bcm43xx WiFI works with Fedora, why not Ubuntu? Status in b43-fwcutter package in Ubuntu: New Status in firmware-nonfree package in Ubuntu: New Bug description: Hi, I run Ubuntu on an older Dell laptop with Broadcom bcm4312 WiFI. Basically, it doesn't work out of the box with Ubuntu, and it is extremely complicated to configure without access to the Internet (when a LAN connection is not available), which is a frequent problem when the WiFI isn't working. It requires these unfriendly instructions to get it working: https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx Fedora 22, on the other hand, works out of the box on this same machine. So, if Fedora 22, with its paranoid insistence on only free software, is able to make this work out of the box, why can't Ubuntu? "Linux for human beings" is looking more like Fedora in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1463164/+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 1490785] tarf (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/tarf__3.19.0-28.30~14.04.1__2015-09-04_00-27-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1490785 Title: linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-28.30~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, 01. September 2015 01:02 UTC kernel-stable-master-bug:1490606 kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1490785/+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 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver
@alexandre-mbm I followed the instructions (these two ones) from your coment: https://github.com/alexandre-mbm/rt3290/wiki/Checkinstall I'm able to see devices, and when I try to pair both devices (laptop and phone) will give me the same paircode, but after clicking "It matches" it'll fail to pair, leaving bt unusable with a padlock in the icon tray. I'd like to provide you logs in order to fix it. Tell me if you want some logs. -- 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/1189721 Title: Ralink RT3290 doesn't have a bluetooth driver Status in Linux: Unknown Status in Linux Mint: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: As of Raring Ubuntu has a wifi driver for the RT3290 that works out of the box. It still does not have bluetooth support. This thread in the Ubuntu forums links to a driver that is claimed to work: http://ubuntuforums.org/showthread.php?t=2115570 --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graeme 2412 F pulseaudio CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70 InstallationDate: Installed on 2013-05-17 (144 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/06/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.32 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1189721/+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 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
A few weeks ago I installed xubuntu 15.04 on my computer, without this bug. After hearing about 15.10 beta 1 being released I decided to wipe the partiton and start from scratch. sudo update-grub revealed this bug. I tried installing 15.10 beta 1 again, same bug. I then decided to use the 15.04 netinstall and then install the 15.10 packages over it. Same bug. Finally, I installed 15.04 netinstall without doing the 15.10 upgrade, and I still have the same bug. What Happened? -- 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/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in os-prober package in Ubuntu: Confirmed Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108]
[Kernel-packages] [Bug 1454758] Re: [Hyper-V] storvsc: Set the SRB flags correctly when no data transfer is needed
The add to my last comment, other prerequisits were also required to get a cherry-pick of commit dc45708c. The following commits were needed: 610071c38, 37f7278b8, eafa7072e and 8b612fa23 -- 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/1454758 Title: [Hyper-V] storvsc: Set the SRB flags correctly when no data transfer is needed Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: In Progress Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Bug description: The following critical bugfix has been accepted into the upstream kernel. It is needed for 15.10, 15.02, 14.10, 14.04 and 14.04 HWE (and, by extension, 12.04 and 12.04 HWE). We have seen IHV drivers in the field throw errors and time out due to receiving SRB flags set when no data transfer is expected. storvsc: Set the SRB flags correctly when no data transfer is needed Set the SRB flags correctly when there is no data transfer. Without this change some IHV drivers will fail valid commands such as TEST_UNIT_READY. Commit http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=dc45708ca9988656d706940df5fd102672c5de92 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454758/+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 1484799] Re: CVE-2015-5707
This has not been committed to the linux-lts-utopic backport branch yet. ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: Fix Committed => Triaged ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: Triaged => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1484799 Title: CVE-2015-5707 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package
[Kernel-packages] [Bug 1490606] tarf (i386) - tests ran: 170, failed: 2
tests ran: 170, failed: 2; http://kernel.ubuntu.com/testing/tarf__3.19.0-28.30__2015-09-03_15-42-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/1490606 Title: linux: 3.19.0-28.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-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: 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 Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1490606/+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 1491494] Re: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile
** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- 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/1491494 Title: Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed from profile Status in linux package in Ubuntu: Triaged Bug description: -- Problem Description -- The failure related to the BELL-3 (2 port-Async EIA-232 adapter). Ubuntu always hit exception when the adapter is not present. See my test scenarios below. Test #1: Boot Ubuntu with BELL-3 adapter === - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on the LPAR. => Ubuntu boot fine this time. Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile === - I powered down the Ubuntu partition and removed the BELL-3 adapter from LPAR profile then powered on the LPAR. => Ubuntu hit the exception. Elapsed time since release of system processors: 0 mins 9 secs error: no suitable video mode found. OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2) Detected machine type: 0101 Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7 memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0b42 alloc_top: 1000 alloc_top_hi : 1000 rmo_top : 1000 ram_top : 1000 instantiating rtas at 0x0ecb... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0b43 -> 0x0b4316b1 Device tree struct 0x0b44 -> 0x0b47 Calling quiesce... returning from prom_init -> smp_release_cpus() spinning_secondaries = 15 <- smp_release_cpus() <- setup_system() [0.661510] /build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through [4.658302] device-mapper: table: 252:0: multipath: error getting device [4.691990] device-mapper: table: 252:0: multipath: error getting device [4.934034] device-mapper: table: 252:0: multipath: error getting device [4.951977] device-mapper: table: 252:0: multipath: error getting device * Discovering and coalescing multipaths... [ OK ] Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd * Starting AppArmor profiles[ OK ] Loading the saved-state of the serial devices... [5.109665] Unable to handle kernel paging request for data at address 0xd803 [5.109677] Faulting instruction address: 0xc060fec4 [5.109685] Oops: Kernel access of bad area, sig: 11 [#1] [5.109691] SMP NR_CPUS=2048 NUMA pSeries [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) mlx4_core(OE) mlx_compat(OE) [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G OE 3.19.0-23-generic #24~14.04.1-Ubuntu [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: c000f0528000 [5.109777] NIP: c060fec4 LR: c0617498 CTR: c060fe20 [5.109785] REGS: c000f052b6b0 TRAP: 0300 Tainted: G OE (3.19.0-23-generic) [5.109793] MSR: 80009033 CR: 84002022 XER: [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 SOFTE: 1 GPR00: c0617498 c000f052b930 c144c700 00bf GPR04: d803 00bf c000f399 0141 GPR08: c0611d20 c13539e0 d800 c1351ba8 GPR12: c060fe20 ce830900 GPR16: GPR20: 007d 0040 00
[Kernel-packages] [Bug 1489318] Re: CVE-2015-6526
** Changed in: linux (Ubuntu Precise) Status: New => Fix Committed ** Description changed: - Description needed + The perf_callchain_user_64 function in arch/powerpc/perf/callchain.c in + the Linux kernel before 4.0.2 on ppc64 platforms allows local users to + cause a denial of service (infinite loop) via a deep 64-bit userspace + backtrace. Break-Fix: - 9a5cbce421a283e6aea3c4007f141735bf9da8c3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1489318 Title: CVE-2015-6526 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-f
Re: [Kernel-packages] [Bug 1437988] Re: 10ec:8179 wireless network and browser issues
No I've still had problems with disconnects. On Sep 3, 2015 4:25 PM, "TJ" wrote: > So it seems since reconfiguring the Access Point to use mode 'auto' and > channel 'auto' the poor performace has been cured? > > The disconnect you report looks to be isolated: > > Aug 31 18:00:00 Saria-Lin kernel: [ 7467.759694] wlan0: deauthenticating > from 00:25:9c:9d:47:37 by local choice (Reason: 3=DEAUTH_LEAVING) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1437988 > > Title: > 10ec:8179 wireless network and browser issues > > Status in linux package in Ubuntu: > In Progress > > Bug description: > My wireless adapter connecting to my Linsksys wrt120N (firmware > version 1.0.07) that constantly drops, only when running Ubuntu. Also > no matter which browser I use it will arbitrarily max out the CPU > usage and lock me up at times. > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: linux-image-3.13.0-48-generic 3.13.0-48.80 > ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 > Uname: Linux 3.13.0-48-generic x86_64 > ApportVersion: 2.14.1-0ubuntu3.7 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: karl 2708 F pulseaudio >/dev/snd/controlC1: karl 2708 F pulseaudio > CurrentDesktop: Unity > Date: Sun Mar 29 22:45:34 2015 > HibernationDevice: RESUME=UUID=e720cd76-77cb-4087-bfcc-876f10ecb858 > InstallationDate: Installed on 2015-02-13 (44 days ago) > InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 > (20140722.2) > Lsusb: >Bus 001 Device 002: ID 8087:8000 Intel Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 002 Device 002: ID 0c45:6516 Microdia >Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Hewlett-Packard HP 15 Notebook PC > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic.efi.signed > root=UUID=fd43416e-9f3d-47f8-826d-37ffc7fdf565 ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-3.13.0-48-generic N/A >linux-backports-modules-3.13.0-48-generic N/A >linux-firmware 1.127.11 > RfKill: >0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/25/2014 > dmi.bios.vendor: Insyde > dmi.bios.version: F.04 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 8014 > dmi.board.vendor: Hewlett-Packard > dmi.board.version: 10.02 > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnInsyde:bvrF.04:bd08/25/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn8014:rvr10.02:cvnHewlett-Packard:ct10:cvrChassisVersion: > dmi.product.name: HP 15 Notebook PC > dmi.product.version: 097412405F0620180 > dmi.sys.vendor: Hewlett-Packard > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437988/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1437988 Title: 10ec:8179 wireless network and browser issues Status in linux package in Ubuntu: In Progress Bug description: My wireless adapter connecting to my Linsksys wrt120N (firmware version 1.0.07) that constantly drops, only when running Ubuntu. Also no matter which browser I use it will arbitrarily max out the CPU usage and lock me up at times. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-48-generic 3.13.0-48.80 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: karl 2708 F pulseaudio /dev/snd/controlC1: karl 2708 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 22:45:34 2015 HibernationDevice: RESUME=UUID=e720cd76-77cb-4087-bfcc-876f10ecb858 InstallationDate: Installed on 2015-02-13 (44 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0c45:6516 Microdia Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/b
[Kernel-packages] [Bug 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544
I built the next test kernel, up to the following commit: d3f180ea1a44aecba1b0dab2a253428e77f906bf The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1491467 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- 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/1491467 Title: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544 Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: On Fujitsu A544 laptop (and likely others) fitted with SSD, kworker takes 100% of one core of CPU due to GPE13 interrupt storm See upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=53071 The bug can be identified by repeatedly running cat /sys/firmware/acpi/interrupts/gpe13 where a rapidly increasing count will be seen. Workaround: sudo sh -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe13' disables it until reboot Using sudo crontab -e and adding the line @reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe13 works around for subsequent boots. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: colinl 1699 F pulseaudio /dev/snd/controlC1: colinl 1699 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 2 16:03:19 2015 InstallationDate: Installed on 2014-10-21 (316 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.147 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-08-31 (1 days ago) dmi.bios.date: 04/01/2015 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.19 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd04/01/2015:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1491467/+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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
@ubuntu Is it possible for you to test the latest Wily kernel? The Wily kernel has been rebased to the upstream 4.2 kernel, so it should have all the latest Hyper-V updates in mainline. The Wily kernel can be downloaded from: https://launchpad.net/ubuntu/+source/linux/4.2.0-7.7/+build/7856238 -- 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/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
hello this helped me out. sudo apt-get purge pulseaudio-module-bluetooth bluetooth bluez-* bluez sudo apt-get install blueman bluez pulseaudio-module-bluetooth --install-suggests pactl load-module module-bluetooth-discover found here -> http://firstdoit.com/quick-tip-bluetooth-a2dp-on-linux- mint-17-qiana-mate/?utm_source=blog.gadr.me but works on Ubuntu 14.04 perfect (for me) .. good luck -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+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 1492007] Re: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration canno
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1492007 Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half- installed') Status in linux package in Ubuntu: Incomplete Bug description: The system came apart after I used BleachBit (root) and opted to clean the system. I had no desktop (xfce4) but managed to get it back ok. Tried using Computer Janitor to remove old packages to make room on /boot for upgrades. Now system is (may be) down on next re-boot. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.79 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2076 F pulseaudio Date: Thu Sep 3 20:24:34 2015 DuplicateSignature: package:linux-image-extra-3.13.0-46-generic:3.13.0-46.79:package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=UUID=8292c581-0794-4d64-8b76-dd50aee7d9a9 InstallationDate: Installed on 2015-02-25 (189 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: MICRO-STAR INTERNATIONAL CO., LTD KM266-8235 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2003 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-6738 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/22/2003:svnMICRO-STARINTERNATIONALCO.,LTD:pnKM266-8235:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6738:rvr:cvn:ct3:cvr: dmi.product.name: KM266-8235 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492007/+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 1489314] Re: CVE-2015-6252
** Changed in: linux (Ubuntu Precise) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1489314 Title: CVE-2015-6252 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in Wily: New Status in linux-lts-backport-natty source package in Wily: New Status in linux-lts-quantal source package in
[Kernel-packages] [Bug 1484799] Re: CVE-2015-5707
** Changed in: linux (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1484799 Title: CVE-2015-5707 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Committed Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-fsl-imx51 source package in Wily: Invalid Status in linux-goldfish source package in Wily: New Status in linux-lts-backport-maverick source package in
[Kernel-packages] [Bug 1469829] Comment bridged from LTC Bugzilla
--- Comment From cdead...@us.ibm.com 2015-09-03 20:26 EDT--- *** Bug 125891 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1469829 Title: ppc64el should use 'deadline' as default io scheduler Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Bug description: [Impact] Using cfq instead of deadline as the default io scheduler starves certain workloads and causes performance issues. In addition every other arch we build uses deadline as the default scheduler. [Fix] Change the configuration to the following for ppc64el: CONFIG_DEFAULT_DEADLINE=y CONFIG_DEFAULT_IOSCHED="deadline" [Test Case] Boot and cat /sys/block/*/queue/scheduler to see if deadline is being used. -- -- Problem Description -- Firestone system given to DASD group failed HTX overnight test with miscompare error. HTX mdt.hdbuster was running on secondary drive and failed about 12 hours into test HTX miscompare analysis: -== Device under test: /dev/sdb Stanza running: rule_3 miscompare offset: 0x40 Transfer size: Random Size LBA number: 0x70fc miscompare length: all the blocks in the transfer size *- STANZA 3: Creates number of threads twice the queue depth. Each thread -* *- doing 2 num_oper with RC operation with xfer size between 1 block -* *- to 256K.-* This miscompare shows read operation is unable to get the expected data from the disk. The re-read buffer also shows the same data as the first read operation. Since the first read and next re-read shows same data, there could be a write operation (of previous rule stanza to initialize disk with pattern 007 ) failure on the disk. The same miscompare behavior shows for all the blocks in the transfer size. /dev/sdb Jun 2 02:29:43 2015 err=03b6 sev=2 hxestorage <<=== device name (/dev/sdb) rule_3_13 numopers= 2 loop= 767 blk=0x70fc len=89088 min_blkno=0 max_blkno=0x74706daf, RANDOM access Seed Values= 37303, 290, 23235 Data Pattern Seed Values = 37303, 291, 23235 BWRC LBA fencepost Detail: th_nummin_lba max_lba status 0 01c9be3ffR 1 1d1c1b6c3a3836d7F 2 3a3836d857545243F 3 5754524474706dafF Miscompare at buffer offset 64 (0x40) <<=== miscompare offset (0x40) (Flags: badsig=0; cksum=0x6) Maximum LBA = 0x74706daf wbuf (baseaddr 0x3ffe1c0e6600) b0ff rbuf (baseaddr 0x3ffe1c0fc400) 850100fc700200fd700300fe700400ff7005 Write buffer saved in /tmp/htxsdb.wbuf1 Read buffer saved in /tmp/htxsdb.rbuf1 Re-read fails compare at offset64; buffer saved in /tmp/htxsdb.rerd1 errno: 950(Unknown error 950) Asghar reproduced that HTX hang he is seeing. Looking in the kernel logs I see some messages from the kernel that there are user threads blocked on getting reads serviced. So likely HTX is seeing the same thing. I've asked Asghar to try using the deadline I/O scheduler rather than CFQ to see if that makes any difference. If that does not make any difference, the next thing to try is reducing the queue depth of the device. Right now its 31, which I think is pretty high. Step 1: echo deadline > /sys/block/sda/queue/scheduler echo deadline > /sys/block/sdb/queue/scheduler If that reproduces the issue, go to step 2: echo cfq > /sys/block/sda/queue/scheduler echo cfq > /sys/block/sdb/queue/scheduler echo 8 > /sys/block/sda/device/queue_depth echo 8 > /sys/block/sdb/device/queue_depth Breno - it looks like the default I/O scheduler + default queue depth for the SATA disks in Firestone is not optimal, in that when running a heavy I/O workload, we see read starvation occurring, which is making the system nearly unusable. Once we changed the I/O scheduler from cfq to deadline, all the issues went away and the system is able to run the same workload yet still be responsive. Suggest we either encourage Canonical to change the default I/O scheduler to deadline or at the very least provide documentation to encourage our customers to make this change themselves. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post t
[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Patch added: "wily_bcmwl_6.30.223.248+bdcom-0ubuntu4.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4457002/+files/wily_bcmwl_6.30.223.248%2Bbdcom-0ubuntu4.1.debdiff ** Description changed: + [Impact] + + * bcmwl does not compile on new kernels (or HWE kernels) + * bcmwl suffers from null reference bug + + [Test Case] + + * public PPA provided to community and feedback + * based on patch available to other distros + * comment #42 + + [Regression Potential] + + * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) + * for the null reference change -> proved to fix problem for community based on feedback + + [Other Info] + + Original bug description: + The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in Dell Sputnik: Confirmed Status in bcmwl package in Ubuntu: In Progress Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+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 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
I've subscribed Ubuntu Sponsors team seeking for sponsorship on Precise (Updates), Trusty, Vivid and Wily fixes (attached to this case). Let me know if I can assist with anything else. Best Regards Rafael Tinoco -- 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/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in Dell Sputnik: Confirmed Status in bcmwl package in Ubuntu: In Progress Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+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 1484797] Re: CVE-2015-5706
** Description changed: - [Use-after-free in path lookup] + Use-after-free vulnerability in the path_openat function in fs/namei.c + in the Linux kernel 3.x and 4.x before 4.0.4 allows local users to cause + a denial of service or possibly have unspecified other impact via + O_TMPFILE filesystem operations that leverage a duplicate cleanup + operation. Break-Fix: 60545d0d4610b02e55f65d141c95b18ccf855b6e f15133df088ecadd141ea1907f2c96df67c729f0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1484797 Title: CVE-2015-5706 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: Invalid Status in linux-manta source package in Vivid: Invalid Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-arm
[Kernel-packages] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Patch added: "vivid-bcmwl_6.30.223.248+bdcom-0ubuntu2.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4457001/+files/vivid-bcmwl_6.30.223.248%2Bbdcom-0ubuntu2.1.debdiff -- 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/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in Dell Sputnik: Confirmed Status in bcmwl package in Ubuntu: In Progress Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+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 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Patch added: "precise-updates_bcmwl_6.30.223.248+bdcom-0ubuntu0.0.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4456999/+files/precise-updates_bcmwl_6.30.223.248%2Bbdcom-0ubuntu0.0.3.debdiff -- 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/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in Dell Sputnik: Confirmed Status in bcmwl package in Ubuntu: In Progress Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+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 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Patch added: "trusty_bcmwl_6.30.223.248+bdcom-0ubuntu0.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4457000/+files/trusty_bcmwl_6.30.223.248%2Bbdcom-0ubuntu0.2.debdiff -- 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/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in Dell Sputnik: Confirmed Status in bcmwl package in Ubuntu: In Progress Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+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 1437988] Re: 10ec:8179 wireless network and browser issues
So it seems since reconfiguring the Access Point to use mode 'auto' and channel 'auto' the poor performace has been cured? The disconnect you report looks to be isolated: Aug 31 18:00:00 Saria-Lin kernel: [ 7467.759694] wlan0: deauthenticating from 00:25:9c:9d:47:37 by local choice (Reason: 3=DEAUTH_LEAVING) -- 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/1437988 Title: 10ec:8179 wireless network and browser issues Status in linux package in Ubuntu: In Progress Bug description: My wireless adapter connecting to my Linsksys wrt120N (firmware version 1.0.07) that constantly drops, only when running Ubuntu. Also no matter which browser I use it will arbitrarily max out the CPU usage and lock me up at times. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-48-generic 3.13.0-48.80 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: karl 2708 F pulseaudio /dev/snd/controlC1: karl 2708 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 22:45:34 2015 HibernationDevice: RESUME=UUID=e720cd76-77cb-4087-bfcc-876f10ecb858 InstallationDate: Installed on 2015-02-13 (44 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0c45:6516 Microdia Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic.efi.signed root=UUID=fd43416e-9f3d-47f8-826d-37ffc7fdf565 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-48-generic N/A linux-backports-modules-3.13.0-48-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8014 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.02 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd08/25/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn8014:rvr10.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437988/+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 1481039] Re: CVE-2015-5697
** Description changed: - [information leak in md driver] + The get_bitmap_file function in drivers/md/md.c in the Linux kernel + before 4.1.6 does not initialize a certain bitmap data structure, which + allows local users to obtain sensitive information from kernel memory + via a GET_BITMAP_FILE ioctl call. Break-Fix: - b6878d9e03043695dbf3fa1caa6dfc09db225b16 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1481039 Title: CVE-2015-5697 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Committed Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source package in Wily: Invalid Status in linux-flo
[Kernel-packages] [Bug 1478826] Re: CVE-2015-5157
** Description changed: - An NMI that interrupts userspace and encounters an IRET fault is - incorrectly handled. + arch/x86/entry/entry_64.S in the Linux kernel before 4.1.6 on the x86_64 + platform mishandles IRET faults in processing NMIs that occurred during + userspace execution, which might allow local users to gain privileges by + triggering an NMI. Break-Fix: - 9b6e6a8334d56354853f9c255d1395c2ba570e0a -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1478826 Title: CVE-2015-5157 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Invalid Status in linux-armadaxp source package in Wily: Invalid Status in linux-ec2 source pa
[Kernel-packages] [Bug 1472165] Re: CVE-2015-5366
** Description changed: - [Linux UDP checksum DoS EGAIN part] + The (1) udp_recvmsg and (2) udpv6_recvmsg functions in the Linux kernel + before 4.0.6 provide inappropriate -EAGAIN return values, which allows + remote attackers to cause a denial of service (EPOLLET epoll application + read outage) via an incorrect checksum in a UDP packet, a different + vulnerability than CVE-2015-5364. Break-Fix: - beb39db59d14990e401e235faf66a6b9b31240b0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1472165 Title: CVE-2015-5366 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Sta
[Kernel-packages] [Bug 1472160] Re: CVE-2015-5364
** Description changed: - [Linux UDP checksum DoS] + The (1) udp_recvmsg and (2) udpv6_recvmsg functions in the Linux kernel + before 4.0.6 do not properly consider yielding a processor, which allows + remote attackers to cause a denial of service (system hang) via + incorrect checksums within a UDP packet flood. Break-Fix: - beb39db59d14990e401e235faf66a6b9b31240b0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1472160 Title: CVE-2015-5364 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux so
[Kernel-packages] [Bug 1492007] BOT: Examined VarLogDistupgradeApttermlog.gz
done dpkg: error processing package linux-image-extra-3.13.0-46-generic (--configure): package linux-image-extra-3.13.0-46-generic is not ready for configuration ** Tags added: varlogdistupgradeapttermlog-examined -- 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/1492007 Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half- installed') Status in linux package in Ubuntu: Confirmed Bug description: The system came apart after I used BleachBit (root) and opted to clean the system. I had no desktop (xfce4) but managed to get it back ok. Tried using Computer Janitor to remove old packages to make room on /boot for upgrades. Now system is (may be) down on next re-boot. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.79 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2076 F pulseaudio Date: Thu Sep 3 20:24:34 2015 DuplicateSignature: package:linux-image-extra-3.13.0-46-generic:3.13.0-46.79:package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=UUID=8292c581-0794-4d64-8b76-dd50aee7d9a9 InstallationDate: Installed on 2015-02-25 (189 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: MICRO-STAR INTERNATIONAL CO., LTD KM266-8235 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2003 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-6738 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/22/2003:svnMICRO-STARINTERNATIONALCO.,LTD:pnKM266-8235:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6738:rvr:cvn:ct3:cvr: dmi.product.name: KM266-8235 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492007/+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 1490606] Re: linux: 3.19.0-28.30 -proposed tracker
** Description changed: This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC + kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20:00 UTC -- 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/1490606 Title: linux: 3.19.0-28.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-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: 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 Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1490606/+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 1490785] Re: linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker
** Description changed: This bug is for tracking the 3.19.0-28.30~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, 01. September 2015 01:02 UTC kernel-stable-master-bug:1490606 kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC + kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1490785 Title: linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-28.30~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, 01. September 2015 01:02 UTC kernel-stable-master-bug:1490606 kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-end:Thursday, 03. September 2015 20:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1490785/+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 1492007] 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/1492007 Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half- installed') Status in linux package in Ubuntu: Confirmed Bug description: The system came apart after I used BleachBit (root) and opted to clean the system. I had no desktop (xfce4) but managed to get it back ok. Tried using Computer Janitor to remove old packages to make room on /boot for upgrades. Now system is (may be) down on next re-boot. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.79 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2076 F pulseaudio Date: Thu Sep 3 20:24:34 2015 DuplicateSignature: package:linux-image-extra-3.13.0-46-generic:3.13.0-46.79:package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=UUID=8292c581-0794-4d64-8b76-dd50aee7d9a9 InstallationDate: Installed on 2015-02-25 (189 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: MICRO-STAR INTERNATIONAL CO., LTD KM266-8235 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2003 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-6738 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/22/2003:svnMICRO-STARINTERNATIONALCO.,LTD:pnKM266-8235:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6738:rvr:cvn:ct3:cvr: dmi.product.name: KM266-8235 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492007/+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 1469320] Re: CVE-2015-4700
** Description changed: - Crafted BPF filters may crash kernel during JIT optimisation + The bpf_int_jit_compile function in arch/x86/net/bpf_jit_comp.c in the + Linux kernel before 4.0.6 allows local users to cause a denial of + service (system crash) by creating a packet filter and then loading + crafted BPF instructions that trigger late convergence by the JIT + compiler. Break-Fix: 0a14842f5a3c0e88a1e59fac5c3025db39721f74 3f7352bf21f8fd7ba3e2fcef9488756f188e12be -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1469320 Title: CVE-2015-4700 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source pa
[Kernel-packages] [Bug 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544
8cc748aa76c921d8834ef00f762f31acd2c93aa8 linux-image-3.19.0-031900-generic_3.19.0-031900.201509031637_amd64.deb is BAD -- 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/1491467 Title: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544 Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: On Fujitsu A544 laptop (and likely others) fitted with SSD, kworker takes 100% of one core of CPU due to GPE13 interrupt storm See upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=53071 The bug can be identified by repeatedly running cat /sys/firmware/acpi/interrupts/gpe13 where a rapidly increasing count will be seen. Workaround: sudo sh -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe13' disables it until reboot Using sudo crontab -e and adding the line @reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe13 works around for subsequent boots. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: colinl 1699 F pulseaudio /dev/snd/controlC1: colinl 1699 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 2 16:03:19 2015 InstallationDate: Installed on 2014-10-21 (316 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.147 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-08-31 (1 days ago) dmi.bios.date: 04/01/2015 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.19 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd04/01/2015:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1491467/+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 1490785] Re: linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Assignee: John Johansen (jjohansen) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1490785 Title: linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-28.30~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, 01. September 2015 01:02 UTC kernel-stable-master-bug:1490606 kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1490785/+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 1457807] Re: CVE-2015-4036
** Description changed: - [drivers/vhost/scsi.c: potential memory corruption] + Array index error in the tcm_vhost_make_tpg function in + drivers/vhost/scsi.c in the Linux kernel before 4.0 might allow guest OS + users to cause a denial of service (memory corruption) or possibly have + unspecified other impact via a crafted VHOST_SCSI_SET_ENDPOINT ioctl + call. NOTE: the affected function was renamed to vhost_scsi_make_tpg + before the vulnerability was announced. Break-Fix: 057cbf49a1f08297877e46c82f707b1bfea806a8 59c816c1f24df0204e01851431d3bab3eb76719c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1457807 Title: CVE-2015-4036 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: Inv
[Kernel-packages] [Bug 1469488] Re: Suspend crashes ubuntu every now and then
The problem persists... -- 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/1469488 Title: Suspend crashes ubuntu every now and then Status in linux package in Ubuntu: Incomplete Bug description: Once every 5 or so suspends, ubuntu crashes immediately: power leds are still indicating the hardware is running, monitor falls asleep as on successful suspend, cannot ctr-alt-f into terminal, cannot ssh into ubuntu, logs show no errors... ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-21-generic 3.19.0-21.21 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: izak 1957 F...m pulseaudio /dev/snd/pcmC1D0p: izak 1957 F...m pulseaudio /dev/snd/controlC0: izak 1957 F pulseaudio /dev/snd/controlC1: izak 1957 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 28 11:28:11 2015 HibernationDevice: RESUME=UUID=4226b1a5-ebed-4bf9-afa2-33431caa2763 InstallationDate: Installed on 2014-10-24 (246 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-21-generic N/A linux-backports-modules-3.19.0-21-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-04 (54 days ago) dmi.bios.date: 09/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2012 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO(Wi-Fi ac) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2012:bd09/30/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO(Wi-Fiac):rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469488/+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 1492007] [NEW] package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration can
Public bug reported: The system came apart after I used BleachBit (root) and opted to clean the system. I had no desktop (xfce4) but managed to get it back ok. Tried using Computer Janitor to remove old packages to make room on /boot for upgrades. Now system is (may be) down on next re-boot. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.79 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2076 F pulseaudio Date: Thu Sep 3 20:24:34 2015 DuplicateSignature: package:linux-image-extra-3.13.0-46-generic:3.13.0-46.79:package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=UUID=8292c581-0794-4d64-8b76-dd50aee7d9a9 InstallationDate: Installed on 2015-02-25 (189 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: MICRO-STAR INTERNATIONAL CO., LTD KM266-8235 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2003 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-6738 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/22/2003:svnMICRO-STARINTERNATIONALCO.,LTD:pnKM266-8235:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6738:rvr:cvn:ct3:cvr: dmi.product.name: KM266-8235 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package dist-upgrade i386 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/1492007 Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half- installed') Status in linux package in Ubuntu: New Bug description: The system came apart after I used BleachBit (root) and opted to clean the system. I had no desktop (xfce4) but managed to get it back ok. Tried using Computer Janitor to remove old packages to make room on /boot for upgrades. Now system is (may be) down on next re-boot. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.79 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2076 F pulseaudio Date: Thu Sep 3 20:24:34 2015 DuplicateSignature: package:linux-image-extra-3.13.0-46-generic:3.13.0-46.79:package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=UUID=8292c581-0794-4d64-8b76-dd50aee7d9a9 InstallationDate: Installed on 2015-02-25 (189 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: MICRO-STAR INTERNATIONAL CO., LTD KM266-8235 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not
[Kernel-packages] [Bug 1492007] Re: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration canno
** Tags removed: need-duplicate-check -- 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/1492007 Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half- installed') Status in linux package in Ubuntu: New Bug description: The system came apart after I used BleachBit (root) and opted to clean the system. I had no desktop (xfce4) but managed to get it back ok. Tried using Computer Janitor to remove old packages to make room on /boot for upgrades. Now system is (may be) down on next re-boot. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-46-generic 3.13.0-46.79 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic i686 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2076 F pulseaudio Date: Thu Sep 3 20:24:34 2015 DuplicateSignature: package:linux-image-extra-3.13.0-46-generic:3.13.0-46.79:package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') HibernationDevice: RESUME=UUID=8292c581-0794-4d64-8b76-dd50aee7d9a9 InstallationDate: Installed on 2015-02-25 (189 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: MICRO-STAR INTERNATIONAL CO., LTD KM266-8235 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3 RfKill: SourcePackage: linux Title: package linux-image-extra-3.13.0-46-generic 3.13.0-46.79 failed to install/upgrade: package linux-image-extra-3.13.0-46-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2003 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-6738 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/22/2003:svnMICRO-STARINTERNATIONALCO.,LTD:pnKM266-8235:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6738:rvr:cvn:ct3:cvr: dmi.product.name: KM266-8235 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492007/+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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
To add to comment #30 I posted, the read-only bug continues to occur on both Generation 1 and Generation 2 VMs. -- 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/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1490606] Re: linux: 3.19.0-28.30 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Assignee: John Johansen (jjohansen) => Steve Beattie (sbeattie) -- 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/1490606 Title: linux: 3.19.0-28.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-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: 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 Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1490606/+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 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups
Bug is still present in Vivid 3.19.0-26-generic. Is there a workaround that avoids this problem? There's considerable pressure to move off of Hyper-V and I'd rather not do it. [57055.788468] sd 0:0:0:0: [storvsc] Sense Key : Unit Attention [current] [57055.788561] sd 0:0:0:0: [storvsc] Add. Sense: Changed operating definition [57055.788704] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. [57055.788719] blk_update_request: I/O error, dev sda, sector 207053224 [57055.788924] Aborting journal on device sda2-8. [57055.880744] EXT4-fs error (device sda2): ext4_journal_check_start:56: Detected aborted journal [57055.880833] EXT4-fs (sda2): Remounting filesystem read-only [57055.885165] sd 0:0:0:1: [storvsc] Sense Key : Unit Attention [current] [57055.885269] sd 0:0:0:1: [storvsc] Add. Sense: Changed operating definition [57055.885342] sd 0:0:0:1: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. [57315.373166] sd 0:0:0:2: [storvsc] Sense Key : Unit Attention [current] [57315.373230] sd 0:0:0:2: [storvsc] Add. Sense: Changed operating definition [57315.373379] sd 0:0:0:2: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Linux db003 3.19.0-26-generic #28-Ubuntu SMP Tue Aug 11 14:16:32 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts.On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here).As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+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 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
Attached is a spreadsheet with the above data and some graphs. The first graph compares normalized data from the ACPI thermal zones (acpiz), CPU freq and CPU utilization. This shows a good correlation on CPU utilization and temperature (as we would expect). CPU frequencies are scaling according to the load and looks OK to me. The second graph is a comparison of ACPI thermal zones and CPU utilization in absolute terms (e.g. degrees C and CPU %). Note that the CPU is loaded never less than 20% and that at this level the temperature seems to be levelling out to around 70 degrees C which seems rather high. The CPU is bouncing around 800Mhz - 1.8GHz at that point, which I guess is to be expected if one has so many context switches and IRQs occurring. So. Some interesting data: 1. The IRQ rate does seem high. 2. The Context switch rate seems high too. 3. The machine is not that idle. 4. Even at a low-ish load, the system is rather hot. (This makes me wonder if there is something physically wrong between the CPU and the heatpipe/fan unit.) 5. Dropping from fully loaded to partially loaded we see heat being dissipated but not that well, e.g. it drops from nearly 100 C down to 70-65 C, which is surprising and I expected this to go lower. Hence I think it may be a physical hardware issue with the cooling. ** Attachment added: "LibreOffice spreadsheet" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+attachment/4456965/+files/powerstat-lenovo-W500-2015.09.03.ods -- 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/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: In Progress Bug description: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+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 1491988] [NEW] 15.10: Multiple Bluetooth controllers not found
Public bug reported: $ hcitool dev Devices: hci100:10:7A:4D:15:33 hci000:1F:3A:E0:0A:AF $ hcitool -i hci1 scan Scanning ... 00:0A:95:4B:BD:C2 Apple Wireless Keyboard $ sudo systemctl restart bluetooth $ journalctl -u bluetooth | grep adapter_service_add Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: src/adapter.c:adapter_service_add() /org/bluez/hci0 $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard [bluetooth]# list Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1491988 Title: 15.10: Multiple Bluetooth controllers not found Status in bluez package in Ubuntu: New Bug description: $ hcitool dev Devices: hci100:10:7A:4D:15:33 hci000:1F:3A:E0:0A:AF $ hcitool -i hci1 scan Scanning ... 00:0A:95:4B:BD:C2 Apple Wireless Keyboard $ sudo systemctl restart bluetooth $ journalctl -u bluetooth | grep adapter_service_add Sep 03 19:39:12 hephaestion.lan.iam.tj bluetoothd[3973]: src/adapter.c:adapter_service_add() /org/bluez/hci0 $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [NEW] Device 00:19:15:29:83:14 Think Outside Keyboard [bluetooth]# list Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491988/+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 1490606] onza (amd64) - tests ran: 197, failed: 1
tests ran: 197, failed: 1; http://kernel.ubuntu.com/testing/onza__3.19.0-28.30__2015-09-03_10-56-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/1490606 Title: linux: 3.19.0-28.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1490606/+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 1478819] Re: CVE-2015-3291
** Description changed: - Malicious user code can cause some fraction of NMIs to be ignored. + arch/x86/entry/entry_64.S in the Linux kernel before 4.1.6 on the x86_64 + platform does not properly determine when nested NMI processing is + occurring, which allows local users to cause a denial of service + (skipped NMI) by modifying the rsp register, issuing a syscall + instruction, and triggering an NMI. Break-Fix: 3f3c8b8c4b2a34776c3470142a7c8baafcda6eb0 810bc075f78ff2c221536eb3008eac6a492dba2d -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1478819 Title: CVE-2015-3291 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wil
[Kernel-packages] [Bug 1477026] Re: CVE-2015-3290
** Description changed: - High impact NMI bug on x86_64 + arch/x86/entry/entry_64.S in the Linux kernel before 4.1.6 on the x86_64 + platform improperly relies on espfix64 during nested NMI processing, + which allows local users to gain privileges by triggering an NMI within + a certain instruction window. Break-Fix: - 9b6e6a8334d56354853f9c255d1395c2ba570e0a -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1477026 Title: CVE-2015-3290 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily:
[Kernel-packages] [Bug 1471096] Re: CVE-2015-3212
** Description changed: - [SCTP race condition allows list corruption and panic from userlevel] + Race condition in net/sctp/socket.c in the Linux kernel before 4.1.2 + allows local users to cause a denial of service (list corruption and + panic) via a rapid series of system calls related to sockets, as + demonstrated by setsockopt calls. Break-Fix: 9f7d653b67aed2d92540fbb0a8adaf32fcf352ae 2d45a02d0166caf2627fe91897c6ffc3b19514c4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1471096 Title: CVE-2015-3212 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Status in linux-lts-trusty source package in Vivid: Invalid Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Invalid Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-mvl-dove source package in Vivid: Invalid Status in l
[Kernel-packages] [Bug 1491957] Re: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem
And because I moved back to previous kernel, I cannot create more logs. But is you really need the "apport-collect 1491957" then maybe I can upgrade again to the new kernel, but after I removed it, now I cannot see it if I try apt upgrade, so in this case please tell me how I can re-update the kernel after I removed it. ** 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/1491957 Title: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem Status in linux package in Ubuntu: Confirmed Bug description: I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I have network connection problems, and have a lot of error message on screen like the above ones. Sep 3 18:48:07 RailGun kernel: [ 71.437967] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.438276] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.438596] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.439016] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.439434] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.439847] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.440155] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.465593] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.466165] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.466827] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.467508] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.468056] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.474507] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.474998] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.475419] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.475833] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.476145] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.483356] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.483823] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.484266] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.484683] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.484993] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.491738] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.492223] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.492645] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.493060] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.493369] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.493689] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.494109] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 2 Sep 3
[Kernel-packages] [Bug 1491957] Re: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem
Joseph, yes, I moved back to the prior kernel. And now it works again. -- 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/1491957 Title: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem Status in linux package in Ubuntu: Confirmed Bug description: I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I have network connection problems, and have a lot of error message on screen like the above ones. Sep 3 18:48:07 RailGun kernel: [ 71.437967] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.438276] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.438596] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.439016] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.439434] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.439847] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.440155] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.465593] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.466165] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.466827] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.467508] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.468056] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.474507] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.474998] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.475419] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.475833] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.476145] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.483356] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.483823] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.484266] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.484683] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.484993] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.491738] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.492223] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.492645] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.493060] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.493369] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.493689] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.494109] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.494527] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.494941] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.495249] hv
[Kernel-packages] [Bug 1491957] Re: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem
Due to the nature of the issue I am unable to run "apport-collect 1491957", because I changed back the kernel to the previos 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/1491957 Title: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem Status in linux package in Ubuntu: Confirmed Bug description: I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I have network connection problems, and have a lot of error message on screen like the above ones. Sep 3 18:48:07 RailGun kernel: [ 71.437967] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.438276] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.438596] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.439016] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.439434] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.439847] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.440155] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.465593] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.466165] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.466827] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.467508] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.468056] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.474507] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.474998] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.475419] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.475833] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.476145] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.483356] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.483823] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.484266] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.484683] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.484993] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.491738] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.492223] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.492645] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.493060] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.493369] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.493689] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.494109] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.494527] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.494941] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...ret
[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
Attachment from "powerstat -za 1 480". ** Attachment added: "Intermittent full load over 30% base load" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+attachment/4456951/+files/powerstat-lenovo-W500-2015.09.03.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: In Progress Bug description: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+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 1491850] Re: ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1510 -- 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/1491850 Title: ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages Status in linux package in Ubuntu: New Bug description: == Comment: #0 - YUECHANG E. MEI - 2015-09-02 12:57:52 == ---Problem Description--- We tried to install linux-crashdump package (using "apt-get install linux-crashdump") in Ubuntu 15.10 lpar, but fails and hit some errors. Since we have similar bug 122925 open in Ubuntu 15.04 (LP bug# LP1436448), we used the work around in bug 122925 and the linux-crashdump get install successfully. Error we see when we install linux-crashdump: root@conelp2:~# apt-get install linux-crashdump Unpacking linux-crashdump (4.1.0.3.3) ... Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-11_ppc64el.deb ... Unpacking policykit-1 (0.105-11) ... Processing triggers for man-db (2.7.2-1) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (224-2ubuntu2) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.PolicyKit1': timed out (g-dbus-error-quark, 20) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for dbus (1.9.20-1ubuntu2) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) root@conelp2:~# dpkg -l | grep linux-crashdump iU linux-crashdump 4.1.0.3.3 ppc64el Linux kernel crashdump setup for the latest generic kernel ---uname output--- Linux conelp2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:23:44 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = n/a ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install Ubuntu 15.10 in a lpar 2. Login as root, and run "apt-get update". 3. Install linux-crashdump packages, run "apt-get install linux-crashdump", then you will see the error Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com, Raja Sunkari /rajas...@in.ibm.com: -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491850/+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 1491957] Re: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem
Does this issue go away if you boot back into the prior kernel? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key kernel-hyper-v -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1491957 Title: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem Status in linux package in Ubuntu: Incomplete Bug description: I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I have network connection problems, and have a lot of error message on screen like the above ones. Sep 3 18:48:07 RailGun kernel: [ 71.437967] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.438276] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.438596] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.439016] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.439434] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.439847] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.440155] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.465593] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.466165] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.466827] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.467508] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.468056] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.474507] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.474998] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.475419] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.475833] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.476145] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.483356] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.483823] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.484266] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.484683] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.484993] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.491738] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.492223] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.492645] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.493060] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.493369] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.493689] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.494109] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.494527] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.494941] hv_netvsc vmbus_0_16 eth0: unable t
[Kernel-packages] [Bug 1491467] Re: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544
I built the next test kernel, up to the following commit: 8cc748aa76c921d8834ef00f762f31acd2c93aa8 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1491467 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- 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/1491467 Title: kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544 Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: On Fujitsu A544 laptop (and likely others) fitted with SSD, kworker takes 100% of one core of CPU due to GPE13 interrupt storm See upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=53071 The bug can be identified by repeatedly running cat /sys/firmware/acpi/interrupts/gpe13 where a rapidly increasing count will be seen. Workaround: sudo sh -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe13' disables it until reboot Using sudo crontab -e and adding the line @reboot echo "disable" > /sys/firmware/acpi/interrupts/gpe13 works around for subsequent boots. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.1.0-3-generic 4.1.0-3.3 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: colinl 1699 F pulseaudio /dev/snd/controlC1: colinl 1699 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 2 16:03:19 2015 InstallationDate: Installed on 2014-10-21 (316 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro RelatedPackageVersions: linux-restricted-modules-4.1.0-3-generic N/A linux-backports-modules-4.1.0-3-generic N/A linux-firmware 1.147 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-08-31 (1 days ago) dmi.bios.date: 04/01/2015 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.19 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd04/01/2015:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1491467/+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 1491957] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1491957 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/1491957 Title: 3.16.0.48 kernel in hyper-v cause hv_netvsc problem Status in linux package in Ubuntu: Incomplete Bug description: I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I have network connection problems, and have a lot of error message on screen like the above ones. Sep 3 18:48:07 RailGun kernel: [ 71.437967] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.438276] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.438596] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.439016] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.439434] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.439847] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.440155] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.465593] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.466165] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.466827] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.467508] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.468056] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.474507] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.474998] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.475419] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.475833] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.476145] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.483356] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.483823] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.484266] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.484683] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.484993] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.491738] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.492223] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.492645] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.493060] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.493369] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.493689] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 1 Sep 3 18:48:07 RailGu
[Kernel-packages] [Bug 1491850] Re: ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages
** Package changed: linux-meta (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/1491850 Title: ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages Status in linux package in Ubuntu: New Bug description: == Comment: #0 - YUECHANG E. MEI - 2015-09-02 12:57:52 == ---Problem Description--- We tried to install linux-crashdump package (using "apt-get install linux-crashdump") in Ubuntu 15.10 lpar, but fails and hit some errors. Since we have similar bug 122925 open in Ubuntu 15.04 (LP bug# LP1436448), we used the work around in bug 122925 and the linux-crashdump get install successfully. Error we see when we install linux-crashdump: root@conelp2:~# apt-get install linux-crashdump Unpacking linux-crashdump (4.1.0.3.3) ... Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-11_ppc64el.deb ... Unpacking policykit-1 (0.105-11) ... Processing triggers for man-db (2.7.2-1) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (224-2ubuntu2) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.PolicyKit1': timed out (g-dbus-error-quark, 20) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for dbus (1.9.20-1ubuntu2) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) root@conelp2:~# dpkg -l | grep linux-crashdump iU linux-crashdump 4.1.0.3.3 ppc64el Linux kernel crashdump setup for the latest generic kernel ---uname output--- Linux conelp2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:23:44 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = n/a ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install Ubuntu 15.10 in a lpar 2. Login as root, and run "apt-get update". 3. Install linux-crashdump packages, run "apt-get install linux-crashdump", then you will see the error Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com, Raja Sunkari /rajas...@in.ibm.com: -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491850/+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 874694] Re: [i845] Resolution cannot be set higher than 640x480 and doesn't fit screen
I have update the Amilo config to 15.04. The bug is still there. Settting i915.modeset=0 does not bring improvement anymore : instead of 640x480 max resolution stuck at top left of the screen you now get the 640x480 max reslution in the middle of the screen. Any fix on this is highly welcomed to be able to run Ubuntu on those machine. ** 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/874694 Title: [i845] Resolution cannot be set higher than 640x480 and doesn't fit screen Status in linux package in Ubuntu: Confirmed Bug description: In Lubuntu 11.10 I cannot set the resolution higher than 640x480. The screen clearly doesn't like this and doesn't fit the desktop. See attached photo https://bugs.launchpad.net/ubuntu/+source/linux/+bug/874694/+attachment/2545700/+files/2011-10-15%2000.59.24.jpg . WORKAROUND: Use kernel parameter: i915.modeset=0 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Sat Oct 15 00:43:38 2011 InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/874694/+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 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
We can examine the thermald issues later, lets get some idea of what powerstat says and then I can ponder on the next best step to make. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- 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/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: In Progress Bug description: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+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 1491957] [NEW] 3.16.0.48 kernel in hyper-v cause hv_netvsc problem
Public bug reported: I have an Ubuntu 14.04 LTS in Hyper-V. It works well. Today I apt upgrade the kernel from 3.16.0.46 to 3.16.0.48 and after reboot, I have network connection problems, and have a lot of error message on screen like the above ones. Sep 3 18:48:07 RailGun kernel: [ 71.437967] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.438276] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2068)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.438596] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.439016] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.439434] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.439847] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.440155] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 2069)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.465593] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.466165] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.466827] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.467508] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.468056] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206a)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.474507] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.474998] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.475419] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.475833] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.476145] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206b)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.483356] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.483823] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.484266] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.484683] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.484993] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206c)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.491738] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.492223] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.492645] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.493060] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.493369] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206d)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.493689] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.494109] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.494527] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 3 Sep 3 18:48:07 RailGun kernel: [ 71.494941] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...retrying 4 Sep 3 18:48:07 RailGun kernel: [ 71.495249] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206e)...give up retrying Sep 3 18:48:07 RailGun kernel: [ 71.509010] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206f)...retrying 1 Sep 3 18:48:07 RailGun kernel: [ 71.509467] hv_netvsc vmbus_0_16 eth0: unable to send receive completion pkt (tid 206f)...retrying 2 Sep 3 18:48:07 RailGun kernel: [ 71.509892]
[Kernel-packages] [Bug 1491850] Re: ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages
** Package changed: ubuntu => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1491850 Title: ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages Status in linux-meta package in Ubuntu: New Bug description: == Comment: #0 - YUECHANG E. MEI - 2015-09-02 12:57:52 == ---Problem Description--- We tried to install linux-crashdump package (using "apt-get install linux-crashdump") in Ubuntu 15.10 lpar, but fails and hit some errors. Since we have similar bug 122925 open in Ubuntu 15.04 (LP bug# LP1436448), we used the work around in bug 122925 and the linux-crashdump get install successfully. Error we see when we install linux-crashdump: root@conelp2:~# apt-get install linux-crashdump Unpacking linux-crashdump (4.1.0.3.3) ... Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-11_ppc64el.deb ... Unpacking policykit-1 (0.105-11) ... Processing triggers for man-db (2.7.2-1) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (224-2ubuntu2) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.PolicyKit1': timed out (g-dbus-error-quark, 20) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for dbus (1.9.20-1ubuntu2) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) root@conelp2:~# dpkg -l | grep linux-crashdump iU linux-crashdump 4.1.0.3.3 ppc64el Linux kernel crashdump setup for the latest generic kernel ---uname output--- Linux conelp2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:23:44 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = n/a ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install Ubuntu 15.10 in a lpar 2. Login as root, and run "apt-get update". 3. Install linux-crashdump packages, run "apt-get install linux-crashdump", then you will see the error Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com, Raja Sunkari /rajas...@in.ibm.com: -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1491850/+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 1454758] Re: [Hyper-V] storvsc: Set the SRB flags correctly when no data transfer is needed
The cherry-pick of commit dc45708c into Precise also required 8b612fa as a prereq. I built a test kernel with these two commits. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1454758/ Can folks affected by this bug test this kernel? If it resolves this bug, I will SRU these commits to Precise. Thanks in advance. -- 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/1454758 Title: [Hyper-V] storvsc: Set the SRB flags correctly when no data transfer is needed Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: In Progress Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Bug description: The following critical bugfix has been accepted into the upstream kernel. It is needed for 15.10, 15.02, 14.10, 14.04 and 14.04 HWE (and, by extension, 12.04 and 12.04 HWE). We have seen IHV drivers in the field throw errors and time out due to receiving SRB flags set when no data transfer is expected. storvsc: Set the SRB flags correctly when no data transfer is needed Set the SRB flags correctly when there is no data transfer. Without this change some IHV drivers will fail valid commands such as TEST_UNIT_READY. Commit http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=dc45708ca9988656d706940df5fd102672c5de92 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454758/+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 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
If thermald is supposed to throttle CPU according to temperature, it doesn't work. Whatever is throttling the CPU seems to be unaware of temperature, because the more I load the machine, the more reliably "cpufreq-info -w" returns "2801000" while temperature is at 90-95 C. Only when there is less load, does the CPU run at lower frequencies. -- 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/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: Confirmed Bug description: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+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 1491850] [NEW] ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages
You have been subscribed to a public bug: == Comment: #0 - YUECHANG E. MEI - 2015-09-02 12:57:52 == ---Problem Description--- We tried to install linux-crashdump package (using "apt-get install linux-crashdump") in Ubuntu 15.10 lpar, but fails and hit some errors. Since we have similar bug 122925 open in Ubuntu 15.04 (LP bug# LP1436448), we used the work around in bug 122925 and the linux-crashdump get install successfully. Error we see when we install linux-crashdump: root@conelp2:~# apt-get install linux-crashdump Unpacking linux-crashdump (4.1.0.3.3) ... Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-11_ppc64el.deb ... Unpacking policykit-1 (0.105-11) ... Processing triggers for man-db (2.7.2-1) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (224-2ubuntu2) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.PolicyKit1': timed out (g-dbus-error-quark, 20) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for dbus (1.9.20-1ubuntu2) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) root@conelp2:~# dpkg -l | grep linux-crashdump iU linux-crashdump 4.1.0.3.3 ppc64el Linux kernel crashdump setup for the latest generic kernel ---uname output--- Linux conelp2 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:23:44 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = n/a ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install Ubuntu 15.10 in a lpar 2. Login as root, and run "apt-get update". 3. Install linux-crashdump packages, run "apt-get install linux-crashdump", then you will see the error Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Yuechang (Erin) Mei /ye...@us.ibm.com, Raja Sunkari /rajas...@in.ibm.com: -Attach sysctl -a output output to the bug. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: architecture-ppc64le bot-comment bugnameltc-129812 severity-high targetmilestone-inin--- -- ISST-LTE: Ubuntu 15.10 fails to install Linux-crashdump packages https://bugs.launchpad.net/bugs/1491850 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta 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 1473584] Re: AUDIT_USER_AVC messages are not printk'ed when auditd is not running
This bug was fixed in the package linux-flo - 3.4.0-4.18~15.04.1
---
linux-flo (3.4.0-4.18~15.04.1) vivid; urgency=low
[ Upstream Kernel Changes ]
* audit: printk USER_AVC messages when audit isn't enabled
- LP: #1473584
-- Tim Gardner Mon, 13 Jul 2015 14:39:54
-0700
** Changed in: linux-flo (Ubuntu Vivid)
Status: Fix Committed => Fix Released
** Changed in: linux-manta (Ubuntu Vivid)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-manta in Ubuntu.
https://bugs.launchpad.net/bugs/1473584
Title:
AUDIT_USER_AVC messages are not printk'ed when auditd is not running
Status in linux-flo package in Ubuntu:
Fix Released
Status in linux-goldfish package in Ubuntu:
Fix Released
Status in linux-mako package in Ubuntu:
Fix Released
Status in linux-manta package in Ubuntu:
Fix Released
Status in linux-flo source package in Vivid:
Fix Released
Status in linux-goldfish source package in Vivid:
Fix Released
Status in linux-mako source package in Vivid:
Fix Released
Status in linux-manta source package in Vivid:
Fix Released
Bug description:
The auditd daemon is not part of the default phone images. At the
kernel level, the audit_enabled variable remains 0 until an auditd
daemon registers itself. There is a bug in old kernels that causes
AUDIT_USER_AVC messages to be ignored when audit_enabled is 0. I fixed
the bug several years ago and marked the patch for the stable tree but
the phone kernels (mako, at least) did not pull in the patch. The
upstream commit id is:
0868a5e150bc4c47e7a003367cd755811eb41e0b
What this means for our phone images is that any denial messages from
the system D-Bus daemon are dropped instead of being properly routed
to the syslog. This results in headaches for debugging app confinement
denials.
== Verification Steps ==
# Load an AppArmor profile for testing
$ echo "profile test { file, signal, unix, }" | sudo apparmor_parser -rq
# Verify that we can talk to the system bus
$ dbus-send --print-reply --system --dest=org.freedesktop.DBus
/org/freedesktop/DBus org.freedesktop.DBus.ListNames
method return sender=org.freedesktop.DBus -> dest=:1.90 reply_serial=2
array [
string "org.freedesktop.DBus"
...
# Clear the dmesg buffer
$ sudo dmesg -C
# Attempt to talk to the system bus under confinement
$ aa-exec -p test -- dbus-send --print-reply --system
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
Failed to open connection to "system" message bus: An AppArmor policy
prevents this sender from sending this message to this recipient;
type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus"
member="Hello" error name="(unset)" requested_reply="0"
destination="org.freedesktop.DBus" (bus)
# We should now see an AppArmor denial in the dmesg output.
# Successful fix verification *must* show the denial from the D-Bus daemon.
$ sudo dmesg | grep DENIED
[ 187.737219] type=1107 audit(1438385684.065:149): pid=826 uid=102
auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus"
interface="org.freedesktop.DBus" member="Hello" mask="send"
name="org.freedesktop.DBus" pid=6721 label="test" peer_label="unconfined"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-flo/+bug/1473584/+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 1473584] Re: AUDIT_USER_AVC messages are not printk'ed when auditd is not running
This bug was fixed in the package linux-manta - 3.4.0-7.32~15.04.1
---
linux-manta (3.4.0-7.32~15.04.1) vivid; urgency=low
[ Upstream Kernel Changes ]
* audit: printk USER_AVC messages when audit isn't enabled
- LP: #1473584
-- Tim Gardner Mon, 13 Jul 2015 14:49:51
-0700
** Changed in: linux-mako (Ubuntu Vivid)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-manta in Ubuntu.
https://bugs.launchpad.net/bugs/1473584
Title:
AUDIT_USER_AVC messages are not printk'ed when auditd is not running
Status in linux-flo package in Ubuntu:
Fix Released
Status in linux-goldfish package in Ubuntu:
Fix Released
Status in linux-mako package in Ubuntu:
Fix Released
Status in linux-manta package in Ubuntu:
Fix Released
Status in linux-flo source package in Vivid:
Fix Released
Status in linux-goldfish source package in Vivid:
Fix Released
Status in linux-mako source package in Vivid:
Fix Released
Status in linux-manta source package in Vivid:
Fix Released
Bug description:
The auditd daemon is not part of the default phone images. At the
kernel level, the audit_enabled variable remains 0 until an auditd
daemon registers itself. There is a bug in old kernels that causes
AUDIT_USER_AVC messages to be ignored when audit_enabled is 0. I fixed
the bug several years ago and marked the patch for the stable tree but
the phone kernels (mako, at least) did not pull in the patch. The
upstream commit id is:
0868a5e150bc4c47e7a003367cd755811eb41e0b
What this means for our phone images is that any denial messages from
the system D-Bus daemon are dropped instead of being properly routed
to the syslog. This results in headaches for debugging app confinement
denials.
== Verification Steps ==
# Load an AppArmor profile for testing
$ echo "profile test { file, signal, unix, }" | sudo apparmor_parser -rq
# Verify that we can talk to the system bus
$ dbus-send --print-reply --system --dest=org.freedesktop.DBus
/org/freedesktop/DBus org.freedesktop.DBus.ListNames
method return sender=org.freedesktop.DBus -> dest=:1.90 reply_serial=2
array [
string "org.freedesktop.DBus"
...
# Clear the dmesg buffer
$ sudo dmesg -C
# Attempt to talk to the system bus under confinement
$ aa-exec -p test -- dbus-send --print-reply --system
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
Failed to open connection to "system" message bus: An AppArmor policy
prevents this sender from sending this message to this recipient;
type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus"
member="Hello" error name="(unset)" requested_reply="0"
destination="org.freedesktop.DBus" (bus)
# We should now see an AppArmor denial in the dmesg output.
# Successful fix verification *must* show the denial from the D-Bus daemon.
$ sudo dmesg | grep DENIED
[ 187.737219] type=1107 audit(1438385684.065:149): pid=826 uid=102
auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus"
interface="org.freedesktop.DBus" member="Hello" mask="send"
name="org.freedesktop.DBus" pid=6721 label="test" peer_label="unconfined"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-flo/+bug/1473584/+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 1473584] Re: AUDIT_USER_AVC messages are not printk'ed when auditd is not running
This bug was fixed in the package linux-goldfish - 3.4.0-4.24~15.04.1
---
linux-goldfish (3.4.0-4.24~15.04.1) vivid; urgency=low
[ Upstream Kernel Changes ]
* audit: printk USER_AVC messages when audit isn't enabled
- LP: #1473584
-- Tim Gardner Mon, 13 Jul 2015 14:57:44
-0700
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-manta in Ubuntu.
https://bugs.launchpad.net/bugs/1473584
Title:
AUDIT_USER_AVC messages are not printk'ed when auditd is not running
Status in linux-flo package in Ubuntu:
Fix Released
Status in linux-goldfish package in Ubuntu:
Fix Released
Status in linux-mako package in Ubuntu:
Fix Released
Status in linux-manta package in Ubuntu:
Fix Released
Status in linux-flo source package in Vivid:
Fix Released
Status in linux-goldfish source package in Vivid:
Fix Released
Status in linux-mako source package in Vivid:
Fix Released
Status in linux-manta source package in Vivid:
Fix Released
Bug description:
The auditd daemon is not part of the default phone images. At the
kernel level, the audit_enabled variable remains 0 until an auditd
daemon registers itself. There is a bug in old kernels that causes
AUDIT_USER_AVC messages to be ignored when audit_enabled is 0. I fixed
the bug several years ago and marked the patch for the stable tree but
the phone kernels (mako, at least) did not pull in the patch. The
upstream commit id is:
0868a5e150bc4c47e7a003367cd755811eb41e0b
What this means for our phone images is that any denial messages from
the system D-Bus daemon are dropped instead of being properly routed
to the syslog. This results in headaches for debugging app confinement
denials.
== Verification Steps ==
# Load an AppArmor profile for testing
$ echo "profile test { file, signal, unix, }" | sudo apparmor_parser -rq
# Verify that we can talk to the system bus
$ dbus-send --print-reply --system --dest=org.freedesktop.DBus
/org/freedesktop/DBus org.freedesktop.DBus.ListNames
method return sender=org.freedesktop.DBus -> dest=:1.90 reply_serial=2
array [
string "org.freedesktop.DBus"
...
# Clear the dmesg buffer
$ sudo dmesg -C
# Attempt to talk to the system bus under confinement
$ aa-exec -p test -- dbus-send --print-reply --system
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
Failed to open connection to "system" message bus: An AppArmor policy
prevents this sender from sending this message to this recipient;
type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus"
member="Hello" error name="(unset)" requested_reply="0"
destination="org.freedesktop.DBus" (bus)
# We should now see an AppArmor denial in the dmesg output.
# Successful fix verification *must* show the denial from the D-Bus daemon.
$ sudo dmesg | grep DENIED
[ 187.737219] type=1107 audit(1438385684.065:149): pid=826 uid=102
auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus"
interface="org.freedesktop.DBus" member="Hello" mask="send"
name="org.freedesktop.DBus" pid=6721 label="test" peer_label="unconfined"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-flo/+bug/1473584/+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 1473584] Re: AUDIT_USER_AVC messages are not printk'ed when auditd is not running
This bug was fixed in the package linux-mako - 3.4.0-6.37~15.04.1
---
linux-mako (3.4.0-6.37~15.04.1) vivid; urgency=low
[ Upstream Kernel Changes ]
* audit: printk USER_AVC messages when audit isn't enabled
- LP: #1473584
-- Tim Gardner Mon, 13 Jul 2015 14:53:48
-0700
** Changed in: linux-goldfish (Ubuntu Vivid)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-manta in Ubuntu.
https://bugs.launchpad.net/bugs/1473584
Title:
AUDIT_USER_AVC messages are not printk'ed when auditd is not running
Status in linux-flo package in Ubuntu:
Fix Released
Status in linux-goldfish package in Ubuntu:
Fix Released
Status in linux-mako package in Ubuntu:
Fix Released
Status in linux-manta package in Ubuntu:
Fix Released
Status in linux-flo source package in Vivid:
Fix Released
Status in linux-goldfish source package in Vivid:
Fix Released
Status in linux-mako source package in Vivid:
Fix Released
Status in linux-manta source package in Vivid:
Fix Released
Bug description:
The auditd daemon is not part of the default phone images. At the
kernel level, the audit_enabled variable remains 0 until an auditd
daemon registers itself. There is a bug in old kernels that causes
AUDIT_USER_AVC messages to be ignored when audit_enabled is 0. I fixed
the bug several years ago and marked the patch for the stable tree but
the phone kernels (mako, at least) did not pull in the patch. The
upstream commit id is:
0868a5e150bc4c47e7a003367cd755811eb41e0b
What this means for our phone images is that any denial messages from
the system D-Bus daemon are dropped instead of being properly routed
to the syslog. This results in headaches for debugging app confinement
denials.
== Verification Steps ==
# Load an AppArmor profile for testing
$ echo "profile test { file, signal, unix, }" | sudo apparmor_parser -rq
# Verify that we can talk to the system bus
$ dbus-send --print-reply --system --dest=org.freedesktop.DBus
/org/freedesktop/DBus org.freedesktop.DBus.ListNames
method return sender=org.freedesktop.DBus -> dest=:1.90 reply_serial=2
array [
string "org.freedesktop.DBus"
...
# Clear the dmesg buffer
$ sudo dmesg -C
# Attempt to talk to the system bus under confinement
$ aa-exec -p test -- dbus-send --print-reply --system
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
Failed to open connection to "system" message bus: An AppArmor policy
prevents this sender from sending this message to this recipient;
type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus"
member="Hello" error name="(unset)" requested_reply="0"
destination="org.freedesktop.DBus" (bus)
# We should now see an AppArmor denial in the dmesg output.
# Successful fix verification *must* show the denial from the D-Bus daemon.
$ sudo dmesg | grep DENIED
[ 187.737219] type=1107 audit(1438385684.065:149): pid=826 uid=102
auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/DBus"
interface="org.freedesktop.DBus" member="Hello" mask="send"
name="org.freedesktop.DBus" pid=6721 label="test" peer_label="unconfined"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-flo/+bug/1473584/+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 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
OK, no RAPL interface, so can you run "powerstat -za 1 480" instead. The default mode for the fan is to be controlled by the firmware and not the kernel, so the kernel has no direct control by default. The alternative mechanism is to enable the thinkpad_acpi fan control and twiddle the settings either manually or by software control. By default though, one would expect the firmware do be able to control the fan correctly since that what the system designers intended to be the default fan control mode. If you do intend to try twiddling the fan controls manually, I believe the following instructions may work (but I've not tried these myself, so I can't vouch that they are correct): as root, create a new file /etc/modprobe.d/thinkpad_acpi.conf and add the following line to it: options thinkpad_acpi fan_control=1 ..and reboot. as root try the following to set the fan to the highest "engaged" fan speed: echo level 7 > /proc/acpi/ibm/fan ..hopefully that will crank the fan up to ~5100 RPM in engaged mode. you can enabled disengaged mode using: echo level disengaged > /proc/acpi/ibm/fan Essentially, "engaged" mode is where the fan speed is locked to a defined fan speed. "disengaged" mode can be used to drive the fan faster (I believe there is no feedback loop between the speed and a firmware control that sets the speed in disengaged mode). For more details, see http://www.thinkwiki.org/wiki/How_to_control_fan_speed -- 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/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: Confirmed Bug description: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+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 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
I also get "Device does not have any RAPL domains, cannot power measure power usage." Thinkpad X201, Ubuntu 14.04 LTS. -- 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/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: Confirmed Bug description: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+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 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
Valentine, your problem is almost certainly not related to the one I reported here. You should seek advice in forums or on mailing lists for your computer and/or distribution. -- 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/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+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 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
As suggested on the linux.usb mailing list, I've added some additional debug print statements to the first bad kernel. They are not triggered by "lsusb -v" though. I'm attaching kernel debug output from the boot sequence of two kernels: - the bad one, with additional print statements - the last good one, without additional print statements The difference in the startup behavior is remarkable. ** Attachment added: "first bad kernel, extra output "entry" and "exit"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4456918/+files/dmesg.bad.full.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+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 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
** Attachment added: "last good kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4456919/+files/dmesg.good.full.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+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 1487085] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2015-09-03 16:44 EDT--- *** Bug 129843 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1487085 Title: Ubuntu 14.04.3 LTS Crash in notifier_call_chain after boot Status in linux package in Ubuntu: New Status in linux source package in Vivid: Fix Committed Bug description: SRU Justification: [Impact] Users of 3.19 kernel with power8 machines get a kernel crash on boot. [Test Case] Boot system. [Fix] commit 792f96e9a769b799a2944e9369e4ea1e467135b2 needed to be backported in addition to d7cf83fcaf1b1668201eae4cdd6e6fe7a2448654. Our 3.19 kernel had a partial backport of the first patch. -- ---Problem Description--- Installed Ubuntu 14.04.3 LTS on Palmetto and its crashing after booting to login. This happens every time I boot Ubuntu 14.04.3 LTS. I've reinstalled Ubuntu and replaced the hard disk as well and re-installed. Still crashing. ---uname output--- Linux paul40 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:10:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Palmetto ---System Hang--- Ubuntu OS crashes and cannot access host. Must reboot system ---Steps to Reproduce--- Boot system Oops output: [ 33.132376] Unable to handle kernel paging request for data at address 0x200 [ 33.132565] Faulting instruction address: 0xc00dbc60 [ 33.133422] Oops: Kernel access of bad area, sig: 11 [#1] [ 33.134410] SMP NR_CPUS=2048 NUMA PowerNV [ 33.134478] Modules linked in: ast ttm drm_kms_helper joydev mac_hid drm hid_generic usbhid hid syscopyarea sysfillrect sysimgblt i2c_algo_bit ofpart cmdlinepart at24 uio_pdrv_genirq powernv_flash mtd ipmi_powernv powernv_rng opal_prd ipmi_msghandler uio uas usb_storage ahci libahci [ 33.139112] CPU: 24 PID: 0 Comm: swapper/24 Not tainted 3.19.0-26-generic #28~14.04.1-Ubuntu [ 33.139943] task: c13cccb0 ti: c00fff70 task.ti: c1448000 [ 33.141642] NIP: c00dbc60 LR: c00dbd94 CTR: [ 33.142605] REGS: c00fff703980 TRAP: 0300 Not tainted (3.19.0-26-generic) [ 33.143417] MSR: 90009033 CR: 28002888 XER: [ 33.144244] CFAR: c0008468 DAR: 0200 DSISR: 4000 SOFTE: 0 GPR00: c00dbd94 c00fff703c00 c144cc00 c15f03c0 GPR04: 0007 c15f03b8 GPR08: 0200 c006c394 90001003 GPR12: 2200 cfb8d800 0058 GPR16: c1448000 c1448000 c1448080 c0e9a880 GPR20: c1448080 0001 0002 0012 GPR24: c00f1e432200 c15f03b8 GPR28: 0007 c15f03c0 [ 33.157013] NIP [c00dbc60] notifier_call_chain+0x70/0x100 [ 33.157818] LR [c00dbd94] atomic_notifier_call_chain+0x44/0x60 [ 33.162090] Call Trace: [ 33.162845] [c00fff703c00] [0008] 0x8 (unreliable) [ 33.163644] [c00fff703c50] [c00dbd94] atomic_notifier_call_chain+0x44/0x60 [ 33.164647] [c00fff703c90] [c006f2a8] opal_message_notify+0xa8/0x100 [ 33.165476] [c00fff703d00] [c00dbc88] notifier_call_chain+0x98/0x100 [ 33.167007] [c00fff703d50] [c00dbd94] atomic_notifier_call_chain+0x44/0x60 [ 33.167816] [c00fff703d90] [c006f654] opal_do_notifier.part.5+0x74/0xa0 [ 33.172166] [c00fff703dd0] [c006f6d8] opal_interrupt+0x58/0x70 [ 33.172997] [c00fff703e10] [c01273d0] handle_irq_event_percpu+0x90/0x2b0 [ 33.174507] [c00fff703ed0] [c0127658] handle_irq_event+0x68/0xd0 [ 33.175312] [c00fff703f00] [c012baf4] handle_fasteoi_irq+0xe4/0x240 [ 33.176124] [c00fff703f30] [c01265c8] generic_handle_irq+0x58/0x90 [ 33.176936] [c00fff703f60] [c0010f10] __do_irq+0x80/0x190 [ 33.182406] [c00fff703f90] [c002476c] call_do_irq+0x14/0x24 [ 33.183258] [c144ba30] [c00110c0] do_IRQ+0xa0/0x120 [ 33.184072] [c144ba90] [c00025d8] hardware_interrupt_common+0x158/0x180 [ 33.184907] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90 [ 33.184907] LR = arch_local_irq_restore+0x40/0x90 [ 33.186473] [c144bd80] [c00f2ae19808] 0xc00f2ae19808 (unreliable) [ 33.188024] [c144bda0] [c085d5d8] cpuidle_enter_state+0xa8/
[Kernel-packages] [Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
I might renew the cooler paste some day. Why isn't the fan being run in disengaged mode at 5100 RPM by the kernel in a thermal emergency? Surely that would be easier to do than to have every Lenovo W500's cooler pastes renewed? -- 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/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: Confirmed Bug description: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+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 1394368] Re: Bluetooth with AR9462 doesn't work (New ID /Firmware)
I've been following this bug as I'm also affected. I've AR9462 in Acer
Aspire V3-371-79RJ and Ubuntu 15.04 (3.19.0-26-generic).
I made a clean install about a month ago and have now all updates
installed. Still dmesg says: "Bluetooth: Patch file not found
ar3k/AthrBT_0x11020100.dfu" and bluetooth is not working.
Could someone please recap the above discussion and point out what steps
a general user needs to take to make Bluetooth work?
Thanks for fixing this for us!
--
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/1394368
Title:
Bluetooth with AR9462 doesn't work (New ID /Firmware)
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux source package in Vivid:
Fix Released
Status in linux-firmware source package in Vivid:
Confirmed
Bug description:
This is (kind of) a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1024884
(please read)
I can't use Bluetooth with my AR9462 WLAN/BT-Combo.
In the link above, it has been fixed, but not for my Adapter ID/Firmware:
System:
Ubuntu 14.10 utopic 64bit - 3.16.0-24-generic x86_64
lspci -nnk
02:00.0 Network controller [0280]: Qualcomm Atheros AR9462
Wireless Network Adapter [168c:0034] (rev 01)
Subsystem: Lite-On Communications Inc Device [11ad:0802]
Kernel driver in use: ath9k
lsusb (identified Bluetooth Device)
Bus 002 Device 003: ID 04ca:300d Lite-On Technology Corp.
ath9k.conf
options ath9k btcoex_enable=1
The "04ca:300d" ID is not in the Kernel, so i added it via dkms.
I took ath3k.c and btusb.c out of the 3.16.0-24-generic source files
and changed them:
diff -urN ./linux-3.16.0/drivers/bluetooth/ath3k.c
/usr/src/ar9462-1.5.1/ath3k.c
--- ./linux-3.16.0/drivers/bluetooth/ath3k.c 2014-08-04 00:25:02.0
+0200
+++ /usr/src/ar9462-1.5.1/ath3k.c 2014-11-19 21:12:46.646265890 +0100
@@ -85,6 +85,7 @@
{ USB_DEVICE(0x04CA, 0x3007) },
{ USB_DEVICE(0x04CA, 0x3008) },
{ USB_DEVICE(0x04CA, 0x300b) },
+ { USB_DEVICE(0x04CA, 0x300d) },
{ USB_DEVICE(0x0930, 0x0219) },
{ USB_DEVICE(0x0930, 0x0220) },
{ USB_DEVICE(0x0b05, 0x17d0) },
@@ -134,6 +135,7 @@
{ USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x04ca, 0x300b), .driver_info = BTUSB_ATH3012 },
+ { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0220), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },
diff -urN ./linux-3.16.0/drivers/bluetooth/btusb.c
/usr/src/ar9462-1.5.1/btusb.c
--- ./linux-3.16.0/drivers/bluetooth/btusb.c 2014-08-04 00:25:02.0
+0200
+++ /usr/src/ar9462-1.5.1/btusb.c 2014-11-19 21:12:46.646265890 +0100
@@ -157,6 +157,7 @@
{ USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x04ca, 0x300b), .driver_info = BTUSB_ATH3012 },
+ { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0930, 0x0220), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },
sudo dkms add -m ar9462 -v 1.5.1
sudo dkms build -m ar9462 -v 1.5.1
sudo dkms install -m ar9462 -v 1.5.1
(DKMS package in the same style/versioning as in the bug report above)
dkms status
ar9462, 1.5.1, 3.16.0-24-generic, x86_64: installed
Now the new output:
dmesg | egrep 'ath3|ar3|Bluet'
[2.787819] Bluetooth: Core ver 2.19
[2.787833] Bluetooth: HCI device and connection manager initialized
[2.787839] Bluetooth: HCI socket layer initialized
[2.787842] Bluetooth: L2CAP socket layer initialized
[2.787848] Bluetooth: SCO socket layer initialized
[2.793551] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[2.793554] Bluetooth: BNEP filters: protocol multicast
[2.793561] Bluetooth: BNEP socket layer initialized
[3.130779] Bluetooth: Patch file not found ar3k/AthrBT_0x11020100.dfu
[3.130783] Bluetooth: Loading patch file failed
[3.130788] ath3k: probe of 2-5:1.0 failed with error -12
[3.130823] usbcore: registered new interface driver ath3k
[9.776503] Bluetooth: RFCOMM TTY layer initialized
[9.776512] Bluetooth: RFCOMM socket layer initialized
[9.776517] Bluetooth: RFCOMM ver 1.11
My patch works, but just like in the bug report above, a Firmware file is
missing:
AthrBT_0x11020100.dfu
I found it neither in linux-firmware
(http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ar3k)
nor elsewhere.
To manage notif
[Kernel-packages] [Bug 1490785] Re: linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => John Johansen (jjohansen) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1490785 Title: linux-lts-vivid: 3.19.0-28.30~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: New Bug description: This bug is for tracking the 3.19.0-28.30~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, 01. September 2015 01:02 UTC kernel-stable-master-bug:1490606 kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 18:01 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1490785/+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 1462761] Re: [MacBook8, 1] TouchPad doesn't work
Hi Guys. This is quite a serious bug. I have installed 15.10Beta1 and still no keyboard no mouse ... basically completely useless :( I updated to kernel 4.2 from the ubuntu kernel team. same behavior. I saw comments, that is because of USB-c ? How can I help to debug this? You guys need new logfiles? Tanks derarnold ** 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/1462761 Title: [MacBook8,1] TouchPad doesn't work Status in linux package in Ubuntu: Confirmed Bug description: Touchpad doesn't work. --- ApportVersion: 2.17.3-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1889 F pulseaudio /dev/snd/controlC0: ubuntu 1889 F pulseaudio CasperVersion: 1.360 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150603) MachineType: Apple Inc. MacBook8,1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-generic N/A linux-backports-modules-3.19.0-20-generic N/A linux-firmware 1.144 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/24/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB81.88Z.0164.B02.1503241252 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-BE0E8AC46FE800CC dmi.board.vendor: Apple Inc. dmi.board.version: MacBook8,1 dmi.chassis.asset.tag: Chassis Board Asset Tag# dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-BE0E8AC46FE800CC dmi.modalias: dmi:bvnAppleInc.:bvrMB81.88Z.0164.B02.1503241252:bd03/24/2015:svnAppleInc.:pnMacBook8,1:pvr1.0:rvnAppleInc.:rnMac-BE0E8AC46FE800CC:rvrMacBook8,1:cvnAppleInc.:ct9:cvrMac-BE0E8AC46FE800CC: dmi.product.name: MacBook8,1 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/1462761/+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 1490606] Re: linux: 3.19.0-28.30 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => John Johansen (jjohansen) -- 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/1490606 Title: linux: 3.19.0-28.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow package-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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-28.30 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, 31. August 2015 15:07 UTC kernel-stable-Prepare-package-end:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 01. September 2015 01:04 UTC kernel-stable-Promote-to-proposed-end:Wednesday, 02. September 2015 16:18 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Verification-testing-start:Wednesday, 02. September 2015 18:01 UTC kernel-stable-Certification-testing-start:Wednesday, 02. September 2015 18:02 UTC kernel-stable-Security-signoff-start:Wednesday, 02. September 2015 18:02 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Wednesday, 02. September 2015 18:02 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1490606/+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 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
running "powerstat -Da 1 60" returns "Device does not have any RAPL domains, cannot power measure power usage." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost Status in linux package in Ubuntu: Confirmed Bug description: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+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
