[Kernel-packages] [Bug 1504219] Re: [To Be Filled By O.E.M. To Be Filled By O.E.M.] suspend/resume failure
[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/1504219 Title: [To Be Filled By O.E.M. To Be Filled By O.E.M.] suspend/resume failure Status in linux package in Ubuntu: Expired Bug description: Rebooted after trying to suspend ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-15-generic 4.2.0-15.18 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timmillwood 1627 F pulseaudio /dev/snd/controlC1: timmillwood 1627 F pulseaudio Date: Thu Oct 8 17:37:07 2015 DuplicateSignature: suspend/resume:To Be Filled By O.E.M. To Be Filled By O.E.M.:P1.30 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=3415ec44-04bc-4d6d-8fc8-bd4f7b6c3451 InstallationDate: Installed on 2015-10-04 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) InterpreterPath: /usr/bin/python3.4 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 ProcFB: 0 radeondrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-15-generic root=UUID=c621629a-b55c-47f1-8534-ccdd44a1c5dd 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: linux-restricted-modules-4.2.0-15-generic N/A linux-backports-modules-4.2.0-15-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux Title: [To Be Filled By O.E.M. To Be Filled By O.E.M.] suspend/resume failure UpgradeStatus: Upgraded to wily on 2015-10-07 (0 days ago) UserGroups: dmi.bios.date: 05/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: Z68 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd05/04/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504219/+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 1504417] Re: BUG: unable to handle kernel NULL pointer dereference at 00000011
[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/1504417 Title: BUG: unable to handle kernel NULL pointer dereference at 0011 Status in linux package in Ubuntu: Expired Bug description: The boot was failed. This session was start with "GRUB menù" ProblemType: KernelOops DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-15-generic 4.2.0-15.17 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-15-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.19-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emsidj 2468 F pulseaudio Date: Thu Oct 8 13:12:38 2015 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at location EIP: location show_map_vma+0x45/0x2d0 SS:ESP 0068:d58b3e88 Failure: oops HibernationDevice: RESUME=UUID=ad686395-81e9-40d1-86a3-708eead8c6b4 InstallationDate: Installed on 2012-01-14 (1364 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=69b276ef-4078-4eff-a226-1f20f85929ba ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at 0011 UpgradeStatus: Upgraded to wily on 2015-09-20 (18 days ago) dmi.bios.date: 12/11/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04CA.MP00.20081211.KTW dmi.board.name: NC10 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04CA.MP00.20081211.KTW:bd12/11/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: NC10 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504417/+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 1389675] Re: Function keys will not adjust brightness
[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/1389675 Title: Function keys will not adjust brightness Status in linux package in Ubuntu: Expired Bug description: I have just installed Ubuntu 14.04, and I cannot make the function keys adjust the brightness. I have been trying to get a solution to the problem in this forum http://ubuntuforums.org/showthread.php?t=2250862&page=2&p=13159626#post13159626 . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 1336 F pulseaudio /dev/snd/pcmC0D0p: paul 1336 F...m pulseaudio CurrentDesktop: Unity Date: Wed Nov 5 13:31:30 2014 HibernationDevice: RESUME=UUID=6357ccbf-2f39-4ca6-9cc1-65eb05bf30f6 InstallationDate: Installed on 2014-10-29 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b404 Chicony Electronics Co., Ltd Bus 001 Device 006: ID 1c4f:0003 SiGma Micro HID controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed root=UUID=730dc0d2-8142-4bc0-a5ee-a2928da9bd65 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.510:bd06/27/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X551MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389675/+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 1497520] Re: Slow performance after resuming from/on battery (CPUs do not scale above 800MHz) with intel_pstate
[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/1497520
Title:
Slow performance after resuming from/on battery (CPUs do not scale
above 800MHz) with intel_pstate
Status in linux package in Ubuntu:
Expired
Bug description:
I have noticed slow performance after resuming from STR on battery.
I can not trigger this always, but it seems to be related to
suspending and resuming while on battery.
The CPU scaling governors look like this then:
% cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
powersave
performance
performance
performance
% cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_driver
intel_pstate
intel_pstate
intel_pstate
intel_pstate
% cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq
320
320
320
320
When watching the current CPU frequencies, it can be seen that they
don't go above 80 ('watch grep \"cpu MHz\" /proc/cpuinfo').
I cannot see why they are limited to 80.
It looks like https://bugzilla.kernel.org/show_bug.cgi?id=61241, but
/sys/devices/system/cpu/intel_pstate/max_perf_pct is at 100.
Just writing the same setting for cpu0 again fixes it, and all CPUs
will be scaled above 800MHz again:
% echo powersave | sudo tee
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-28-generic 3.19.0-28.30
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Sep 19 10:39:02 2015
HibernationDevice: RESUME=UUID=d39463f5-889e-42ba-a729-f3f442f0c8dd
InstallationDate: Installed on 2012-05-28 (1208 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MachineType: LENOVO 42992PG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic
root=/dev/mapper/vg0-rootlv ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-3.19.0-28-generic N/A
linux-backports-modules-3.19.0-28-generic N/A
linux-firmware 1.143.3
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-05-14 (127 days ago)
dmi.bios.date: 05/14/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET70WW (1.40 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42992PG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET70WW(1.40):bd05/14/2015:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 42992PG
dmi.product.version: ThinkPad X220 Tablet
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497520/+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 1525251] Re: linux: 4.3.0-4.13 -proposed tracker
** Changed in: kernel-development-workflow/prepare-package-signed Status: New => Fix Released ** Changed in: kernel-development-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1525251 Title: linux: 4.3.0-4.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.3.0-4.13 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 11. December 2015 13:51 UTC kernel-phase-changed:Friday, 11. December 2015 13:51 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Friday, 11. December 2015 14:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1525251/+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 1447053] Re: IO_PAGE_FAULT
I did that. Will that affect new boot images as well? i.e. the ones I get after installing updates. -- 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/1447053 Title: IO_PAGE_FAULT Status in linux package in Ubuntu: Confirmed Bug description: Since a couple of weeks I'm experiencing a problem with my motherboard. For some reason the network goes randomly offline and I get a error messages about AMD-Vi. [ 6462.248434] AMD-Vi: Event logged [IO_PAGE_FAULT device=04:00.0 domain=0x0019 address=0x3000 flags=0x0050] I didn't changed anything except for the internet modem is changed and I installed updates as I always do. When using google I see there are more people with this problem exactly the same motherboard, I find this strange because my pc is almost a year old and I never had this problem. Could it be a problem in the kernel of *ubuntu 14.04? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-49-generic 3.13.0-49.83 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allard 2282 F pulseaudio allard 2467 F pulseaudio /dev/snd/controlC0: allard 2282 F pulseaudio allard 2467 F pulseaudio CurrentDesktop: KDE Date: Wed Apr 22 11:34:46 2015 HibernationDevice: RESUME=UUID=96633d31-18c6-4b01-b756-f5f919c43fb4 InstallationDate: Installed on 2015-03-27 (25 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=2c77ade3-e2ea-4d88-94d6-e131053f8ac8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-49-generic N/A linux-backports-modules-3.13.0-49-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd04/02/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447053/+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 1516102] Re: 10ec:b723 [HP Notebook - 15-af008ax] Wifi unstable and unresponsive
soumyajyoti, could you please advise to the router manufacturer, model, and firmware version? ** Summary changed: - [HP Notebook - 15-af008ax] Wifi unstable and unresponsive + 10ec:b723 [HP Notebook - 15-af008ax] Wifi unstable and unresponsive ** Changed in: linux (Ubuntu) Importance: Medium => High -- 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/1516102 Title: 10ec:b723 [HP Notebook - 15-af008ax] Wifi unstable and unresponsive Status in linux package in Ubuntu: Incomplete Bug description: The connections are not shown in the Network Manager.After a long wait though the Network manager shows up but the SSID but doesn't connect when chosen.Even if sometimes it connects it is very slow,unstable and eventually disconnects. I have installed new drivers @https://github.com/lwfinger/rtlwifi_new but to no avail. I have also changed the mode of the router to b,b/g,g operating at 20 MHz from b/g/n operation at 40Mhz . I am attaching the Wireless script details herewith. Point to be noted the Network Manager works well with the WIfi Network of my LAVA df800 CDMA Rev b dongle. The router is working fine with 3 other systems(Android/Windows/Linux Mint).The Router is TL-WR720N ---System Details--- Description: Ubuntu 15.10 Release: 15.10 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: soumyajyoti 1257 F pulseaudio /dev/snd/controlC0: soumyajyoti 1257 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 13 22:49:21 2015 HibernationDevice: RESUME=UUID=32bbfbc8-d105-43a2-97d8-e6026bffbdab InstallationDate: Installed on 2015-11-11 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Hewlett-Packard HP Notebook ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=79ea6210-b7e1-4a35-b0e5-741b260fabf5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80CC dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/13/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80CC:rvr99.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516102/+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 1516102] Re: [HP Notebook - 15-af008ax] Wifi unstable and unresponsive
** Tags removed: kernel-bug-exists-upstream-4.3 ** Tags added: kernel-bug-exists-upstream-4.4-rc4 -- 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/1516102 Title: [HP Notebook - 15-af008ax] Wifi unstable and unresponsive Status in linux package in Ubuntu: Incomplete Bug description: The connections are not shown in the Network Manager.After a long wait though the Network manager shows up but the SSID but doesn't connect when chosen.Even if sometimes it connects it is very slow,unstable and eventually disconnects. I have installed new drivers @https://github.com/lwfinger/rtlwifi_new but to no avail. I have also changed the mode of the router to b,b/g,g operating at 20 MHz from b/g/n operation at 40Mhz . I am attaching the Wireless script details herewith. Point to be noted the Network Manager works well with the WIfi Network of my LAVA df800 CDMA Rev b dongle. The router is working fine with 3 other systems(Android/Windows/Linux Mint).The Router is TL-WR720N ---System Details--- Description: Ubuntu 15.10 Release: 15.10 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: soumyajyoti 1257 F pulseaudio /dev/snd/controlC0: soumyajyoti 1257 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 13 22:49:21 2015 HibernationDevice: RESUME=UUID=32bbfbc8-d105-43a2-97d8-e6026bffbdab InstallationDate: Installed on 2015-11-11 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Hewlett-Packard HP Notebook ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=79ea6210-b7e1-4a35-b0e5-741b260fabf5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80CC dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/13/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80CC:rvr99.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516102/+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 1525228] Re: Qualcomm Atheros QCA61x4 cannot connect to encrypted 5Ghz networks
Roman, thank you for reporting this and helping make Ubuntu better. While you may have tested a later version of the firmware than is in a Ubuntu repository, it appears there is a later version available from upstream. Hence, could you please test https://github.com/kvalo/ath10k- firmware/tree/master/QCA6174/hw3.0 and advise to the results? ** Package changed: linux (Ubuntu) => linux-firmware (Ubuntu) ** Changed in: linux-firmware (Ubuntu) Importance: Critical => High ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Incomplete -- 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/1525228 Title: Qualcomm Atheros QCA61x4 cannot connect to encrypted 5Ghz networks Status in linux-firmware package in Ubuntu: Incomplete Bug description: The device works fine with Ubuntu 15.10 mainline kernel 4.2.0 and the firmware provided in linux-firmware on 2,4 Ghz wifi networks or unencrypted 5GHz networks. But when i connect to a encrypted 5Ghz network. The firmware provide in linux-firmware (WLAN.RM.1.1-00141) crashed like i think is described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516384 So i installed the latest firmware release SW_RM.1.1.1-00157-QCARMSWPZ-1 from ath10k-firmware (https://github.com/kvalo/ath10k-firmware/) In this version the firmware doesn't crash but goes into a loop. Like you see in dmesg, the device associates with the AP, but from an unknown reason it cannot connect. At the moment i cannot provide you any details about the AP im testing with, because im using my universities network, but if you really need them i can test the device with an known AP in a week or so. I reported the bug to the ath10k mailing list, but i think the topic got lost: http://lists.infradead.org/pipermail/ath10k/2015-November/006478.html PS: I tested the problem with all mainline and upstream kernels(4.2.6, 4.3.0,4.4rc4) without any difference. - ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roman 2043 F pulseaudio /dev/snd/controlC1: roman 2043 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 11 14:01:58 2015 HibernationDevice: RESUME=UUID=38f2bb72-0ff3-498e-ab17-249df8b33aef InstallationDate: Installed on 2015-10-23 (49 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire VN7-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=da03328e-3129-4dfc-98d7-b8b06fa3d5f1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-571G dmi.board.vendor: Acer dmi.board.version: V1.14 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14: dmi.product.name: Aspire VN7-571G dmi.product.version: V1.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1525228/+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 1524426] Re: linux: 4.3.0-3.12 -proposed tracker
*** This bug is a duplicate of bug 1525251 *** https://bugs.launchpad.net/bugs/1525251 ** This bug has been marked a duplicate of bug 1525251 linux: 4.3.0-4.13 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1524426 Title: linux: 4.3.0-3.12 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.3.0-3.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Wednesday, 09. December 2015 17:20 UTC kernel-phase-changed:Wednesday, 09. December 2015 17:20 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Wednesday, 09. December 2015 18:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1524426/+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 1525251] Re: linux: 4.3.0-4.13 -proposed tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1525251 Title: linux: 4.3.0-4.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.3.0-4.13 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Friday, 11. December 2015 13:51 UTC kernel-phase-changed:Friday, 11. December 2015 13:51 UTC kernel-phase:Prepare kernel-stable-Promote-to-proposed-end:Friday, 11. December 2015 14:00 UTC proposed-announcement-sent:True To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1525251/+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 1525459] 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/1525459 Title: Touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: USB Optical mouse is detected and functioning, xinput does not detect the touchpad. cat /proc/bus/input/devices does not detect the touchpad either. xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt Lenovo USB Optical Mouse id=9[slave pointer (2)] evert@evert-laptop:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=17ef Product=6019 Version=0111 N: Name="PixArt Lenovo USB Optical Mouse" P: Phys=usb-:00:14.0-6/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:17EF:6019.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=100013 B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input6 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 Include an attachment (Optional) Attachment: (Optio B: EV=21 B: SW=140 I: Bus=0003 Vendor=04f2 Product=b424 Version=6969 N: Name="USB2.0 HD UVC WebCam" P: Phys=usb-:00:14.0-4/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input9 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: boot/vmlinuz-3.19.0-15-generic] ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evert 1749 F pulseaudio CurrentDesktop: GNOME Date: Fri Dec 11 21:01:01 2015 HibernationDevice: RESUME=UUID=33cc4efa-1999-47ad-b0f6-2c6fa5cc2d24 InstallationDate: Installed on 2015-12-11 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 17ef:6019 Lenovo Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL552VW ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=ebbce668-5e09-4c15-b5c8-83a1b796ad4a ro recovery nomodeset reboot=efi RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 So
[Kernel-packages] [Bug 1525459] Re: Touchpad not detected
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525459/+attachment/4533531/+files/Xorg.0.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/1525459 Title: Touchpad not detected Status in linux package in Ubuntu: New Bug description: USB Optical mouse is detected and functioning, xinput does not detect the touchpad. cat /proc/bus/input/devices does not detect the touchpad either. xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt Lenovo USB Optical Mouse id=9[slave pointer (2)] evert@evert-laptop:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=17ef Product=6019 Version=0111 N: Name="PixArt Lenovo USB Optical Mouse" P: Phys=usb-:00:14.0-6/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:17EF:6019.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=100013 B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input6 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 Include an attachment (Optional) Attachment: (Optio B: EV=21 B: SW=140 I: Bus=0003 Vendor=04f2 Product=b424 Version=6969 N: Name="USB2.0 HD UVC WebCam" P: Phys=usb-:00:14.0-4/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input9 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: boot/vmlinuz-3.19.0-15-generic] ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evert 1749 F pulseaudio CurrentDesktop: GNOME Date: Fri Dec 11 21:01:01 2015 HibernationDevice: RESUME=UUID=33cc4efa-1999-47ad-b0f6-2c6fa5cc2d24 InstallationDate: Installed on 2015-12-11 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 17ef:6019 Lenovo Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL552VW ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=ebbce668-5e09-4c15-b5c8-83a1b796ad4a ro recovery nomodeset reboot=efi RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware
[Kernel-packages] [Bug 1525459] Re: Touchpad not detected
** Attachment added: "~devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525459/+attachment/4533532/+files/%7Edevices -- 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/1525459 Title: Touchpad not detected Status in linux package in Ubuntu: New Bug description: USB Optical mouse is detected and functioning, xinput does not detect the touchpad. cat /proc/bus/input/devices does not detect the touchpad either. xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt Lenovo USB Optical Mouse id=9[slave pointer (2)] evert@evert-laptop:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=17ef Product=6019 Version=0111 N: Name="PixArt Lenovo USB Optical Mouse" P: Phys=usb-:00:14.0-6/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:17EF:6019.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=100013 B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input6 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 Include an attachment (Optional) Attachment: (Optio B: EV=21 B: SW=140 I: Bus=0003 Vendor=04f2 Product=b424 Version=6969 N: Name="USB2.0 HD UVC WebCam" P: Phys=usb-:00:14.0-4/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input9 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: boot/vmlinuz-3.19.0-15-generic] ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evert 1749 F pulseaudio CurrentDesktop: GNOME Date: Fri Dec 11 21:01:01 2015 HibernationDevice: RESUME=UUID=33cc4efa-1999-47ad-b0f6-2c6fa5cc2d24 InstallationDate: Installed on 2015-12-11 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 17ef:6019 Lenovo Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL552VW ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=ebbce668-5e09-4c15-b5c8-83a1b796ad4a ro recovery nomodeset reboot=efi RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware
[Kernel-packages] [Bug 1525228] Re: Qualcomm Atheros QCA61x4 cannot connect to encrypted 5Ghz networks
** Tags added: latest-bios-1.14 ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.4-rc4 -- 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/1525228 Title: Qualcomm Atheros QCA61x4 cannot connect to encrypted 5Ghz networks Status in linux package in Ubuntu: Confirmed Bug description: The device works fine with Ubuntu 15.10 mainline kernel 4.2.0 and the firmware provided in linux-firmware on 2,4 Ghz wifi networks or unencrypted 5GHz networks. But when i connect to a encrypted 5Ghz network. The firmware provide in linux-firmware (WLAN.RM.1.1-00141) crashed like i think is described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516384 So i installed the latest firmware release SW_RM.1.1.1-00157-QCARMSWPZ-1 from ath10k-firmware (https://github.com/kvalo/ath10k-firmware/) In this version the firmware doesn't crash but goes into a loop. Like you see in dmesg, the device associates with the AP, but from an unknown reason it cannot connect. At the moment i cannot provide you any details about the AP im testing with, because im using my universities network, but if you really need them i can test the device with an known AP in a week or so. I reported the bug to the ath10k mailing list, but i think the topic got lost: http://lists.infradead.org/pipermail/ath10k/2015-November/006478.html PS: I tested the problem with all mainline and upstream kernels(4.2.6, 4.3.0,4.4rc4) without any difference. - ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roman 2043 F pulseaudio /dev/snd/controlC1: roman 2043 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 11 14:01:58 2015 HibernationDevice: RESUME=UUID=38f2bb72-0ff3-498e-ab17-249df8b33aef InstallationDate: Installed on 2015-10-23 (49 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire VN7-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=da03328e-3129-4dfc-98d7-b8b06fa3d5f1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-571G dmi.board.vendor: Acer dmi.board.version: V1.14 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14: dmi.product.name: Aspire VN7-571G dmi.product.version: V1.14 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525228/+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 1525459] [NEW] Touchpad not detected
Public bug reported: USB Optical mouse is detected and functioning, xinput does not detect the touchpad. cat /proc/bus/input/devices does not detect the touchpad either. xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PixArt Lenovo USB Optical Mouse id=9[slave pointer (2)] evert@evert-laptop:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=17ef Product=6019 Version=0111 N: Name="PixArt Lenovo USB Optical Mouse" P: Phys=usb-:00:14.0-6/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/0003:17EF:6019.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=100013 B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input6 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 Include an attachment (Optional) Attachment: (Optio B: EV=21 B: SW=140 I: Bus=0003 Vendor=04f2 Product=b424 Version=6969 N: Name="USB2.0 HD UVC WebCam" P: Phys=usb-:00:14.0-4/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input9 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: boot/vmlinuz-3.19.0-15-generic] ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evert 1749 F pulseaudio CurrentDesktop: GNOME Date: Fri Dec 11 21:01:01 2015 HibernationDevice: RESUME=UUID=33cc4efa-1999-47ad-b0f6-2c6fa5cc2d24 InstallationDate: Installed on 2015-12-11 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 17ef:6019 Lenovo Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL552VW ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=ebbce668-5e09-4c15-b5c8-83a1b796ad4a ro recovery nomodeset reboot=efi RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.210:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnGL552VW:pv
[Kernel-packages] [Bug 1523765] Re: USB performance extremely unstable
Why incomplete @Alberto? -- 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/1523765 Title: USB performance extremely unstable Status in linux package in Ubuntu: Incomplete Bug description: Since I upgraded from Trusty to Wily, the USB performance has become extremely unstable. Sometimes file transfers were fast, like 1GB in 30 sec, then most days it is so slow like 1 GB in 20 minutes for no reason. Here some relevant log lines from the `dmesg` command when I USB is plugged in: ``` [ 496.912939] usb 4-5: new high-speed USB device number 2 using ehci-pci [ 497.111419] usb 4-5: New USB device found, idVendor=1b1c, idProduct=1ab1 [ 497.111425] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 497.111428] usb 4-5: Product: Voyager [ 497.111430] usb 4-5: Manufacturer: Corsair [ 497.111433] usb 4-5: SerialNumber: AA400825 [ 497.134497] usb-storage 4-5:1.0: USB Mass Storage device detected [ 497.134600] scsi host12: usb-storage 4-5:1.0 [ 497.134713] usbcore: registered new interface driver usb-storage [ 497.137090] usbcore: registered new interface driver uas [ 498.420795] scsi 12:0:0:0: Direct-Access Corsair Voyager 1100 PQ: 0 ANSI: 0 CCS [ 498.421211] sd 12:0:0:0: Attached scsi generic sg5 type 0 [ 498.913643] sd 12:0:0:0: [sdd] 15663104 512-byte logical blocks: (8.01 GB/7.46 GiB) [ 498.914804] sd 12:0:0:0: [sdd] Write Protect is off [ 498.914809] sd 12:0:0:0: [sdd] Mode Sense: 43 00 00 00 [ 498.915930] sd 12:0:0:0: [sdd] No Caching mode page found [ 498.915934] sd 12:0:0:0: [sdd] Assuming drive cache: write through [ 498.920710] sdd: sdd1 [ 498.924684] sd 12:0:0:0: [sdd] Attached SCSI removable disk [ 1184.038007] usb 4-5: USB disconnect, device number 2 ``` these two lines appear in *red* ``` [ 498.915930] sd 12:0:0:0: [sdd] No Caching mode page found [ 498.915934] sd 12:0:0:0: [sdd] Assuming drive cache: write through ``` What can we do here? How can this be investigated and fixed properly? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael-heuberger 4363 F pulseaudio /dev/snd/controlC2: michael-heuberger 4363 F pulseaudio /dev/snd/controlC0: michael-heuberger 4363 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028 InstallationDate: Installed on 2014-10-31 (403 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: wily Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data _MarkForUpload: True dmi.bios.date: 08/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523765/+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 1525450] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1525450 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/1525450 Title: SATA III recognized as SATA II Status in linux package in Ubuntu: Incomplete Bug description: Following #889071, I want to say that even on Kernel linux-image-4.2.0-19-generic 4.2.0-19.23~14.04.1 (14.04 LTS with wily-kernel ) the SATA III recognition is a bit shaky, but less than it used to be in the 3.x series. Also, the SATA-Numbers keep changing, so it is hard to tell which disk has the issue...: [2.481536] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.481568] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.481600] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.485425] ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.649406] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.481503] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) <= Thats unexpected [2.501404] ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.557461] ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [3.468992] ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (about 10-20% of boots) --- That's OK, but why different numbers? [2.476286] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476324] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476356] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476386] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476409] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.480199] ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.500201] ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.500229] ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [3.303818] ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) That is on Asus Sabertooth AMD-FX8350-Board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1525270] Re: Wi-Di Realtek 8192E disconnects after a while and fails to reconnect
Title should read "Wi-Fi Realtek 8192E" etc. g 2015-12-11 18:45 GMT-05:00 Alberto Salvia Novella : > ** Changed in: linux (Ubuntu) >Importance: Undecided => High > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1525270 > > Title: > Wi-Di Realtek 8192E disconnects after a while and fails to reconnect > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > A few minutes after booting my Samsung R580 laptop, the Wi-Fi > disconnects and it fails to reconnect until I restart the machine. > This happens with all the 64 bit versions of Ubuntu I tried, from > 14.04 to 15.10. With the 32 bit versions, everything runs perfectly. > No loss of connection at all, even after 48 hours in a row. > > Here is the output of iwconfig after loss of connexion: > > eth7 no wireless extensions. > > lono wireless extensions. > > wlan6 802.11bgn ESSID:"JeLisVosCourriels" Nickname:"rtl8192E" > Mode:Managed Frequency=2.417 GHz Access Point: Not-Associated > Bit Rate:19.5 Mb/s > Retry min limit:7 RTS thr:off Fragment thr:off > Power Management:off > Link Quality=10/100 Signal level=0 dBm Noise level=-100 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > ProblemType: Bug > DistroRelease: Ubuntu 15.10 > Package: linux-image-4.2.0-19-generic 4.2.0-19.23 > ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 > Uname: Linux 4.2.0-19-generic x86_64 > ApportVersion: 2.19.1-0ubuntu5 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: gilbert3115 F pulseaudio >/dev/snd/controlC0: gilbert3115 F pulseaudio > CurrentDesktop: Unity > Date: Fri Dec 11 09:27:18 2015 > HibernationDevice: RESUME=UUID=e19f92d5-541f-412f-b5b0-7d97bfa1b7ec > InstallationDate: Installed on 2015-12-03 (7 days ago) > InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 > (20141022.1) > MachineType: SAMSUNG ELECTRONICS CO., LTD. R580 > ProcFB: 0 nouveaufb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic > root=UUID=f6b1d099-6ed1-4e82-823a-352535c7596c ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-4.2.0-19-generic N/A >linux-backports-modules-4.2.0-19-generic N/A >linux-firmware1.149.3 > SourcePackage: linux > UpgradeStatus: Upgraded to wily on 2015-12-03 (7 days ago) > dmi.bios.date: 12/21/2009 > dmi.bios.vendor: Phoenix Technologies Ltd. > dmi.bios.version: 04JB.M014.20091221.hkk > dmi.board.asset.tag: Tag 12345 > dmi.board.name: R580 > dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. > dmi.board.version: Not Applicable > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 9 > dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnPhoenixTechnologiesLtd.:bvr04JB.M014.20091221.hkk:bd12/21/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnR580:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR580:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: > dmi.product.name: R580 > dmi.product.version: Not Applicable > dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525270/+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/1525270 Title: Wi-Di Realtek 8192E disconnects after a while and fails to reconnect Status in linux package in Ubuntu: Confirmed Bug description: A few minutes after booting my Samsung R580 laptop, the Wi-Fi disconnects and it fails to reconnect until I restart the machine. This happens with all the 64 bit versions of Ubuntu I tried, from 14.04 to 15.10. With the 32 bit versions, everything runs perfectly. No loss of connection at all, even after 48 hours in a row. Here is the output of iwconfig after loss of connexion: eth7 no wireless extensions. lono wireless extensions. wlan6 802.11bgn ESSID:"JeLisVosCourriels" Nickname:"rtl8192E" Mode:Managed Frequency=2.417 GHz Access Point: Not-Associated Bit Rate:19.5 Mb/s Retry min limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=10/100 Signal level=0 dBm Noise level=-100 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
[Kernel-packages] [Bug 1525450] [NEW] SATA III recognized as SATA II
Public bug reported: Following #889071, I want to say that even on Kernel linux-image-4.2.0-19-generic 4.2.0-19.23~14.04.1 (14.04 LTS with wily-kernel ) the SATA III recognition is a bit shaky, but less than it used to be in the 3.x series. Also, the SATA-Numbers keep changing, so it is hard to tell which disk has the issue...: [2.481536] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.481568] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.481600] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.485425] ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.649406] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.481503] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) <= Thats unexpected [2.501404] ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.557461] ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [3.468992] ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (about 10-20% of boots) --- That's OK, but why different numbers? [2.476286] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476324] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476356] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476386] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476409] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.480199] ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.500201] ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.500229] ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [3.303818] ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) That is on Asus Sabertooth AMD-FX8350-Board. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1525450 Title: SATA III recognized as SATA II Status in linux package in Ubuntu: New Bug description: Following #889071, I want to say that even on Kernel linux-image-4.2.0-19-generic 4.2.0-19.23~14.04.1 (14.04 LTS with wily-kernel ) the SATA III recognition is a bit shaky, but less than it used to be in the 3.x series. Also, the SATA-Numbers keep changing, so it is hard to tell which disk has the issue...: [2.481536] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.481568] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.481600] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.485425] ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.649406] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.481503] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) <= Thats unexpected [2.501404] ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.557461] ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [3.468992] ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (about 10-20% of boots) --- That's OK, but why different numbers? [2.476286] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476324] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476356] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476386] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.476409] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.480199] ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.500201] ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.500229] ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [3.303818] ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) That is on Asus Sabertooth AMD-FX8350-Board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525450/+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 889071] Re: SATA III recognized as SATA II (chipset intel z68)
On Kernel 4.2 now. Less shaky, but sometimes one of the crucial's is SATA II only. Also, the ATA-Numbers are changing from time to time. So indeed, I am filing a new 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/889071 Title: SATA III recognized as SATA II (chipset intel z68) Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: My SSD OCZ vertex 3 60Go SATAIII and my WesternDigital 500Go/s SATAIII are recognized as SATA II discs, according to palimpsest. When I run hdparm -tT /dev/sd?, it returns me that my SSD works à 300Mo/s which means that the disc is effectively limited by the SATA II norm. I have tested the same configuration under windows, and the SSD runs at 480Mo/s in average. My chipset is the intel Z68, and I have updated both the motherboard's and SSD's BIOS. The AHCI mode is activated. Since Ubuntu 12.04, the hdd speed go from 330Mo/s to 360Mo/so. I have tested the kenerl 3.4 rc6 without any improvement. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 1777 F pulseaudio CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfa30 irq 59' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,1043841b,00100302' Controls : 35 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfa08 irq 17' Mixer name : 'Nvidia GPU 12 HDMI/DP' Components : 'HDA:10de0012,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Fri Nov 11 12:40:07 2011 HibernationDevice: RESUME=UUID=aec865ce-43e4-4b3e-9bf1-16375f15d4ad InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111010.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=15b45aa7-65f1-4983-bb8a-7d6e8575f68f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 09/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd09/14/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/889071/+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 1521982] Re: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/le
Translation (best effort): package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extract Data for »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« can not be copied to »/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new« : unexpected end of file or stream. ** 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/1521982 Title: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« können nicht nach »/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko .dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms Status in linux package in Ubuntu: Confirmed Bug description: none ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-extra-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carsten1741 F pulseaudio /dev/snd/controlC1: carsten1741 F pulseaudio Date: Tue Dec 1 21:46:29 2015 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« können nicht nach »/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms HibernationDevice: RESUME=UUID=55b16c37-9a10-448a-8d4e-f59a0ed550ea InstallationDate: Installed on 2015-11-19 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P67A-UD3-B3 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=9c54422a-2851-4e1a-b9f6-28e6374aa754 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-29 RfKill: SourcePackage: linux Title: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« können nicht nach »/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: P67A-UD3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67A-UD3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521982/+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 1518566] Re: Ubuntu 15.10 freezing randomly
Ubuntu froze again after BIOS upgrade, so this is reproducible. ** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => 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/1518566 Title: Ubuntu 15.10 freezing randomly Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 15.10 freezing randomly ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spyros 3013 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 21 16:15:04 2015 HibernationDevice: RESUME=UUID=3fbc151c-b9b3-492c-a1f4-c598a0b080bb InstallationDate: Installed on 2015-09-23 (58 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 0bda:57bc Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X751MA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=59242a09-40d6-4231-b79b-543e0a88dbde ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-05 (15 days ago) dmi.bios.date: 01/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X751MA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X751MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX751MA.208:bd01/26/2015:svnASUSTeKCOMPUTERINC.:pnX751MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X751MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518566/+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 1525254] Re: The r8188eu driver shipped with wily is broken, new working driver exists
** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1525254 Title: The r8188eu driver shipped with wily is broken, new working driver exists Status in linux package in Ubuntu: Confirmed Bug description: After update to wily, I have continuous disconnections with a tplink 725N wifi usb dongle that uses the r8188eu driver to the point that the dongle is completely useless. In vivid, the driver driver shipped with the kernel was problematic but working a bit better (some disconnections, and incorrect link quality reporting, but OK for the rest) so we definitely have a REGRESSION. Furthermore, on the tplink driver the *source* or a driver that works fine is available: http://www.tp-link.us/res/down/soft/TL-WN725N_V2_150911.zip Porting to a format consistent with the pristine kernel has been done, see https://github.com/lwfinger/rtl8188eu/issues/152 and https://www.dropbox.com/s/znp5munr03oow0b/rtl8188eu-linux- driver.zip?dl=0 The thing still does not compile cleanly against the 4.2 kernel shipped in wily, because the interface of cfg80211_disconnected has changed, but the fix is trivial diff -r rtl8188eu-linux-driver/os_dep/linux/ioctl_cfg80211.c rtl8188eu-linux-driver2/os_dep/linux/ioctl_cfg80211.c 907c907 < cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, GFP_ATOMIC); --- > cfg80211_disconnected(padapter->pnetdev, 0, NULL, 0, false, GFP_ATOMIC); Furthermore there is a re-definition that needs removing diff -r rtl8188eu-linux-driver/hal/hal_com_phycfg.c rtl8188eu-linux-driver2/hal/hal_com_phycfg.c 2578c2578 < char file_path[PATH_LENGTH_MAX]; --- > //charfile_path[PATH_LENGTH_MAX]; Once that is done, the tplink driver works perfectly. Please update wily to use the new driver. It may be worth informing the upstream kernel maintainer and Greg K.H. about the new opensource driver for possible inclusion in the upstream kernel staging tree in place of the troublesome driver that is currently there. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-generic 4.2.0.19.21 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2596 F pulseaudio CurrentDesktop: KDE Date: Fri Dec 11 14:50:16 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c50b4249-43ed-49ef-a3d8-ec7aa9718265 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic root=/dev/mapper/DISK00-root ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 SourcePackage: linux StagingDrivers: r8188eu UpgradeStatus: Upgraded to wily on 2015-11-28 (12 days ago) WpaSupplicantLog: dmi.bios.date: 04/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: N68-S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525254/+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 1525270] Re: Wi-Di Realtek 8192E disconnects after a while and fails to reconnect
** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1525270 Title: Wi-Di Realtek 8192E disconnects after a while and fails to reconnect Status in linux package in Ubuntu: Confirmed Bug description: A few minutes after booting my Samsung R580 laptop, the Wi-Fi disconnects and it fails to reconnect until I restart the machine. This happens with all the 64 bit versions of Ubuntu I tried, from 14.04 to 15.10. With the 32 bit versions, everything runs perfectly. No loss of connection at all, even after 48 hours in a row. Here is the output of iwconfig after loss of connexion: eth7 no wireless extensions. lono wireless extensions. wlan6 802.11bgn ESSID:"JeLisVosCourriels" Nickname:"rtl8192E" Mode:Managed Frequency=2.417 GHz Access Point: Not-Associated Bit Rate:19.5 Mb/s Retry min limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=10/100 Signal level=0 dBm Noise level=-100 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gilbert3115 F pulseaudio /dev/snd/controlC0: gilbert3115 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 11 09:27:18 2015 HibernationDevice: RESUME=UUID=e19f92d5-541f-412f-b5b0-7d97bfa1b7ec InstallationDate: Installed on 2015-12-03 (7 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. R580 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=f6b1d099-6ed1-4e82-823a-352535c7596c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-12-03 (7 days ago) dmi.bios.date: 12/21/2009 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JB.M014.20091221.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R580 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JB.M014.20091221.hkk:bd12/21/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnR580:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR580:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R580 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525270/+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 1013807] Re: transparent hugepages and thrashing on amd64
What may be useful to a 3 year old bug report other than the log files? The problem still exists on that computer. I added zram swap shortly after this bug report and it helped some. Some. Using hugepages currently and there times when it's easier to walk away and do something else for 10 minutes while some i/o intensive cron job like mlocate (since uninstalled) thrashes. Obscuring the problem is that some apt update set the scheduler to "deadline" rather than "cfq" so ionice values don't work. Forcing it back to "cfq" helps some - at least the entire user interface isn't locked up for half an hour. -- 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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If
[Kernel-packages] [Bug 1013807] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533451/+files/UdevLog.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseaudio Curren
[Kernel-packages] [Bug 1013807] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533450/+files/UdevDb.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseaudio CurrentDe
[Kernel-packages] [Bug 1013807] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533452/+files/WifiSyslog.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseaudio
[Kernel-packages] [Bug 1013807] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533436/+files/JournalErrors.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseau
[Kernel-packages] [Bug 1013807] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533438/+files/Lsusb.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseaudio CurrentDesk
[Kernel-packages] [Bug 1013807] Re: transparent hugepages and thrashing on amd64
apport information ** Tags added: apport-collected wily ** Description changed: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. + --- + ApportVersion: 2.19.1-0ubuntu5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: garyrich 2339 F pulseaudio + /dev/snd/controlC1: garyrich 2339 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.10 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=5b22d42d-33c8-435c-bea0-c1fbba7f88bf + InstallationDate: Installed on 2010-01-22 (2149 days ago) + InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) + IwConfig: + eth0 no wireless extensi
[Kernel-packages] [Bug 1013807] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533437/+files/Lspci.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseaudio CurrentDesk
[Kernel-packages] [Bug 1013807] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533434/+files/CRDA.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseaudio CurrentDeskto
[Kernel-packages] [Bug 1013807] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533449/+files/PulseList.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseaudio Cu
[Kernel-packages] [Bug 1013807] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533448/+files/ProcModules.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseaudio
[Kernel-packages] [Bug 1013807] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533447/+files/ProcInterrupts.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulse
[Kernel-packages] [Bug 1013807] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533439/+files/ProcCpuinfo.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseaudio
[Kernel-packages] [Bug 1013807] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533446/+files/ProcEnviron.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseaudio
[Kernel-packages] [Bug 1013807] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1013807/+attachment/4533435/+files/CurrentDmesg.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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: garyrich 2339 F pulseaudio /dev/snd/controlC1: garyrich 2339 F pulseaudi
[Kernel-packages] [Bug 1433906] Re: Acer, Inc ID 5986:055a is useless after 14.04.2 installed.
While it's wonderful that a patch has been created, could someone out there PLEASE wrap it up in a nice and simple .DEB package so the rest of us idiots can install it without having to manually recompile the kernel? After all, most of us *buntu users are simpletons who can't work a BASH shell if our lives depended on it, at least if you go by the continual dumbing down of the interface with each successive version :P -- 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/1433906 Title: Acer, Inc ID 5986:055a is useless after 14.04.2 installed. Status in HWE Next: Won't Fix Status in linux-lts-utopic package in Ubuntu: Confirmed Status in linux-lts-vivid package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Status in Fedora: Unknown Bug description: CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic) CID : 201408-15472 Lenovo E555 (A+A) with 14.04.2 (utopic) Steps: 1. Install 14.04.2 on E450 or E555. 2. Log in system and open a terminal. 3. $ gst-launch-0.10 v4l2src ! xvimagesink Expected result: Camara is activated Actual result: $ gst-launch-0.10 v4l2src ! xvimagesink Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot identify device '/dev/video0'. Additional debug info: v4l2_calls.c(497): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: system error: No such file or directory Setting pipeline to NULL ... Freeing pipeline ... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 02:21:31 2015 InstallationDate: Installed on 2015-03-16 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1433906/+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 1447053] Re: IO_PAGE_FAULT
You can make that option permanent by editing GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then running update-grub. -- 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/1447053 Title: IO_PAGE_FAULT Status in linux package in Ubuntu: Confirmed Bug description: Since a couple of weeks I'm experiencing a problem with my motherboard. For some reason the network goes randomly offline and I get a error messages about AMD-Vi. [ 6462.248434] AMD-Vi: Event logged [IO_PAGE_FAULT device=04:00.0 domain=0x0019 address=0x3000 flags=0x0050] I didn't changed anything except for the internet modem is changed and I installed updates as I always do. When using google I see there are more people with this problem exactly the same motherboard, I find this strange because my pc is almost a year old and I never had this problem. Could it be a problem in the kernel of *ubuntu 14.04? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-49-generic 3.13.0-49.83 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: allard 2282 F pulseaudio allard 2467 F pulseaudio /dev/snd/controlC0: allard 2282 F pulseaudio allard 2467 F pulseaudio CurrentDesktop: KDE Date: Wed Apr 22 11:34:46 2015 HibernationDevice: RESUME=UUID=96633d31-18c6-4b01-b756-f5f919c43fb4 InstallationDate: Installed on 2015-03-27 (25 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=2c77ade3-e2ea-4d88-94d6-e131053f8ac8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-49-generic N/A linux-backports-modules-3.13.0-49-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd04/02/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447053/+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 1013807] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1013807 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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: Incomplete Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Mül
[Kernel-packages] [Bug 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug
Indeed. Sorry, I should have recognized it. Too many parallel threads of
effort.
--
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/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Triaged
Status in linux source package in Vivid:
Fix Released
Status in linux source package in Wily:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The following fix has been submitted upstream, but has high enough
severity that we would like early inclusion into the Ubuntu kernel.
Please consider for wily, vivid, and trusty (and the HWE kernels for
the same).
Patch follows:
Currently we have two policies for deciding when to signal the host:
One based on the ring buffer state and the other based on what the VMBUS
client driver wants to do. Consider the case when the client wants to
explicitly control when to signal the host. In this case, if the client were to
defer signaling, we will not be able to signal the host subsequently when the
client does want to signal since the ring buffer state will prevent the
signaling. Implement logic to have only one signaling policy in force for a
given channel.
Signed-off-by: K. Y. Srinivasan
Reviewed-by: Haiyang Zhang
Tested-by: Haiyang Zhang
Cc: # v4.2+
---
drivers/hv/channel.c | 18 ++
include/linux/hyperv.h | 12
2 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index
77d2579..c6278c7 100644
--- a/drivers/hv/channel.c
+++ b/drivers/hv/channel.c
@@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel,
void *buffer,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
@@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct
vmbus_channel *channel,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index
437c9c8..7b1af52 100644
--- a/include/linux/hyperv.h
+++ b/include/linux/hyperv.h
@@ -756,8 +756,20 @@ struct vmbus_channel {
* link up channels based on their CPU affinity.
*/
struct list_head percpu_list;
+ /*
+ * Host signaling policy: The default policy will be
+ * based on the ring buffer state. We will also support
+ * a policy where the client driver can have explicit
+ * signaling control.
+ */
+ bool signal_state;
};
+static inline void set_channel_signal_state(struct vmbus_channel *c,
+bool state) {
+ c->signal_state = state;
+}
+
static inline void set_channel_read_state(struct vmbus_channel *c, bool
state) {
c->batched_reading = state;
--
1.7.4.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug
Also, it looks like it's the V1 version of the patch in Vivid. However,
it will be replace by V2 when it comes down from stable as an update.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Triaged
Status in linux source package in Vivid:
Fix Released
Status in linux source package in Wily:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The following fix has been submitted upstream, but has high enough
severity that we would like early inclusion into the Ubuntu kernel.
Please consider for wily, vivid, and trusty (and the HWE kernels for
the same).
Patch follows:
Currently we have two policies for deciding when to signal the host:
One based on the ring buffer state and the other based on what the VMBUS
client driver wants to do. Consider the case when the client wants to
explicitly control when to signal the host. In this case, if the client were to
defer signaling, we will not be able to signal the host subsequently when the
client does want to signal since the ring buffer state will prevent the
signaling. Implement logic to have only one signaling policy in force for a
given channel.
Signed-off-by: K. Y. Srinivasan
Reviewed-by: Haiyang Zhang
Tested-by: Haiyang Zhang
Cc: # v4.2+
---
drivers/hv/channel.c | 18 ++
include/linux/hyperv.h | 12
2 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index
77d2579..c6278c7 100644
--- a/drivers/hv/channel.c
+++ b/drivers/hv/channel.c
@@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel,
void *buffer,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
@@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct
vmbus_channel *channel,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index
437c9c8..7b1af52 100644
--- a/include/linux/hyperv.h
+++ b/include/linux/hyperv.h
@@ -756,8 +756,20 @@ struct vmbus_channel {
* link up channels based on their CPU affinity.
*/
struct list_head percpu_list;
+ /*
+ * Host signaling policy: The default policy will be
+ * based on the ring buffer state. We will also support
+ * a policy where the client driver can have explicit
+ * signaling control.
+ */
+ bool signal_state;
};
+static inline void set_channel_signal_state(struct vmbus_channel *c,
+bool state) {
+ c->signal_state = state;
+}
+
static inline void set_channel_read_state(struct vmbus_channel *c, bool
state) {
c->batched_reading = state;
--
1.7.4.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1525297] Re: nic-modules udeb missing s390 modules
** Also affects: linux (Ubuntu Xenial) Importance: Medium Status: Triaged ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1525297 Title: nic-modules udeb missing s390 modules Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: should have things similar to debian: ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/cio/ccwgroup.ko ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/ ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/ctcm.ko ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/fsm.ko ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/lcs.ko ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/netiucv.ko ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth.ko ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l2.ko ./lib/modules/4.2.0-1-s390x/kernel/drivers/s390/net/qeth_l3.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525297/+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 1013807] Re: transparent hugepages and thrashing on amd64
Since you seem to be using transparent hugepages and not libhugetlbfs (LD_PRELOAD=libhugetlbfs.so), I'm going to reassign this bug to the Linux kernel package. (It's also entirely possible this bug got solved in the last 3 years, to be fair) ** Package changed: libhugetlbfs (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/1013807 Title: transparent hugepages and thrashing on amd64 Status in linux package in Ubuntu: New Bug description: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu
[Kernel-packages] [Bug 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug
The patch is actually already in Vivid due to bug 1508706 .
** Changed in: linux (Ubuntu Vivid)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Triaged
Status in linux source package in Vivid:
Fix Released
Status in linux source package in Wily:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The following fix has been submitted upstream, but has high enough
severity that we would like early inclusion into the Ubuntu kernel.
Please consider for wily, vivid, and trusty (and the HWE kernels for
the same).
Patch follows:
Currently we have two policies for deciding when to signal the host:
One based on the ring buffer state and the other based on what the VMBUS
client driver wants to do. Consider the case when the client wants to
explicitly control when to signal the host. In this case, if the client were to
defer signaling, we will not be able to signal the host subsequently when the
client does want to signal since the ring buffer state will prevent the
signaling. Implement logic to have only one signaling policy in force for a
given channel.
Signed-off-by: K. Y. Srinivasan
Reviewed-by: Haiyang Zhang
Tested-by: Haiyang Zhang
Cc: # v4.2+
---
drivers/hv/channel.c | 18 ++
include/linux/hyperv.h | 12
2 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index
77d2579..c6278c7 100644
--- a/drivers/hv/channel.c
+++ b/drivers/hv/channel.c
@@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel,
void *buffer,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
@@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct
vmbus_channel *channel,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index
437c9c8..7b1af52 100644
--- a/include/linux/hyperv.h
+++ b/include/linux/hyperv.h
@@ -756,8 +756,20 @@ struct vmbus_channel {
* link up channels based on their CPU affinity.
*/
struct list_head percpu_list;
+ /*
+ * Host signaling policy: The default policy will be
+ * based on the ring buffer state. We will also support
+ * a policy where the client driver can have explicit
+ * signaling control.
+ */
+ bool signal_state;
};
+static inline void set_channel_signal_state(struct vmbus_channel *c,
+bool state) {
+ c->signal_state = state;
+}
+
static inline void set_channel_read_state(struct vmbus_channel *c, bool
state) {
c->batched_reading = state;
--
1.7.4.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1013807] [NEW] transparent hugepages and thrashing on amd64
You have been subscribed to a public bug: I seem to have found a solution to a severe thrashing/swapping/freezing problem that I've been having for months now. I guess the real question is - should I turn it into a bug report and what would be useful data to include if so. This is a quad core AMD Phaeom system with 4G of ram, dual monitors and a single 1TB WD caviar black HD. It had been behaving normally until something broke sometime late in the 11.x release cycle and continues in the current 12.04 LTS. The symptoms are running a moderate load of apps (firefox with ~8 tabs, a terminal or 2, and aisleriot solitaire for example) and experiencing system freezes where the entire UI becomes totally unresponsive for 20 seconds - 5 minutes with solid disk activity. Trying to figure out what was going on via iotop and top show jbd2 and kswapd accounting for the largest load, but since it freezes iotop like everything else I can't tell what's going during the worst storms. Googling around shows a fair number of other people with similar problems, most of them with multi core amd64 systems. The other day I spotted this report on opensuse that looked similar but not identical: http://lists.opensuse.org/opensuse/2012-03/msg00657.html I booted with the grub parameter transparent_hugepage=never yesterday and the problem went and away and hasn't come back. I've streesed the system by running a bunch of flash/java tabs in firefox, running a large java based stock app (ThinkorSwim) in another workspace and playing a 1080p 60fps movie in a third workspace. This certainly causes swapping, but not freezing or stumbling. It actually did a bit of swapping a minute ago while I was typing and it managed to make Pandora radio stumble for a moment - but that's orders of magnitude better than it has been. I think there may be a fundamental problem with how transparent hugepages are handled with some AMD CPUs. I think this problem started when this feature was implemented and enabled by default. The manpage for madvise() says this was added in 2.6.38, but I don't know if it was enabled by default at that point. Hre's a partial list of things that haven't worked well in the past: Playing with the swappiness value: setting swappiness to very low values makes the problem take longer to surface, but (unsurprisinglly) makes it even worse once it does. swapoff-a ; swapon-a: this makes it go away for a while. A potentially interesting thing is that as soon as I can get the system to act on the swapoff -a the system becomes responsive again. It pegs once CPU core at 100% and the HD grinds like crazy but it stops freezing right away. Moving swap from the HD to a USB thumb drive: Obviously I didn't expect that to be faster but wanted to see if segregating swap to a different device on a different bus would make it swap more smoothly - it didn't. Playing with nice and ionice priorities for jdb2, kswapd. The fact that running these processes at a lower priority than anything else on the system makes no difference leads me to think they were just symptoms and not at the root of the problem. I think this may be a tip of the iceberg and there may be a lot of other having this problem. Looking around I see a fair number of reports, most of them unsolved. Some may have been fixed by just adding enough RAM that dirty hugepages just don't collect. Some may have been fixed by chaanging filesystems - ext4 seems like something a lot of people with this problem have in common. Workaround: hold down the spacebar during boot in order to bring up the grub menu, edit the command line and add transparent_hugepage=never If this fixes the problem you can make it permanent by editing /etc/default/grub and adding the ransparent_hugepage=never to the GRUB_CMDLINE_LINUX_DEFAULT line and then running update-grub Problems with this workaround: 1) transparent hugepages should work. This may cause a small performance hit in some situations and a larger hit in others. 2) If you do this you will probably never know when or if it actually gets fixed. PS: Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany is looking for bugzilla reports on this too. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- transparent hugepages and thrashing on amd64 https://bugs.launchpad.net/bugs/1013807 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1525061] Re: linux-headers-4.3.0-2 have unstable to connect in Acer Aspire 4740 after close the lid.
Please: 1. Edit the bug so it is clear what becomes unstable. 2. Set this bug status back to "confirmed". Thank you. ** 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/1525061 Title: linux-headers-4.3.0-2 have unstable to connect in Acer Aspire 4740 after close the lid. Status in linux package in Ubuntu: Incomplete Bug description: linux-headers-4.3.0-2 have unstable to connect in Acer Aspire 4740 after close the lid. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-headers-4.3.0-2 4.3.0-2.11 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic i686 ApportVersion: 2.19.3-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sumate 2095 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 11 11:20:28 2015 HibernationDevice: RESUME=UUID=fddd00e8-74d2-41b5-9315-8ef84a5fc982 InstallationDate: Installed on 2011-01-30 (1775 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Acer Aspire 4740 PackageArchitecture: all ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic root=UUID=974de5d6-f5a0-47e0-badd-13eb79a5ba69 ro quiet splash acpi_osi=Linux acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.3.0-2-generic N/A linux-backports-modules-4.3.0-2-generic N/A linux-firmware 1.154 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2015-10-29 (42 days ago) dmi.bios.date: 10/20/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 4740 dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnAcer:bvrV1.10:bd10/20/2010:svnAcer:pnAspire4740:pvrV1.10:rvnAcer:rnAspire4740:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.name: Aspire 4740 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525061/+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 1524122] Re: XPS 15 (9550) Won't boot with 4.4
** Bug watch added: Linux Kernel Bug Tracker #108981 http://bugzilla.kernel.org/show_bug.cgi?id=108981 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=108981 Importance: Unknown Status: Unknown ** Description changed: Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550). 4.3 boots fine. The boot process halts with "ALERT! /dev/disk/by-uuid/ does not exist", although the UUID does exist, and other kernels boot fine. I'm attaching a screenshot of the console boot log. I apologize that it is hard to read, because my screen is 3840x2160 and each line is less that 2mm high. Here's my grub stanza: - load_video - gfxmode $linux_gfx_mode - insmod gzio - if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi - insmod part_gpt - insmod ext2 - if [ x$feature_platform_search_hint = xy ]; then - search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a - else - search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a - fi - echo'Loading Linux 4.4.0-040400rc4-generic ...' - linux /boot/vmlinuz-4.4.0-040400rc4-generic root=UUID=7e2ed448-28a7-465e-a5b0-58db19b2711a ro quiet splash i915.preliminary_hw_support=1 i915.enable_ips=0 $vt_handoff - echo'Loading initial ramdisk ...' - initrd /boot/initrd.img-4.4.0-040400rc4-generic + load_video + gfxmode $linux_gfx_mode + insmod gzio + if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi + insmod part_gpt + insmod ext2 + if [ x$feature_platform_search_hint = xy ]; then + search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a + else + search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a + fi + echo'Loading Linux 4.4.0-040400rc4-generic ...' + linux /boot/vmlinuz-4.4.0-040400rc4-generic root=UUID=7e2ed448-28a7-465e-a5b0-58db19b2711a ro quiet splash i915.preliminary_hw_support=1 i915.enable_ips=0 $vt_handoff + echo'Loading initial ramdisk ...' + initrd /boot/initrd.img-4.4.0-040400rc4-generic Possibly related is the following warning when i update-initramfs: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.4.0-040400rc4-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_ver4.bin for module i915 - I have also reported this bug upstream: - https://bugzilla.kernel.org/show_bug.cgi?id=108981 - Please let me know what other info would be helpful. Thanks! - --- + --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-11-18 (20 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: linux (not installed) Tags: wily Uname: Linux 4.3.0-040300-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users video wireshark _MarkForUpload: True ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- 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/1524122 Title: XPS 15 (9550) Won't boot with 4.4 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Neither 4.4rc3 nor 4.3rc4 will boot on my Dell XPS 15 (9550). 4.3 boots fine. The boot process halts with "ALERT! /dev/disk/by-uuid/ does not exist", although the UUID does exist, and other kernels boot fine. I'm attaching a screenshot of the console boot log. I apologize that it is hard to read, because my screen is 3840x2160 and each line is less that 2mm high. Here's my grub stanza: load_video gfxmode $linux_gfx_mode insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a else search --no-floppy --fs-uuid --set=root 7e2ed448-28a7-465e-a5b0-58db19b2711a fi echo'Loading Linux 4.4.0-040400rc4-generic ...'
[Kernel-packages] [Bug 1525008] Re: Ubuntu doesn't boot after laptop runs out of battery
** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1525008 Title: Ubuntu doesn't boot after laptop runs out of battery Status in linux package in Ubuntu: Confirmed Bug description: If my laptop runs out of battery, the next time I start it up and put in my disk password, I get a black screen that goes nowhere. I always have to hard-reset the laptop in order for the OS to load after I put in the disk password. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vadi 2571 F pulseaudio /dev/snd/controlC0: vadi 2571 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 11 08:42:12 2015 HibernationDevice: RESUME=UUID=745d185e-0cf7-47d5-8900-9f89f21b1af8 InstallationDate: Installed on 2014-06-26 (531 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP ZBook 14 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-26 (44 days ago) dmi.bios.date: 04/29/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.11 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.54 dmi.chassis.asset.tag: CNU424B3ZZ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:svnHewlett-Packard:pnHPZBook14:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 14 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525008/+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 1524167] Re: Computer freezes since 15.10 upgrade
It happened to me three times, and in my case looked like an xorg freeze. ** Package changed: linux (Ubuntu) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided => Critical -- 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/1524167 Title: Computer freezes since 15.10 upgrade Status in xorg package in Ubuntu: Confirmed Bug description: Machine freezes randomly. No crash logs or anything in syslog. Not enough know-how to figure it out. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jd 2303 F pulseaudio Date: Tue Dec 8 22:23:17 2015 HibernationDevice: RESUME=UUID=97af6a20-8cf6-48bb-a4a4-20d55865a2e3 MachineType: Acer Aspire ES1-512 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=af5dae25-82ce-4518-83af-ee2f6e077b25 ro recovery nomodeset PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-11-01 (37 days ago) dmi.bios.date: 09/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-512 dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/11/2014:svnAcer:pnAspireES1-512:pvrV1.07:rvnAcer:rnAspireES1-512:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire ES1-512 dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1524167/+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 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug
Ah, we hadn't started Xenial testing yet. Give me a little more time to
spin that up.
--
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/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Triaged
Status in linux source package in Vivid:
Triaged
Status in linux source package in Wily:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The following fix has been submitted upstream, but has high enough
severity that we would like early inclusion into the Ubuntu kernel.
Please consider for wily, vivid, and trusty (and the HWE kernels for
the same).
Patch follows:
Currently we have two policies for deciding when to signal the host:
One based on the ring buffer state and the other based on what the VMBUS
client driver wants to do. Consider the case when the client wants to
explicitly control when to signal the host. In this case, if the client were to
defer signaling, we will not be able to signal the host subsequently when the
client does want to signal since the ring buffer state will prevent the
signaling. Implement logic to have only one signaling policy in force for a
given channel.
Signed-off-by: K. Y. Srinivasan
Reviewed-by: Haiyang Zhang
Tested-by: Haiyang Zhang
Cc: # v4.2+
---
drivers/hv/channel.c | 18 ++
include/linux/hyperv.h | 12
2 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index
77d2579..c6278c7 100644
--- a/drivers/hv/channel.c
+++ b/drivers/hv/channel.c
@@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel,
void *buffer,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
@@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct
vmbus_channel *channel,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index
437c9c8..7b1af52 100644
--- a/include/linux/hyperv.h
+++ b/include/linux/hyperv.h
@@ -756,8 +756,20 @@ struct vmbus_channel {
* link up channels based on their CPU affinity.
*/
struct list_head percpu_list;
+ /*
+ * Host signaling policy: The default policy will be
+ * based on the ring buffer state. We will also support
+ * a policy where the client driver can have explicit
+ * signaling control.
+ */
+ bool signal_state;
};
+static inline void set_channel_signal_state(struct vmbus_channel *c,
+bool state) {
+ c->signal_state = state;
+}
+
static inline void set_channel_read_state(struct vmbus_channel *c, bool
state) {
c->batched_reading = state;
--
1.7.4.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1523565] Re: Qualcomm atheros network controller [168c:0042] (rev 30) does not work
** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1523565 Title: Qualcomm atheros network controller [168c:0042] (rev 30) does not work Status in linux package in Ubuntu: Confirmed Bug description: I installed the latest ath10k kernels, which changed the status of the hardware from unclaimed to claimed, but it still does not seem to be recognized as a wireless device ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: (removed for privacy) 1358 F pulseaudio /dev/snd/controlC0: (removed for privacy) 1358 F pulseaudio CurrentDesktop: Unity Date: Mon Dec 7 21:22:43 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ec603e54-8e2b-40c2-9bd4-559d5e329d2c InstallationDate: Installed on 2015-12-07 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Acer Aspire E5-573 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH 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.15:bd05/27/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-573 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523565/+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 1523738] Re: touchpad not working alienware 13 on ubuntu 15.10
** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1523738 Title: touchpad not working alienware 13 on ubuntu 15.10 Status in linux package in Ubuntu: Confirmed Bug description: Installed ubuntu 15.10 on alienware 13, touchpad is showing up in xinput list as expected, but is totally unresponsive. Was working fine on 14.05 --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sean 1610 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=ed54b297-8650-46ee-b615-6d543bb47b7a InstallationDate: Installed on 2015-12-07 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Alienware Alienware 13 R2 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=4c119f73-b6e4-4100-9d32-f6052a303bcf ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/15/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.0 dmi.board.name: Alienware 13 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.0:bd10/15/2015:svnAlienware:pnAlienware13R2:pvr1.2.0:rvnAlienware:rnAlienware13R2:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 13 R2 dmi.product.version: 1.2.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523738/+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 1522201] Re: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19)
** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- 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/1522201 Title: NUC NUC5CPYH Does not reboot on Ubuntu 15.10 (linux-image-4.2.0-19) Status in linux package in Ubuntu: Confirmed Bug description: I have an Intel NUC NUC5CPYH. This is the unit: http://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc5cpyh.html It boots and reboots beautifully on Ubuntu 15.04 and Ubuntu 15.10 with linux-image-3.19.0-34-generic -- but when I try to boot with linux- image-4.2.0-19-generic on the latest PY0044 BIOS version, it freezes on boot almost every time, reported bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521749 If I downgrade the BIOS to PY0043, it boots most of the time, but when I run "reboot" it freezes almost every single time. This is what I see on the screen when it freezes: https://www.dropbox.com/s/fxy4opcqwnmjmwo/IMG_1489.jpg?dl=0 I am also attaching the full syslog, dmesg and the relevant part of the syslog when the system froze. I tried to boot with acpi_osi="Windows 2013" as well as Windows 2015 and Windows 2009, that did not seem to make any difference. Any ideas? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 DistroRelease: Ubuntu 15.10 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG= SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=4fa37335-eed0-4580-ae4b-62c996dfc275 ro vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 RfKill: Error: [Errno 2] No such file or directory Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/04/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522201/+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 1523765] Re: USB performance extremely unstable
** 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/1523765 Title: USB performance extremely unstable Status in linux package in Ubuntu: Incomplete Bug description: Since I upgraded from Trusty to Wily, the USB performance has become extremely unstable. Sometimes file transfers were fast, like 1GB in 30 sec, then most days it is so slow like 1 GB in 20 minutes for no reason. Here some relevant log lines from the `dmesg` command when I USB is plugged in: ``` [ 496.912939] usb 4-5: new high-speed USB device number 2 using ehci-pci [ 497.111419] usb 4-5: New USB device found, idVendor=1b1c, idProduct=1ab1 [ 497.111425] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 497.111428] usb 4-5: Product: Voyager [ 497.111430] usb 4-5: Manufacturer: Corsair [ 497.111433] usb 4-5: SerialNumber: AA400825 [ 497.134497] usb-storage 4-5:1.0: USB Mass Storage device detected [ 497.134600] scsi host12: usb-storage 4-5:1.0 [ 497.134713] usbcore: registered new interface driver usb-storage [ 497.137090] usbcore: registered new interface driver uas [ 498.420795] scsi 12:0:0:0: Direct-Access Corsair Voyager 1100 PQ: 0 ANSI: 0 CCS [ 498.421211] sd 12:0:0:0: Attached scsi generic sg5 type 0 [ 498.913643] sd 12:0:0:0: [sdd] 15663104 512-byte logical blocks: (8.01 GB/7.46 GiB) [ 498.914804] sd 12:0:0:0: [sdd] Write Protect is off [ 498.914809] sd 12:0:0:0: [sdd] Mode Sense: 43 00 00 00 [ 498.915930] sd 12:0:0:0: [sdd] No Caching mode page found [ 498.915934] sd 12:0:0:0: [sdd] Assuming drive cache: write through [ 498.920710] sdd: sdd1 [ 498.924684] sd 12:0:0:0: [sdd] Attached SCSI removable disk [ 1184.038007] usb 4-5: USB disconnect, device number 2 ``` these two lines appear in *red* ``` [ 498.915930] sd 12:0:0:0: [sdd] No Caching mode page found [ 498.915934] sd 12:0:0:0: [sdd] Assuming drive cache: write through ``` What can we do here? How can this be investigated and fixed properly? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael-heuberger 4363 F pulseaudio /dev/snd/controlC2: michael-heuberger 4363 F pulseaudio /dev/snd/controlC0: michael-heuberger 4363 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028 InstallationDate: Installed on 2014-10-31 (403 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: wily Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data _MarkForUpload: True dmi.bios.date: 08/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523765/+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 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug
Dear Joshua,
I built a Xenial test kernel with the V2 patch.
Please test the kernel and let us know your results. If we can receive
positive test feedback by December 18, we can proceed to submit the
patches for kernel SRU review in an attempt to make the upcoming kernel
SRU cycle starting on December 20th. Assuming the patches are accepted
for SRU and land in the upcoming SRU cycle, the fix should be available
from the -updates pocket by January 9th.
The Xenial test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1519897/xenial
This kernel will cover both Xenial and Wily testing. Vivid and Trusty
will need some backporting of the patch, so separate test kernels will
be posted for them.
--
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/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Triaged
Status in linux source package in Vivid:
Triaged
Status in linux source package in Wily:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The following fix has been submitted upstream, but has high enough
severity that we would like early inclusion into the Ubuntu kernel.
Please consider for wily, vivid, and trusty (and the HWE kernels for
the same).
Patch follows:
Currently we have two policies for deciding when to signal the host:
One based on the ring buffer state and the other based on what the VMBUS
client driver wants to do. Consider the case when the client wants to
explicitly control when to signal the host. In this case, if the client were to
defer signaling, we will not be able to signal the host subsequently when the
client does want to signal since the ring buffer state will prevent the
signaling. Implement logic to have only one signaling policy in force for a
given channel.
Signed-off-by: K. Y. Srinivasan
Reviewed-by: Haiyang Zhang
Tested-by: Haiyang Zhang
Cc: # v4.2+
---
drivers/hv/channel.c | 18 ++
include/linux/hyperv.h | 12
2 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index
77d2579..c6278c7 100644
--- a/drivers/hv/channel.c
+++ b/drivers/hv/channel.c
@@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel,
void *buffer,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
@@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct
vmbus_channel *channel,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index
437c9c8..7b1af52 100644
--- a/include/linux/hyperv.h
+++ b/include/linux/hyperv.h
@@ -756,8 +756,20 @@ struct vmbus_channel {
* link up channels based on their CPU affinity.
*/
struct list_head percpu_list;
+ /*
+ * Host signaling policy: The default policy will be
+ * based on the ring buffer state. We will also support
+ * a policy where the client driver can have explicit
+ * signaling control.
+ */
+ bool signal_state;
};
+static inline void set_channel_signal_state(struct vmbus_channel *c,
+bool state) {
+ c->signal_state = state;
+}
+
static inline void set_channel_read_state(struct vmbus_channel *c, bool
state) {
c->batched_reading = state;
--
1.7.4.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1518566] Re: Ubuntu 15.10 freezing randomly
Updated BIOS X751MA.403 08/10/2015 Now will wait to see if it still reproducible. -- 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/1518566 Title: Ubuntu 15.10 freezing randomly Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 15.10 freezing randomly ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spyros 3013 F pulseaudio CurrentDesktop: Unity Date: Sat Nov 21 16:15:04 2015 HibernationDevice: RESUME=UUID=3fbc151c-b9b3-492c-a1f4-c598a0b080bb InstallationDate: Installed on 2015-09-23 (58 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 0bda:57bc Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X751MA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=59242a09-40d6-4231-b79b-543e0a88dbde ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-05 (15 days ago) dmi.bios.date: 01/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X751MA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X751MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX751MA.208:bd01/26/2015:svnASUSTeKCOMPUTERINC.:pnX751MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X751MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518566/+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 1523346] Re: package linux-image-4.2.0-19-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1523346 Title: package linux-image-4.2.0-19-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: standard periodic update was being processed - had a few programs open at the time usually this does not impact the update process ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic (not installed) ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mothball 1743 F pulseaudio /dev/snd/controlC0: mothball 1743 F pulseaudio /dev/snd/controlC2: mothball 1743 F pulseaudio Date: Sun Dec 6 21:28:36 2015 DuplicateSignature: package:linux-image-4.2.0-19-generic:(not installed):subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=4a96c000-65e7-44d7-8d74-80708ebfff95 InstallationDate: Installed on 2015-11-01 (35 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: enp2s0no wireless extensions. enp3s0no wireless extensions. lono wireless extensions. MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7577 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=e58b6016-2b89-46e2-94db-1ec5edaa4fd7 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-29 RfKill: SourcePackage: linux Title: package linux-image-4.2.0-19-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.16 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 790FX-GD70(MS-7577) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.16:bd12/01/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7577:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn790FX-GD70(MS-7577):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7577 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523346/+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 1523126] Re: Kernel bug on WILY - ALSA on Lenovo x220
Please: 1. Edit the bug description, so it is clear what are the steps to recreate the error and what are the consequences of it. 2. Set this bug status back to "confirmed". Thank you. ** 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/1523126 Title: Kernel bug on WILY - ALSA on Lenovo x220 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 4.2.0-18.22-generic 4.2.3 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09) Subsystem: Lenovo Device [17aa:21da] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) Subsystem: Lenovo Device [17aa:21da] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #0, PowerLimit 0.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range BC, TimeoutDis+, LTR-, OBFF Not Supported ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Address: Data: Capabilities: [90] Subsystem: Lenovo Device [17aa:21da] Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kerne
[Kernel-packages] [Bug 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug
Yeah, at the time I submitted we had determined that the first patch
would work, but that there might be dialogue in the upstreaming. The V2
submission is okay with us.
--
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/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Triaged
Status in linux source package in Vivid:
Triaged
Status in linux source package in Wily:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The following fix has been submitted upstream, but has high enough
severity that we would like early inclusion into the Ubuntu kernel.
Please consider for wily, vivid, and trusty (and the HWE kernels for
the same).
Patch follows:
Currently we have two policies for deciding when to signal the host:
One based on the ring buffer state and the other based on what the VMBUS
client driver wants to do. Consider the case when the client wants to
explicitly control when to signal the host. In this case, if the client were to
defer signaling, we will not be able to signal the host subsequently when the
client does want to signal since the ring buffer state will prevent the
signaling. Implement logic to have only one signaling policy in force for a
given channel.
Signed-off-by: K. Y. Srinivasan
Reviewed-by: Haiyang Zhang
Tested-by: Haiyang Zhang
Cc: # v4.2+
---
drivers/hv/channel.c | 18 ++
include/linux/hyperv.h | 12
2 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index
77d2579..c6278c7 100644
--- a/drivers/hv/channel.c
+++ b/drivers/hv/channel.c
@@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel,
void *buffer,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
@@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct
vmbus_channel *channel,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index
437c9c8..7b1af52 100644
--- a/include/linux/hyperv.h
+++ b/include/linux/hyperv.h
@@ -756,8 +756,20 @@ struct vmbus_channel {
* link up channels based on their CPU affinity.
*/
struct list_head percpu_list;
+ /*
+ * Host signaling policy: The default policy will be
+ * based on the ring buffer state. We will also support
+ * a policy where the client driver can have explicit
+ * signaling control.
+ */
+ bool signal_state;
};
+static inline void set_channel_signal_state(struct vmbus_channel *c,
+bool state) {
+ c->signal_state = state;
+}
+
static inline void set_channel_read_state(struct vmbus_channel *c, bool
state) {
c->batched_reading = state;
--
1.7.4.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1523301] Re: ACPI: 4 ACPI AML tables successfully acquired and loaded
Please: 1. Edit the bug description, so it explains how to reproduce the bug and which are the consequences of it. 2. Set this bug status back to "confirmed". Thank you. ** 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/1523301 Title: ACPI: 4 ACPI AML tables successfully acquired and loaded Status in linux package in Ubuntu: Incomplete Bug description: dmesg: [0.010903] ACPI: 4 ACPI AML tables successfully acquired and loaded ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-2-generic 4.3.0-2.11 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1689 F pulseaudio CurrentDesktop: GNOME Date: Sun Dec 6 21:50:55 2015 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (133 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.3.0-2-generic N/A linux-backports-modules-4.3.0-2-generic N/A linux-firmware 1.153 SourcePackage: linux UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523301/+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 1523300] Re: ACPI: RSDP 0x00000000000F0120 000024 (v02 SECCSD)
*** This bug is a duplicate of bug 1522983 *** https://bugs.launchpad.net/bugs/1522983 You! reported twice! ** This bug has been marked a duplicate of bug 1522983 ACPI: RSDP 0x000F0120 24 (v02 SECCSD) -- 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/1523300 Title: ACPI: RSDP 0x000F0120 24 (v02 SECCSD) Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [0.00] ACPI: RSDP 0x000F0120 24 (v02 SECCSD) [0.00] ACPI: XSDT 0xDAFFE170 94 (v01 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: FACP 0xDAFEE000 00010C (v05 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: DSDT 0xDAFF1000 0092DA (v02 SECCSD IVB-CPT INTL 20061109) [0.00] ACPI: FACS 0xDAF7B000 40 [0.00] ACPI: SLIC 0xDAFFD000 000176 (v01 SECCSD LH43STAR 0002 PTL 0001) [0.00] ACPI: SSDT 0xDAFFB000 001068 (v01 SECCSD PtidDevc 1000 INTL 20061109) [0.00] ACPI: ASF! 0xDAFF A5 (v32 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: HPET 0xDAFED000 38 (v01 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: APIC 0xDAFEC000 98 (v03 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: MCFG 0xDAFEB000 3C (v01 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: FPDT 0xDAFEA000 54 (v01 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: SSDT 0xDAFE9000 0007D7 (v01 PmRef Cpu0Ist 3000 INTL 20061109) [0.00] ACPI: SSDT 0xDAFE8000 000AD0 (v01 PmRef CpuPm 3000 INTL 20061109) [0.00] ACPI: UEFI 0xDAFE7000 3E (v01 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: UEFI 0xDAFE6000 42 (v01 PTLCOMBUF 0001 PTL 0001) [0.00] ACPI: POAT 0xDAF78000 55 (v03 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: UEFI 0xDAFE5000 00022E (v01 SECCSD LH43STAR 0002 PTL 0002) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-2-generic 4.3.0-2.11 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1689 F pulseaudio CurrentDesktop: GNOME Date: Sun Dec 6 21:49:37 2015 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (133 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.3.0-2-generic N/A linux-backports-modules-4.3.0-2-generic N/A linux-firmware 1.153 SourcePackage: linux UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523300/+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 1501281] Re: Frequent freezes on 15.04 with kernel 3.19.0-29+
I built the next test kernel, up to the following commit: 4b630e4e471c138161ab053471d97b0cdd367a31 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1501281 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/1501281 Title: Frequent freezes on 15.04 with kernel 3.19.0-29+ Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Incomplete Bug description: I am experiencing systematic freezes since my kernel was automatically upgraded to 3.19.0-29. Same problem happens if I use kernel 3.19.0-30. If I use kernel 3.19.0-28 it does not freeze any more. Behaviour is described with more details at http://askubuntu.com/questions/679212/frequent-freezes-on-15-04-with- kernel-3-19-0-29 and at http://askubuntu.com/questions/673767/frequent-freezes ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andrea 3174 F pulseaudio /dev/snd/pcmC0D0p: andrea 3174 F...m pulseaudio /dev/snd/controlC0: andrea 3174 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 30 12:45:03 2015 HibernationDevice: RESUME=UUID=7f029a53-8d17-4db1-b66f-d131578efe68 InstallationDate: Installed on 2010-04-15 (1993 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) IwConfig: eth2 no wireless extensions. lono wireless extensions. MachineType: ASUS All Series ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=5d76a02d-2ed2-484a-81da-3cf5ce0ab3fb ro crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-30 (153 days ago) dmi.bios.date: 04/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0303:bd04/18/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: 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/1501281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1518457] Re: kswapd0 100% CPU usage
I built the next test kernel, up to the following commit: ab0169bb5cc4a5c86756dde662087f9d12302eb0 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1518457 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/1518457 Title: kswapd0 100% CPU usage Status in linux package in Ubuntu: In Progress Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1523108] Re: Bluetooth doesn't work on ASUS Zenbook UX301LAA
** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1523108 Title: Bluetooth doesn't work on ASUS Zenbook UX301LAA Status in linux package in Ubuntu: Confirmed Bug description: It's not possible to make bluetooth work. Pressing Fn+F2 doesn't change anything. Sometimes a grey (inactive) bluetooth icon appears but disappears instantly after attempt to turn it on. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-21-generic 4.2.0-21.25 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shadowlmd 2409 F pulseaudio /dev/snd/controlC1: shadowlmd 2409 F pulseaudio CurrentDesktop: Unity Date: Sat Dec 5 18:03:20 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=4443577b-ebf9-4f35-bd95-660448592ddb InstallationDate: Installed on 2015-10-22 (43 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=e7df807f-bc9b-4cdf-85ae-38b8a3c6f016 ro quiet splash rootfstype=ext4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-21-generic N/A linux-backports-modules-4.2.0-21-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX301LAA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1523086] Re: Ubuntu 15.10: GNOME Terminal window loses mouse cursor
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Package changed: linux (Ubuntu) => gnome-terminal (Ubuntu) ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg (Ubuntu) Importance: Undecided => High ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1523086 Title: Ubuntu 15.10: GNOME Terminal window loses mouse cursor Status in gnome-terminal package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Ubuntu: Ubuntu 15.10 Package: gnome-terminal-3.16.2-1ubuntu4 Problem: Sometimes, but always when out of focus, a GNOME terminal window will lose mouse icon when it is hovered over the window. Clicking the window (and thus bringing it back in focus) restores the mouse icon. Once all that starts to happen, any URLs in the terminal stop showing pointer cursor when hovered over, but they do respond to clicks and right-clicks. --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vlad 1856 F pulseaudio DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=a666043d-11d1-472f-8ccd-3ef13cae559a InstallationDate: Installed on 2015-11-19 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic root=UUID=7671ab7d-b593-4193-9a95-3f7b4389bf8f ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 RfKill: Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: A770DE+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd11/26/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA770DE+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1523086/+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 1522983] Re: ACPI: RSDP 0x00000000000F0120 000024 (v02 SECCSD)
Please: 1. Edit the bug description, so it explains how to reproduce the bug and which are the consequences of it. 2. Set this bug status back to "confirmed". Thank you. ** 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/1522983 Title: ACPI: RSDP 0x000F0120 24 (v02 SECCSD) Status in linux package in Ubuntu: Incomplete Bug description: dmesg: [0.00] ACPI: RSDP 0x000F0120 24 (v02 SECCSD) [0.00] ACPI: XSDT 0xDAFFE170 94 (v01 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: FACP 0xDAFEE000 00010C (v05 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: DSDT 0xDAFF1000 0092DA (v02 SECCSD IVB-CPT INTL 20061109) [0.00] ACPI: FACS 0xDAF7B000 40 [0.00] ACPI: SLIC 0xDAFFD000 000176 (v01 SECCSD LH43STAR 0002 PTL 0001) [0.00] ACPI: SSDT 0xDAFFB000 001068 (v01 SECCSD PtidDevc 1000 INTL 20061109) [0.00] ACPI: ASF! 0xDAFF A5 (v32 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: HPET 0xDAFED000 38 (v01 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: APIC 0xDAFEC000 98 (v03 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: MCFG 0xDAFEB000 3C (v01 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: FPDT 0xDAFEA000 54 (v01 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: SSDT 0xDAFE9000 0007D7 (v01 PmRef Cpu0Ist 3000 INTL 20061109) [0.00] ACPI: SSDT 0xDAFE8000 000AD0 (v01 PmRef CpuPm 3000 INTL 20061109) [0.00] ACPI: UEFI 0xDAFE7000 3E (v01 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: UEFI 0xDAFE6000 42 (v01 PTLCOMBUF 0001 PTL 0001) [0.00] ACPI: POAT 0xDAF78000 55 (v03 SECCSD LH43STAR 0002 PTL 0002) [0.00] ACPI: UEFI 0xDAFE5000 00022E (v01 SECCSD LH43STAR 0002 PTL 0002) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-1-generic 4.3.0-1.10 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 1673 F...m pulseaudio /dev/snd/controlC0: caravena 1673 F pulseaudio CurrentDesktop: GNOME Date: Fri Dec 4 19:30:45 2015 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (131 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-1-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.3.0-1-generic N/A linux-backports-modules-4.3.0-1-generic N/A linux-firmware 1.153 SourcePackage: linux UdevLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522983/+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 1519917] Re: [Hyper-V] Rebase Hyper-V to 4.3 kernel
I would rather move forward with known issues. Simon is looking deeper at the storage performance results, but otherwise we are close to saying "good to go". -- 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/1519917 Title: [Hyper-V] Rebase Hyper-V to 4.3 kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: In Progress Bug description: Please rebase Hyper-V support to the final upstream 4.3 kernel. The following files and directories contain Hyper-V support: arch/x86/include/asm/mshyperv.h arch/x86/include/uapi/asm/hyperv.h arch/x86/kernel/cpu/mshyperv.c drivers/hid/hid-hyperv.c drivers/hv/ drivers/input/serio/hyperv-keyboard.c drivers/net/hyperv/ drivers/scsi/storvsc_drv.c drivers/video/hyperv_fb.c include/linux/hyperv.h tools/hv/ There are, of course, a number of sauce items already present in Ubuntu to keep. Please add the following additional sauce item for networking performance [attached]. This rebase request is intended for wily/15.10. We should investigate it's applicability to vivid/15.04 and HWE kernels as well. Because 14.04's HWE kernel will change to wily in January, 15.10 may be sufficient in the long term. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519917/+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 1522944] Re: Wifi broken and strange screen resolution after update
Please: 1. Edit this bug, so it only addresses one issue. 2. Make a new report for the second issue. 3. Set this bug status back to "confirmed". Thank you. ** 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/1522944 Title: Wifi broken and strange screen resolution after update Status in linux package in Ubuntu: Incomplete Bug description: After update from kernel 4.2.0-18 to 4.2.0-19, my wifi got broken and the video driver had some problems too, because my resolution was downgraded to 1024x768. Boot startup screen was changed from a graphics mode to a low resolution text mode (25x80 maybe). I had to boot back to 4.2.0-18 to report this bug. Please let me know what extra information is needed. From /var/log/apt/history.log: Start-Date: 2015-12-02 07:38:24 Commandline: /usr/bin/unattended-upgrade Install: linux-headers-4.2.0-19:amd64 (4.2.0-19.23, automatic), linux-headers-4.2.0-19-generic:amd64 (4.2.0-19.23, automatic), linux-image-extra-4.2.0-19-generic:amd64 (4.2.0-19.23, automatic), linux-image-4.2.0-19-generic:amd64 (4.2.0-19.23, automatic) Upgrade: linux-headers-generic:amd64 (4.2.0.18.20, 4.2.0.19.21), thunderbird-locale-en-us:amd64 (38.3.0+build1-0ubuntu2, 38.4.0+build3-0ubuntu0.15.10.1), thunderbird:amd64 (38.3.0+build1-0ubuntu2, 38.4.0+build3-0ubuntu0.15.10.1), thunderbird-locale-en:amd64 (38.3.0+build1-0ubuntu2, 38.4.0+build3-0ubuntu0.15.10.1), thunderbird-locale-fi:amd64 (38.3.0+build1-0ubuntu2, 38.4.0+build3-0ubuntu0.15.10.1), thunderbird-gnome-support:amd64 (38.3.0+build1-0ubuntu2, 38.4.0+build3-0ubuntu0.15.10.1), linux-libc-dev:amd64 (4.2.0-18.22, 4.2.0-19.23), linux-image-generic:amd64 (4.2.0.18.20, 4.2.0.19.21), linux-generic:amd64 (4.2.0.18.20, 4.2.0.19.21) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic:amd64 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nikke 4087 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 4 21:20:27 2015 HibernationDevice: RESUME=UUID=46f62d42-a77b-4f1a-be16-b3b015057bd6 InstallationDate: Installed on 2014-06-25 (527 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 42912WG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-18-generic root=/dev/mapper/ubuntu--vg-root ro vesafb.invalid=1 splash quiet nopat RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.2 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-11-19 (15 days ago) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912WG 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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912WG:pvrThinkPadX220:rvnLENOVO:rn42912WG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912WG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522944/+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 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug
It looks like there was a V2 to the patch mentioned in the description:
https://lkml.org/lkml/2015/11/19/795
I'll build the test kernels using the V2 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/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Triaged
Status in linux source package in Vivid:
Triaged
Status in linux source package in Wily:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The following fix has been submitted upstream, but has high enough
severity that we would like early inclusion into the Ubuntu kernel.
Please consider for wily, vivid, and trusty (and the HWE kernels for
the same).
Patch follows:
Currently we have two policies for deciding when to signal the host:
One based on the ring buffer state and the other based on what the VMBUS
client driver wants to do. Consider the case when the client wants to
explicitly control when to signal the host. In this case, if the client were to
defer signaling, we will not be able to signal the host subsequently when the
client does want to signal since the ring buffer state will prevent the
signaling. Implement logic to have only one signaling policy in force for a
given channel.
Signed-off-by: K. Y. Srinivasan
Reviewed-by: Haiyang Zhang
Tested-by: Haiyang Zhang
Cc: # v4.2+
---
drivers/hv/channel.c | 18 ++
include/linux/hyperv.h | 12
2 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index
77d2579..c6278c7 100644
--- a/drivers/hv/channel.c
+++ b/drivers/hv/channel.c
@@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel,
void *buffer,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
@@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct
vmbus_channel *channel,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index
437c9c8..7b1af52 100644
--- a/include/linux/hyperv.h
+++ b/include/linux/hyperv.h
@@ -756,8 +756,20 @@ struct vmbus_channel {
* link up channels based on their CPU affinity.
*/
struct list_head percpu_list;
+ /*
+ * Host signaling policy: The default policy will be
+ * based on the ring buffer state. We will also support
+ * a policy where the client driver can have explicit
+ * signaling control.
+ */
+ bool signal_state;
};
+static inline void set_channel_signal_state(struct vmbus_channel *c,
+bool state) {
+ c->signal_state = state;
+}
+
static inline void set_channel_read_state(struct vmbus_channel *c, bool
state) {
c->batched_reading = state;
--
1.7.4.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1522922] Re: Screen flickering in Intel i915 driver
** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Bug watch added: freedesktop.org Bugzilla #91393 https://bugs.freedesktop.org/show_bug.cgi?id=91393 ** Also affects: nouveau via https://bugs.freedesktop.org/show_bug.cgi?id=91393 Importance: Unknown Status: Unknown ** No longer affects: linux (Ubuntu) ** Changed in: libdrm (Ubuntu) Importance: Undecided => Critical ** Changed in: libdrm (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/1522922 Title: Screen flickering in Intel i915 driver Status in Nouveau Xorg driver: Unknown Status in libdrm package in Ubuntu: Confirmed Bug description: There's an upstream bug reported here https://bugs.freedesktop.org/show_bug.cgi?id=91393 that causes screen flickering when using the Intel i915 builtin driver (at resolutions lower than the maximal one). I think that it will be fixed in newer kernel versions, but for the time being, as reported here https://bugs.freedesktop.org/show_bug.cgi?id=91393#c25 (and as personally tested) reverting those two commits fixes the problem. Would that be possible to release a fixed version for the 4.2.0 stream? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bettini1378 F pulseaudio /dev/snd/controlC1: bettini1378 F pulseaudio CurrentDesktop: KDE Date: Fri Dec 4 19:01:00 2015 HibernationDevice: RESUME=UUID=7ddbc972-3ad6-40de-9313-2bb9395145f9 InstallationDate: Installed on 2015-05-08 (210 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell Precision M3800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=dd2c7064-53b9-4720-96ab-5e8a3f2db3ea ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-11-07 (26 days ago) dmi.bios.date: 08/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1522922/+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 1522596] Re: I dont know
*** This bug is a duplicate of bug 1492764 *** https://bugs.launchpad.net/bugs/1492764 ** This bug has been marked a duplicate of bug 1492764 [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) -- 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/1522596 Title: I dont know Status in linux package in Ubuntu: Confirmed Bug description: I dont know whats wrong but its annoying and its making my computer slow and lightdm stops working. Sometimes the tty are not working. Just shows errors like [ 421.764373] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) [ 421.764594] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) [ 421.765109] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0) Here i tried to open gdm instead lightdm ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Thu Dec 3 22:47:44 2015 HibernationDevice: RESUME=UUID=0f7f19d0-7e4e-492c-92e5-f55eba8d6939 InstallationDate: Installed on 2015-10-23 (41 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20354 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed root=UUID=a6c2d2ef-8b41-4003-8d93-d1bcf28a7cc0 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN26WW:bd07/31/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.name: 20354 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522596/+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 1509029] Re: [Hyper-V] Crash in hot-add/remove scsi devices (smp)
Tested the -proposed kernels on all 3 releases, couldn't reproduce the
bug.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-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/1509029
Title:
[Hyper-V] Crash in hot-add/remove scsi devices (smp)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Status in linux source package in Wily:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
On some host errors storvsc module tries to remove sdev by scheduling a job
which does the following:
sdev = scsi_device_lookup(wrk->host, 0, 0, wrk->lun);
if (sdev) {
scsi_remove_device(sdev);
scsi_device_put(sdev);
}
While this code seems correct the following crash is observed:
general protection fault: [#1] SMP DEBUG_PAGEALLOC
RIP: 0010:[] [] bdi_destroy+0x39/0x220
...
[] ? _raw_spin_unlock_irq+0x2c/0x40
[] blk_cleanup_queue+0x17b/0x270
[] __scsi_remove_device+0x54/0xd0 [scsi_mod]
[] scsi_remove_device+0x2b/0x40 [scsi_mod]
[] storvsc_remove_lun+0x3d/0x60 [hv_storvsc]
[] process_one_work+0x1b1/0x530
...
The problem comes with the fact that many such jobs (for the same device)
are being scheduled simultaneously. While scsi_remove_device() uses
shost->scan_mutex and scsi_device_lookup() will fail for a device in
SDEV_DEL state there is no protection against someone who did
scsi_device_lookup() before we actually entered __scsi_remove_device(). So
the whole scenario looks like that: two callers do simultaneous (or
preemption happens) calls to scsi_device_lookup() ant these calls succeed
for all of them, after that both callers try doing scsi_remove_device().
shost->scan_mutex only serializes their calls to __scsi_remove_device()
and we end up doing the cleanup path twice.
Signed-off-by: Vitaly Kuznetsov
---
drivers/scsi/scsi_sysfs.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
index b89..e0d2707 100644
--- a/drivers/scsi/scsi_sysfs.c
+++ b/drivers/scsi/scsi_sysfs.c
@@ -1076,6 +1076,14 @@ void __scsi_remove_device(struct scsi_device *sdev)
{
struct device *dev = &sdev->sdev_gendev;
+ /*
+* This cleanup path is not reentrant and while it is impossible
+* to get a new reference with scsi_device_get() someone can still
+* hold a previously acquired one.
+*/
+ if (sdev->sdev_state == SDEV_DEL)
+ return;
+
if (sdev->is_visible) {
if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
return;
--
2.4.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509029/+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 1521982] Re: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/le
Please: 1. Translate the bug title and description into English. 2. Set this bug status back to "confirmed". Thank you. ** 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/1521982 Title: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« können nicht nach »/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko .dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms Status in linux package in Ubuntu: Incomplete Bug description: none ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-extra-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carsten1741 F pulseaudio /dev/snd/controlC1: carsten1741 F pulseaudio Date: Tue Dec 1 21:46:29 2015 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« können nicht nach »/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms HibernationDevice: RESUME=UUID=55b16c37-9a10-448a-8d4e-f59a0ed550ea InstallationDate: Installed on 2015-11-19 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P67A-UD3-B3 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=9c54422a-2851-4e1a-b9f6-28e6374aa754 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-29 RfKill: SourcePackage: linux Title: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« können nicht nach »/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: P67A-UD3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67A-UD3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521982/+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 1522139] Re: Unable to adjust brightness
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1522139 Title: Unable to adjust brightness Status in linux package in Ubuntu: Confirmed Bug description: I have an Intel NUC that's otherwise running Ubuntu 15.10 great! It's hooked up to a ViewSonic monitor via mini-DV / DVI. The brightness controls are disabled on the monitor. xbacklight does nothing. And I don't have the Brightness slider in Brightness & Lock. I've been poking around, and have seen where to create a file in xorg.conf.d. The problem is, I have an empty /sys/class/backlight dir. Per the following, I'm submitting a support ticket: https://askubuntu.com/questions/577539/dell-chromebook-11-unable-to- set-backlight-and-sys-class-backlight-folder-is/578497#578497 I'd like to be able to increase the brightness on my screen. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 2213 F pulseaudio /dev/snd/controlC0: mark 2213 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 2 15:24:39 2015 HibernationDevice: RESUME=UUID=475f89b0-71dc-465f-997e-e88d611d948d InstallationDate: Installed on 2015-11-24 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1522139/+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 1519917] Re: [Hyper-V] Rebase Hyper-V to 4.3 kernel
Based on your testing, do you think the Wily rebase to the 4.3 kernel would be ok to perform? Or do you want to wait until bug 1515301 is resolved first? -- 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/1519917 Title: [Hyper-V] Rebase Hyper-V to 4.3 kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: In Progress Bug description: Please rebase Hyper-V support to the final upstream 4.3 kernel. The following files and directories contain Hyper-V support: arch/x86/include/asm/mshyperv.h arch/x86/include/uapi/asm/hyperv.h arch/x86/kernel/cpu/mshyperv.c drivers/hid/hid-hyperv.c drivers/hv/ drivers/input/serio/hyperv-keyboard.c drivers/net/hyperv/ drivers/scsi/storvsc_drv.c drivers/video/hyperv_fb.c include/linux/hyperv.h tools/hv/ There are, of course, a number of sauce items already present in Ubuntu to keep. Please add the following additional sauce item for networking performance [attached]. This rebase request is intended for wily/15.10. We should investigate it's applicability to vivid/15.04 and HWE kernels as well. Because 14.04's HWE kernel will change to wily in January, 15.10 may be sufficient in the long term. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519917/+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 1521972] Re: Touchpad not working after installing of Ubuntu 15.10
** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1521972 Title: Touchpad not working after installing of Ubuntu 15.10 Status in linux package in Ubuntu: Confirmed Bug description: Before fresh installation of Ubuntu 15.10, I had multi-boot of Xorin and windows 8.1. Later I installed Ubuntu 15.10 on the DELL Vostro 3558, where my touch-pad doesn’t work. But the external mouse works fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anston 1457 F pulseaudio /dev/snd/controlC0: anston 1457 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 2 16:18:00 2015 HibernationDevice: RESUME=UUID=4d3f9258-ca19-40d8-9ce8-877268831b4a InstallationDate: Installed on 2015-11-30 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Vostro 3558 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/09/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 05JF1T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/09/2015:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn05JF1T:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521972/+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 1521848] Re: Toshiba Satalite L50-A touchpad does not work after kernal update
** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1521848 Title: Toshiba Satalite L50-A touchpad does not work after kernal update Status in linux package in Ubuntu: Confirmed Bug description: Hello, Ever since 2 days ago, I cannot get the touchpad on my Toshiba Laptop to work with Ubuntu. It works fine on Windows (dual booting.) It worked before that, and i'm guessing an update messed something up. This happened once before, but an update fixed the issue before I reported it. I'm not sure what the deal is, but let me know if there's anything else I can provide to help you fix the issue. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seaver 2039 F pulseaudio /dev/snd/controlC1: seaver 2039 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 1 23:21:06 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-03 (28 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: TOSHIBA Satellite L50-A ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=f06955e3-4b16-46c5-839b-eccf9692643a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.80 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.80:bd04/28/2014:svnTOSHIBA:pnSatelliteL50-A:pvrPSKLJU-00D004:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L50-A dmi.product.version: PSKLJU-00D004 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521848/+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 1521721] Re: wireless adapter not working
Please: 1. Edit the bug description, so it is clear if the adapter is internal or external. 2. Set this bug status back to "confirmed". Thank you. ** 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/1521721 Title: wireless adapter not working Status in linux package in Ubuntu: Incomplete Bug description: Wireless adapter is not supported by kernel. Output: dmitry@dmitry-Aspire:~$ lspci -nn | grep 0280 03:00.0 Network controller [0280]: Qualcomm Atheros Device [168c:0042] (rev 30) Googling showed that this is usual problem with this adapter. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dmitry 1622 F pulseaudio /dev/snd/controlC0: dmitry 1622 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 1 20:14:18 2015 HibernationDevice: RESUME=UUID=f2b7d192-0855-4d69-b859-a37591352ec2 InstallationDate: Installed on 2015-12-01 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Acer Aspire E5-573G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=79750c04-717b-481d-bfb2-f5050c612f91 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH 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.15:bd05/27/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-573G dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521721/+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 1506521] Re: [Hyper-V] hv_set_ifconfig issues on Wily 15.10
** Tags added: wily xenial ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Changed in: linux (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Wily) 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/1506521 Title: [Hyper-V] hv_set_ifconfig issues on Wily 15.10 Status in linux package in Ubuntu: Confirmed Status in linux source package in Wily: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Hello, It seems that during the Wily development, some changes have occurred that broke the hv_set_ifconfig script. Please see the below details and update the script accordingly. From my understanding the changes in python versioning on 15.10 are causing this, and when running hv_set_ifconfig with Python v3, it will give some code errors. This has been verified with the daily build from Oct 12, kernel 4.2.0-16-generic and the matching linux-cloud-tools/common are installed. # whereis hv_set_ifconfig hv_set_ifconfig: /usr/sbin/hv_set_ifconfig # /usr/sbin/hv_set_ifconfig /usr/bin/env: python: No such file or directory Indeed there is no python executable by default, only python3. Modifying the header for hv_set_ifconfig to use python3, returns the below: ~# /usr/sbin/hv_set_ifconfig File "/usr/sbin/hv_set_ifconfig", line 130 print "===" ^ SyntaxError: Missing parentheses in call to 'print' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1523133] Re: strongswan vpn does not work
volker, it's in 4.3.0-4.13: http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_4.3.0-4.13/changelog -- 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/1523133 Title: strongswan vpn does not work Status in linux package in Ubuntu: Fix Committed Status in strongswan package in Ubuntu: Invalid Bug description: strongswan vpn does not work with any of the published kernels 4.3 (including 4.3.0-2): I have already reported this problem some days ago to strongswan.org under ticket #1189: "I'm using strongswan 5.1.2-0ubuntu8 in lubuntu-16.04 (development) with kernel 4.3. Setting up VPN with the NetworkManager, I get no error, BUT VPN does not work; establishing VPN manually with: sudo ipsec restart, sudo ipsec up ..., I get the following in the console: received netlink error: invalid argument (22). Unable to install source route for 139.174.7.. But finally it says: "connection "" established correctly" (as when using the NetworkManager VPN connection does not work however!!)." No such problem occur when using the kernel 4.2.0-19 (also 4.2.0-21) instead: VPN works okay. The same behaviour is found for lubuntu-15.10 with all kernels 4.3 where a older version of strongswan is still installed. I was told by strongswan.org that this is a kernel bug (a patch appears to exist; see the discussion at #1189). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: strongswan 5.1.2-0ubuntu6.2 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 CurrentDesktop: LXDE Date: Sat Dec 5 17:22:51 2015 InstallationDate: Installed on 2014-02-12 (660 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) PackageArchitecture: all SourcePackage: strongswan UpgradeStatus: Upgraded to wily on 2015-10-09 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1518457] Re: kswapd0 100% CPU usage
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Triaged => 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/1518457 Title: kswapd0 100% CPU usage Status in linux package in Ubuntu: In Progress Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1508593] Re: [Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
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/1508593
Title:
[Hyper-V] x86/ioapic: Disable interrupts when re-routing legacy IRQs
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
In Progress
Status in linux source package in Vivid:
In Progress
Status in linux source package in Wily:
Fix Committed
Bug description:
A sporadic hang with consequent crash is observed when booting Hyper-V
Gen1 guests...
Sauce request for upstream submission:
https://lkml.org/lkml/2015/10/15/673
From Vitaly Kuznetsov <>
Subject [PATCH] x86/ioapic: Disable interrupts when re-routing legacy IRQs
Date Thu, 15 Oct 2015 19:42:23 +0200
A sporadic hang with consequent crash is observed when booting Hyper-V Gen1
guests:
Call Trace:
[] ? trace_hardirqs_off+0xd/0x10
[] queue_work_on+0x46/0x90
[] ? add_interrupt_randomness+0x176/0x1d0
...
[] ? _raw_spin_unlock_irqrestore+0x3b/0x60
[] __irq_put_desc_unlock+0x1e/0x40
[] irq_modify_status+0xb5/0xd0
[] mp_register_handler+0x4b/0x70
[] mp_irqdomain_alloc+0x1ea/0x2a0
[] irq_domain_alloc_irqs_recursive+0x40/0xa0
[] __irq_domain_alloc_irqs+0x13c/0x2b0
[] alloc_isa_irq_from_domain.isra.1+0xc0/0xe0
[] mp_map_pin_to_irq+0x165/0x2d0
[] pin_2_irq+0x47/0x80
[] setup_IO_APIC+0xfe/0x802
...
[] ? rest_init+0x140/0x140
The issue is easily reproducible with a simple instrumentation: if
mdelay(10) is put between mp_setup_entry() and mp_register_handler() calls
in mp_irqdomain_alloc() Hyper-V guest always fails to boot when re-routing
IRQ0. The issue seems to be caused by the fact that we don't disable
interrupts while doing IOPIC programming for legacy IRQs and IRQ0 actually
happens. Decorate manipulations with legacy IRQs with local_irq_save()/
local_irq_restore().
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: Jiang Liu
Cc: Yinghai Lu
Cc: K. Y. Srinivasan
Signed-off-by: Vitaly Kuznetsov
---
It may make sense to have interrupts disabled for non-legacy IRQs as well
but I'm unaware of any bugs with them at this moment.
---
arch/x86/kernel/apic/io_apic.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
index 5c60bb1..9aac777 100644
--- a/arch/x86/kernel/apic/io_apic.c
+++ b/arch/x86/kernel/apic/io_apic.c
@@ -2907,6 +2907,7 @@ int mp_irqdomain_alloc(struct irq_domain *domain,
unsigned int virq,
struct irq_data *irq_data;
struct mp_chip_data *data;
struct irq_alloc_info *info = arg;
+ unsigned long flags = 0;
if (!info || nr_irqs > 1)
return -EINVAL;
@@ -2939,11 +2940,16 @@ int mp_irqdomain_alloc(struct irq_domain *domain,
unsigned int virq,
cfg = irqd_cfg(irq_data);
add_pin_to_irq_node(data, ioapic_alloc_attr_node(info), ioapic, pin);
+
+ if (virq < nr_legacy_irqs())
+ local_irq_save(flags);
if (info->ioapic_entry)
mp_setup_entry(cfg, data, info->ioapic_entry);
mp_register_handler(virq, data->trigger);
- if (virq < nr_legacy_irqs())
+ if (virq < nr_legacy_irqs()) {
legacy_pic->mask(virq);
+ local_irq_restore(flags);
+ }
apic_printk(APIC_VERBOSE, KERN_DEBUG
"IOAPIC[%d]: Set routing entry (%d-%d -> 0x%x -> IRQ %d
Mode:%i Active:%i Dest:%d)\n",
--
2.4.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508593/+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 1494423] Re: Upstream commits for NUMA node performance in Hyper-V
** Changed in: linux (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1494423 Title: Upstream commits for NUMA node performance in Hyper-V Status in linux package in Ubuntu: In Progress Status in linux-lts-trusty package in Ubuntu: In Progress Status in linux-lts-trusty source package in Precise: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Bug description: Microsoft has investigated networking with NUMA nodes and Hyper-V and found a number of areas where Linux performance could be corrected to be in line with other virtual machine types. Please include the following commits and their necessary prerequisites (which have been accepted upstream into the 4.2 kernel series) into the kernels for 15.10, 15.04, 14.04 (including HWE), and 12.04 (including HWE): 8/5 "Drivers: hv: vmbus: Further improve CPU affiliation logic" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3b71107d73b16074afa7658f3f0fcf837aabfe24 8/5 "Drivers: hv: vmbus: Improve the CPU affiliation for channels" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9f01ec53458d9e9b68f1c555e773b5d1a1f66e94 6/12 "Drivers: hv: vmbus: Allocate ring buffer memory in NUMA aware fashion" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=294409d20572e9bcf857328286433f851168d54a 6/1 "Drivers: hv: vmbus: Implement NUMA aware CPU affinity for channels" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f656ff3fdddc2f59649cc84b633b799908f1f7b 5/31 "hv_netvsc: Allocate the receive buffer from the correct NUMA node" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0a726c2b499e390b1c1fc3092bd789f2192a2d03 5/31 "hv_netvsc: Allocate the sendbuf in a NUMA aware way" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5defde5946676ee23cd6a9d0e1de899410f4a33f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494423/+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 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid
** Changed in: linux (Ubuntu) Status: Fix Released => 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/1440103 Title: [Hyper-V] Kernel panic not functional on Vivid Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: Fix Released Bug description: Issue description: Triggering a kernel panic will not produce a crash dump file. Steps to Reproduce: 1. install kdump related packages. 2. verify crashmem value - defaults to 384M-:129M 3. verify that the system is ready for crash: # cat /sys/kernel/kexec_crash_loaded 1 4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger 5. The system will freeze and no kernel dump will be generated, system is not rebooted automatically as configured in kdump-tools config. Versions details: Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter build 9600 Distribution name and release: Ubuntu Vivid Vervet Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 SMP Repro output with VM settings as follows: 2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M [ 149.328829] SysRq : Trigger a crash [ 149.342418] BUG: unable to handle kernel NULL pointer dereference at (null) [ 149.346369] IP: [] sysrq_handle_crash+0x16/0x20 [ 149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0 [ 149.346369] Oops: 0002 [#1] SMP [ 149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 8250_fintek hyperv_keyboard hv_balloon hyp erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy pata_acpi hv_vmbus [ 149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic #11lp14233432v201504021617 [ 149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006 05/23/2012 [ 149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 88007be7c000 [ 149.346369] RIP: 0010:[] [] sysrq_handle_crash+0x16/0x20 [ 149.346369] RSP: 0018:88007be7fe68 EFLAGS: 00010292 [ 149.346369] RAX: 000f RBX: 0063 RCX: 000f [ 149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 0063 [ 149.346369] RBP: 88007be7fe68 R08: 0002 R09: 0275 [ 149.346369] R10: 0092 R11: 0275 R12: 0004 [ 149.346369] R13: R14: 81cb38e0 R15: 0008 [ 149.346369] FS: 7f0a2e22a700() GS:88007ce0() knlGS: [ 149.346369] CS: 0010 DS: ES: CR0: 8005003b [ 149.346369] CR2: CR3: 36047000 CR4: 06f0 [ 149.346369] Stack: [ 149.346369] 88007be7fe98 814aef96 0002 fffb [ 149.346369] 7ffc64e934b0 0002 88007be7feb8 814af443 [ 149.346369] 7ffc64e934b0 8800364f15c0 88007be7fed8 8125ad98 [ 149.346369] Call Trace: [ 149.346369] [] __handle_sysrq+0x106/0x170 [ 149.346369] [] write_sysrq_trigger+0x33/0x40 [ 149.346369] [] proc_reg_write+0x48/0x70 [ 149.346369] [] vfs_write+0xb7/0x1f0 [ 149.346369] [] ? vfs_read+0x11e/0x140 [ 149.346369] [] SyS_write+0x46/0xb0 [ 149.346369] [] system_call_fastpath+0x16/0x1b [ 149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00 01 00 00 00 48 89 e5 0f ae f8 04 25 00 00 00 00 01 5d c3 66 66 66 66 90 55 31 c0 48 89 e5 [ 149.346369] RIP [] sysrq_handle_crash+0x16/0x20 [ 149.346369] RSP [ 149.346369] CR2: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v 201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 3.19.0-11.11lp14233432v201504021617-generic 3.19.3) [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service elfcorehdr=867700K To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1454892] Re: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host
** Changed in: linux (Ubuntu) Status: Fix Released => 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/1454892 Title: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host Status in linux package in Ubuntu: In Progress Status in linux-lts-utopic package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux-lts-utopic source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Bug description: hv_netvsc: Use the xmit_more skb flag to optimize signaling the host Based on the information given to this driver (via the xmit_more skb flag), we can defer signaling the host if more packets are on the way. This will help make the host more efficient since it can potentially process a larger batch of packets. Implement this optimization. Upstream commit: https://git.kernel.org/cgit/linux/kernel/git/davem /net-next.git/commit/?id=82fa3c776e5abba7ed6e4b4f4983d14731c37d6a This commit may imply other commits previously requested, for example https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452074 Requested for all typical Hyper-V targets: 15.10, 15.04, 14.10, 14.04, 14.04 HWE, 12.02, and 12.02 HWE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1511534] Re: [Hyper-V] Fibre Channel multipath error message
Does this bug still happen after applying the latest updates? -- 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/1511534 Title: [Hyper-V] Fibre Channel multipath error message Status in linux package in Ubuntu: Triaged Bug description: Problem statement: Wily (and probably other previous releases with the updated kernels) return a multipath error for vFC (virtual Fibre Channel). Symptoms: The following messages are in the dmesg log during booting: device-mapper: table: 252:4: multipath: error getting device device-mapper: IOCtl: error adding target to table After logging in, run the command: multipath -ll The multipath command does not return any errors, and no new messages are added to the dmesg log or syslog after running the multipath command. Steps to repro Tested with the released Wily (15.10), kernel 4.2.0-16-generic. 1. Create a Wily VM. 2. Boot and install the multipath-tools package. 3. Shutdown and attach a Virtual Fiber Channel adapter and connect it to a virtual SAN. Note: The host must have a Fiber Channel adapter. Use Hyper-V managers Virtual SAN Manager to create a Virtual Fiber Channel Storage Area Network. 4. Boot the VM. 5. Issue the following command to see any errors were reported during the boot. dmesg | grep -i error You should see the following two error: device-mapper: table: 252:4: multipath: error getting device device-mapper: IOCtl: error adding target to table Otherwise, the vFC disks are usable and show no issues at a use test case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511534/+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 1508706] Re: Networking hangs on azure using hv_netvsc; bisected
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => High -- 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/1508706 Title: Networking hangs on azure using hv_netvsc; bisected Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Bug description: Running Ubuntu instances on azure, testing basic networking between two instances. This involves configuring VXLAN between the two instances and running iperf and rsync of the kernel tree between the instances, e.g., ip link add vxlan0 type vxlan id 999 local 10.88.0.12 remote 10.88.0.11 dev eth0 ip l set vxlan0 up ip addr add 242.0.0.12/8 dev vxlan0 After some time (sometimes instantly, sometimes up to 30 minutes of activity), the networking will hang. This hang takes two forms: a complete loss of connectivity (all network, even the ssh session used to log in), or just a loss of connectivity between instances (the ssh session remains active). Sometimes for the latter case, the ssh session will then later hang. This first appeared when testing with the Ubuntu 3.19 kernel, and I subsequently bisected this to: commit effa2012d207f78cbc5a8360e62d420a8860b7e9 Author: KY Srinivasan Date: Mon May 11 15:39:46 2015 -0700 hv_netvsc: Use the xmit_more skb flag to optimize signaling the host BugLink: http://bugs.launchpad.net/bugs/1454892 Based on the information given to this driver (via the xmit_more skb flag), we can defer signaling the host if more packets are on the way. This will help make the host more efficient since it can potentially process a larger batch of packets. Implement this optimization. Signed-off-by: K. Y. Srinivasan Signed-off-by: David S. Miller Acked-by: Tim Gardner Acked-by: Brad Figg Signed-off-by: Brad Figg I also tested the mainline kernel (net-next); it fails with the equivalent commit: commit 82fa3c776e5abba7ed6e4b4f4983d14731c37d6a Author: KY Srinivasan Date: Mon May 11 15:39:46 2015 -0700 hv_netvsc: Use the xmit_more skb flag to optimize signaling the host For both kernel trees, I also tested the prior commit and it did not exhibit the failure after many hours. For ubuntu, this was commit a4aeb290bd75af5e16a6144a418291476ac6140c Author: K. Y. Srinivasan Date: Wed Mar 18 12:29:29 2015 -0700 Drivers: hv: vmbus: Export the vmbus_sendpacket_pagebuffer_ctl() and for mainline it was commit 9eea92226407e7a117ef1ceef45380ebd000a0e2 Author: Alexei Starovoitov Date: Mon May 11 15:19:48 2015 -0700 pktgen: fix packet generation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508706/+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 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Wily)
Status: Triaged => 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/1519897
Title:
[Hyper-V] hv: vmbus: Fix a host signaling bug
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Triaged
Status in linux source package in Vivid:
Triaged
Status in linux source package in Wily:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The following fix has been submitted upstream, but has high enough
severity that we would like early inclusion into the Ubuntu kernel.
Please consider for wily, vivid, and trusty (and the HWE kernels for
the same).
Patch follows:
Currently we have two policies for deciding when to signal the host:
One based on the ring buffer state and the other based on what the VMBUS
client driver wants to do. Consider the case when the client wants to
explicitly control when to signal the host. In this case, if the client were to
defer signaling, we will not be able to signal the host subsequently when the
client does want to signal since the ring buffer state will prevent the
signaling. Implement logic to have only one signaling policy in force for a
given channel.
Signed-off-by: K. Y. Srinivasan
Reviewed-by: Haiyang Zhang
Tested-by: Haiyang Zhang
Cc: # v4.2+
---
drivers/hv/channel.c | 18 ++
include/linux/hyperv.h | 12
2 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index
77d2579..c6278c7 100644
--- a/drivers/hv/channel.c
+++ b/drivers/hv/channel.c
@@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel,
void *buffer,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
@@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct
vmbus_channel *channel,
*on the ring. We will not signal if more data is
*to be placed.
*
+ * Based on the channel signal state, we will decide
+ * which signaling policy will be applied.
+ *
* If we cannot write to the ring-buffer; signal the host
* even if we may not have written anything. This is a rare
* enough condition that it should not matter.
*/
+
+ if (channel->signal_state)
+ signal = true;
+ else
+ kick_q = true;
+
if (((ret == 0) && kick_q && signal) || (ret))
vmbus_setevent(channel);
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index
437c9c8..7b1af52 100644
--- a/include/linux/hyperv.h
+++ b/include/linux/hyperv.h
@@ -756,8 +756,20 @@ struct vmbus_channel {
* link up channels based on their CPU affinity.
*/
struct list_head percpu_list;
+ /*
+ * Host signaling policy: The default policy will be
+ * based on the ring buffer state. We will also support
+ * a policy where the client driver can have explicit
+ * signaling control.
+ */
+ bool signal_state;
};
+static inline void set_channel_signal_state(struct vmbus_channel *c,
+bool state) {
+ c->signal_state = state;
+}
+
static inline void set_channel_read_state(struct vmbus_channel *c, bool
state) {
c->batched_reading = state;
--
1.7.4.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1499203] Re: memory leak in hv_storvsc (3.13.0-63-generic)
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Trusty) Status: Confirmed => In Progress ** 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/1499203 Title: memory leak in hv_storvsc (3.13.0-63-generic) Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: Slab and SUnreclaim values in /proc/meminfo keep increasing. On one servers it reached 85% of physical memory after 14 days - but on most other servers it increases more slowly. I checked /proc/slabinfo and almost all allocations were in kmalloc-512. So I enabled "slub_debug=U,kmalloc-512" on one server, and after only 24h of uptime 11% of the memory was used by kmalloc-512 and unreclaimable. With debugging enabled I could see the following in /sys/kernel/slab/kmalloc-512/alloc_calls: 521294 storvsc_queuecommand+0x359/0x790 [hv_storvsc] age=161922/955116/20882927 pid=1-41545 All other counters were below 2000. In /sys/kernel/slab/kmalloc-512/free_calls I see the following: 516823 age=4315783846 pid=0 The hv_storvsc module is for Hyper-V. We are (unfortunately) running Hyper-V 6.3.9600.16384 with Microsoft System Center 2012 R2 Update rollup 3 for all the servers with this issue. Kernels are stock linux-image-3.13.0-63-generic, 3.13.0-63.103, x86_64, from Ubuntu 14.04 LTS . /proc/version_signature contains: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 No output from lspci -vnvn. The problem described above happens on both single and multicore virtual machines. CPU in hypervisors are E5-2630 v2 @ 2.60GHz. Let me know if you need more info or if I can do more debugging. Regards, Oskar Liljeblad --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 24 00:31 seq crw-rw 1 root audio 116, 33 Sep 24 00:31 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [59081.977909] systemd-udevd[26480]: starting version 204 [59124.051974] init: systemd-logind main process (756) killed by TERM signal DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-09-09 (380 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic.efi.signed root=UUID=f4d228d6-2eee-40fc-bf3f-633e46fa8301 ro slub_debug=U,kmalloc-512 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 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: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: Sep 24 02:06:19 adm-backup1 dhclient: message repeated 1447 times: [ DHCPREQUEST of 10.40.128.9 on eth0 to 192.0.2.253 port 67 (xid=0x429dad4)] Sep 24 02:06:37 adm-backup1 dhclient: DHCPREQUEST of 10.40.128.9 on eth0 to 255.255.255.255 port 67 (xid=0x429dad4) Sep 24 02:06:37 adm-backup1 dhclient: DHCPACK of 10.40.128.9 from 192.0.2.253 Sep 24 02:06:37 adm-backup1 dhclient: bound to 10.40.128.9 -- renewal in 44877 seconds. _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6126-4244-1659-0314-3158-3955-44 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHy
[Kernel-packages] [Bug 1292400] Re: task systemd-udevd:1906 blocked for more than 120 seconds.
** 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/1292400 Title: task systemd-udevd:1906 blocked for more than 120 seconds. Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Incomplete Status in linux source package in Vivid: Incomplete Bug description: System log shows repeated incidents of "task systemd-udevd:1906 blocked for more than 120 seconds." ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 [modified: boot/vmlinuz-3.13.0-17-generic] ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Fri Mar 14 08:54:36 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (1 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video:hyperv_fb=1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (1 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video:hyperv_fb=1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 RfKill: Tags: trusty Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.v
[Kernel-packages] [Bug 1508609] Re: [Hyper-V] Race condition in SMP bootup
** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1508609
Title:
[Hyper-V] Race condition in SMP bootup
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Invalid
Status in linux source package in Vivid:
Fix Released
Status in linux source package in Wily:
Fix Released
Bug description:
Please integrate the following upstream commit.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=dd9d3843755da95f63dd3a376f62b3e45c011210
sched: Fix cpu_active_mask/cpu_online_mask race
There is a race condition in SMP bootup code, which may result
in
WARNING: CPU: 0 PID: 1 at kernel/workqueue.c:4418
workqueue_cpu_up_callback()
or
kernel BUG at kernel/smpboot.c:135!
It can be triggered with a bit of luck in Linux guests running
on busy hosts.
CPU0CPUn
_cpu_up()
__cpu_up()
start_secondary()
set_cpu_online()
cpumask_set_cpu(cpu,
to_cpumask(cpu_online_bits));
cpu_notify(CPU_ONLINE)
cpumask_set_cpu(cpu,
to_cpumask(cpu_active_bits));
During the various CPU_ONLINE callbacks CPUn is online but not
active. Several things can go wrong at that point, depending on
the scheduling of tasks on CPU0.
Variant 1:
cpu_notify(CPU_ONLINE)
workqueue_cpu_up_callback()
rebind_workers()
set_cpus_allowed_ptr()
This call fails because it requires an active CPU; rebind_workers()
ends with a warning:
WARNING: CPU: 0 PID: 1 at kernel/workqueue.c:4418
workqueue_cpu_up_callback()
Variant 2:
cpu_notify(CPU_ONLINE)
smpboot_thread_call()
smpboot_unpark_threads()
..
__kthread_unpark()
__kthread_bind()
wake_up_state()
..
select_task_rq()
select_fallback_rq()
The ->wake_cpu of the unparked thread is not allowed, making a call
to select_fallback_rq() necessary. Then, select_fallback_rq() cannot
find an allowed, active CPU and promptly resets the allowed CPUs, so
that the task in question ends up on CPU0.
When those unparked tasks are eventually executed, they run
immediately into a BUG:
kernel BUG at kernel/smpboot.c:135!
Just changing the order in which the online/active bits are set
(and adding some memory barriers), would solve the two issues
above. However, it would change the order of operations back to
the one before commit 6acbfb96976f ("sched: Fix hotplug vs.
set_cpus_allowed_ptr()"), thus, reintroducing that particular
problem.
Going further back into history, we have at least the following
commits touching this topic:
- commit 2baab4e90495 ("sched: Fix select_fallback_rq() vs
cpu_active/cpu_online")
- commit 5fbd036b552f ("sched: Cleanup cpu_active madness")
Together, these give us the following non-working solutions:
- secondary CPU sets active before online, because active is assumed to
be a subset of online;
- secondary CPU sets online before active, because the primary CPU
assumes that an online CPU is also active;
- secondary CPU sets online and waits for primary CPU to set active,
because it might deadlock.
Commit 875ebe940d77 ("powerpc/smp: Wait until secondaries are
active & online") introduces an arch-specific solution to this
arch-independent problem.
Now, go for a more general solution without explicit waiting and
simply set active twice: once on the secondary CPU after online
was set and once on the primary CPU after online was seen.
set_cpus_allowed_ptr()")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508609/+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 1282696] Re: hyper-v: screen corruption on resume
@Dexuan, Is this bug still an issue, or can it be closed? -- 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/1282696 Title: hyper-v: screen corruption on resume Status in linux package in Ubuntu: Triaged Bug description: d) Patch to fix screen corruption during suspend/resume of virtual machine https://patchwork.kernel.org/patch/3481181/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1282696/+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 1292400] Re: task systemd-udevd:1906 blocked for more than 120 seconds.
I don't see the patch mentioned in comment #22 in Vivid or Trusty, but I do see it in Wily. Is this bug still an issue for releases prior to Wily? ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Status: New => Incomplete ** Changed in: linux (Ubuntu Vivid) 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/1292400 Title: task systemd-udevd:1906 blocked for more than 120 seconds. Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Incomplete Status in linux source package in Vivid: Incomplete Bug description: System log shows repeated incidents of "task systemd-udevd:1906 blocked for more than 120 seconds." ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 [modified: boot/vmlinuz-3.13.0-17-generic] ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Fri Mar 14 08:54:36 2014 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (1 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video:hyperv_fb=1920x1080 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 6485-6574-9248-6162-4701-6267-50 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=0d223c65-8c7e-41b4-95b3-05b22ff4679b InstallationDate: Installed on 2014-03-12 (1 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=61b52c1b-300d-4c30-8966-db1745f4a4bc ro video:hyperv_fb=1920x1080 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 RfKill: Tags: trusty Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chas
[Kernel-packages] [Bug 1463584] Re: [Hyper-V] Add support for VMBus panic notifier handler
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1463584 Title: [Hyper-V] Add support for VMBus panic notifier handler Status in linux package in Ubuntu: Fix Released 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: Please take these patches to our Hyper-V VMBus driver to enable kernel crash notification: Drivers: hv: vmbus: Add support for VMBus panic notifier handler https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=96c1d0581d00f7abe033350edb021a9d947d8d81 Drivers: hv: vmbus: Correcting truncation error for constant HV_CRASH_CTL_CRASH_NOTIFY https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/hv?id=5ef5b6927f14f29cacd78fa1fb861661a5367f13 In the event of a kernel panic, VMBus driver supports sending five 64-bit values to be recorded in the log. On Hyper-V this is recorded in the event log, and on Azure we can use this data to better detect failures like this in the guest VM and surface that as part of our diagnostics information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+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 1509029] Re: [Hyper-V] Crash in hot-add/remove scsi devices (smp)
** Tags removed: verification-needed-wily
** Tags added: verification-done-wily
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1509029
Title:
[Hyper-V] Crash in hot-add/remove scsi devices (smp)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Status in linux source package in Wily:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
On some host errors storvsc module tries to remove sdev by scheduling a job
which does the following:
sdev = scsi_device_lookup(wrk->host, 0, 0, wrk->lun);
if (sdev) {
scsi_remove_device(sdev);
scsi_device_put(sdev);
}
While this code seems correct the following crash is observed:
general protection fault: [#1] SMP DEBUG_PAGEALLOC
RIP: 0010:[] [] bdi_destroy+0x39/0x220
...
[] ? _raw_spin_unlock_irq+0x2c/0x40
[] blk_cleanup_queue+0x17b/0x270
[] __scsi_remove_device+0x54/0xd0 [scsi_mod]
[] scsi_remove_device+0x2b/0x40 [scsi_mod]
[] storvsc_remove_lun+0x3d/0x60 [hv_storvsc]
[] process_one_work+0x1b1/0x530
...
The problem comes with the fact that many such jobs (for the same device)
are being scheduled simultaneously. While scsi_remove_device() uses
shost->scan_mutex and scsi_device_lookup() will fail for a device in
SDEV_DEL state there is no protection against someone who did
scsi_device_lookup() before we actually entered __scsi_remove_device(). So
the whole scenario looks like that: two callers do simultaneous (or
preemption happens) calls to scsi_device_lookup() ant these calls succeed
for all of them, after that both callers try doing scsi_remove_device().
shost->scan_mutex only serializes their calls to __scsi_remove_device()
and we end up doing the cleanup path twice.
Signed-off-by: Vitaly Kuznetsov
---
drivers/scsi/scsi_sysfs.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
index b89..e0d2707 100644
--- a/drivers/scsi/scsi_sysfs.c
+++ b/drivers/scsi/scsi_sysfs.c
@@ -1076,6 +1076,14 @@ void __scsi_remove_device(struct scsi_device *sdev)
{
struct device *dev = &sdev->sdev_gendev;
+ /*
+* This cleanup path is not reentrant and while it is impossible
+* to get a new reference with scsi_device_get() someone can still
+* hold a previously acquired one.
+*/
+ if (sdev->sdev_state == SDEV_DEL)
+ return;
+
if (sdev->is_visible) {
if (scsi_device_set_state(sdev, SDEV_CANCEL) != 0)
return;
--
2.4.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509029/+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 1523178] Re: 1217:8520 [Dell Latitude E7450] O2 Micro, SD/MMC Card Reader doesn't work
Hello Christopher, Raised https://bugzilla.kernel.org/show_bug.cgi?id=109231 Could not include the people you mentioned though. Please let me know if anything is missing. Thanks ** Bug watch added: Linux Kernel Bug Tracker #109231 http://bugzilla.kernel.org/show_bug.cgi?id=109231 -- 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/1523178 Title: 1217:8520 [Dell Latitude E7450] O2 Micro, SD/MMC Card Reader doesn't work Status in linux package in Ubuntu: Triaged Bug description: Under ubuntu 15.10 I can't use my Sandisk ultra 64GB microSD (with a SD card adapter) with the built in SD card reader. I seem to be getting the following errors. [ 1268.126602] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock [ 1268.128381] mmc0: tuning execution failed [ 1268.128386] mmc0: error -5 whilst initialising SD card [ 1268.554319] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock [ 1268.556098] mmc0: tuning execution failed [ 1268.556103] mmc0: error -5 whilst initialising SD card [ 1268.993995] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock [ 1268.995778] mmc0: tuning execution failed [ 1268.995786] mmc0: error -5 whilst initialising SD card [ 1269.453666] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock [ 1269.455449] mmc0: tuning execution failed [ 1269.455458] mmc0: error -5 whilst initialising SD card It was working fine under vivid with kernel 3.19. Went through all the kernels from 3.19 to 4.2 (http://kernel.ubuntu.com/~kernel-ppa/) and found out that until 4.1.8-040108-generic the SD card reader would play fine and only after I put 4.1.9 and on I started getting the errors. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: alex 1606 F pulseaudio /dev/snd/controlC0: alex 1606 F pulseaudio /dev/snd/controlC1: alex 1606 F pulseaudio CurrentDesktop: Unity Date: Sun Dec 6 01:40:18 2015 HibernationDevice: RESUME=UUID=acf75838-59f9-4461-9fe4-e9bdf33b28be InstallationDate: Installed on 2015-10-27 (38 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. Latitude E7450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=c654e4bc-b0e1-4a85-844f-99f068b2efff ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.149.3 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-11-04 (31 days ago) dmi.bios.date: 10/28/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0R1VJD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/28/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0R1VJD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523178/+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
