The task "linux-goldfish (Ubuntu Vivid)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life. If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Changed in: linux-goldfish (Ubuntu Vivid) Status: New => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1589041 Title: CVE-2016-5244 Status in linux package in Ubuntu: Expired Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Expired Status in linux-goldfish package in Ubuntu: Expired Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Expired Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid 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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-snapdragon 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid 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: Expired Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Expired Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Won't Fix Status in linux-flo source package in Vivid: Won't Fix Status in linux-goldfish source package in Vivid: Won't Fix Status in linux-lts-quantal source package in Vivid: Won't Fix Status in linux-lts-raring source package in Vivid: Won't Fix Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Won't Fix Status in linux-lts-utopic source package in Vivid: Won't Fix Status in linux-lts-vivid source package in Vivid: Won't Fix Status in linux-lts-wily source package in Vivid: Won't Fix Status in linux-lts-xenial source package in Vivid: Won't Fix Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: Won't Fix Status in linux-raspi2 source package in Vivid: Won't Fix Status in linux-snapdragon source package in Vivid: Won't Fix Status in linux-ti-omap4 source package in Vivid: Won't Fix Status in linux source package in Wily: Won't Fix Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: Won't Fix Status in linux-goldfish source package in Wily: Won't Fix Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: Won't Fix Status in linux-manta source package in Wily: Won't Fix Status in linux-raspi2 source package in Wily: Won't Fix Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Released Status in linux-armadaxp source package in Xenial: Invalid Status in linux-flo source package in Xenial: Expired Status in linux-goldfish source package in Xenial: Expired Status in linux-lts-quantal source package in Xenial: Invalid Status in linux-lts-raring source package in Xenial: Invalid Status in linux-lts-saucy source package in Xenial: Invalid Status in linux-lts-trusty source package in Xenial: Invalid Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Expired Status in linux-manta source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: Fix Released Status in linux-snapdragon source package in Xenial: Fix Released Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Won't Fix Status in linux-armadaxp source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Won't Fix Status in linux-goldfish source package in Yakkety: Won't Fix Status in linux-lts-quantal source package in Yakkety: Invalid Status in linux-lts-raring source package in Yakkety: Invalid Status in linux-lts-saucy source package in Yakkety: Invalid Status in linux-lts-trusty source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Won't Fix Status in linux-manta source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: Fix Released Status in linux-snapdragon source package in Yakkety: Fix Released Status in linux-ti-omap4 source package in Yakkety: Invalid Bug description: [rds: fix an infoleak in rds_inc_info_copy] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589041/+subscriptions
воскресенье
[Bug 1589041] Re: CVE-2016-5244
The task "linux-lts-vivid (Ubuntu Vivid)" has been closed automatically because it was filed against an Ubuntu release that is now end-of-life. If this issue is still present in a supported Ubuntu kernel, please open a new bug and provide updated details. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Changed in: linux-lts-vivid (Ubuntu Vivid) Status: New => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1589041 Title: CVE-2016-5244 Status in linux package in Ubuntu: Expired Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Expired Status in linux-goldfish package in Ubuntu: Expired Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Expired Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid 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-lts-wily source package in Precise: Invalid Status in linux-lts-xenial 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-raspi2 source package in Precise: Invalid Status in linux-snapdragon 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-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid 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: Expired Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Expired Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Won't Fix Status in linux-flo source package in Vivid: Won't Fix Status in linux-goldfish source package in Vivid: Won't Fix Status in linux-lts-quantal source package in Vivid: Won't Fix Status in linux-lts-raring source package in Vivid: Won't Fix Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Won't Fix Status in linux-lts-utopic source package in Vivid: Won't Fix Status in linux-lts-vivid source package in Vivid: Won't Fix Status in linux-lts-wily source package in Vivid: Won't Fix Status in linux-lts-xenial source package in Vivid: Won't Fix Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: Won't Fix Status in linux-raspi2 source package in Vivid: Won't Fix Status in linux-snapdragon source package in Vivid: Won't Fix Status in linux-ti-omap4 source package in Vivid: Won't Fix Status in linux source package in Wily: Won't Fix Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: Won't Fix Status in linux-goldfish source package in Wily: Won't Fix Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: Won't Fix Status in linux-manta source package in Wily: Won't Fix Status in linux-raspi2 source package in Wily: Won't Fix Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Fix Released Status in linux-armadaxp source package in Xenial: Invalid Status in linux-flo source package in Xenial: Expired Status in linux-goldfish source package in Xenial: Expired Status in linux-lts-quantal source package in Xenial: Invalid Status in linux-lts-raring source package in Xenial: Invalid Status in linux-lts-saucy source package in Xenial: Invalid Status in linux-lts-trusty source package in Xenial: Invalid Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Expired Status in linux-manta source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: Fix Released Status in linux-snapdragon source package in Xenial: Fix Released Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Won't Fix Status in linux-armadaxp source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Won't Fix Status in linux-goldfish source package in Yakkety: Won't Fix Status in linux-lts-quantal source package in Yakkety: Invalid Status in linux-lts-raring source package in Yakkety: Invalid Status in linux-lts-saucy source package in Yakkety: Invalid Status in linux-lts-trusty source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Won't Fix Status in linux-manta source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: Fix Released Status in linux-snapdragon source package in Yakkety: Fix Released Status in linux-ti-omap4 source package in Yakkety: Invalid Bug description: [rds: fix an infoleak in rds_inc_info_copy] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589041/+subscriptions
[Bug 1558646] Re: Apple Magic Keyboard A1644 fn key does not work
The task "linux (Ubuntu)" has been closed automatically because requested additional information has not been added. If this issue is still present in a supported Ubuntu kernel, please reopen the task and provide the requested information, and any other updated details. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1558646 Title: Apple Magic Keyboard A1644 fn key does not work Status in linux package in Ubuntu: Invalid Bug description: I recently purchased an Apple Magic Keyboard model #A1644 (the newest model). Sadly, the fn key seems to be completely nonfunctional. In other words, I cannot hold down fn+left arrow and get the equivalent of the Home key, etc. It just ignores the fn key and behaves like a left arrow key. I am on Ubuntu 14.04. version_signature output is: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Output from running hidd is: 04:69:F8:D5:46:48 Magic Keyboard [004c:0267] connected FYI, my function keys (F1-F12) work perfectly fine and are not mapping to media keys by default, but I had tried all the suggestions on the Ubuntu wiki anyway (https://help.ubuntu.com/community/AppleKeyboard, "Change Function Key behavior"). Still no go. I suspect this is a kernel issue, since there was a bug report several years ago for back then's latest Apple wireless keyboard that had the same issue, and the kernel just needed a patch for the new device ID. But who knows? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1558646/+subscriptions
[Bug 1443976] Re: splash+KMS+radeon causes screen to freeze
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1443976 Title: splash+KMS+radeon causes screen to freeze Status in linux package in Ubuntu: Expired Bug description: I have Radeon HD 7970 video card and I'm using open source radeon driver. If I try to boot with kernel parameters "quiet splash", system boots normally at first, splash screen is shown, but when it's time to start X server, screen instead shows garbage (http://s014.radikal.ru/i327/1504/3a/281b75b0ef2d.jpg), turns off and on several times, then shows quickly changing pattern (http://s020.radikal.ru/i704/1504/88/b9d2169bca29.jpg). The system don't respond to Ctrl-Alt-F?, but I still can connect using ssh. "reboot" doesn't work. kern.log has following error messages: Apr 14 15:01:52 gurren kernel: [ 35.081980] [drm:si_dpm_set_power_state] *ERROR* si_restrict_performance_levels_before_switch failed Apr 14 15:01:59 gurren kernel: [ 42.601562] radeon 0000:01:00.0: Saved 193 dwords of commands on ring 0. Apr 14 15:01:59 gurren kernel: [ 42.601606] radeon 0000:01:00.0: GPU softreset: 0x0000016C Apr 14 15:01:59 gurren kernel: [ 42.601608] radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028 Apr 14 15:01:59 gurren kernel: [ 42.601609] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 Apr 14 15:01:59 gurren kernel: [ 42.601610] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 Apr 14 15:01:59 gurren kernel: [ 42.601611] radeon 0000:01:00.0: SRBM_STATUS = 0x200206C0 Apr 14 15:01:59 gurren kernel: [ 42.601645] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Apr 14 15:01:59 gurren kernel: [ 42.601646] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Apr 14 15:01:59 gurren kernel: [ 42.601647] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Apr 14 15:01:59 gurren kernel: [ 42.601648] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000802 Apr 14 15:01:59 gurren kernel: [ 42.601649] radeon 0000:01:00.0: R_008680_CP_STAT = 0x800000E3 Apr 14 15:01:59 gurren kernel: [ 42.601650] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83506 Apr 14 15:01:59 gurren kernel: [ 42.601651] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44E83566 Apr 14 15:01:59 gurren kernel: [ 42.601652] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 Apr 14 15:01:59 gurren kernel: [ 42.601653] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 Apr 14 15:02:00 gurren kernel: [ 43.280219] radeon 0000:01:00.0: Wait for MC idle timedout ! Apr 14 15:02:00 gurren kernel: [ 43.280222] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF Apr 14 15:02:00 gurren kernel: [ 43.280273] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100540 Apr 14 15:02:00 gurren kernel: [ 43.281420] radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 Apr 14 15:02:00 gurren kernel: [ 43.281421] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 Apr 14 15:02:00 gurren kernel: [ 43.281422] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 Apr 14 15:02:00 gurren kernel: [ 43.281423] radeon 0000:01:00.0: SRBM_STATUS = 0x200006C0 Apr 14 15:02:00 gurren kernel: [ 43.281457] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 Apr 14 15:02:00 gurren kernel: [ 43.281458] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 Apr 14 15:02:00 gurren kernel: [ 43.281459] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 Apr 14 15:02:00 gurren kernel: [ 43.281460] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 Apr 14 15:02:00 gurren kernel: [ 43.281461] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 Apr 14 15:02:00 gurren kernel: [ 43.281462] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 Apr 14 15:02:00 gurren kernel: [ 43.281463] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 Apr 14 15:02:00 gurren kernel: [ 43.281543] radeon 0000:01:00.0: GPU reset succeeded, trying to resume Apr 14 15:02:05 gurren kernel: [ 48.292813] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting Apr 14 15:02:05 gurren kernel: [ 48.292816] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C973 (len 254, WS 0, PS 4) @ 0xC99D Apr 14 15:02:05 gurren kernel: [ 48.292817] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C009 (len 106, WS 0, PS 8) @ 0xC05E Apr 14 15:02:05 gurren kernel: [ 48.296773] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e Apr 14 15:02:05 gurren kernel: [ 48.296775] [drm] PCIE gen 3 link speeds already enabled Apr 14 15:02:05 gurren kernel: [ 48.558122] radeon 0000:01:00.0: Wait for MC idle timedout ! Apr 14 15:02:05 gurren kernel: [ 48.688713] radeon 0000:01:00.0: Wait for MC idle timedout ! Apr 14 15:02:05 gurren kernel: [ 48.690354] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). Apr 14 15:02:05 gurren kernel: [ 48.690440] radeon 0000:01:00.0: WB enabled Apr 14 15:02:05 gurren kernel: [ 48.690442] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000c0000c00 and cpu addr 0xffff88020f636c00 Apr 14 15:02:05 gurren kernel: [ 48.690443] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x00000000c0000c04 and cpu addr 0xffff88020f636c04 Apr 14 15:02:05 gurren kernel: [ 48.690444] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x00000000c0000c08 and cpu addr 0xffff88020f636c08 Apr 14 15:02:05 gurren kernel: [ 48.690445] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x00000000c0000c0c and cpu addr 0xffff88020f636c0c Apr 14 15:02:05 gurren kernel: [ 48.690446] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x00000000c0000c10 and cpu addr 0xffff88020f636c10 Apr 14 15:02:05 gurren kernel: [ 48.690813] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90005ab5a18 Apr 14 15:02:05 gurren kernel: [ 48.968423] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) Apr 14 15:02:05 gurren kernel: [ 48.968425] [drm:si_resume] *ERROR* si startup failed on resume If I ether add "nomodeset" or remove "splash" from kernel command line system boots normally. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-34-generic 3.16.0-34.47 ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ranma 5617 F.... pulseaudio /dev/snd/controlC1: ranma 5617 F.... pulseaudio CurrentDesktop: KDE Date: Tue Apr 14 16:43:04 2015 IwConfig: eth0 no wireless extensions. lo no wireless extensions. MachineType: ASUS All Series ProcFB: 0 radeondrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-34-generic root=UUID=cb5dacd2-d63f-4cf5-a9fa-0ec0f85ec4b4 ro rootflags=subvol=@ drm.debug=0x06 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 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-29 (166 days ago) dmi.bios.date: 04/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0329 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0329:bd04/23/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-C:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443976/+subscriptions
[Bug 1592369] Re: On function native_apic_mem_write issue.
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1592369 Title: On function native_apic_mem_write issue. Status in linux package in Ubuntu: Expired Bug description: Execute xchg %ax,%ax after finishing the running funtion. Here is content of perf report: native_apic_mem_write /proc/kcore │ ▒ │ ▒ │ ▒ │ Disassembly of section load0: ▒ │ ▒ │ ffffffff8105a2a0 <load0>: ▒ │ push %rbp ▒ │ mov %edi,%edi ▒ │ mov %rsp,%rbp ◆ │ mov %esi,-0xa07000(%rdi) ▒ 100,00 │ pop %rbp ▒ │ ← retq ▒ │ xchg %ax,%ax ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-24-generic 4.4.0-24.43 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: asu 3226 F.... pulseaudio CurrentDesktop: MATE Date: Tue Jun 14 14:16:23 2016 InstallationDate: Installed on 2016-04-29 (45 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lo no wireless extensions. enp1s0 no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic root=/dev/mapper/192--168--0--108--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-24-generic N/A linux-backports-modules-4.4.0-24-generic N/A linux-firmware 1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592369/+subscriptions
[Bug 1261063] Re: [Dell Inspiron 660] Occasional "The disk drive for /dev/mapper/cryptswap1 is not ready yet or not present" on system startup
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1261063 Title: [Dell Inspiron 660] Occasional "The disk drive for /dev/mapper/cryptswap1 is not ready yet or not present" on system startup Status in linux package in Ubuntu: Expired Bug description: Occasional "The disk drive for /dev/mapper/cryptswap1 is not ready yet or not present" on system startup. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-7-generic 3.12.0-7.15 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 ApportVersion: 2.12.7-0ubuntu2 Architecture: i386 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2833 F.... pulseaudio CasperVersion: 1.336ubuntu1 CurrentDesktop: Unity Date: Sun Dec 15 01:18:43 2013 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131214) MachineType: Dell Inc. Inspiron 660 ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware 1.117 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 084J0R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/13/2013:svnDellInc.:pnInspiron660:pvr:rvnDellInc.:rn084J0R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Inspiron 660 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261063/+subscriptions
[Bug 921000] Re: no logging if using non-existent child profile
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Triaged => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/921000 Title: no logging if using non-existent child profile Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Expired Bug description: Ubuntu recently added the ubuntu-helpers abstraction with the sanitized_helper child profile. If I do the following: /bin/foo { /usr/bin/bar Cxr -> sanitized_helper, } and then execute /bin/foo, the execution of /usr/bin/bar fails but with no logging. This is because in the above profile I forgot to add '#include <abstractions/ubuntu-helpers>', which is what defines the sanitized_helper profile. This can either be fixed in the logging mechanism or apparmor_parser should fail if the parent profile references a child profile that is not defined. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/921000/+subscriptions
[Bug 1038188] Re: [Lenovo-T430s]: Internal Mic does not work.
The task "linux (Ubuntu)" has been closed automatically because requested additional information has not been added. If this issue is still present in a supported Ubuntu kernel, please reopen the task and provide the requested information, and any other updated details. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1038188 Title: [Lenovo-T430s]: Internal Mic does not work. Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Won't Fix Bug description: [Lenovo-T430s]: Internal Mic does not work. 201202-10635 kernel: Linux 201202-10635 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Problem: Internal Mic is detected and input meter changes but not from outside noise. If you open sound recorder the recorded track is just static. Changing the input volume or pressing the mute microphone button does not do anything. I've adjusted all the mic volumes in alsamixer to max, and that did not fix the issue. 00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04) sound card info: Welcome to PulseAudio! Use "help" for usage information. >>> 1 card(s) available. index: 0 name: <alsa_card.pci-0000_00_1b.0> driver: <module-alsa-card.c> owner module: 4 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xb3530000 irq 46" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1b.0" sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.name = "Panther Point High Definition Audio Controller" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:analog-stereo: Analog Stereo Output (priority 6000) output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060) output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5400) output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5460) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 300) output:hdmi-surround+input:analog-stereo: Digital Surround 5.1 (HDMI) Output + Analog Stereo Input (priority 360) output:hdmi-stereo-extra1: Digital Stereo (HDMI) Output (priority 5200) output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5260) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI) Output (priority 100) output:hdmi-surround-extra1+input:analog-stereo: Digital Surround 5.1 (HDMI) Output + Analog Stereo Input (priority 160) output:hdmi-stereo-extra2: Digital Stereo (HDMI) Output (priority 5200) output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5260) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI) Output (priority 100) output:hdmi-surround-extra2+input:analog-stereo: Digital Surround 5.1 (HDMI) Output + Analog Stereo Input (priority 160) input:analog-stereo: Analog Stereo Input (priority 60) off: Off (priority 0) active profile: <output:analog-stereo+input:analog-stereo> sinks: alsa_output.pci-0000_00_1b.0.analog-stereo/#0: Built-in Audio Analog Stereo sources: alsa_output.pci-0000_00_1b.0.analog-stereo.monitor/#0: Monitor of Built-in Audio Analog Stereo alsa_input.pci-0000_00_1b.0.analog-stereo/#1: Built-in Audio Analog Stereo ports: analog-output-speaker: Speakers (priority 10000, available: unknown) properties: analog-output-headphones: Headphones (priority 9000, available: no) properties: analog-input-microphone-internal: Internal Microphone (priority 8900, available: unknown) properties: analog-input-microphone: Microphone (priority 8700, available: no) properties: hdmi-output-0: HDMI / DisplayPort (priority 5900, available: no) properties: hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, available: no) properties: hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, available: no) properties: ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 ArecordDevices: **** List of CAPTURE Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1660 F.... pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xb3530000 irq 46' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa21fb,00100203 HDA:80862806,80860101,00100000' Controls : 36 Simple ctrls : 13 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Fri Aug 17 13:25:39 2012 HibernationDevice: RESUME=UUID=f5c0be8d-26f4-4dec-83cc-25f05df105b8 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: LENOVO 814Q18G ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=15352ee3-bd29-46dc-ac61-afb3864aff9c ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware 1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET25WW (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 814Q18G 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:bvrG7ET25WW(1.07):bd04/27/2012:svnLENOVO:pn814Q18G:pvrThinkPadT430s:rvnLENOVO:rn814Q18G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 814Q18G dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 ArecordDevices: **** List of CAPTURE Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1660 F.... pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xb3530000 irq 46' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa21fb,00100203 HDA:80862806,80860101,00100000' Controls : 36 Simple ctrls : 13 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=f5c0be8d-26f4-4dec-83cc-25f05df105b8 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: LENOVO 814Q18G 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=/boot/vmlinuz-3.2.0-23-generic root=UUID=15352ee3-bd29-46dc-ac61-afb3864aff9c ro quiet splash initcall_debug vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware 1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: mei Tags: precise staging precise staging Uname: Linux 3.2.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/27/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET25WW (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 814Q18G 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:bvrG7ET25WW(1.07):bd04/27/2012:svnLENOVO:pn814Q18G:pvrThinkPadT430s:rvnLENOVO:rn814Q18G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 814Q18G dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1038188/+subscriptions
[Bug 1583750] Re: 8086:1502 e1000e: probe of 0000:00:19.0 failed with error -3
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Triaged => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1583750 Title: 8086:1502 e1000e: probe of 0000:00:19.0 failed with error -3 Status in linux package in Ubuntu: Expired Bug description: When I switch on my laptop, running Ubuntu 14.04 LTS amd64, it will boot and load e1000e, but no eth* interface is present. Even repeated rmmod and modprobe don't bring up the interface. After a restart (i.e. no fresh power-up) it works just fine. After the next power-cycle the problem is there again. Laptop is a Lenovo Thinkpad T520 (Optimus graphics). joerg@x61:~$ sudo dmesg | grep e1000e [ 1.622695] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 1.622697] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. [ 1.659146] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 1.659168] e1000e 0000:00:19.0: irq 42 for MSI/MSI-X [ 2.673058] e1000e: probe of 0000:00:19.0 failed with error -3 Same error happens with a vanilla kernel 4.6.0: cat /proc/version Linux version 4.6.0-jal2+ (root at x61) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.1) ) #4 SMP Mon May 16 01:06:19 CEST 2016 dmesg | grep e1000e [ 1.081798] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 1.081800] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.082068] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 2.106194] e1000e: probe of 0000:00:19.0 failed with error -3 Afterwards I've added some error output and changed some debugs into error prints in the e1000e: [ 7900.183212] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): Failed to acquire the semaphore, FW or HW has it: FWSM=0x60000040 EXTCNF_CTRL=0x002800c9) lspci -s 00:19 -vvv 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) Subsystem: Lenovo Device 21ce Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 20 Region 0: Memory at f3900000 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at f3929000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 6080 [size=32] Capabilities: [c8] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [e0] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- See also this very similar bug on other hardware https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576953 and my bug report to intel-wired-lan http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20160516/005381.html ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-86-generic 3.13.0-86.131 ProcVersionSignature: Ubuntu 3.13.0-86.131-generic 3.13.11-ckt39 Uname: Linux 3.13.0-86-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: joerg 2120 F.... pulseaudio CurrentDesktop: XFCE Date: Thu May 19 20:53:38 2016 HibernationDevice: RESUME=UUID=24909a47-1377-480a-93f0-66165f6c88a3 InstallationDate: Installed on 2015-03-21 (424 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: LENOVO 4242PT2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-86-generic root=UUID=7e46d0b3-a960-4a36-a56c-8a6ac934c07e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-86-generic N/A linux-backports-modules-3.13.0-86-generic N/A linux-firmware 1.127.22 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET62WW (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 4242PT2 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:bvr8AET62WW(1.42):bd01/24/2013:svnLENOVO:pn4242PT2:pvrThinkPadT520:rvnLENOVO:rn4242PT2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4242PT2 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1583750/+subscriptions
[Bug 1552551] Re: Dell CERC Adapter hangs temporarily until reset. REGRESSION
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Triaged => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1552551 Title: Dell CERC Adapter hangs temporarily until reset. REGRESSION Status in linux package in Ubuntu: Expired Bug description: The HD CERC SATA 1.5 RAID controller (PCI-64 slot) hangs regularly for 10-60 seconds until reset. The CERC card firmware is the newest I can find reference to: 4.1-0 [bld 7419]. The Dell Poweredge 1800 has newest BIOS (A07). All hardware has been tested thoroughly OK except possibly the APIC component (Serverset Northbridge?). The 14.04LTS with all updates (or not) works fine with a perfectly consistent throughput of 77MB/s (slowest HD=66MB/s), RAID5. 15.10 has the hangs of 10-60 seconds, AND with newest updates as of 26-FEB-2016. I have changed PCI interrupts around and moved card slots to minimize sharing and removed cards - repeatedly. All hard drives and cables have been thoroughly tested, but the drives are mixed: 1 of 66MB/s, 1 of 125 MB/s, and 3 of 100MB/s. The drives not only work perfectly in 14.04LTS, but all Windows versions and DOS/BIOS-INT 19 as well (0x13). I have tried all combinations of card RAID options Read ahead, Write cache, and other BIOS options. Relevant dmesg lines (these were consecutive): [ 1046.808027] aacraid: Host adapter abort request (4,0,0,0) [ 1046.808123] aacraid: Host adapter reset request. SCSI hang ? [ 1297.828038] aacraid: Host adapter abort request (4,0,0,0) [ 1297.828168] aacraid: Host adapter reset request. SCSI hang ? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.365 CurrentDesktop: Unity Date: Thu Mar 3 05:08:57 2016 LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 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: Dell Computer Corporation PowerEdge 1800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=u15.10-64/casper/vmlinuz.efi file=u15.10-64/preseed/username.seed boot=casper netboot=nfs nfsroot=10.100.1.86:/data2/tftpboot/u15.10-64 initrd=u15.10-64/casper/initrd.lz ipv6.disable=1 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware 1.149 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: 09/29/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0P8611 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A04 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd09/29/2006:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0P8611:rvrA04:cvnDellComputerCorporation:ct17:cvr: dmi.product.name: PowerEdge 1800 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551/+subscriptions
[Bug 1811162] Re: Turn on CONFIG_REFCOUNT_FULL for non-x86 arches
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Triaged => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1811162 Title: Turn on CONFIG_REFCOUNT_FULL for non-x86 arches Status in linux package in Ubuntu: Expired Bug description: The upstream kernel has added refcount protection, in two ways. For arches that have provided a fast refcount_t implementation, they get it automatically (this is signaled by ARCH_HAS_REFCOUNT, which as of 4.20 kernels, is only the x86 arch). For other arches, they can get refcount protection via the CONFIG_REFCOUNT_FULL configure option. The upstream arm64 and arm maintainers have enabled this configuration by default for those arches, which has been carried into the ubuntu kernel config. We should enable that for our other arches that do not provide ARCH_HAS_REFCOUNT, namely ppc64el and s390x, to gain protection parity with the rest of the architectures supported by ubuntu kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811162/+subscriptions
[Bug 1536837] Re: Severe performance regression in Infiniband or IPoIB
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Triaged => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1536837 Title: Severe performance regression in Infiniband or IPoIB Status in Linux: Unknown Status in linux package in Ubuntu: Expired Bug description: When upgrading to the latest 4.4 test kernel from mainline development, all IPoIB links showed a severe performance regression as compared with kernel 4.2. The bandwidth of each link dropped from around 3Gbps to around 3Mbps (3 orders of magnitude worse!); reverting to the 4.2 kernel immediately fixed this problem. The 4.3 kernel from Debian does not appear to suffer from this regression. The regression shows up on both IB ports of the Mellanox MT25208 controller. Other hardware has not been tested. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1536837/+subscriptions
[Bug 1372967] Re: Touchpad not working and not recognized
The task "linux (Ubuntu)" has expired because it has had no new comments or updates for more than three years. If this issue is still present in an Ubuntu LTS kernel still under active support, please reopen the bug and provide updated details. If this issue was reported against an Ubuntu kernel no longer under active support but the issue still exists in a currently supported Ubuntu kernel, please open a new bug against that kernel version and provide the updated details, with a reference link to the original bug. This action was performed by an automated process maintained by the Ubuntu Kernel Team. ** Tags added: kernel-autoclosed kernel-autoclosed-expired ** Changed in: linux (Ubuntu) Status: Confirmed => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1372967 Title: Touchpad not working and not recognized Status in linux package in Ubuntu: Expired Bug description: Even during installation the touchpad did not work, after installing ubuntu 14.04 i tried to use xinput list but this is the result: ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Fujitsu FUJ02E3 id=7 [slave keyboard (3)] ↳ Video Bus id=8 [slave keyboard (3)] ↳ Fujitsu FUJ02B1 id=9 [slave keyboard (3)] ↳ Power Button id=10 [slave keyboard (3)] ↳ FJ Camera id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3) The "SynPS/2 Synaptics TouchPad" is not present anywhere. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: dquaglio 1524 F.... pulseaudio /dev/snd/controlC0: dquaglio 1524 F.... pulseaudio CurrentDesktop: Unity Date: Tue Sep 23 16:19:31 2014 HibernationDevice: RESUME=UUID=40f80e5e-5fc1-40a8-b253-836e81028831 InstallationDate: Installed on 2014-09-23 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: FUJITSU LIFEBOOK A544 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=04575c6d-aff9-4da6-8b8b-f7cdfdb0a5a4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.6 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.13 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd11/18/2013:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372967/+subscriptions