[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads
@Shih-Yuan, How about this kernel, which contains all the patches we might need? http://kernel.ubuntu.com/~adamlee/lp1456881_all_patches/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456881 Title: Some touchpads' right button doesn't work under I2C mode, need support of clickpads Status in HWE Next Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: We need to add this support, otherwise some touchpads' right button doesn't work under I2C mode. commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch) HID: multitouch: add support of clickpads Touchpads that have only one button are called clickpads and should be advertised as such by the kernel. Signed-off-by: Benjamin Tissoires Tested-by: Jason Ekstrand Signed-off-by: Jiri Kosina To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads
The touchpad of Dell XPS 13 (2015) in I2C mode doesn't work at all. So there is no regression that I can tell. It doesn't work worse. It doesn't work better either. Maybe it does work on some platform, however I don't know. ** Tags removed: verification-failed-trusty ** Tags added: verification-needed-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/1456881 Title: Some touchpads' right button doesn't work under I2C mode, need support of clickpads Status in HWE Next Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: We need to add this support, otherwise some touchpads' right button doesn't work under I2C mode. commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch) HID: multitouch: add support of clickpads Touchpads that have only one button are called clickpads and should be advertised as such by the kernel. Signed-off-by: Benjamin Tissoires Tested-by: Jason Ekstrand Signed-off-by: Jiri Kosina To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449372] Re: Scsi kernel messages are being printed on separate lines.
** Description changed: + [Impact] + + * The move to dev_printk has sufficiently modified the scsi error + output that it confuses some automated log monitoring. This causes some + errors to not be definitively connected to a disk. Context does help, + but separate line context is difficult to automatedly parse. + + [Test Case] + + * Use a misbehaving disk that uses the scsi layer and look in kern.log + for what appears to be errantly wrapped lines in the scsi error output + + [Regression Potential] + + * Minimal both changes are clean cherry-picks. However as I do not + have any misbehaving discs I was only able to boot test this. I could + get fancy, but that would take more time. + + * Both patches are upstream starting in utopic and vivid respectively. + + [Other Info] + + * This only partially resolves the issue. That's because the fix (9e5ed2a5b3) that does solve this is very large, not a clean cherry-pick or easily backportable, and requires too many prerequisites and in my opinion not SRUable. That fix is available starting in v4.0. My guess is this should be available in wily. + + + - Original description + It seems to me that kernel errors, specifically those from the scsi driver, are being wrapped, which can confound automated log monitoring. Example from dmesg -- the lines I marked with X are being printed on separate lines where they previously weren't. [6461080.699629] sd 0:2:2:0: [sdc] Unhandled sense code [6461080.699646] sd 0:2:2:0: [sdc] [6461080.699650] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE X [6461080.699653] sd 0:2:2:0: [sdc] [6461080.699655] Sense Key : Medium Error [current] X [6461080.699661] sd 0:2:2:0: [sdc] [6461080.699663] Add. Sense: No additional sense information X [6461080.699667] sd 0:2:2:0: [sdc] CDB: [6461080.699669] Read(16): 88 00 00 00 00 00 0c 23 92 e0 00 00 00 08 00 00 X [6461080.699684] end_request: I/O error, dev sdc, sector 203657952 This appears to affect 3.2 to pre-4.0, and was sane in lucid. I'm certain it affects quantal to utopic, and vivid is partially mitigated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1449372 Title: Scsi kernel messages are being printed on separate lines. Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * The move to dev_printk has sufficiently modified the scsi error output that it confuses some automated log monitoring. This causes some errors to not be definitively connected to a disk. Context does help, but separate line context is difficult to automatedly parse. [Test Case] * Use a misbehaving disk that uses the scsi layer and look in kern.log for what appears to be errantly wrapped lines in the scsi error output [Regression Potential] * Minimal both changes are clean cherry-picks. However as I do not have any misbehaving discs I was only able to boot test this. I could get fancy, but that would take more time. * Both patches are upstream starting in utopic and vivid respectively. [Other Info] * This only partially resolves the issue. That's because the fix (9e5ed2a5b3) that does solve this is very large, not a clean cherry-pick or easily backportable, and requires too many prerequisites and in my opinion not SRUable. That fix is available starting in v4.0. My guess is this should be available in wily. - Original description It seems to me that kernel errors, specifically those from the scsi driver, are being wrapped, which can confound automated log monitoring. Example from dmesg -- the lines I marked with X are being printed on separate lines where they previously weren't. [6461080.699629] sd 0:2:2:0: [sdc] Unhandled sense code [6461080.699646] sd 0:2:2:0: [sdc] [6461080.699650] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE X [6461080.699653] sd 0:2:2:0: [sdc] [6461080.699655] Sense Key : Medium Error [current] X [6461080.699661] sd 0:2:2:0: [sdc] [6461080.699663] Add. Sense: No additional sense information X [6461080.699667] sd 0:2:2:0: [sdc] CDB: [6461080.699669] Read(16): 88 00 00 00 00 00 0c 23 92 e0 00 00 00 08 00 00 X [6461080.699684] end_request: I/O error, dev sdc, sector 203657952 This appears to affect 3.2 to pre-4.0, and was sane in lucid. I'm certain it affects quantal to utopic, and vivid is partially mitigated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1449372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462180] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: 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/1462180 Title: Bad page map / bad pte Status in linux package in Ubuntu: Confirmed Bug description: I have received very similar bugs on 3.13.0-53, 3.13-0.52, 3.13.0-51 and 3.13.0-49. I will be falling back to 3.13.0-45, which is the last kernel where I believe I didn't have this problem. 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 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Thu Jun 4 23:21:23 2015 HibernationDevice: RESUME=UUID=b170f305-49ff-4e37-b417-1a977a8dc002 InstallationDate: Installed on 2014-06-06 (363 days ago) InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530 IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-49-generic root=UUID=3c298b14-cd0f-4d75-a2ca-c79623676014 ro crashkernel=384M-2G:64M,2G-:128M quiet splash crashkernel=384M-:128M 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-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: 07/08/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7c dmi.board.name: GA-MA790GP-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790GP-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462180] [NEW] Bad page map / bad pte
Public bug reported: I have received very similar bugs on 3.13.0-53, 3.13-0.52, 3.13.0-51 and 3.13.0-49. I will be falling back to 3.13.0-45, which is the last kernel where I believe I didn't have this problem. 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 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Thu Jun 4 23:21:23 2015 HibernationDevice: RESUME=UUID=b170f305-49ff-4e37-b417-1a977a8dc002 InstallationDate: Installed on 2014-06-06 (363 days ago) InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530 IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-49-generic root=UUID=3c298b14-cd0f-4d75-a2ca-c79623676014 ro crashkernel=384M-2G:64M,2G-:128M quiet splash crashkernel=384M-:128M 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-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: 07/08/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7c dmi.board.name: GA-MA790GP-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790GP-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug rebecca third-party-packages 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/1462180 Title: Bad page map / bad pte Status in linux package in Ubuntu: Confirmed Bug description: I have received very similar bugs on 3.13.0-53, 3.13-0.52, 3.13.0-51 and 3.13.0-49. I will be falling back to 3.13.0-45, which is the last kernel where I believe I didn't have this problem. 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 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Thu Jun 4 23:21:23 2015 HibernationDevice: RESUME=UUID=b170f305-49ff-4e37-b417-1a977a8dc002 InstallationDate: Installed on 2014-06-06 (363 days ago) InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530 IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-49-generic root=UUID=3c298b14-cd0f-4d75-a2ca-c79623676014 ro crashkernel=384M-2G:64M,2G-:128M quiet splash crashkernel=384M-:128M 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-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: 07/08/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7c dmi.board.name: GA-MA790GP-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790GP-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscr
[Kernel-packages] [Bug 1440409] Re: can't write in usb stick
[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/1440409 Title: can't write in usb stick Status in linux package in Ubuntu: Expired Bug description: after update of my Ubuntu 14.04.2 LTS (kubuntu) all USB sticks are mounted as RO. All are formatted in FAT32 e did work until yesterday (before upgrade) Tried different solutions (chomod etc.) but none works. Big problem Thanks W --- ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vuk1554 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=4a6bbc02-cc9a-4430-ae70-7a094e91d6b3 InstallationDate: Installed on 2015-03-10 (26 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. X200MA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=074a73c7-4823-49de-9d3b-15fe65efbb0a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.16.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200MA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200MA 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.:bvrX200MA.302:bd01/21/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X200MA 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/1440409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440344] Re: Intel 7260 AC rev 6 - Will not associate unless directly under AP
[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/1440344 Title: Intel 7260 AC rev 6 - Will not associate unless directly under AP Status in linux package in Ubuntu: Expired Bug description: Below is a copy of the wireless script, and I have tried a bunch of things to get this to work and it appears that it can barely pick up any APs that I know that are broadcasting. My Personal home AP Dacanez will work, only if I am 6 feet from it. inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:111 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) # iwconfig ## eth0 no wireless extensions. vmnet1no wireless extensions. vmnet8no wireless extensions. lono wireless extensions. wlan0 IEEE 802.11abgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on # route # Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.10.10.0.0.0 UG0 00 eth0 172.16.251.00.0.0.0 255.255.255.0 U 0 00 vmnet1 192.168.10.00.0.0.0 255.255.255.0 U 1 00 eth0 192.168.207.0 0.0.0.0 255.255.255.0 U 0 00 vmnet8 # resolv.conf ### nameserver 127.0.1.1 search TEW-653AP # nm-tool ### NetworkManager Tool State: connected (global) - Device: eth0 [Wired connection 1] --- Type: Wired Driver:asix State: connected Default: yes HW Address: Capabilities: Carrier Detect: yes Speed: 100 Mb/s Wired Properties Carrier: on IPv4 Settings: Address: 192.168.10.108 Prefix: 24 (255.255.255.0) Gateway: 192.168.10.1 DNS: 68.87.77.130 - Device: Type: Bluetooth Driver:bluez State: disconnected Default: no Capabilities: - Device: wlan0 Type: 802.11 WiFi Driver:iwlwifi State: disconnected Default: no HW Address: Capabilities: Wireless Properties WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Access Points Dacanez: Infra, , Freq 2462 MHz, Rate 54 Mb/s, Strength 20 WPA # NetworkManager.state ## [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true # NetworkManager.conf ### [main] plugins=ifupdown,keyfile,ofono dns=dnsmasq [ifupdown] managed=false # NetworkManager profiles ### [[/etc/NetworkManager/system-connections/Orange-Guest-Internet 1]] (600 root) [connection] id=Orange-Guest-Internet 1 | type=802-11-wireless [802-11-wireless] ssid=Orange-Guest-Internet | mac-address= [ipv4] method=auto [ipv6] method=auto [[/etc/NetworkManager/system-connections/Orange-Guest-Internet 2]] (600 root) [connection] id=Orange-Guest-Internet 2 | type=802-11-wireless [802-11-wireless] ssid=Orange-Guest-Internet | mac-address= [ipv4] method=auto [ipv6] method=auto [[/etc/NetworkManager/system-connections/DIRECT-roku-CA0F13]] (600 root) [connection] id=DIRECT-roku-CA0F13 | type=802-11-wireless [802-11-wireless] ssid=DIRECT-roku-CA0F13 | mac-address= [ipv4] method=auto [ipv6] method=auto [[/etc/NetworkManager/system-connections/Orange-Guest-Internet]] (600 root) [connection] id=Orange-Guest-Internet | type=802-11-wireless [802-11-wireless] ssid=Orange-Guest-Internet | mac-address= [ipv4] method=auto [ipv6] method=auto [[/etc/NetworkManager/system-connec
[Kernel-packages] [Bug 1440298] Re: Excessive NAK Bailouts flooding logs
[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/1440298 Title: Excessive NAK Bailouts flooding logs Status in linux package in Ubuntu: Expired Bug description: I decided to try fglrx drivers when an update resulted in very choppy flash video when connected to second monitor via displayport. Upon reverting back through the Additional Drivers utility, I promptly discovered my video was very choppy and had a lot of defects -- UI was even notably lagged. As I attempted to gather info to address the issue, I realized the logs had been overtaken with these duplicate entries every 30-90sec. Not only do these entries confound other issues but they don't seem to specify anything particular. Searches for a solution were fruitless, mostly just turning up suggestions to recompile/reinstall kernel or video drivers but no insight into what the error actually means. After a day or so of reinstalling and reconfiguring various Xorg deps I've finally managed to wrestle my Unity back to a usable state but the log errors are still prevalent and I don't want to risk losing full compiz/unity support by blindly tinkering around further to resolve this issue. Any assistance would be very helpful ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-34-generic 3.16.0-34.45 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic i686 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lektronx 3085 F pulseaudio /dev/snd/controlC0: lektronx 3085 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 4 01:18:32 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-07 (27 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) MachineType: Acer Aspire V5-122P ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-34-generic root=/dev/mapper/ubuntu--vg-root ro vesafb.invalid=1 nopat radeon.dpm=1 RelatedPackageVersions: linux-restricted-modules-3.16.0-34-generic N/A linux-backports-modules-3.16.0-34-generic N/A linux-firmware 1.138.1 SourcePackage: linux SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire V5-122P dmi.board.vendor: Acer dmi.board.version: V2.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd05/10/2013:svnAcer:pnAspireV5-122P:pvrV2.04:rvnAcer:rnAspireV5-122P:rvrV2.04:cvnAcer:ct10:cvrV2.04: dmi.product.name: Aspire V5-122P dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440516] Re: sdhci.c:1013 sdhci_send_command+0x5d1/0xda0 [sdhci]()
[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/1440516 Title: sdhci.c:1013 sdhci_send_command+0x5d1/0xda0 [sdhci]() Status in linux package in Ubuntu: Expired Bug description: Just a warning, but maybe to useful to report what dmesg is telling me: [ 4653.114802] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock [ 4653.116957] [ cut here ] [ 4653.116995] WARNING: CPU: 0 PID: 2196 at /build/buildd/linux-3.19.0/drivers/mmc/host/sdhci.c:1013 sdhci_send_command+0x5d1/0xda0 [sdhci]() [ 4653.116998] Modules linked in: rfcomm bnep nls_iso8859_1 hid_generic btusb bluetooth hp_wmi sparse_keymap joydev intel_rapl intel_soc_dts_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd serio_raw uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev usbhid media arc4 snd_hda_codec_hdmi rtl8723be btcoexist rtl8723_common rtl_pci rtlwifi snd_hda_codec_realtek mac80211 snd_hda_codec_generic rtsx_pci_ms snd_intel_sst_acpi i915 snd_intel_sst_core memstick cfg80211 snd_soc_sst_mfld_platform drm_kms_helper drm snd_hda_intel snd_seq_midi snd_hda_controller snd_seq_midi_event snd_hda_codec lpc_ich snd_hwdep shpchp i2c_algo_bit mei_txe mei snd_soc_rt5640 snd_soc_rl6231 iosf_mbi snd_soc_core wmi snd_compress snd_rawmidi snd_pcm_dmaengine [ 4653.117048] snd_pcm hp_wireless video dw_dmac snd_seq dw_dmac_core snd_seq_device int3400_thermal int3403_thermal acpi_thermal_rel processor_thermal_device snd_timer intel_smartconnect i2c_hid snd hid i2c_designware_platform i2c_designware_core rfkill_gpio soundcore snd_soc_sst_acpi pwm_lpss_platform pwm_lpss spi_pxa2xx_platform 8250_dw mac_hid parport_pc ppdev lp parport autofs4 mmc_block rtsx_pci_sdmmc psmouse rtsx_pci sdhci_acpi sdhci [ 4653.117080] CPU: 0 PID: 2196 Comm: Chrome_ChildIOT Not tainted 3.19.0-12-generic #12-Ubuntu [ 4653.117083] Hardware name: Hewlett-Packard HP Stream Notebook PC 13/802A, BIOS F.05 11/28/2014 [ 4653.117086] c0184460 880076c03ca8 817c2175 0007 [ 4653.117091] 880076c03ce8 8107595a 880043e1 [ 4653.117095] 0001 0002 88007005da80 880071b34500 [ 4653.117100] Call Trace: [ 4653.117103][] dump_stack+0x45/0x57 [ 4653.117119] [] warn_slowpath_common+0x8a/0xc0 [ 4653.117123] [] warn_slowpath_null+0x1a/0x20 [ 4653.117133] [] sdhci_send_command+0x5d1/0xda0 [sdhci] [ 4653.117140] [] ? delay_tsc+0x3b/0x80 [ 4653.117144] [] ? __const_udelay+0x2b/0x30 [ 4653.117154] [] ? sdhci_reset+0x60/0xd0 [sdhci] [ 4653.117163] [] sdhci_finish_data+0x115/0x3c0 [sdhci] [ 4653.117170] [] ? intel_pstate_timer_func+0x321/0x3c0 [ 4653.117180] [] sdhci_irq+0x42b/0x929 [sdhci] [ 4653.117185] [] ? show_no_turbo+0x90/0x90 [ 4653.117190] [] handle_irq_event_percpu+0x77/0x1a0 [ 4653.117195] [] handle_irq_event+0x41/0x70 [ 4653.117200] [] handle_fasteoi_irq+0x86/0x140 [ 4653.117205] [] handle_irq+0x22/0x40 [ 4653.117210] [] do_IRQ+0x4f/0xf0 [ 4653.117215] [] common_interrupt+0x6d/0x6d [ 4653.117217][] ? system_call_fastpath+0x16/0x1b [ 4653.117225] ---[ end trace 25ab47a2ddd6fced ]--- [ 4653.117247] mmc0: Got data interrupt 0x0002 even though no data operation was in progress. [ 4653.119317] mmcblk0: error -110 sending stop command, original cmd response 0x0, card status 0x400900 [ 4653.119322] mmcblk0: error -84 transferring data, sector 39229736, nr 8, cmd response 0x0, card status 0x0 [ 4653.119327] mmcblk0: retrying using single block read ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-12-generic 3.19.0-12.12 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 1576 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 5 14:13:35 2015 HibernationDevice: RESUME=UUID=1cce7297-b185-4592-a4a0-dfdc069ad5a1 InstallationDate: Installed on 2015-02-03 (60 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150203) MachineType: Hewlett-Packard HP Stream Notebook PC 13 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=07d60846-8d52-4911-b233-7e5b8611e217 ro quiet splash memory_corruption_check=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-12-generic N/A linux-backports-modules-3.19.0-12-generic N/A linux-firmware
[Kernel-packages] [Bug 1462175] Re: CVE-2015-4170
CVE-2015-4170 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: Ne
[Kernel-packages] [Bug 1462175] [NEW] CVE-2015-4170
*** This bug is a security vulnerability *** Public security bug reported: [vulnerability in the kernel tty subsystem] Break-Fix: - 4898e640caf03fdbaf2122d5a33949bf3e4a5b34 Break-Fix: - cf872776fc84128bb779ce2b83a37c884c3203ae ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Sta
[Kernel-packages] [Bug 1462173] Re: CVE-2015-4167
CVE-2015-4167 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: Ne
[Kernel-packages] [Bug 1462173] [NEW] CVE-2015-4167
*** This bug is a security vulnerability *** Public security bug reported: [fs: udf kernel oops] Break-Fix: - 23b133bdc452aa441fcb9b82cbf6dd05cfd342d0 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Me
[Kernel-packages] [Bug 1462170] Re: CVE-2015-1805
CVE-2015-1805 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: Ne
[Kernel-packages] [Bug 1462170] [NEW] CVE-2015-1805
*** This bug is a security vulnerability *** Public security bug reported: A flaw was found in the way pipe_iov_copy_from_user() and pipe_iov_copy_to_user() functions handled iovecs remaining len accounting on failed atomic access. An unprivileged local user could this flaw to crash the system or, potentially, escalate their privileges on the system. Break-Fix: - f0d1bec9d58d4c038d0ac958c9af82be6eb18045 Break-Fix: - 637b58c2887e5e57850865839cc75f59184b23d1 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (
[Kernel-packages] [Bug 1462169] Re: CVE-2014-9731
CVE-2014-9731 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: Ne
[Kernel-packages] [Bug 1462169] [NEW] CVE-2014-9731
*** This bug is a security vulnerability *** Public security bug reported: [udf: information leakage when reading symlink] Break-Fix: - 0e5cc9a40ada6046e6bc3bdfcd0c0d7e4b706b14 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu T
[Kernel-packages] [Bug 1462167] Re: CVE-2014-9730
CVE-2014-9730 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: Ne
[Kernel-packages] [Bug 1462167] [NEW] CVE-2014-9730
*** This bug is a security vulnerability *** Public security bug reported: [properly ignore component length for component types that do not use it] Break-Fix: - e237ec37ec154564f8690c5bd1795339955eeef9 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects
[Kernel-packages] [Bug 1462165] Re: CVE-2014-9729
CVE-2014-9729 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: Ne
[Kernel-packages] [Bug 1462165] [NEW] CVE-2014-9729
*** This bug is a security vulnerability *** Public security bug reported: [iinfo->i_lenAlloc != inode->i_size] Break-Fix: - e159332b9af4b04d882dbcfe1bb0117f0a6d4b58 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty)
[Kernel-packages] [Bug 1462164] Re: CVE-2014-9728
CVE-2014-9728 ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Utopic) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: Ne
[Kernel-packages] [Bug 1462164] [NEW] CVE-2014-9728
*** This bug is a security vulnerability *** Public security bug reported: A UDF filesystem image with malicious lengths specified in multiple datastructures could cause crashes or other undesired behaviours. Break-Fix: - e159332b9af4b04d882dbcfe1bb0117f0a6d4b58 Break-Fix: - e237ec37ec154564f8690c5bd1795339955eeef9 Break-Fix: - a1d47b262952a45aae62bd49cfaf33dd76c11a2c ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu) Importance: Medium Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu) Importance: Medium Status: New ** Affects: linux-manta (Ubuntu) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (
[Kernel-packages] [Bug 1446724] Re: server is stable under older kernel (3.2.0-29.46), but crashes under newer kernels
** 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/1446724 Title: server is stable under older kernel (3.2.0-29.46), but crashes under newer kernels Status in linux package in Ubuntu: Incomplete Bug description: My PC is stable running Ubuntu Server 12.04.5 LTS using the old kernel 3.2.0-29.46. But it crashes whenever I tried to update the kernel to 3.2.0-65.99 or higher (including 14.04.2 LTS). So somewhere between 3.2.0-29.46 and 3.2.0-65.99, changes to the kernel caused my PC to crash (note: I have not tried kernels older than 3.2.0-65.99, so I don't know the exact version that started to cause the crash). I think this is likely a hardware compatibility issue since I could not find any system logs regarding the crashes. My PC is very old (Compaq Evo D510 SFF/07E4h, BIOS 68602 v2.14 08/15/2002), so I am not sure if this bug is worth troubleshooting. In the meantime, I am happy with the performance of my PC running 3.2.0-29.46. But if anyone is interested in troubleshooting this bug, please let me know. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-32-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3262 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981A at irq 17' Mixer name : 'Analog Devices AD1981A' Components : 'AC97a:41445372' Controls : 26 Simple ctrls : 17 CasperVersion: 1.315.1 DistroRelease: Ubuntu 12.04 IwConfig: lono wireless extensions. eth0 no wireless extensions. LiveMediaBuild: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) Lsusb: Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Compaq Evo D510 SFF MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid initrd=/casper/initrd.lz quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.79.16 RfKill: Tags: precise running-unity Uname: Linux 3.13.0-32-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/15/2002 dmi.bios.vendor: Compaq dmi.bios.version: 686O2 v2.14 dmi.board.name: 07E4h dmi.board.vendor: Compaq dmi.chassis.type: 15 dmi.chassis.vendor: Compaq dmi.modalias: dmi:bvnCompaq:bvr686O2v2.14:bd08/15/2002:svnCompaq:pnEvoD510SFF:pvr:rvnCompaq:rn07E4h:rvr:cvnCompaq:ct15:cvr: dmi.product.name: Evo D510 SFF dmi.sys.vendor: Compaq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458569] Re: System freezes randomly
Carl Englund, could you please test the latest mainline kernel (4.1-rc6) and advise to the results? ** Tags removed: kernel-bug-exists-upstream-4.1.0-040100rc5 ** Tags added: kernel-bug-exists-upstream-4.1-rc5 ** 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/1458569 Title: System freezes randomly Status in linux package in Ubuntu: Incomplete Bug description: After 10 min or so, or an hour. Workaround seems to be locking the CPU freq to something. I'm guessing there might be a bug in the powernow-k8 driver that exhibits itself in systems with the XPRESS 200M CPU chipset. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diskdoc1202 F pulseaudio CurrentDesktop: XFCE Date: Mon May 25 16:40:11 2015 HibernationDevice: RESUME=UUID=689195fb-b850-4125-a463-767853093c6a InstallationDate: Installed on 2015-05-23 (2 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard HP Compaq nx6125 (PY416EA#AK8) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=f4a074bf-eb4a-4cda-8a5a-561f66420476 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DTT Ver. F.07 dmi.board.name: 308B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 45.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DTTVer.F.07:bd07/01/2005:svnHewlett-Packard:pnHPCompaqnx6125(PY416EA#AK8):pvrF.07:rvnHewlett-Packard:rn308B:rvrKBCVersion45.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx6125 (PY416EA#AK8) dmi.product.version: F.07 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1461320] Re: first resume fails after suspend
rob loranger, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: needs-bisect regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1461320 Title: first resume fails after suspend Status in linux package in Ubuntu: Incomplete Bug description: Ever since I upgraded from 14.04 through to 15.04 I have had an issue resuming from suspend. The login pops up for a second and then the computer suspends again. Waking a second time resume is successful. With kernel 3.13.0 wifi was typically 'broken' upon resume with the only remedy being to select the network from the connect to hidden wireless network dialogue. no networks were visible in the network tray menu. With kernel 4.1.0 rc2 the wifi appears to resume normally but the double wake is still required. I will attach more info after i restart with the 3.13.0 kernel --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robbie 2556 F pulseaudio /dev/snd/controlC0: robbie 2556 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-03 (272 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard p6706f Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 RelatedPackageVersions: linux-restricted-modules-3.13.0-48-generic N/A linux-backports-modules-3.13.0-48-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.13.0-48-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo www-data _MarkForUpload: True dmi.bios.date: 12/28/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.11 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: MXX1020D7B dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6706f dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460088] Re: [Asus Zenbook Pro UX501JW] Backlight control via hotkeys does not work
ishbalai, please do not adjust the Status from Triaged. For more on this, please see https://wiki.ubuntu.com/Bugs/Status . ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460088 Title: [Asus Zenbook Pro UX501JW] Backlight control via hotkeys does not work Status in linux package in Ubuntu: Triaged Bug description: When using the default open source drivers, backlight control does not work via keyboard hotkeys on Asus Zenbook Pro UX501JW. WORKAROUND: The backlight can be manually set while running on the integrated intel graphics (not with hotkeys). --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2154 F pulseaudio /dev/snd/controlC0: ubuntu 2154 F pulseaudio CasperVersion: 1.360 DistroRelease: Ubuntu 15.04 LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: ASUSTeK COMPUTER INC. N501JW Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash --- ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 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-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/14/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501JW.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501JW 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.:bvrN501JW.203:bd01/14/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N501JW 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/1460088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460313] Re: webcam indicator LED remains lit after resume from suspend
** Tags added: cherry-pick ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460313 Title: webcam indicator LED remains lit after resume from suspend Status in linux package in Ubuntu: Triaged Bug description: After resuming from suspend the webcam indicator light remains on, however the webcam is not on. Opening Cheese and closing Cheese results in the indicator light turning off. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hans109h 1278 F pulseaudio CurrentDesktop: GNOME Date: Sat May 30 10:34:29 2015 HibernationDevice: RESUME=UUID=851878e8-669f-4a9d-806a-0b4ba86a929a InstallationDate: Installed on 2015-04-29 (31 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: ASUSTeK Computer Inc. K60IJ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=c5445ede-5f15-457d-8605-193f57ad6688 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K60IJ 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.:bvr206:bd12/03/2009:svnASUSTeKComputerInc.:pnK60IJ:pvr1.0:rvnASUSTeKComputerInc.:rnK60IJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K60IJ 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/1460313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1459934] Re: Support bluetooth device 0cf3:e006
** Changed in: hwe-next Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1459934 Title: Support bluetooth device 0cf3:e006 Status in HWE Next Project: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Fix Committed Bug description: 0cf3:e006 is one of the ath3k devices. One commit needs to be cherry-picked for supporting it. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ca79f232054abd079648fdb4400c71a1310f7bc8 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1459934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1459937] Re: Support bluetooth device 0cf3:e007
** Changed in: hwe-next Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1459937 Title: Support bluetooth device 0cf3:e007 Status in HWE Next Project: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: Fix Committed Bug description: The firmware of this device is loaded by a new mechanism other than ath3k. At least these commits are required: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ace31982585a323afb194f56b9e0486f7bc6570c https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3267c884cefa86c6d48c4d7c5571c20435271ecf https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf906b3db3c2b4f5d4db1db5f35796629c531ac4 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2054111b107d9449393d96dce6b66731bbfea9ad To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1459937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1461320] Re: first resume fails after suspend
i don't think it's the kernel after all. i just tested the previous 3.13.0-48 kernel and the issue is still present. any ideas on what to check? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1461320 Title: first resume fails after suspend Status in linux package in Ubuntu: Confirmed Bug description: Ever since I upgraded from 14.04 through to 15.04 I have had an issue resuming from suspend. The login pops up for a second and then the computer suspends again. Waking a second time resume is successful. With kernel 3.13.0 wifi was typically 'broken' upon resume with the only remedy being to select the network from the connect to hidden wireless network dialogue. no networks were visible in the network tray menu. With kernel 4.1.0 rc2 the wifi appears to resume normally but the double wake is still required. I will attach more info after i restart with the 3.13.0 kernel --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robbie 2556 F pulseaudio /dev/snd/controlC0: robbie 2556 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-03 (272 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard p6706f Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-48-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 RelatedPackageVersions: linux-restricted-modules-3.13.0-48-generic N/A linux-backports-modules-3.13.0-48-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.13.0-48-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-25 (38 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare saned scanner sudo www-data _MarkForUpload: True dmi.bios.date: 12/28/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.11 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: MXX1020D7B dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6706f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6706f dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416548] Re: IBM Power8 requires rootdelay= in order to boot
This was fixed in bug #1326199 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1416548 Title: IBM Power8 requires rootdelay= in order to boot Status in linux package in Ubuntu: Confirmed Bug description: ubuntu@P8:~$ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 After installing Ubuntu 14.04 onto an IBM Power8 using bare metal mode, the installation will not boot unless setting a rootdelay timeout as a kernel flag. The following error occurs at boot otherwise: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/ad097f75-53df-40dc-9660-2397ac629778 does not exist. Dropping to a shell! A setting of rootdelay=190 seems to work whereas 90 was not long enough. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.6 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Date: Fri Jan 30 16:11:28 2015 HibernationDevice: RESUME=UUID=f8fdf988-698a-424f-99ec-f1bcd83535fd InstallationDate: Installed on 2015-01-29 (1 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release ppc64el (20140416.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=ad097f75-53df-40dc-9660-2397ac629778 ro splash quiet rootdelay=190 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1459365] Re: Can't resume after hibernation
Arvin Razavi, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1459365/comments/23 regarding this being fixed with a BIOS update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1459365 Title: Can't resume after hibernation Status in linux package in Ubuntu: Invalid Bug description: Hi, Since I upgraded from 14.10 to 15.04 I can no longer resume after hibernation. Upon resuming all I see is a blank screen with a blinking underscore at the top left corner, which later freezes. Also I'm using Ubuntu Gnome. Description: Ubuntu 15.04 Release: 15.04 Regards, Arvin --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: arvin 1308 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=bd928b77-1bbc-4835-8697-26d8d6e0b76e InstallationDate: Installed on 2014-11-07 (201 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. XPS13 9333 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=9284c4b7-1cf2-44d1-b438-059d349f5193 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-18 (9 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1459365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1459367] Re: Realtek RTL8723BE wireless card drops connection in Linux kernel 3.19.0-18
Arnaud LE CAM, just to clarify, how long would you go without interruption before the WORKAROUND? >"Can I downgrade back to kernel 3.19.0-18 (setting ips and fwlps options to 0) >to keep a "regular" Ubuntu install ?" Feel free to test and advise if it changes anything. >"Should I do nothing else to help debugging ?" Please test the latest mainline kernel (now 4.1-rc6), with and without the WORKAROUND, and advise to the results. Also, does switching from 802.11n to g at the router change anything? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1459367 Title: Realtek RTL8723BE wireless card drops connection in Linux kernel 3.19.0-18 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I loose my connection randomly (HP laptop, model 15-r207nf) with Realtek RTL8723BE wireless card. Linux 3.19.0-18-generic on Xubuntu 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: arnaud 1415 F...m pulseaudio /dev/snd/controlC0: arnaud 1409 F panel-17-mixer arnaud 1415 F pulseaudio CurrentDesktop: XFCE Date: Wed May 27 19:46:19 2015 HibernationDevice: RESUME=UUID=677c116e-29ca-4442-a248-9302170fbb6b InstallationDate: Installed on 2015-04-18 (38 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=3c2695c5-1341-4096-966f-ad24d315f451 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2213 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.47 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.32:bd10/28/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2213:rvr57.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1459367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads
The touchpad of Dell XPS 13 (2015) in I2C mode never works with trusty 3.13 kernel. However the touchpad of Dell XPS 13 (2015) in PS/2 mode does work with trusty 3.13 kernel by default. I need to use osi_acpi="Windows 2013" to make it function in I2C mode with trusty 3.13 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456881 Title: Some touchpads' right button doesn't work under I2C mode, need support of clickpads Status in HWE Next Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: We need to add this support, otherwise some touchpads' right button doesn't work under I2C mode. commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch) HID: multitouch: add support of clickpads Touchpads that have only one button are called clickpads and should be advertised as such by the kernel. Signed-off-by: Benjamin Tissoires Tested-by: Jason Ekstrand Signed-off-by: Jiri Kosina To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438039] Re: Ubuntu14.04.1 kernel panics with enic driver throwing a NULL Pointer exception
** Changed in: linux (Ubuntu Vivid) Importance: Undecided => High ** Changed in: linux (Ubuntu Utopic) Importance: Undecided => High ** Changed in: linux (Ubuntu Trusty) 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/1438039 Title: Ubuntu14.04.1 kernel panics with enic driver throwing a NULL Pointer exception Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Status in linux source package in Vivid: Fix Released Bug description: Steps to reproduce the bug: 1. Install Ubuntu 14.04.1 on the Cisco M-series server. 2. Run reboot test, OS will come up and go for graceful reboot continuously. 3. I am seeing kernel panic in 3 out of 4 Ubuntu machines . Don't know after how many iterations of reboot it happened. I checked the server 6 hours after starting the reboot test. 4. Don't know whether this panic is happening while the OS was booting or while going for reboot. The bug has been root caused to the enic driver and a fix has been posted upstream. Please find below the details of the patch submitted upstream. 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 enic: do tx cleanup in napi poll. This bug is submitted for the patch to be pulled in from upstream to Ubuntu's releases. === break-fix: - 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447373] Re: CVE-2015-3339
** Description changed: - [chown() was racy relative to execve()] + Race condition in the prepare_binprm function in fs/exec.c in the Linux + kernel before 3.19.6 allows local users to gain privileges by executing + a setuid program at a time instant when a chown to root is in progress, + and the ownership is changed but the setuid bit is not yet stripped. Break-Fix: - 8b01fc86b9f425899f8a3a8fc1c47d73c2c20543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1447373 Title: CVE-2015-3339 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Invalid Statu
[Kernel-packages] [Bug 1441103] Re: CVE-2015-2922
** Description changed: - [IPv6 Hop limit lowering via RA messages] + The ndisc_router_discovery function in net/ipv6/ndisc.c in the Neighbor + Discovery (ND) protocol implementation in the IPv6 stack in the Linux + kernel before 3.19.6 allows remote attackers to reconfigure a hop-limit + setting via a small hop_limit value in a Router Advertisement (RA) + message. Break-Fix: - 6fd99094de2b83d1d4c8457f2c83483b2828e75a -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1441103 Title: CVE-2015-2922 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New Status in linux-mvl-dove source package in Utopic: Inva
[Kernel-packages] [Bug 1440234] Re: CVE-2015-2830
** Description changed: - Linux mishandles int80 fork from 64-bit tasks + arch/x86/kernel/entry_64.S in the Linux kernel before 3.19.2 does not + prevent the TS_COMPAT flag from reaching a user-mode task, which might + allow local users to bypass the seccomp or audit protection mechanism + via a crafted application that uses the (1) fork or (2) close system + call, as demonstrated by an attack against seccomp before 3.16. Break-Fix: - 956421fbb74c3a6261903f3836c0740187cf038b -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1440234 Title: CVE-2015-2830 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source package in Utopic: New S
[Kernel-packages] [Bug 1442080] Re: CVE-2014-9715
** Description changed: - [DoS -- OOPS NULL pointer dereference in nf_nat_setup_info+0x471] + include/net/netfilter/nf_conntrack_extend.h in the netfilter subsystem + in the Linux kernel before 3.14.5 uses an insufficiently large data type + for certain extension data, which allows local users to cause a denial + of service (NULL pointer dereference and OOPS) via outbound network + traffic that triggers extension loading, as demonstrated by configuring + a PPTP tunnel in a NAT environment. Break-Fix: 5b423f6a40a0327f9d40bc8b97ce9be266f74368 223b02d923ecd7c84cf9780bb3686f455d279279 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1442080 Title: CVE-2014-9715 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Invalid Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: I
[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc
Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ Ø澚ŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ ; ¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ Iª¿šŸÐ [H[J[1;1H[0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.16.0-39-generic (root@gloin) (gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) ) #53~lp1445195 SMP Tue May 26 19:27:10 UTC 2015 (Ubuntu 3.16.0-39.53~lp1445195-generic 3.16.7-ckt11) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-39-generic root=UUID=95966cd1-2fc3-498d-b72d-721997da6608 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 nomdmonddf nomdmonisw [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x1ffe] usable [0.00] BIOS-e820: [mem 0x1fff-0x1fffefff] ACPI data [0.00] BIOS-e820: [mem 0x1000-0x1fff] ACPI NVS [0.00] BIOS-e820: [mem 0x0001-0x000edfff] usable [0.00] BIOS-e820: [mem 0x000ee020-0x000fdfff] usable [0.00] BIOS-e820: [mem 0x0010-0x001d001f] usable [0.00] bootconsole [earlyser0] enabled [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.3 present. [0.00] Hypervisor detected: Microsoft HyperV [0.00] HyperV: features 0xe7f, hints 0x2c [0.00] HyperV: LAPIC Timer Frequency: 0xc3500 [0.00] AGP: No AGP bridge found [0.00] e820: last_pfn = 0x1d00200 max_arch_pfn = 0x4 [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] e820: last_pfn = 0x1fff0 max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [880ff780] [0.00] Scanning 1 areas for low memory corruption [0.00] init_memory_mapping: [mem 0x-0x000f] [0.00] init_memory_mapping: [mem 0x1d-0x1d001f] [0.00] init_memory_mapping: [mem 0x1cfc00-0x1c] [0.00] init_memory_mapping: [mem 0x1c8000-0x1cfbff] [0.00] init_memory_mapping: [mem 0x10-0x1c7fff] [0.00] init_memory_mapping: [mem 0x0010-0x1ffe] [0.00] init_memory_mapping: [mem 0x1-0xedfff] [0.00] init_memory_mapping: [
[Kernel-packages] [Bug 1438501] Re: CVE-2014-9710
** Description changed: - [btrfs: non-atomic xattr replace operation] + The Btrfs implementation in the Linux kernel before 3.19 does not ensure + that the visible xattr state is consistent with a requested replacement, + which allows local users to bypass intended ACL settings and gain + privileges via standard filesystem operations (1) during an xattr- + replacement time window, related to a race condition, or (2) after an + xattr-replacement attempt that fails because the data does not fit. Break-Fix: - 5f5bc6b1e2d5a6f827bc860ef2dc5b6f365d1339 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1438501 Title: CVE-2014-9710 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-lts-vivid source package in Utopic: Invalid Status in linux-mako source package in Utopic: New Status in linux-manta source
[Kernel-packages] [Bug 1445195] Re: [Hyper-V] Kernel patches for storvsc
The Utopic kernel does not work for us, it crashes. Continuing with Vivid testing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1445195 Title: [Hyper-V] Kernel patches for storvsc Status in linux package in Ubuntu: Triaged Status in linux source package in Precise: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Utopic: Triaged Status in linux source package in Vivid: Triaged Status in linux source package in Wily: Triaged Bug description: Storage driver performance updates for vivid K. Y. Srinivasan (7): scsi: storvsc: Increase the ring buffer size scsi: storvsc: Size the queue depth based on the ringbuffer size scsi: storvsc: Always send on the selected outgoing channel scsi: storvsc: Retrieve information about the capability of the target scsi: storvsc: Fix a bug in copy_from_bounce_buffer() scsi: storvsc: Don't assume that the scatterlist is not chained scsi: storvsc: Set the tablesize based on the information given by the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1455105] Re: [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown on HP Proliant m400
Verified with both a trusty and vivid base. ** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1455105 Title: [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown on HP Proliant m400 Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Bug description: [Impact] Graceful shutdown from the ILO-CM does not work on Ubuntu 15.04 due to commit 1972c97db5b, but is fixed by commit b90f8f22ed8. [Test Case] Login to the iLO-CM and issue 'set node power off shutdown c<#>n<#>' Check the console to ensure the node is shutting down. [Regression Risk] This re-enables a gpio driver on arm64 that was enabled on older versions of the kernel and is enabled for arm in general currently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1455121] Re: [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the firmware spec
** Tags removed: verification-verified-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/1455121 Title: [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the firmware spec Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Bug description: [Impact] On reboot, initialization commands can timeout causing the mellanox card to not initialize on boot. [Test Case] Reboot the system many, many times (this issue is rare). [Regression Risk] The fix comes from upstream and was submitted by Mellanox to bring the driver in-line with the way their firmware works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1451593] Re: [SRU] Forward port XGene MSI-X driver to vivid
Verified with a trusty and vivid base. ** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1451593 Title: [SRU] Forward port XGene MSI-X driver to vivid Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Committed Bug description: [Impact] Without the MSI-X driver, network performance on the HP Proliant m400 will be degraded in vivid from what can be achieved in trusty and utopic. [Test Case] All commands work on the HP Proliant m400: 'lspci -v' should show 'MSI-X: Enable+' under the Mellanox entry. 'cat /proc/interrupts' will list 'xgene-msi' next to the eth# and mlx4... entries. [Regression Risk] This driver is self contained for the xgene1 platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1409133]
Probably a duplicate of bug 90508. Could you give the patch referenced there a try? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1409133 Title: Heavy black flickering with Intel graphics after VT switching from X to Mir Status in The Linux Kernel: Incomplete Status in Mir: Invalid Status in linux package in Ubuntu: Triaged Status in mir package in Ubuntu: Invalid Bug description: After running mir_demo_server on VT 1, when I switch to VT 7 then back to VT 1, the demo server really flickers black quite a lot (entire screen, pointer included). I'm not sure, but I also upgraded my kernel to 3.18.2-031802-generic at the same time, if it's because of that, please mark invalid. --- ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: william5932 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=f950febe-baf1-425c-8ab5-f4f43a86839b Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 3249CTO Package: mir ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash thinkpad_acpi.fan_control=Y vt.handoff=7 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Tags: vivid Uname: Linux 3.18.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip disk fuse kvm libvirtd lpadmin plugdev sambashare sbuild sudo video _MarkForUpload: True dmi.bios.date: 01/26/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET35WW (1.05 ) dmi.board.name: 3249CTO 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:bvr6QET35WW(1.05):bd01/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3249CTO dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1409133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410093/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410095/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410094/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410096/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410088/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438039] Re: Ubuntu14.04.1 kernel panics with enic driver throwing a NULL Pointer exception
I tried to perform a cherry-pick of 4cfe87853. However, it looks like it will also need the following commits backported or cherry-picked: 7c2ce6e b6e97c1 a145df2 8e09134 14747cd 4cfe8785 I'll try to build a test kernel with these commits, but it may be too many changes for an SRU. In the mean time, can you test the LTS-backport-vivid kernel for Trusty? This is the kernel that comes with 14.04.3. It can be install with: sudo apt-get install linux-generic-lts-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1438039 Title: Ubuntu14.04.1 kernel panics with enic driver throwing a NULL Pointer exception Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Status in linux source package in Vivid: Fix Released Bug description: Steps to reproduce the bug: 1. Install Ubuntu 14.04.1 on the Cisco M-series server. 2. Run reboot test, OS will come up and go for graceful reboot continuously. 3. I am seeing kernel panic in 3 out of 4 Ubuntu machines . Don't know after how many iterations of reboot it happened. I checked the server 6 hours after starting the reboot test. 4. Don't know whether this panic is happening while the OS was booting or while going for reboot. The bug has been root caused to the enic driver and a fix has been posted upstream. Please find below the details of the patch submitted upstream. 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 enic: do tx cleanup in napi poll. This bug is submitted for the patch to be pulled in from upstream to Ubuntu's releases. === break-fix: - 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410098/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410089/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410092/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] Re: kworker high cpu utilization
apport information ** Tags added: apport-collected vivid ** Description changed: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 + --- + ApportVersion: 2.17.2-0ubuntu1.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio + /dev/snd/controlC1: darla 2479 F pulseaudio + /dev/snd/controlC0: darla 2479 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 15.04 + HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 + InstallationDate: Installed on 2015-01-25 (130 days ago) + InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) + MachineType: Hewlett-Packard HP ENVY m6 Sleekbook + NonfreeKernelModules: fglrx + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-18-generic N/A + linux-backports-modules-3.19.0-18-generic N/A + linux-firmware 1.143.1 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: vivid + Uname: Linux 3.19.0-18-generic x86_64 + UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/15/2013 + dmi.bios.vendor: Insyde + dmi.bios.version: F.02 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 1995 + dmi.board.vendor: Hewlett-Packard + dmi.board.version: 04.20 + 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: + dmi.product.name: HP ENVY m6 Sleekbook + dmi.product.version: 0883100022305B0320100 + dmi.sys.vendor: Hewlett-Packard ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410087/+files/AlsaInfo.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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20
[Kernel-packages] [Bug 1462108] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410091/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410101/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410100/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410090/+files/IwConfig.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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410097/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1462108/+attachment/4410099/+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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 --- ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: darla 2479 F...m pulseaudio /dev/snd/controlC1: darla 2479 F pulseaudio /dev/snd/controlC0: darla 2479 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ac85efbe-0ab6-41b5-9397-9eaebaf2f6f8 InstallationDate: Installed on 2015-01-25 (130 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP ENVY m6 Sleekbook NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid Uname: Linux 3.19.0-18-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-05-03 (32 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1995 dmi.board.vendor: Hewlett-Packard dmi.board.version: 04.20 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.02:bd05/15/2013:svnHewlett-Packard:pnHPENVYm6Sleekbook:pvr0883100022305B0320100:rvnHewlett-Packard:rn1995:rvr04.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY m6 Sleekbook dmi.product.version: 0883100022305B0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458901] Re: linux: 3.2.0-85.122 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Description changed: This bug is for tracking the 3.2.0-85.122 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 26. May 2015 14:37 UTC kernel-stable-Prepare-package-end:Tuesday, 26. May 2015 20:06 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 26. May 2015 20:06 UTC kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 21:29 UTC - kernel-stable-phase:Verification & Testing - kernel-stable-phase-changed:Friday, 29. May 2015 23:00 UTC kernel-stable-Verification-testing-start:Friday, 29. May 2015 23:00 UTC kernel-stable-Certification-testing-start:Friday, 29. May 2015 23:00 UTC kernel-stable-Security-signoff-start:Friday, 29. May 2015 23:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Friday, 29. May 2015 23:00 UTC + kernel-stable-phase:Testing + kernel-stable-phase-changed:Thursday, 04. June 2015 21:00 UTC + kernel-stable-Verification-testing-end:Thursday, 04. June 2015 21:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458901 Title: linux: 3.2.0-85.122 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-85.122 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 26. May 2015 14:37 UTC kernel-stable-Prepare-package-end:Tuesday, 26. May 2015 20:06 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 26. May 2015 20:06 UTC kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 21:29 UTC kernel-stable-Verification-testing-start:Friday, 29. May 2015 23:00 UTC kernel-stable-Certification-testing-start:Friday, 29. May 2015 23:00 UTC kernel-stable-Security-signoff-start:Friday, 29. May 2015 23:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Friday, 29. May 2015 23:00 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Thursday, 04. June 2015 21:00 UTC kernel-stable-Verification-testing-end:Thursday, 04. June 2015 21:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1458901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460657] Re: possible infinite loop when parsing CDC headers
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1460657
Title:
possible infinite loop when parsing CDC headers
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Utopic:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Bug description:
Bug #1413992 's patch introduced a possible infinite loop.
commit 0d3bba0287d4e284c3ec7d3397e81eec920d5e7e
Author: Quentin Casasnovas
Date: Tue Apr 14 11:25:43 2015 +0200
cdc-acm: prevent infinite loop when parsing CDC headers.
Phil and I found out a problem with commit:
7e860a6e7aa6 ("cdc-acm: add sanity checks")
It added some sanity checks to ignore potential garbage in CDC headers but
also introduced a potential infinite loop. This can happen at the first
loop iteration (elength = 0 in that case) if the description isn't a
DT_CS_INTERFACE or later if 'buffer[0]' is zero.
It should also be noted that the wrong length was being added to 'buffer'
in case 'buffer[1]' was not a DT_CS_INTERFACE descriptor, since elength
was
assigned after that check in the loop.
A specially crafted USB device could be used to trigger this
infinite loop.
Fixes: 7e860a6e7aa6 ("cdc-acm: add sanity checks")
Signed-off-by: Phil Turnbull
Signed-off-by: Quentin Casasnovas
CC: Sergei Shtylyov
CC: Oliver Neukum
CC: Adam Lee
CC:
Signed-off-by: Greg Kroah-Hartman
===
break-fix: 7e860a6e7aa62b337a61110430cd633db5b0d2dd
0d3bba0287d4e284c3ec7d3397e81eec920d5e7e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438039] Re: Ubuntu14.04.1 kernel panics with enic driver throwing a NULL Pointer exception
** Changed in: linux (Ubuntu Trusty) Status: New => Confirmed ** Changed in: linux (Ubuntu Utopic) Status: New => Confirmed ** Changed in: linux (Ubuntu Vivid) Status: New => Fix Released ** Changed in: linux (Ubuntu) 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/1438039 Title: Ubuntu14.04.1 kernel panics with enic driver throwing a NULL Pointer exception Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Status in linux source package in Vivid: Fix Released Bug description: Steps to reproduce the bug: 1. Install Ubuntu 14.04.1 on the Cisco M-series server. 2. Run reboot test, OS will come up and go for graceful reboot continuously. 3. I am seeing kernel panic in 3 out of 4 Ubuntu machines . Don't know after how many iterations of reboot it happened. I checked the server 6 hours after starting the reboot test. 4. Don't know whether this panic is happening while the OS was booting or while going for reboot. The bug has been root caused to the enic driver and a fix has been posted upstream. Please find below the details of the patch submitted upstream. 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 enic: do tx cleanup in napi poll. This bug is submitted for the patch to be pulled in from upstream to Ubuntu's releases. === break-fix: - 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] Re: kworker high cpu utilization
Let me know what other information to post. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
*** This bug is a duplicate of bug 1338706 *** https://bugs.launchpad.net/bugs/1338706 ** Changed in: linux (Ubuntu Vivid) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Utopic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) Status in fstrim package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in fstrim source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in fstrim source package in Utopic: Invalid Status in linux source package in Utopic: Fix Committed Status in fstrim source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Bug description: Hi, after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the fstream command doesn't work anymore. Besides, there are a lot of file system errors and "bad sectors" reports. The problem is certainly caused by Samsung's firmware but I reported it as a bug because in Windows TRIM works normally after the upgrade. I have attached an image uploaded by a user who is experiencing the same problem. If you execute the command "sudo fstrim /" the console gets stuck. If you add that command in rc.local the boot is compromised. I really hope this problem could be solved. Thanks === break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1462108 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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] Re: kworker high cpu utilization
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+attachment/4410055/+files/lspci-vnvn.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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] Re: kworker high cpu utilization
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+attachment/4410056/+files/version.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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462108] [NEW] kworker high cpu utilization
Public bug reported: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1462108 Title: kworker high cpu utilization Status in linux package in Ubuntu: Incomplete Bug description: I upgraded to vivid 15.04 on my HP Sleekbook (AMD A10 CPU) and it runs very hot. Top shows kworker taking up 60-70% CPU immediately after rebooting and not launching any programs. top - 17:27:55 up 10 min, 3 users, load average: 2.93, 2.75, 1.51 Tasks: 205 total, 3 running, 202 sleeping, 0 stopped, 0 zombie %Cpu(s): 22.8 us, 35.5 sy, 0.0 ni, 39.5 id, 0.2 wa, 0.0 hi, 1.9 si, 0.0 st KiB Mem: 5233588 total, 4715036 used, 518552 free,56484 buffers KiB Swap: 5468156 total,0 used, 5468156 free. 689644 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 97 root 20 0 0 0 0 R 66.0 0.0 6:13.97 kworker/2:3 3512 darla 20 0 1020444 320036 61580 S 45.8 6.1 2:02.92 chrome 22 root 20 0 0 0 0 S 34.2 0.0 3:08.83 ksoftirqd/2 3493 darla 20 0 2868728 1.492g 39876 S 30.5 29.9 2:04.76 chrome 1033 root 20 0 351108 136976 90380 R 24.9 2.6 1:46.40 Xorg 3311 darla 20 0 1085248 205976 90288 S 17.6 3.9 1:26.52 chrome 2479 darla 9 -11 630432 10824 7760 S 6.3 0.2 0:13.21 pulseaudio 3342 darla 20 0 1109672 332000 135212 S 5.6 6.3 0:29.85 chrome 3467 darla 20 0 959564 184012 60188 S 3.0 3.5 0:21.64 chrome 77 root 20 0 0 0 0 S 1.7 0.0 0:08.37 kworker/1:1 2697 darla 20 0 388040 24652 18852 S 1.7 0.5 0:00.85 xfce4-term+ 3483 darla 20 0 1039356 209628 64692 S 1.7 4.0 0:23.44 chrome 3561 darla 20 0 879172 146972 64124 S 1.0 2.8 0:07.04 chrome 50 root 20 0 0 0 0 S 0.7 0.0 0:05.24 kworker/0:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1438039] Re: Ubuntu14.04.1 kernel panics with enic driver throwing a NULL Pointer exception
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Description changed: Steps to reproduce the bug: 1. Install Ubuntu 14.04.1 on the Cisco M-series server. 2. Run reboot test, OS will come up and go for graceful reboot continuously. - 3. I am seeing kernel panic in 3 out of 4 Ubuntu machines . Don't know after how many iterations of reboot it happened. I checked the server 6 hours after starting the reboot test. + 3. I am seeing kernel panic in 3 out of 4 Ubuntu machines . Don't know after how many iterations of reboot it happened. I checked the server 6 hours after starting the reboot test. 4. Don't know whether this panic is happening while the OS was booting or while going for reboot. The bug has been root caused to the enic driver and a fix has been posted upstream. Please find below the details of the patch submitted upstream. 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 enic: do tx cleanup in napi poll. This bug is submitted for the patch to be pulled in from upstream to Ubuntu's releases. + + === + break-fix: - 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 ** Tags added: kernel-bug-break-fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1438039 Title: Ubuntu14.04.1 kernel panics with enic driver throwing a NULL Pointer exception Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: New Status in linux source package in Utopic: New Status in linux source package in Vivid: New Bug description: Steps to reproduce the bug: 1. Install Ubuntu 14.04.1 on the Cisco M-series server. 2. Run reboot test, OS will come up and go for graceful reboot continuously. 3. I am seeing kernel panic in 3 out of 4 Ubuntu machines . Don't know after how many iterations of reboot it happened. I checked the server 6 hours after starting the reboot test. 4. Don't know whether this panic is happening while the OS was booting or while going for reboot. The bug has been root caused to the enic driver and a fix has been posted upstream. Please find below the details of the patch submitted upstream. 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 enic: do tx cleanup in napi poll. This bug is submitted for the patch to be pulled in from upstream to Ubuntu's releases. === break-fix: - 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1409133] Re: Heavy black flickering with Intel graphics after VT switching from X to Mir
** Changed in: linux 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/1409133 Title: Heavy black flickering with Intel graphics after VT switching from X to Mir Status in The Linux Kernel: Incomplete Status in Mir: Invalid Status in linux package in Ubuntu: Triaged Status in mir package in Ubuntu: Invalid Bug description: After running mir_demo_server on VT 1, when I switch to VT 7 then back to VT 1, the demo server really flickers black quite a lot (entire screen, pointer included). I'm not sure, but I also upgraded my kernel to 3.18.2-031802-generic at the same time, if it's because of that, please mark invalid. --- ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: william5932 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=f950febe-baf1-425c-8ab5-f4f43a86839b Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 3249CTO Package: mir ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash thinkpad_acpi.fan_control=Y vt.handoff=7 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 RelatedPackageVersions: linux-restricted-modules-3.18.0-9-generic N/A linux-backports-modules-3.18.0-9-generic N/A linux-firmware1.140 SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Tags: vivid Uname: Linux 3.18.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip disk fuse kvm libvirtd lpadmin plugdev sambashare sbuild sudo video _MarkForUpload: True dmi.bios.date: 01/26/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET35WW (1.05 ) dmi.board.name: 3249CTO 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:bvr6QET35WW(1.05):bd01/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3249CTO dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1409133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447367] Re: CVE-2015-3331
** Description changed: - [Buffer overruns in Linux kernel RFC4106 implementation using AESNI] + The __driver_rfc4106_decrypt function in arch/x86/crypto/aesni- + intel_glue.c in the Linux kernel before 3.19.3 does not properly + determine the memory locations used for encrypted data, which allows + context-dependent attackers to cause a denial of service (buffer + overflow and system crash) or possibly execute arbitrary code by + triggering a crypto API call, as demonstrated by use of a libkcapi test + program with an AF_ALG(aead) socket. Break-Fix: 0bd82f5f6355775fbaf7d3c664432ce1b862be1e ccfe8c3f7e52ae83155cb038753f4c75b774ca8a -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1447367 Title: CVE-2015-3331 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux source package in Precise: Fix Committed Status in linux-armadaxp source package in Precise: Fix Committed Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: New Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: New Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in
[Kernel-packages] [Bug 1439780] Re: [Hyper-V] Fiber Channel critical target error
This test kernel fixes the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1439780 Title: [Hyper-V] Fiber Channel critical target error Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: System details: Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu12) ) #11~lp1423343v201503311833 SMP Tue Mar 31 17:40:01 UTC 2015 (Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3) Ubuntu 3.19.0-11 Ubuntu Vivid 15.04 64bit custom kernel Platform: WS2012R2 Using a fiber channel disk partition ( dev/sde1 in this example) outputs the following error: [ 1307.744496] blk_update_request: critical target error, dev sde, sector 0 [ 1396.052488] blk_update_request: critical target error, dev sde, sector 0 [ 1456.216570] blk_update_request: critical target error, dev sde, sector 0 Creating a partition works, reading too, but first time writing it hangs for around 20 seconds and after a couple more writes the partition goes into read-only mode: #echo "test1" > test1.txt *hangs for 30 seconds* blk_update_request: critical target error, dev sde, sector 0 # echo "test2" > test2.txt blk_update_request: critical target error, dev sde, sector 289671192 Aborting journal on device sde1-8. EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted journal EXT4-fs (sde1): Remounting filesystem read-only # echo "test string" > sample.txt -bash: sample.txt: Read-only file system Dmesg log: [ 461.284362] blk_update_request: critical target error, dev sde, sector 0 [ 484.845659] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null) [ 548.988377] blk_update_request: critical target error, dev sde, sector 0 [ 609.216340] blk_update_request: critical target error, dev sde, sector 289671192 [ 609.221812] Aborting journal on device sde1-8. [ 612.237503] EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted journal [ 612.249529] EXT4-fs (sde1): Remounting filesystem read-only Additional info: cat /proc/version_signature Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439780/+subscriptions -- Mailing list: https://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 1440174] Re: Keyboard and Mouse don't work with latest Kernel
Hi, Yes, WiFi was also failing for me. The workaround solves the WiFi problem also. Good luck. -- Dr Joseph D. Wallach walla...@operamail.com On Wed, Jun 3, 2015, at 09:56 PM, sTiVo wrote: > You don't mention if WiFi was also failing for you. It is for me. Does > your workaround solve that as well? > > Sent from my iPhone > > > On Jun 3, 2015, at 4:41 PM, Dr JD Wallach wrote: > > > > Hi, > > I have found a workaround for this bug: > > Start the machine from scratch with all the USB devices plugged in. > > Wait for the Grub menu to show on the screen. > > Using the keyboard select Ubuntu as the operating system to load. > > Immediately after selecting the Ubuntu OS, disconnect the USB mouse (be > > it direct USB plug-in or remote). > > When the Ubuntu login screen comes up it will be possible to use the > > keyboard to enter the user-name and the password. > > Once the Ubuntu environment is established, reconnect the USB mouse., > > and use it > > normally. > > Problem solved, although a bit annoying. > > Hope this helps. > > > > -- > > Dr Joseph D. Wallach > > walla...@operamail.com > > > >> On Fri, May 29, 2015, at 12:44 PM, Steve Cohen wrote: > >> What, please, is the status of this bug? Is there a fix or candidate > >> fix in any newer version of the kernel? > >> > >> Since I signed on to this bug in early April, I have been looking for > >> some resolution to it. For awhile I was checking each new kernel > >> release to see if the bug was fixed. I have downgraded to 3.13.0-46, > >> the last version that works with my computer. The later releases can > >> not even be installed by the auto-installer. > >> > >> -- > >> You received this bug notification because you are subscribed to the bug > >> report. > >> https://bugs.launchpad.net/bugs/1440174 > >> > >> Title: > >> Keyboard and Mouse don't work with latest Kernel > >> > >> Status in linux package in Ubuntu: > >> Incomplete > >> > >> Bug description: > >> 1) > >> Description:Ubuntu 14.04.2 LTS > >> Release:14.04 > >> > >> 2) Linux / The kernel > >> > >> 3) I expected my usb devices to work on the login page > >> > >> 4) They don't work :) > >> > >> ... > >> > >> Upon the upgrade to kernel 3.13.0-48-generic my USB devices don't > >> work, so when I did a normal launch of my computer, I could not sign > >> into it since my usb devices were not working. > >> > >> I was able to sign and and use my computer as normal when I revert to > >> kernel 3.13.0-46-generic. > >> > >> ProblemType: Bug > >> DistroRelease: Ubuntu 14.04 > >> Package: linux-image-3.13.0-46-generic 3.13.0-46.79 > >> ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 > >> Uname: Linux 3.13.0-46-generic x86_64 > >> ApportVersion: 2.14.1-0ubuntu3.8 > >> Architecture: amd64 > >> CurrentDesktop: Unity > >> Date: Fri Apr 3 13:06:36 2015 > >> HibernationDevice: RESUME=UUID=ae54d2d5-4931-4fcc-8996-aa3adf03cbb6 > >> InstallationDate: Installed on 2015-01-01 (92 days ago) > >> InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 > >> (20140722.2) > >> MachineType: Dell Inc. Inspiron 3847 > >> ProcFB: 0 inteldrmfb > >> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic > >> root=UUID=32967a77-1e86-4f47-abfd-a3b98a6e9af6 ro quiet splash > >> vt.handoff=7 > >> RelatedPackageVersions: > >> linux-restricted-modules-3.13.0-46-generic N/A > >> linux-backports-modules-3.13.0-46-generic N/A > >> linux-firmware 1.127.11 > >> RfKill: > >> 0: phy0: Wireless LAN > >> Soft blocked: no > >> Hard blocked: no > >> SourcePackage: linux > >> UpgradeStatus: No upgrade log present (probably fresh install) > >> dmi.bios.date: 04/03/2014 > >> dmi.bios.vendor: Dell Inc. > >> dmi.bios.version: A04 > >> dmi.board.name: 088DT1 > >> dmi.board.vendor: Dell Inc. > >> dmi.board.version: A01 > >> dmi.chassis.type: 3 > >> dmi.chassis.vendor: Dell Inc. > >> dmi.modalias: > >> > >> dmi:bvnDellInc.:bvrA04:bd04/03/2014:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr: > >> dmi.product.name: Inspiron 3847 > >> dmi.sys.vendor: Dell Inc. > >> > >> To manage notifications about this bug go to: > >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440174/+subscriptions > > > > -- > > http://www.fastmail.com - mmm... Fastmail... > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1440174 > > > > Title: > > Keyboard and Mouse don't work with latest Kernel > > > > Status in linux package in Ubuntu: > > Incomplete > > > > Bug description: > > 1) > > Description:Ubuntu 14.04.2 LTS > > Release:14.04 > > > > 2) Linux / The kernel > > > > 3) I expected my usb devices to work on the login page > > > > 4) They don't work :) > > > > ... > > > > Upon the upgrade to kernel 3.13.0-48-generic my USB devices don't > > work
[Kernel-packages] [Bug 1458901] Re: linux: 3.2.0-85.122 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing 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/1458901 Title: linux: 3.2.0-85.122 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow package-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug is for tracking the 3.2.0-85.122 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 26. May 2015 14:37 UTC kernel-stable-Prepare-package-end:Tuesday, 26. May 2015 20:06 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 26. May 2015 20:06 UTC kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 21:29 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Friday, 29. May 2015 23:00 UTC kernel-stable-Verification-testing-start:Friday, 29. May 2015 23:00 UTC kernel-stable-Certification-testing-start:Friday, 29. May 2015 23:00 UTC kernel-stable-Security-signoff-start:Friday, 29. May 2015 23:00 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Friday, 29. May 2015 23:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1458901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1455121] Re: [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the firmware spec
Tested this on an HP Proliant m400 and verified the issue was not seen. ** Tags removed: verification-needed-trusty ** Tags added: verification-verified-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/1455121 Title: [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the firmware spec Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Bug description: [Impact] On reboot, initialization commands can timeout causing the mellanox card to not initialize on boot. [Test Case] Reboot the system many, many times (this issue is rare). [Regression Risk] The fix comes from upstream and was submitted by Mellanox to bring the driver in-line with the way their firmware works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1411193] Re: [Asus F200MA] bluetooth not working
** Tags removed: verification-needed-precise ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411193 Title: [Asus F200MA] bluetooth not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Bug description: In my opinion, this is a very similar bug to https://bugs.launchpad.net/bugs/1395465 in the sense that the bluetooth indicator works but no external devices are detected. I don't know which information I should provide here so I just insert uname -a and lsusb. lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3423 IMC Networks Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub uname -a Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Any help will be greatly appreciated. Alessandro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436745] Re: Audio can not output via system internal speaker on a HP machine
** Tags removed: verification-needed-precise ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436745 Title: Audio can not output via system internal speaker on a HP machine Status in HWE Next Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Bug description: Steps to Reproduce: 1.Into OS 2.Play an audio file from internal speaker, no sound can be heard 3.Plug an external Speaker to audio jack, and play audio from external speaker, we can hear sound (like headphone) This bug is used for tracking purposes. Please do not triage. === break-fix: - af95b41426e0b58279f8ff0ebe420df49a4e96b8 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1436745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1449372] Re: Scsi kernel messages are being printed on separate lines.
This appears to have been resolved in v4.0 with 9e5ed2a5b3 Additionally e6c11dbb8da mitigates some of this by removing some of the messages altogether. ** Description changed: It seems to me that kernel errors, specifically those from the scsi - driver, are being wrapped, which confounds automated log monitoring. + driver, are being wrapped, which can confound automated log monitoring. Example from dmesg -- the lines I marked with X are being printed on separate lines where they previously weren't. - [6461080.699629] sd 0:2:2:0: [sdc] Unhandled sense code - [6461080.699646] sd 0:2:2:0: [sdc] - [6461080.699650] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE X - [6461080.699653] sd 0:2:2:0: [sdc] - [6461080.699655] Sense Key : Medium Error [current] X - [6461080.699661] sd 0:2:2:0: [sdc] - [6461080.699663] Add. Sense: No additional sense information X - [6461080.699667] sd 0:2:2:0: [sdc] CDB: - [6461080.699669] Read(16): 88 00 00 00 00 00 0c 23 92 e0 00 00 00 08 00 00 X - [6461080.699684] end_request: I/O error, dev sdc, sector 203657952 + [6461080.699629] sd 0:2:2:0: [sdc] Unhandled sense code + [6461080.699646] sd 0:2:2:0: [sdc] + [6461080.699650] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE X + [6461080.699653] sd 0:2:2:0: [sdc] + [6461080.699655] Sense Key : Medium Error [current] X + [6461080.699661] sd 0:2:2:0: [sdc] + [6461080.699663] Add. Sense: No additional sense information X + [6461080.699667] sd 0:2:2:0: [sdc] CDB: + [6461080.699669] Read(16): 88 00 00 00 00 00 0c 23 92 e0 00 00 00 08 00 00 X + [6461080.699684] end_request: I/O error, dev sdc, sector 203657952 - - I'm fairly certain this affects 3.2 to pre-4.1, and was sane in lucid. I'm certain it affects quantal to utopic, and vivid is partially mitigated. + This appears to affect 3.2 to pre-4.0, and was sane in lucid. I'm + certain it affects quantal to utopic, and vivid is partially mitigated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1449372 Title: Scsi kernel messages are being printed on separate lines. Status in linux package in Ubuntu: Confirmed Bug description: It seems to me that kernel errors, specifically those from the scsi driver, are being wrapped, which can confound automated log monitoring. Example from dmesg -- the lines I marked with X are being printed on separate lines where they previously weren't. [6461080.699629] sd 0:2:2:0: [sdc] Unhandled sense code [6461080.699646] sd 0:2:2:0: [sdc] [6461080.699650] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE X [6461080.699653] sd 0:2:2:0: [sdc] [6461080.699655] Sense Key : Medium Error [current] X [6461080.699661] sd 0:2:2:0: [sdc] [6461080.699663] Add. Sense: No additional sense information X [6461080.699667] sd 0:2:2:0: [sdc] CDB: [6461080.699669] Read(16): 88 00 00 00 00 00 0c 23 92 e0 00 00 00 08 00 00 X [6461080.699684] end_request: I/O error, dev sdc, sector 203657952 This appears to affect 3.2 to pre-4.0, and was sane in lucid. I'm certain it affects quantal to utopic, and vivid is partially mitigated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1449372/+subscriptions -- Mailing list: https://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 1460736] Re: package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Hi: I followed the links that you provided, implemented the instructions found, and installed the three packages indicated. The installation proceeded without error. The kernel installed also did not boot. However, I do have a questions regarding the following three instructions: 1 If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. 2. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. 3. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". My first question regards the difference between the first and second instruction. Since the bug encountered has been a non-booting kernel to begin with the both appear the same to me. I would appreciate clarification. Second, I'm new to this process Where and how do I add tags? A bit more information would be helpful. Thanks. > Date: Tue, 2 Jun 2015 21:15:51 + > From: joseph.salisb...@canonical.com > To: t_godf...@hotmail.com > Subject: [Bug 1460736] Re: package linux-image-3.13.0-53-generic 3.13.0-53.89 > failed to install/upgrade: subprocess installed post-installation script > returned error exit status 2 > > Would it be possible for you to test the latest upstream stable kernel? > Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the > latest v3.13 stable kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > If you are unable to test the mainline kernel, for example it will not boot, > please add the tag: 'kernel-unable-to-test-upstream'. > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11-ckt21-trusty/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1460736 > > Title: > package linux-image-3.13.0-53-generic 3.13.0-53.89 failed to > install/upgrade: subprocess installed post-installation script > returned error exit status 2 > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > The problem that I've encountered is that an incomplete Kernel update > crashed my system. I'm currently running in recovery mode. While my > user password works for updates, it does not work in terminal at > present. My installed system is Ubantu 14.04.1 LTS with all updates > added as of 06/01/2015. I've installed and am currently using the KDE > desktop. > > cat /proc/version_signature > version.log Yielded: > > Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 > > > sudo lspci -vnvn > lspci-vnvn.log Yielded: > > > 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM > Controller [8086:0154] (rev 09) > Subsystem: Toshiba America Info Systems Device [1179:ff1e] > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-Latency: 0 > Capabilities: > > 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core > processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA > controller]) > Subsystem: Toshiba America Info Systems Device [1179:fa20] > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-Latency: 0 > Interrupt: pin A routed to IRQ 42 > Region 0: Memory at c800 (64-bit, non-prefetchable) [size=4M] > Region 2: Memory at c000 (64-bit, prefetchable) [size=128M] > Region 4: I/O ports at 3000 [size=64] > Expansion ROM at [disabled] > Capabilities: > Kernel driver in use: i915 > > 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series > Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 > [XHCI]) > Subsystem: Toshiba America Info Systems Device [1179:ff1e] > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > SERR-Latency: 0 > Interrupt: pin A routed to IRQ 40 > Region 0: Memory at c860 (64-bit, non-prefetchable) [size=64K] > Capabilities: > Kernel driver in use: xhci_hcd > > 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 > Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) > Subsystem: Toshiba America Info Systems Device [1179:ff1e] > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
[Kernel-packages] [Bug 1439780] Re: [Hyper-V] Fiber Channel critical target error
I built a Vivid test kernel with a cherry pick of commit dc45708c. Can you test this kernel and confirm it solves the bug? If it does, we can SRU it to Vivid and Wily and request it be included in the upstream stable kernels. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1439780/ Note, for this test kernel you need to install both the linux-image and linux-image-extra .deb packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1439780 Title: [Hyper-V] Fiber Channel critical target error Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: System details: Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu12) ) #11~lp1423343v201503311833 SMP Tue Mar 31 17:40:01 UTC 2015 (Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3) Ubuntu 3.19.0-11 Ubuntu Vivid 15.04 64bit custom kernel Platform: WS2012R2 Using a fiber channel disk partition ( dev/sde1 in this example) outputs the following error: [ 1307.744496] blk_update_request: critical target error, dev sde, sector 0 [ 1396.052488] blk_update_request: critical target error, dev sde, sector 0 [ 1456.216570] blk_update_request: critical target error, dev sde, sector 0 Creating a partition works, reading too, but first time writing it hangs for around 20 seconds and after a couple more writes the partition goes into read-only mode: #echo "test1" > test1.txt *hangs for 30 seconds* blk_update_request: critical target error, dev sde, sector 0 # echo "test2" > test2.txt blk_update_request: critical target error, dev sde, sector 289671192 Aborting journal on device sde1-8. EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted journal EXT4-fs (sde1): Remounting filesystem read-only # echo "test string" > sample.txt -bash: sample.txt: Read-only file system Dmesg log: [ 461.284362] blk_update_request: critical target error, dev sde, sector 0 [ 484.845659] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null) [ 548.988377] blk_update_request: critical target error, dev sde, sector 0 [ 609.216340] blk_update_request: critical target error, dev sde, sector 289671192 [ 609.221812] Aborting journal on device sde1-8. [ 612.237503] EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted journal [ 612.249529] EXT4-fs (sde1): Remounting filesystem read-only Additional info: cat /proc/version_signature Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1425445] Re: Regression: 3.16.0-31-generic breaks touchpad on Dell XPS13 (2015)
This should also be fixed in Utopic as of 3.16.0-34: git describe --contains 33f561e Ubuntu-3.16.0-34.45~27 ** Changed in: linux (Ubuntu Utopic) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) 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/1425445 Title: Regression: 3.16.0-31-generic breaks touchpad on Dell XPS13 (2015) Status in linux package in Ubuntu: Fix Released Status in linux source package in Utopic: Fix Released Bug description: Today’s kernel update breaks the touchpad on the 2015 Dell XPS13. On 3.16.0-30-generic the touchpad worked fine. Symptoms are that the touchpad stops responding at random times. A possible cause is this patch: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d1c7e29e8d276c669e8790bb8be9f505ddc4 See also those two bug reports for a more detailed discussion of the I2C issues caused by the above patch and the XPS13: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416601 https://bugzilla.redhat.com/show_bug.cgi?id=1188439 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-31-generic 3.16.0-31.41 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jan2547 F pulseaudio /dev/snd/controlC1: jan2547 F pulseaudio CurrentDesktop: GNOME Date: Wed Feb 25 10:19:01 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-30 (25 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed root=UUID=e4431ecc-e85e-4e35-92af-58f455c46c2b ro kvm-intel.nested=1 "acpi_osi=!Windows 2013" psmouse.resetafter=0 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-31-generic N/A linux-backports-modules-3.16.0-31-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 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/1425445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1439780] Re: [Hyper-V] Fiber Channel critical target error
** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => High ** Changed in: linux (Ubuntu Vivid) Status: New => In Progress ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Wily) Importance: High Assignee: Joseph Salisbury (jsalisbury) Status: 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/1439780 Title: [Hyper-V] Fiber Channel critical target error Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Bug description: System details: Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu12) ) #11~lp1423343v201503311833 SMP Tue Mar 31 17:40:01 UTC 2015 (Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3) Ubuntu 3.19.0-11 Ubuntu Vivid 15.04 64bit custom kernel Platform: WS2012R2 Using a fiber channel disk partition ( dev/sde1 in this example) outputs the following error: [ 1307.744496] blk_update_request: critical target error, dev sde, sector 0 [ 1396.052488] blk_update_request: critical target error, dev sde, sector 0 [ 1456.216570] blk_update_request: critical target error, dev sde, sector 0 Creating a partition works, reading too, but first time writing it hangs for around 20 seconds and after a couple more writes the partition goes into read-only mode: #echo "test1" > test1.txt *hangs for 30 seconds* blk_update_request: critical target error, dev sde, sector 0 # echo "test2" > test2.txt blk_update_request: critical target error, dev sde, sector 289671192 Aborting journal on device sde1-8. EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted journal EXT4-fs (sde1): Remounting filesystem read-only # echo "test string" > sample.txt -bash: sample.txt: Read-only file system Dmesg log: [ 461.284362] blk_update_request: critical target error, dev sde, sector 0 [ 484.845659] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null) [ 548.988377] blk_update_request: critical target error, dev sde, sector 0 [ 609.216340] blk_update_request: critical target error, dev sde, sector 289671192 [ 609.221812] Aborting journal on device sde1-8. [ 612.237503] EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted journal [ 612.249529] EXT4-fs (sde1): Remounting filesystem read-only Additional info: cat /proc/version_signature Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371634] Re: block devices appear twice
** Branch linked: lp:~strikov/curtin/multipath-2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371634 Title: block devices appear twice Status in curtin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in multipath-tools package in Ubuntu: Confirmed Bug description: $ sudo blkid /dev/sr0: LABEL="Ubuntu-Server 14.04 LTS ppc64el" TYPE="iso9660" /dev/sda2: UUID="795a6e14-ea4e-4718-9e98-c6df3696920c" TYPE="ext4" /dev/sda3: UUID="0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4" TYPE="swap" /dev/sdb2: UUID="1d14c1f3-716f-4fb8-9070-d321b39ffcb3" TYPE="ext4" /dev/sdb3: UUID="9c228177-d65c-4d19-a462-db1891e9781e" TYPE="swap" /dev/sdg2: UUID="795a6e14-ea4e-4718-9e98-c6df3696920c" TYPE="ext4" /dev/sdg3: UUID="0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4" TYPE="swap" /dev/sdh2: UUID="1d14c1f3-716f-4fb8-9070-d321b39ffcb3" TYPE="ext4" /dev/sdh3: UUID="9c228177-d65c-4d19-a462-db1891e9781e" TYPE="swap" I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda -> sdg sdb -> sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. Related bugs: * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1371634] Re: block devices appear twice
I tried following the above workaround on the IBM Power 8 twice on new deployments. Attached is the log. ** Attachment added: "multipath.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4409977/+files/multipath.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/1371634 Title: block devices appear twice Status in curtin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in multipath-tools package in Ubuntu: Confirmed Bug description: $ sudo blkid /dev/sr0: LABEL="Ubuntu-Server 14.04 LTS ppc64el" TYPE="iso9660" /dev/sda2: UUID="795a6e14-ea4e-4718-9e98-c6df3696920c" TYPE="ext4" /dev/sda3: UUID="0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4" TYPE="swap" /dev/sdb2: UUID="1d14c1f3-716f-4fb8-9070-d321b39ffcb3" TYPE="ext4" /dev/sdb3: UUID="9c228177-d65c-4d19-a462-db1891e9781e" TYPE="swap" /dev/sdg2: UUID="795a6e14-ea4e-4718-9e98-c6df3696920c" TYPE="ext4" /dev/sdg3: UUID="0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4" TYPE="swap" /dev/sdh2: UUID="1d14c1f3-716f-4fb8-9070-d321b39ffcb3" TYPE="ext4" /dev/sdh3: UUID="9c228177-d65c-4d19-a462-db1891e9781e" TYPE="swap" I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda -> sdg sdb -> sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. Related bugs: * bug 1432062: multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic ppc64le AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process ended, respawning Date: Fri Sep 19 14:31:20 2014 HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1371634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1437913] Re: 8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel 7265
@sforshee - thank you very much for your explanation, I think I'm starting to understand the issue better. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1437913 Title: 8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel 7265 Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Invalid Status in wireless-regdb package in Ubuntu: Confirmed Status in linux source package in Trusty: Invalid Status in wireless-regdb source package in Trusty: Confirmed Status in linux source package in Vivid: Invalid Status in wireless-regdb source package in Vivid: Confirmed Status in linux source package in Wily: Invalid Status in wireless-regdb source package in Wily: Confirmed Bug description: After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux-firmware 1.143): 03:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095b] (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5210] I'm seeing two primary problems: * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, followed by an immediate reconnect. * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 minutes. A manual reconnect will temporarily fix network activity. This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect. FAOD, the latest utopic kernel/firmware combination (linux-image 3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in vivid if I manually install them. I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and 4.0.0-04rc5.201503230035, which exhibit the same problems. WORKAROUND: iw reg set US ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-10-generic 3.19.0-10.10 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1862 F pulseaudio /dev/snd/controlC1: ryan 1862 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 11:42:13 2015 HibernationDevice: RESUME=UUID=c21a0227-27e2-4c4f-8bd9-30793932acbc InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-10-generic N/A linux-backports-modules-3.19.0-10-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1437913/+subscriptions -- Mailing list: https://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 1437913] Re: 8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel 7265
On Thu, Jun 04, 2015 at 03:45:32PM -, Jason Gerard DeRose wrote: > @sforshee - I'm trying to better understand the consequences of Ubuntu > currently having an "an old regulatory database version", as some > System76 customers are having WiFi problems when connecting to AC > routers with an Intel 7265 and `sudo iw reg set US` seems to fix their > issues. > > In particular, should a regulatory domain be set automatically once the > database is updated? Currently I'm seeing the world-regulatory domain > (ie, not set), which seems to be an intersection of all domains and > means some band that could be used aren't (in the US anyway). The answer is a bit complicated. iwlwifi will actually read out a set of custom regulatory rules from the firmware and supply those to the wireless core. This becomes the "default" set of rules rather than the generic world domain when no specific regulatory domain has been supplied. This could be a similarly conservative set of rules meant to be "safe" around the world, or it could reflect the rules of the country where the device was intended to be sold (I'm not sure off the top of my head which it is for this card, but my best recollection is that it's the former). To emphasize the point - even though the kernel has retrieved the world domain from crda, prints them in dmesg, and outputs them in response to 'iw reg get', these rules are *not* being used for an Intel wireless card unless the user has manually loaded those rules (e.g. 'iw reg set 00'). Instead the kernel is using the rules it was given by the device's firmware. When a specific regulatory domain is set a process in userspace (crda) will read the rules for that domain from the regulatory database and load them into the kernel, and those rules will be used instead of the ones the driver supplied. Sometimes the access point will broadcast information about the regulatory domain in its beacon frames, in which case the regulatory rules for the country will be loaded automatically when connecting to that AP. More often (in my experience at least) the AP does not provide this information. The update to the database will change nothing about this process. The same rules are going to be supplied by iwlwifi, and country-specific rules will still be loaded or not loaded automatically based on what the AP is broadcasting exactly as before. All it will change is the rules which get loaded into the kernel for a given regulatory domain. You aren't specific about what kind of problems your customers are experiencing. One possibility is that the AP is using a channel that the default rules says is not allowed but the US rules do allow, and that loading the US rules opens up use on that channel. If this is the problem then it will not be fixed by updating the database. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1437913 Title: 8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel 7265 Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Invalid Status in wireless-regdb package in Ubuntu: Confirmed Status in linux source package in Trusty: Invalid Status in wireless-regdb source package in Trusty: Confirmed Status in linux source package in Vivid: Invalid Status in wireless-regdb source package in Vivid: Confirmed Status in linux source package in Wily: Invalid Status in wireless-regdb source package in Wily: Confirmed Bug description: After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux-firmware 1.143): 03:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095b] (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5210] I'm seeing two primary problems: * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, followed by an immediate reconnect. * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 minutes. A manual reconnect will temporarily fix network activity. This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect. FAOD, the latest utopic kernel/firmware combination (linux-image 3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in vivid if I manually install them. I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and 4.0.0-04rc5.201503230035, which exhibit the same problems. WORKAROUND: iw reg set US ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-10-generic 3.19.0-10.10 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10
[Kernel-packages] [Bug 1460507] Re: Hibernate fails if resume is done after X hours (X ~ 3+ hours)
With 4.1RC6, I have tried to replicate it twice and it worked fine every time after an hibernate of 12+ hours. Would it be worth getting debugs with the earlier kernel to triage the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460507 Title: Hibernate fails if resume is done after X hours (X ~ 3+ hours) Status in linux package in Ubuntu: Confirmed Bug description: I have a strange issue but I'm not the only one (http://ubuntuforums.org/showthread.php?t=2280045). My hardware is Lenovo t450s with intel Hd 5500. Suspend works fine (Although I haven't tested a long sleep yet). Intel rapidstart is disabled in BIOS. Hibernate saves to disk and resumes fine if I do the wakeup within a few hours. Any long-term hibernates (12 hours) don't resume. The splash screen shows up and then a blank screen and unresponsive keyboard. I don't have a capslock key, so don't know if that is flashing. I have been on multiple kernels 3.16,3.18,3.19 and 4.0 now. All of them have shown this problem. If there are any specific debugs that I could gather to help narrow down the issue, I would appreciate the guidance. Thanks! --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-15 (46 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Package: linux (not installed) Tags: vivid Uname: Linux 4.0.0-04-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to vivid on 2015-04-29 (33 days ago) UserGroups: adm cdrom dip lpadmin netdev plugdev roccat sambashare sudo tomcat6 _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1459937] Re: Support bluetooth device 0cf3:e007
** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1459937 Title: Support bluetooth device 0cf3:e007 Status in HWE Next Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: Fix Committed Bug description: The firmware of this device is loaded by a new mechanism other than ath3k. At least these commits are required: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ace31982585a323afb194f56b9e0486f7bc6570c https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3267c884cefa86c6d48c4d7c5571c20435271ecf https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf906b3db3c2b4f5d4db1db5f35796629c531ac4 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2054111b107d9449393d96dce6b66731bbfea9ad To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1459937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1461730] Re: XFS quota doesn't work after rebooting because of crash
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1461730
Title:
XFS quota doesn't work after rebooting because of crash
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Fix Committed
Bug description:
[Impact]
XFS quota doesn't work after rebooting because of crash or force reboot.
You can see msg on dmesg.
[ 12.309146] XFS (sdb): Failed to initialize disk quotas.
[Fix]
Upstream development
5ef828c41527 ("xfs: avoid false quotacheck after unclean shutdown")
It's affected under 3.17 kernel.
* fixed directory mismatch
There was no libxfs directory on fs/xfs/, I modified upstream
fs/xfs/libxfs/xfs_sb.c to proper position /fs/xfs/xfs_sb.c on ubuntu.
[Testcase]
mkfs.xfs for your extra storage, set the quota 2G with it. Using the
command "dd if=/dev/zero of=test bs=1M count=3000", You can see that they
have quota 2G at first. But after force rebooting, you can see that they
don't limit quota. You can make 3G on 2G quota set directory.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461730/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1450584] Re: mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm
** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1450584 Title: mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: [Impact] The addition of the commit: http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2 Causes SIGSEGVs when running certain workloads on multi-cpu VMs. [Test Case] Mono test case here that causes the SIGSEGV https://bugzilla.xamarin.com/show_bug.cgi?id=29212 [Fix] These two commits are required for fixing this issue: https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27 -- Gradually since late March more and more users started to complain about frequent SIGSEGV crashes in our .net/mono application. Early April I started to investigate it actively. After eliminating possible native libraries, and testing various mono versions I discovered the crashes would occur more frequently on a vbox vm with multiple cpus configured. And discovered that the mono bug-18026.cs testcase would fairly consistently crash. At that point it was reported to the mono bug tracker. I finally got a break when we found a correlation with the kernel version. 3.13.0-46 didn't crash while 3.13.0-48,49 did. More and more users upgrade to these newer kernel versions and start running into issues, which explains the gradual increase in reports. Early this week I performed a full git bisect on the kernel between 3.13.0-46 and -48 and isolated the commit that seems to trigger the crashes. Namely http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2 At this point I don't know if the commit messed up something, or that mono simply handles it incorrectly. However, a few commits for linux 4.x seem to fix it: https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27 I applied these commits myself on top of commit 11f4e033, compiled and ran the testcase... didn't crash in the 200x test runs I did. Although I don't know if those two patches have unknown side-effects. I'm not an expert on the kernel, not even remotely. But I thought it would be nice to be able to point at a possible solution. My current test vm is a virtualbox vm 64bit installed using the 14.04.2 server iso running on an older i7 quad core Windows 7 64bit host. In the vm I've tested numerous mono and kernel combinations. Last test was with kernel 3.16.0-36 and 3.13.0-51 and mono 4.0.1, in which the problem still occurs. By now I've debugged the app using gdb several dozen times on various user setups, compiled mono half a dozen times, and then the 8x3h compile kernel bisect :) Speaking of down the rabbit-hole... So I'm pretty desperate for some expert to help me out here. :D Reference to mono bug report: https://bugzilla.xamarin.com/show_bug.cgi?id=29212 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-51-generic 3.13.0-51.84 ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 Uname: Linux 3.13.0-51-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 30 18:53 seq crw-rw 1 root audio 116, 33 Apr 30 18:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.10 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: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [9.379188] init: plymouth-upstart-bridge main process ended, respawning Date: Thu Apr 30 19:45:43 2015 HibernationDevice: RESUME=UUID=b35ef328-166d-4476-a418-e7e80d22cb30 InstallationDate: Installed on 2015-04-22 (7 days ago) InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=
[Kernel-packages] [Bug 1458617] Re: Avoton server occasionally fails to boot when using SSD disks connected using ahci driver
** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Utopic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458617 Title: Avoton server occasionally fails to boot when using SSD disks connected using ahci driver Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: SRU Justification: Impact: Intermittent OS failure due to SSD disk initialisation failure Fix: Upstream development Testcase: About once per 5000 reboots on one server. If the user has several hundred servers, the frequency isn't negligible. - It was brought to my attention the following BUG: Avoton server occasionally fails to boot when using SSD disks connected using ahci driver. When this problem occurs, the disk is not recognized by the Linux kernel, and the server fails to boot. * Upstream acceptance information: Intel's patch has already been accepted upstream commit dbfe8ef5599a5370abc441fcdbb382b656563eb4 Author: Dan Williams Date: Fri May 8 15:23:55 2015 -0400 ahci: avoton port-disable reset-quirk Refer to http://permalink.gmane.org/gmane.linux.kernel.commits.head/524068 * How reproducible: About once per 5000 reboots on one server. However, if the customer has several hundred servers, the frequency isn't negligible. * Steps to Reproduce: Reboot server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1461553] Re: [Ubuntu 14.04.3] kernel patches for RAS tools
** Changed in: linux (Ubuntu Vivid) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1461553 Title: [Ubuntu 14.04.3] kernel patches for RAS tools Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: [Impact] Patches required to support RAS on 14.04.3 kernel [Test Case] Try using RAS tools on powernv platform. [Fix] commit 3f77df7f81526c932ef681eda56eeaa75d0617da Author: Vasant Hegde Date: Fri Feb 13 15:26:33 2015 +0530 powerpc/powernv: Check image loaded or not before calling flash Present code checks for update_flash_data in opal_flash_term_callback(). update_flash_data has been statically initialized to zero, and that is the value of FLASH_IMG_READY. Also code update initialization happens during subsys init. So if reboot is issued before the subsys init stage then we endup displaying "Flashing new firmware" message.. which may confuse end user. This patch fixes above described issue by initializes update_flash status to invalid state. Reported-by: Sam Bobroff Signed-off-by: Vasant Hegde Signed-off-by: Benjamin Herrenschmidt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1411295] Re: CONFIG_USB_OTG has gotten set again, kernel will not talk to OTG devices
** Changed in: linux (Ubuntu Utopic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1411295 Title: CONFIG_USB_OTG has gotten set again, kernel will not talk to OTG devices Status in linux package in Ubuntu: Fix Released Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Released Bug description: I have a few devices that have USB OTG ports. The kernel in Ubuntu 14.10 and later no longer recognizes these devices because CONFIG_USB_OTG forces the kernel to enter host nego protocol (which is not generally supported on the other end) and ends up rejecting the device. The devices work with Ubuntu 14.04 LTS. This CONFIG_USB_OTG config option was disabled by the fix for #1047527 but has since been reenabled for whatever reason, rendering desktop Ubuntu useless as a development host for these devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1437913] Re: 8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel 7265
@sforshee - I'm trying to better understand the consequences of Ubuntu currently having an "an old regulatory database version", as some System76 customers are having WiFi problems when connecting to AC routers with an Intel 7265 and `sudo iw reg set US` seems to fix their issues. In particular, should a regulatory domain be set automatically once the database is updated? Currently I'm seeing the world-regulatory domain (ie, not set), which seems to be an intersection of all domains and means some band that could be used aren't (in the US anyway). FYI, for anyone experiencing this problem, you can permanently set the reg by editing /etc/default/crda like this, replacing US with your country code: # Set REGDOMAIN to a ISO/IEC 3166-1 alpha2 country code so that iw(8) may set # the initial regulatory domain setting for IEEE 802.11 devices which operate # on this system. # # Governments assert the right to regulate usage of radio spectrum within # their respective territories so make sure you select a ISO/IEC 3166-1 alpha2 # country code suitable for your location or you may infringe on local # legislature. See `/usr/share/zoneinfo/zone.tab' for a table of timezone # descriptions containing ISO/IEC 3166-1 alpha2 country codes. REGDOMAIN=US -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1437913 Title: 8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel 7265 Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Invalid Status in wireless-regdb package in Ubuntu: Confirmed Status in linux source package in Trusty: Invalid Status in wireless-regdb source package in Trusty: Confirmed Status in linux source package in Vivid: Invalid Status in wireless-regdb source package in Vivid: Confirmed Status in linux source package in Wily: Invalid Status in wireless-regdb source package in Wily: Confirmed Bug description: After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux-firmware 1.143): 03:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095b] (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5210] I'm seeing two primary problems: * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, followed by an immediate reconnect. * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 minutes. A manual reconnect will temporarily fix network activity. This is complicated by the fact that the newer firmware requires kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware instead of the old iwlwifi-7265*.ucode firmware, so it's not possible to mix/match older/newer kernel/firmware combinations, nor do a kernel bisect. FAOD, the latest utopic kernel/firmware combination (linux-image 3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in vivid if I manually install them. I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and 4.0.0-04rc5.201503230035, which exhibit the same problems. WORKAROUND: iw reg set US ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-10-generic 3.19.0-10.10 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1862 F pulseaudio /dev/snd/controlC1: ryan 1862 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 11:42:13 2015 HibernationDevice: RESUME=UUID=c21a0227-27e2-4c4f-8bd9-30793932acbc InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-10-generic N/A linux-backports-modules-3.19.0-10-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW
[Kernel-packages] [Bug 1458569] Re: System freezes randomly
Have been trying vmlinuz-4.1.0-040100rc5-generic for about a week, using the laptop for maybe 2h a day, mostly just running Facebook. I was starting to hope but it froze again today. I was hammering ctrl+alt+f2 in hope of a console just after that, and to my surprise it switched (but not immediately) to a black screen. Could have been a coincidence, it might have done that even if I hadn't pressed anything. But after that it was completely unresponsive. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.1.0 ** Tags removed: kernel-bug-exists-upstream-4.1.0 ** Tags added: kernel-bug-exists-upstream-4.1.0-040100rc5 ** 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/1458569 Title: System freezes randomly Status in linux package in Ubuntu: Confirmed Bug description: After 10 min or so, or an hour. Workaround seems to be locking the CPU freq to something. I'm guessing there might be a bug in the powernow-k8 driver that exhibits itself in systems with the XPRESS 200M CPU chipset. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diskdoc1202 F pulseaudio CurrentDesktop: XFCE Date: Mon May 25 16:40:11 2015 HibernationDevice: RESUME=UUID=689195fb-b850-4125-a463-767853093c6a InstallationDate: Installed on 2015-05-23 (2 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard HP Compaq nx6125 (PY416EA#AK8) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=f4a074bf-eb4a-4cda-8a5a-561f66420476 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DTT Ver. F.07 dmi.board.name: 308B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 45.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DTTVer.F.07:bd07/01/2005:svnHewlett-Packard:pnHPCompaqnx6125(PY416EA#AK8):pvrF.07:rvnHewlett-Packard:rn308B:rvrKBCVersion45.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx6125 (PY416EA#AK8) dmi.product.version: F.07 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1458569] Re: System freezes randomly
Will continue to test with the powersave governor. For some reason just setting the frequency and userspace governor doesn't seem to work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1458569 Title: System freezes randomly Status in linux package in Ubuntu: Confirmed Bug description: After 10 min or so, or an hour. Workaround seems to be locking the CPU freq to something. I'm guessing there might be a bug in the powernow-k8 driver that exhibits itself in systems with the XPRESS 200M CPU chipset. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diskdoc1202 F pulseaudio CurrentDesktop: XFCE Date: Mon May 25 16:40:11 2015 HibernationDevice: RESUME=UUID=689195fb-b850-4125-a463-767853093c6a InstallationDate: Installed on 2015-05-23 (2 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard HP Compaq nx6125 (PY416EA#AK8) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=f4a074bf-eb4a-4cda-8a5a-561f66420476 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2005 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68DTT Ver. F.07 dmi.board.name: 308B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 45.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68DTTVer.F.07:bd07/01/2005:svnHewlett-Packard:pnHPCompaqnx6125(PY416EA#AK8):pvrF.07:rvnHewlett-Packard:rn308B:rvrKBCVersion45.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx6125 (PY416EA#AK8) dmi.product.version: F.07 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
